LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

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

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

Print Reply
Bill Verity <[log in to unmask]>
Thu, 27 Jan 2000 13:38:34 -0500
text/plain (30 lines)
>One of the orphans is probably bound to port 2306 and I imagine if you
>check listserv.log after the last restart you'll find that it couldn't
>bind to port 2306.  You have to kill all 'lsv' processes before restarting.
>
>Nathan


That was it.  At the start of listserv's log I found:

        >>> LISTSERV already running on pid 107600 <<<
        -> Clean shutdown of LISTSERV(107600) initiated...
        -> LISTSERV(107600) successfully shut down.
        >>> Cannot bind to local host, port 2306: error 67.

Killing the two processes and restarting listserv solved the problem.  I guess once it can't bind that port it never tries again - right?

The orphans were probably caused at our midnight restart.  I'm going to change that to 12:30 a.m. -- too much happening at 00:00.  Here is the log showing the kill problem:

        >>> LISTSERV already running on pid 55698 <<<
        -> Clean shutdown of LISTSERV(55698) initiated...
        -> Timeout - attempting SIGKILL...
        -> LISTSERV(55698) killed.

We restart every six hours so the log files don't get too big.
--
Bill Verity - 814-865-4758  Fax: 814-863-7049
Postmaster & Listserv maintainer
Center for Academic Computing, Penn State University
At the office - on my Mac, of course ;-)

ATOM RSS1 RSS2