CSWS 'listen setup failed' message

[Adrian Graham_1]

Hi folks,

No doubt this is another message that I should know but have forgotten over time; my work has taken me away from my favourite OS but
I'm fighting back :)

I'm setting up a CSWS 2.1 webserver (Alpha DS10) and it's giving me the classic socket creation message:

failed to get a socket for 0.0.0.0
Syntax error on line 156 of /apache$root/000000/conf/httpd.conf:
Listen setup failed

Line 156 is 'listen 80' as you would expect, in the unix world that message means something else is using port 80 but a "$tcpip show dev" doesn't give anything using port 80, also it doesn't seem to matter which line I use for the Listen directive, I get the same error.

I'm using the latest patches for VMS 7.3-2 and TCPIP 5.4 ECO6, and no doubt I'll be embarassed by the solution because I should've thought of it before posting.

cheers,

[Steven Schweda]

I'm still at CSWS 1.3x, but as a guess, is it
a privilege (wrong user) problem?

If you can create the socket on a non-priv
port, say, 8080 instead of 80, that would be
a clue.

"Syntax error" is not what _I_ would have
said in this case, irregardful.

[Willem Grooters]

"listen" - as such? Try " Listen" it might help (SWS is basiaclly a Unix application and that behaviour hasn't chnaged in it;s port to VMS. (One of my reasons to abandon it))

[Steven Schweda]

> "listen" - as such? Try " Listen" [...]

http://httpd.apache.org/
http://httpd.apache.org/docs/2.0/
http://httpd.apache.org/docs/2.0/configuring.html
http://httpd.apache.org/docs/2.0/configuring.html#syntax

I quote:

Directives in the configuration files are
case-insensitive, but arguments to
directives are often case sensitive.

I'm guessing that "80" was in the right case.

If it didn't understand "listen", my guess is
that it probably wouldn't be complaining
about failing to get a socket.

[Adrian Graham_1]

Hi folks,

The 'listen' bit with a lower-L was my lazy typing, but I know that the directives aren't case-sensitive. I've tried using a non-priv port too, also in the normal state of affairs I'm using the SYSTEM account to start things running; after posting this I wondered if it was a DNS based problem, but BIND is working properly.

Also, I tried to start httpd after issuing a $set watch file/class=major and watched it reference both TCPIP$IPC_SHR and UCX$IPC_SHR which implies it's getting the same error from both of them......

cheers

[Adrian Graham_1]

Replying to myself here,

yesterday I completely removed CSWS and PHP then installed 2.1-1 and PHP 1.3-update......and it started fine.

Reinstalled my customized copy of httpd.conf and.....it started fine?!

Now I'm having difficulty forcing apache to listen on port 8080 (Listen 8080 or Listen 0.0.0.0:8080) and neither of those lines work. Weird.

[Steven Schweda]

> Weird.

Are you sure that you and the program are
looking at the same configuration file?

Any conflicting Port or VirtualHost stuff?

[Adrian Graham_1]

Bah, I've just discovered that I had an apache$common:[conf]httpd.conf that was overriding (as you would expect) my apache$specific:[conf]httpd.conf; I'm still getting 'listen setup failed':

$ httpd -tf apache$root:[conf]httpd.conf
[Tue Oct 17 23:27:49 2006] [crit] (57)socket is not connected : alloc_listener:
failed to get a socket for 0.0.0.0
Syntax error on line 156 of /apache$root/conf/httpd.conf:
Listen setup failed

Time to start stripping things out of that particular httpd.conf, I just *know* the answer will be something amazingly simple :)

[Adrian Graham_1]

bump!

I'm surprised I'm the only bloke to get this error in 6 years!

I now have exactly the same problem with VMS 8.4 and CSWS 2.2-1 on a BL860c I2

Nobody else seen this at all?

Cheers

Adrian

[Peter Barkas]

After you resolved the CONF location issue did you try a different port?

Is it possible that something else is using port 80?