Scalix not accepting logins this morning
Posted: Wed Nov 02, 2005 9:55 am
When I got to work this morning, the mail system was dead. Its been unreasonably flakely for the past couple days, and this morning, Scalix won't permit any logins -- it looks like a bad password to the (IMAP) clients.
Outlook, IMAP, and SWA are all unable to connect to the server.
In the logs, there were a number of Segmentation Violoations like:
SERIOUS ERROR Remote Client (U/I Access ) 11.01.05 19:57:28
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 21520
Procedure trace follows:
<- ual_BuildListEntry
-> ct_CloseCpactCtner
-> sfl_WriteBlockedData
<- sfl_WriteBlockedData
-> sfl_WriteBlockedData
<- sfl_WriteBlockedData
-> sfl_CloseItem
<- sfl_CloseItem
<- ct_CloseCpactCtner
-> ual_RemoveListFromCache
<- ual_RemoveListFromCache
<- ual_CancelList
<- ual_CloseListRefsForDI
-> ct_CloseCpactCtner
-> ual_TidyUp
-> nf_Close
Followed by this:
WARNING Service Router(Service Router) 11.01.05 20:24:10
[OM 7850] There was no message-id record in the message, so one was added.
New message-id is X0000000001414f0.1130894650.mail.forthill.int
And three of these:
WARNING Administration(omstat ) 11.02.05 08:23:58
[OM.DMON 2205] Failed to connect to Session Monitor: mdc_connect: No such file or directory
is mdc_connect a unix socket or what?
We're dead in the water for the moment, so any help would be great.
Outlook, IMAP, and SWA are all unable to connect to the server.
In the logs, there were a number of Segmentation Violoations like:
SERIOUS ERROR Remote Client (U/I Access ) 11.01.05 19:57:28
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 21520
Procedure trace follows:
<- ual_BuildListEntry
-> ct_CloseCpactCtner
-> sfl_WriteBlockedData
<- sfl_WriteBlockedData
-> sfl_WriteBlockedData
<- sfl_WriteBlockedData
-> sfl_CloseItem
<- sfl_CloseItem
<- ct_CloseCpactCtner
-> ual_RemoveListFromCache
<- ual_RemoveListFromCache
<- ual_CancelList
<- ual_CloseListRefsForDI
-> ct_CloseCpactCtner
-> ual_TidyUp
-> nf_Close
Followed by this:
WARNING Service Router(Service Router) 11.01.05 20:24:10
[OM 7850] There was no message-id record in the message, so one was added.
New message-id is X0000000001414f0.1130894650.mail.forthill.int
And three of these:
WARNING Administration(omstat ) 11.02.05 08:23:58
[OM.DMON 2205] Failed to connect to Session Monitor: mdc_connect: No such file or directory
is mdc_connect a unix socket or what?
We're dead in the water for the moment, so any help would be great.