Problems with cyrus-imapd 2.1.11 under Solaris 8

[Jason Fesler]

I'm seeing some form of crashes as well, but I'm not getting enough
details to really report on them :(  When it crashes, I have to kill
everything off including the master, and restart it.

-- 
 Jason Fesler, <jfesler at gigo.com> http://gigo.com/resume.html
 "You'll finish first - or not at all" - Death Race 2000

On Thu, 5 Dec 2002, Oleg Derevenetz wrote:

> Hi all,
>
> I have a problem with cyrus-imapd 2.1.11 working under Solaris 8. Imapd
> was built with gcc 2.95.3 and configured with following options:
>
> ./configure --with-cyrus-prefix=/usr/local/cyrus
>
> This is a piece of cyrus.conf file:
>
> SERVICES {
>    imap1 cmd="imapd -C /usr/local/cyrus/etc/1/imapd.conf"
> listen="[192.168.0.1]:imap" prefork = 0
>    pop31 cmd="pop3d -C /usr/local/cyrus/etc/1/imapd.conf"
> listen="[192.168.0.1]:pop3" prefork = 0
>    imap2 cmd="imapd -C /usr/local/cyrus/etc/2/imapd.conf"
> listen="[192.168.0.2]:imap" prefork = 0
>    pop32 cmd="pop3d -C /usr/local/cyrus/etc/2/imapd.conf"
> listen="[192.168.0.2]:pop3" prefork = 0
> }
>
> 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
>
> and then
>
> $ 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.
>
> Any ideas ?
>
>
>