Scalix Forums

Posted: **Thu Dec 14, 2006 6:29 pm**

Hi Everyone,

Been using Scalix for the last 2 weeks and everyone here at work is very happy with it. I've setup ommaint maintenance in the cron jobs as per the ommaint documentation as well as ombackup to run nightly. Then about 3 days ago I started getting these maintenance errors but as far as i can see, everything is working fine. I went to the console and requested the error queue and Scalix reported no errors in the queue... Does anyone have any ideas? Here's the emailed report....

Thanks in Advance!
Dennis.

Code: Select all

Messages on the Scalix ERROR Queue
----------------------------------------------------
omstat : [OM.DMON 1013] The queue manager is not running.

The following daemons are ABORTED:
-------------------------------------------
0   13   PC Monitor   Aborted   NON-STOP   0
3   31   Shared memory daemon   Aborted   NON-STOP   -1
4   33   Notification Monitor   Aborted   NON-STOP   -1
5   34   Session Monitor   Aborted   NON-STOP   -1
6   52   Container Access Monitor   Aborted   NON-STOP   -1
9   57   Licence Monitor Daemon   Aborted   NON-STOP   -1
11   100   Queue Manager   Aborted   NON-STOP   -1
12   101   Item Delete Daemon   Aborted   NON-STOP   -1

-------------------------------------------
The following text is the output from the fatal log


SERIOUS ERROR           Administration(omsearch      ) Mon Dec 11 20:56:06 2006
[SYS 2] No such file or directory
File Name: /var/opt/scalix/admin/.dtls
Pid of logging process: 3670
Current errno value: 2


ERROR                   IMAP Server Da(IMAP Server Pr) Tue Dec 12 01:15:58 2006
[OM 24070] Debug message for Lab use :
imapSatServer: Connect to Core socket FAILED: No such file or directory  Satellite aborting ...
User Name: Dennis Advani / scalix, enex/CN=Dennis Advani Pid of logging process: 13237


ERROR                   IMAP Server Da(IMAP Server Pr) Tue Dec 12 01:15:58 2006
[OM 24070] Debug message for Lab use :
imapSatServer: Connect to Core socket FAILED: No such file or directory  Satellite aborting ...
User Name: Dennis Advani / scalix, enex/CN=Dennis Advani Pid of logging process: 13236


SERIOUS ERROR           Administration(omstat        ) Tue Dec 12 01:30:04 2006
[OM.DMON 1013] The queue manager is not running.
Pid of logging process: 13392


SERIOUS ERROR           Administration(omstat        ) Wed Dec 13 02:00:04 2006
[OM.DMON 1013] The queue manager is not running.
Pid of logging process: 12964


SERIOUS ERROR           Administration(omstat        ) Thu Dec 14 04:00:04 2006
[OM.DMON 1013] The queue manager is not running.
Pid of logging process: 1235


SERIOUS ERROR           Administration(omstat        ) Fri Dec 15 04:00:02 2006
[OM.DMON 1013] The queue manager is not running.
Pid of logging process: 14300

End of File - Fatal Long

Posted: **Fri Dec 15, 2006 4:44 am**

I don't have the ombackup script in front of me now, but I would suspect it does a shutdown to prepare for backup (have a look in there for omshut). When ommaint checks to see if the services are all up and running, it will report a failure because the server is shut down. The Queue Manager errors are typical of a omstat -q <QUEUE> to determine the number of messages while the Scalix server is shut down.

Scalix Forums

Errors every night but nothing is wrong...

Errors every night but nothing is wrong...