segfault of imapd and pop3d

[Michael Menge]

Quoting Bron Gondwana <brong at fastmail.fm>:

> On Tue, Jan 15, 2008 at 09:18:27AM +0100, Michael Menge wrote:
>> Hi,
>>
>> I found some segmentation faults of my "imapd -s"  and "pop3d -s""proceses
>> in my logs.Has anybody seen this before. I'm running cyrus 2.3.8 on an
>> SLES10 x86_64.
>>
>> Jan 14 09:37:44 mailserv08 kernel: imapd[1898]: segfault at
>> 00002b9042669978 rip
>> 00000000004805d4 rsp 00007fffdf6b51c0 error 4
>> Jan 14 10:11:44 mailserv08 kernel: imapd[32213]: segfault at
>> 00002b1c29b16978 rip
>> 00000000004805d4 rsp 00007ffff81f9d00 error 4
>> Jan 14 10:13:47 mailserv08 kernel: imapd[30415]: segfault at
>> 00002b6440346978 rip
>> 00000000004805d4 rsp 00007fffe19d4360 error 4
>> Jan 14 10:17:51 mailserv08 kernel: imapd[30420]: segfault at
>> 00002adb7dd67978 rip
>> 00000000004805d4 rsp 00007fffa3fb3ab0 error 4
>> Jan 14 10:53:18 mailserv08 kernel: imapd[2072]: segfault at
>> 00002ae8ce23e978 rip
>> 00000000004805d4 rsp 00007fff5368d190 error 4
>> Jan 14 11:07:14 mailserv08 kernel: pop3d[3402]: segfault at
>> 00002b29a2f6a978 rip
>> 000000000043fe4c rsp 00007fff7e8fc510 error 4
>> Jan 14 11:33:41 mailserv08 kernel: imapd[3797]: segfault at
>> 00002b5a2e971978 rip
>> 00000000004805d4 rsp 00007ffff33aaeb0 error 4
>> Jan 14 12:00:20 mailserv08 kernel: pop3d[5015]: segfault at
>> 00002ad8925f3978 rip
>> 000000000043fe4c rsp 00007fff8f72b340 error 4
>>
>> The last corresponding entry in cyrus logs is always "accepted connection"
>>
>> Jan 14 11:33:41 mailserv08 imaps[3797]: accepted connection
>> Jan 14 12:00:20 mailserv08 pop3s[5015]: accepted connection
>
> Sounds like a corrupted mailbox to me - there's heaps of stuff where
> cyrus mmaps a file and blindly goes adding offsets read from it to
> the mmap base and accessing the memory there.  Recipe for segfaults
> if I ever saw one.
>
> Do you know which user is logging in when this happens?  They're
> rare enough that I assume it's not every user on the box!
>
> Bron.
>



Syslog is logging Cyrus at debug level, and the last line for that process is
"accepted connection". Normaly this line is followd by a STARTTLS line  
and a LOGIN line.
proc/pid shows the host they are connected with. These IPs are  
different for most processes and i see other succesfull logins from  
these hosts.

So i don't think it's a corrupt mailbox. Maybe the tls_sessions.db is corrupt.
Is there a way to check a skiplist if the file is corrupted?

--------------------------------------------------------------------------------
M.Menge                                 Tel.: (49) 7071/29-70316
Universitaet Tuebingen                  Fax.: (49) 7071/29-5912
Zentrum fuer Datenverarbeitung          mail:  
michael.menge at zdv.uni-tuebingen.de
Waechterstrasse 76
72074 Tuebingen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5339 bytes
Desc: S/MIME krytographische Unterschrift
Url : http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20080115/0537ba69/attachment.bin