imaps service terminated abnormally

[Gavin McCullagh]

Hi folks,

recently, I'm seeing this warning in our cyrus logs.  It appears in small
bunches like below, fairly sporadically:

Jul 12 13:21:03 paidi <debug> master[10962]: process 10274 exited, status 75
Jul 12 13:21:03 paidi <debug> master[10962]: service imapsxxx2 pid 10274 in BUSY state: terminated abnormally
Jul 12 13:21:07 paidi <debug> master[10962]: process 10276 exited, status 75
Jul 12 13:21:07 paidi <debug> master[10962]: service imapsxxx2 pid 10276 in BUSY state: terminated abnormally
Jul 12 13:21:07 paidi <debug> master[10962]: process 10275 exited, status 75
Jul 12 13:21:07 paidi <debug> master[10962]: service imapsxxx2 pid 10275 in BUSY state: terminated abnormally
Jul 12 13:21:12 paidi <debug> master[10962]: process 10259 exited, status 75
Jul 12 13:21:12 paidi <debug> master[10962]: service imapsxxx2 pid 10259 in BUSY state: terminated abnormally

I'm a little concerned by it.  Is there a usual explanation for the above?
Is this an imapd process crashing, the client disappearing or something
else?  Is there some way I can see more detail? 

Gavin


PS:

I should explain that we have configured extra services in the cyrus.conf
in order to bind to several IP addresses with different SSL certs.  I don't
imagine this is a problem.

imapsxxx2 cmd="imapd -s -C /kolab/etc/imapd/imapd.conf" listen="xxx.xx.xx.xxx:imaps" prefork=0