Just to be clear, that's cyr_expire dying, not being killed by master. Signal 11 is SIGSEGV, which is to say a segmentation violation, i.e., a bug in cyr_expire. Personally, I've seen this error on a lot of systems. The mailbox after the last one you listed probably has a corrupt meta file -- indicative of a bug in another process. Reconstruct will typically correct these sorts of problems. :wes On 04 Sep 2007, at 06:03, Rudy Gevaert wrote: > mail3r/master[27338]: about to exec /usr/cyrus-replica/bin/cyr_expire > mail3r/master[28619]: process 27338 exited, signaled to death by 11 > > As you can see we have a cyr_expire on our replica running, and for > some > reason it get's signaled to death. This has been done the last three > nights. > > If I go through the log it happened always after the same user. > > Has anybody seen this? Should I run reconstruct on the replica > mailbox? ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
