Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: Chrille on February 08, 2011, 05:52:06 PM
-
Hi,
Yesterday evening I suddenly couldn't reach my mail server (received
messages) with Thunderbird (connection timed out) I still can send
messages. I started to look through the logs (I can access server with
Server-manager, SSH etc) and I found this (that I don't understand,
googled it but still don't understand, even if this is the problem but
I suspect it is ...) SME 7.5.1 in /var/log/imap/current:
imapfront-auth[22196]: SASL AUTH login username=XXXXXX
2011-02-07 18:44:47.186802500 imap(XXXXXX): Panic: file maildir-sync.c:
line 1092 (maildir_sync_index): assertion failed: (uid > prev_uid)
2011-02-07 18:44:47.187267500 imap(XXXXXX): Error: Raw backtrace:
/usr/libexec/dovecot/imap [0x80a8f70] ->
/usr/libexec/dovecot/imap(i_fatal+0) [0x80a8faa] ->
/usr/libexec/dovecot/imap(maildir_sync_index+0x971) [0x8067f8d] ->
/usr/libexec/dovecot/imap [0x80680ee] ->
/usr/libexec/dovecot/imap(maildir_storage_sync_init+0x4c) [0x80682f0]
-> /usr/libexec/dovecot/imap(imap_sync_nonselected+0x1c) [0x806173b] ->
/usr/libexec/dovecot/imap(_cmd_select_full+0xb2) [0x80595fa] ->
/usr/libexec/dovecot/imap(cmd_select+0x19) [0x80597ae] ->
/usr/libexec/dovecot/imap [0x805b1ab] -> /usr/libexec/dovecot/imap
[0x805b140] -> /usr/libexec/dovecot/imap(_client_input+0x6e)
[0x805b2e6] -> /usr/libexec/dovecot/imap(io_loop_handler_run+0x15a)
[0x80af277] -> /usr/libexec/dovecot/imap(io_loop_run+0x1f) [0x80ae74c]
-> /usr/libexec/dovecot/imap(main+0x4a2) [0x80630ff] ->
/lib/tls/libc.so.6(__libc_start_main+0xd3) [0xb82e93] ->
/usr/libexec/dovecot/imap [0x8055ee1]
2011-02-07 19:25:25.415472500 imap(XXXXXX): Info: Disconnected in IDLE
Can someone please help me?
:-)
/Chrille
-
If you did nothing to your SME Server this should be reported in the bugtracker and not in the forums. Sudden breakage of stock SME Server functionality should be considered as a bug.
Please post back a pointer here for future readers after raising your issue. Thanks in advance.
-
Thanks for you answer Cactus,
I did that yesterday evening and the only answer I got so far was to post in the forum.. :-? so I'm trying to do the right thing. Last yum update of my server before the break was on the 15th of january
My bug is here: http://bugs.contribs.org/show_bug.cgi?id=6513
:)
/Chrille
-
I did that yesterday evening and the only answer I got so far was to post in the forum.. :-?
The right thing is the bugtracker. You should not have been pointed back to the forums.
I have added some comments to the bug you raised. Please provide the requested information. Thanks in advance.