Re: Tracking down signaled to death by 11 errors

2004-06-01 Thread Shawn Sivy
I think the problem is related to the cyrus.* files. It seems that a lot of the users having problems and causing the signaled to death by 11 errors have cyrus.*.NEW files. What would cause the .NEW files to remain? A reconstruct seems to fix the problem, but anyone know what may be causing

Re: Tracking down signaled to death by 11 errors

2004-06-01 Thread Shawn Sivy
I was able to get the truss output of one of the imapd processes that died. I also have the core file that was generated. Is there anything I can do with the core file to see what was happening at the time it died? Here's the last few lines of the truss output if it helps. open("33275.", O_R

Tracking down signaled to death by 11 errors

2004-06-01 Thread Shawn Sivy
After the upgrade to Cyrus IMAP 2.2.5 (SASL 2.1.18), I've been seeing a lot of these errors in the logs: Jun 1 08:42:19 cyrus master[21185]: [ID 970914 local6.error] process 21886 exited, signaled to death by 11 Jun 1 08:43:26 cyrus master[21185]: [ID 970914 local6.error] process 20660 exited