Httpd: "Invalid argument: alloc_listener: failed to get a socket for (null)"

nirox · 09-16-2009, 01:48 PM

EDIT: Post is rewritten to give info about the problem using 13/current "httpd apr apr-util" and older kernel (in my situation: 2.6.24)

Symptoms:

Code:

# apachectl start
[Wed Sep 16 20:37:56 2009] [crit] (22)Invalid argument: alloc_listener: failed to get a socket for (null)
Syntax error on line 40 of /etc/httpd/httpd.conf:
Listen setup failed

Line 40 of /etc/httpd/httpd.conf:

Quote:

Listen 80

Problem can tempory be solved by downgrading your apr to ftp://ftp.slackware.com/pub/slackwar..._slack12.2.tgz
but its recomended that you upgrade your kernel.

tux_dude · 09-16-2009, 02:08 PM

No problem here on slackware64-current. Trying removing the ':' from your config.

nirox · 09-16-2009, 11:50 PM

Uh, that was a typo.
It is "Listen 80", but tried with ":80" and "*:80"

I got same error on two different machines using the same versions

disturbed1 · 09-17-2009, 12:32 AM

Quote:

Originally Posted by nirox

After installing "httpd apr apr-util" using 13/current im getting this:

Code:

# apachectl start
[Wed Sep 16 20:37:56 2009] [crit] (22)Invalid argument: alloc_listener: failed to get a socket for (null)
Syntax error on line 40 of /etc/httpd/httpd.conf:
Listen setup failed

What happens if you start apache with
sh /etc/rc.d/rc.httpd start

Are you actually root when using apachectl?

Both apachectl and rc.httpd work on my end with Slackware64-13.0 and and 32bit 13.0 with the same application versions you have.

What are you editing the config file with? Perhaps it placed some junk on the line. Try blowing out line 40 and retyping Listen 80. Not sure which editors do or do not leave junk behind, I do know nano works.

nirox · 09-17-2009, 01:15 AM

Quote:

sh /etc/rc.d/rc.httpd start

Is just a script that execute "apachectl -k start", so its give the same error.
And ofc doing it as root.

Im using "pico" for editing, but shouldnt be the problem as a fresh install without editing any config files gives the same error.
Just to confirm, i commented "Listen 80" and wrote it again on line 41 getting same error with the line referance 41.

EDIT 1: Found this info while googling:
http://rackerhacker.com/2009/08/14/f...cket-for-null/

Quote:

The issue is related to three kernel calls that are used in apr-1.3.8-1: accept4(), dup3() and epoll_create1(). Without these calls, apache is unable to start.

EDIT 2: And the above is solving the problem. Downloaded "slackware-12.2/slackware/l/apr-1.3.3-i486-1.tgz", installed it and the problem is gone, httpd is working
So the problem must be in "apr-1.3.8"?

EDIT 2: replacing apr-1.3.8 with apr-1.3.3-i486-1 solves the problem on both my servers...

EDIT 3: As im getting this problem on 3 different machines, there must be others having same problem?

EDIT 4:
slackware-12.2/patches/packages/apr-1.3.8-i486-1_slack12.2.tgz
Works OK

slackware-current/slackware/l/apr-1.3.8-i486-1.txz
Fails

El Nigromante · 09-17-2009, 01:40 PM

Hello,

Executing:

Code:

# sh /etc/rc.d/rc.httpd start 
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName

Works just right for me in Slackware 13.0 (32 bits). Here is the log:

Code:

[Thu Sep 17 20:30:57 2009] [notice] Digest: generating secret for digest authentication ...
[Thu Sep 17 20:30:57 2009] [notice] Digest: done
[Thu Sep 17 20:30:58 2009] [notice] Apache/2.2.13 (Unix) DAV/2 configured -- resuming normal operations
[Thu Sep 17 20:31:07 2009] [error] [client 127.0.0.1] File does not exist: /srv/httpd/htdocs/favicon.ico
[Thu Sep 17 20:31:10 2009] [error] [client 127.0.0.1] File does not exist: /srv/httpd/htdocs/favicon.ico

Note: I did a fresh new installation of Slackware 13.0 (32 bits)

rg3 · 09-17-2009, 01:58 PM

I'm thinking it could be related to kernel versions. Which kernel version are you running? Are you using the official kernel from Slackware 13.0/current? Can you verify that?

nirox · 09-17-2009, 04:18 PM

Tbh i feel abit shamed for not remember last time i upgraded my kernels.
But they where official huge-smp/smp kernels from -current at the time they arrived

Linux Alpha 2.6.24.4-smp #2 SMP
Linux Bravo 2.6.24.5-smp #2 SMP
Linux Charlie 2.6.23.16-smp #2 SMP

Will do a restart with up2date kernel when i got time to go onsite to be sure they get back-up after reboot.

nirox · 09-18-2009, 08:37 AM

Okey, did a kernel upgrade and it seems to be the reason for the problem.

Will cleanup start post so ppl with same problem easy can get hand on what it can be...

zulsolar · 04-10-2010, 08:26 PM

Quote:

Originally Posted by nirox

EDIT 2: And the above is solving the problem. Downloaded "slackware-12.2/slackware/l/apr-1.3.3-i486-1.tgz", installed it and the problem is gone, httpd is working
So the problem must be in "apr-1.3.8"?

EDIT 2: replacing apr-1.3.8 with apr-1.3.3-i486-1 solves the problem on both my servers...

EDIT 3: As im getting this problem on 3 different machines, there must be others having same problem?

Same issue here. Thanks nirox!! I replaced apr-1.3.8-i486-1.txz with apr-1.3.8-i486-1_slack12.2.tgz and issue resolved. It works now!!

Thanks again dude!!

daidoji · 07-22-2012, 03:13 PM

Ummm, I'm a little confused. Does anyone know why this works? Is it a kernel issue or a package issue? I seem to be getting the same thing with httpd-2.2.22, apr-1.4.5, and apr-util-1.4.1. If its a kernel issue should I just use a lower version of apache as my VPS provider is being a bit dense on getting a 3.0 kernel installed (current kernel 2.6.26). Any help would be greatly appreciated as it doesn't seem to be located in the apache docs as far as I can tell.