Problems with cyrus-imapd 2.1.11 under Solaris 8
rjs3 at andrew.cmu.edu
Thu Dec 5 15:01:27 EST 2002
On Thu, 5 Dec 2002, Oleg Derevenetz wrote:
> When some pop3d dies with signal (i.e. SIGTERM), all incoming
> connections to corresponding address:port are hangs. For example, if I
> have pop3d running on 192.168.0.1:110, and issue a command:
> $ kill PID_OF_THIS_POP3D
I can't duplicate this. I might be able to come up with a scenario if ALL
of the pop3ds died in the queue (similar to the bugs that have been
intermittantly reported with master losing count of the number of
processes that are around).
> $ telnet 192.168.0.1 110
> I couldn't see pop3d banner after successful connection. Looks like all
> incoming connections to this address holds in kernel queue and doesn't
> reach accept(). Last message in log is "process PID exited, signaled to
> death by 15".
> In the same time all connections to 192.168.0.2:110 are successfully
> completes and I can see a standard pop3d banner.
This makes sense, since master will maintain separate queues for each
entry in the SERVICES list.
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper
More information about the Info-cyrus