LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (22 lines)
Print Reply
Sender:
LISTSERV give-and-take forum <[log in to unmask]>
Subject:
From:
Valdis Kletnieks <[log in to unmask]>
Date:
Fri, 21 Sep 2001 10:31:53 -0400
In-Reply-To:
Your message of "Fri, 21 Sep 2001 09:31:36 EDT." <p05100306b7d0f0b7b5a8@[128.118.59.8]>
Comments:
To: Bill Verity <[log in to unmask]> To: [log in to unmask]
Reply-To:
LISTSERV give-and-take forum <[log in to unmask]>
On Fri, 21 Sep 2001 09:31:36 EDT, Bill Verity <[log in to unmask]>  said:
> Error - unable to initiate communication with LISTSERV (errno=78). The server is probably not started.
>
> I stopped and restarted listserv, but that didn't help.  I can get to many of the web pages through WA, but none that require authentication.

Hmm.. there's a known issue with the 'lsv' process not opening port 2306 on the way
up after a crash or a kill -9, because the old process didn't close() the socket
and it doesn't use SO_REUSEADDR, but restarting the lsv process again should fix
that (because the second restart will almost certainly be more than SO_LINGER time
after, so the port will be available).

You probably want to use 'netstat -a -n' and/or 'lsof' to see who, if anybody, has
port 2306 open, and double-check that any firewalling in effect has a punch-out
for that port.

I find the 'lcmdx.c' program very useful for diagnosing this stuff - using it
to submit a 'release' command directly to the 'lsv' process bypasses all of the
webserver issues - if 'lcmdx release' doesnt return a proper output for 'release',
it's either a networking issue or an 'lsv' issue.

/Valdis

ATOM RSS1 RSS2