Package: cyrus21-imapd Version: 2.1.18-1 Followup-For: Bug #303092 Hello again,
I tried to find the last successful login and the first fatal login. But this boundary is fuzzy. But I found another log message around the time period when this problem arose: Sep 26 13:55:01 feyerabend cyrus/master[14008]: about to exec /usr/lib/cyrus/bin/imapd Sep 26 13:55:01 feyerabend cyrus/imaps[14008]: executed Sep 26 13:55:01 feyerabend cyrus/imapd[14008]: accepted connection Sep 26 13:55:01 feyerabend cyrus/imapd[14008]: starttls: TLSv1 with cipher RC4-MD5 (128/128 bits reused) no authentication Sep 26 13:55:01 feyerabend cyrus/imapd[14008]: login: [134.102.123.95] arehling plaintext+TLS messages Sep 26 13:55:01 feyerabend cyrus/imapd[14008]: seen_db: user arehling opened /var/lib/cyrus/user/a/arehling.seen Sep 26 13:55:01 feyerabend cyrus/imapd[14008]: Fatal error: Internal error: assertion failed: cyrusdb_skiplist.c: 377: TYPE(ptr) == DUMMY || TYPE(ptr) == INORDER || TYPE(ptr) == ADD Sep 26 13:55:01 feyerabend cyrus/master[2155]: process 14008 exited, status 75 Sep 26 13:55:01 feyerabend cyrus/master[2155]: service imaps pid 14008 in BUSY state: terminated abnormally This message occured several times during the time span, when the problem started. Later, when there are no successful login attempts anymore, there are none of these assertion errors. I think the corruption of the arehling.seen file was a longer progress. :-) Wollie -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages cyrus21-imapd depends on: hi cyrus21-common 2.1.18-1 Cyrus mail system (common files) ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdb3 3.2.9-22 Berkeley v3 Database Libraries [ru ii libsasl2 2.1.19-1.5 Authentication abstraction library ii libssl0.9.7 0.9.7e-3 SSL shared libraries ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
