Is this an error or just ignore it?

[packets]

I just wanna ask if I need to worry on the output of omshowlog below. My boss called me up and says that the server is busy. When I login, load is gradually becoming lower up to the point that it is 0. There is no other apps running such as anti-spam since it is only a internal mail server.

Code: Select all

WARNING                        Indexer       (Indexer       ) 02.17.11 13:22:49
[OM.DMON 3008] The Indexer cannot connect to SIS at this time. Details:
Failed to connect to SIS.
Reason: Time out on socket read
Is SIS currently unavailable?
Current message details:
         User name: Mark Tiu /mailsrv
         IndexId: fd02a8c0-4cc0663a-4d5c9c98-1eb1db
         Attempted action: Update the flags of item 000be6d71a8ab0b9 in folder 00011c11a4eae38c


WARNING                        IMAP Server Da(IMAP Server Pr) 02.17.11 16:50:26
[SYS 32] Broken pipe
User Name: Dennis Rodman / mailsrv/CN=Dennis Rodman
        -> getMessageInfo
        <- getMessageInfo
        -> sendMessageInfo
        <- sendMessageInfo
        -> getMessageInfo
        <- getMessageInfo
        -> sendMessageInfo
        <- sendMessageInfo
        -> getMessageInfo
        <- getMessageInfo
        -> sendMessageInfo
        <- sendMessageInfo
        -> getMessageInfo
        <- getMessageInfo
        -> sendMessageInfo
        <- /build/11.4.6/src/lib/ombase/os/os_fputs.c:39[1,32]

I found this on scalix-sis-indexer.log but it seems its just a warning. Correct me if I need to pay attention to this.

Code: Select all

2011-02-17 19:29:34,822  WARN [QueueManager] [BatchUpdater.performReferenceDeletes:219] No documents deleted for DeleteInfo{IndexInfo{userID='0b700000a3660cc4-161.96.861.291'}, indexID='fd02a8c0-4cc0663a-4d5d067e-1ebbd9', directRef='000beb42f93d723a', parentDirectRef='00011a186d8cdb1e'}
2011-02-17 19:29:34,825  INFO [QueueManager] [BatchUpdater.processMods:169] User 0b700000a3660cc4-161.96.861.291: added 0 content, added 1 refs, deleted 0 content, deleted 1 refs in 5 ms
2011-02-17 19:29:34,826  WARN [QueueManager] [BatchUpdater.performReferenceDeletes:219] No documents deleted for DeleteInfo{IndexInfo{userID='0f800000a3660cc4-161.96.861.291'}, indexID='fd02a8c0-4cc0663a-4d5d067e-1ebbd9', directRef='000beb3fcf888853', parentDirectRef='0001060fcf5836fa'}
2011-02-17 19:29:34,829  INFO [QueueManager] [BatchUpdater.processMods:169] User 0f800000a3660cc4-161.96.861.291: added 0 content, added 1 refs, deleted 0 content, deleted 1 refs in 4 ms

I found this one on catalina.out

Code: Select all

Feb 17, 2011 2:17:47 PM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Feb 17, 2011 2:22:00 PM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Feb 17, 2011 2:22:00 PM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Feb 17, 2011 4:30:08 PM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Feb 17, 2011 6:38:45 PM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Feb 17, 2011 6:39:08 PM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Feb 17, 2011 6:39:10 PM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2

Could it be possibly that there are many users using scalix that's why the load is quite high on that time. My physical ram is 3GB, 1.86Ghz dual core and with 73 users. I just created a script to monitor the load if there is a pattern on memory spikes.

[ltward]

It should resolve itself.

# omsolve -n dmon 3008
-------------------------------------------------------------------------------
Error Group: OM.DMON Error Number: 3008

The Indexer cannot connect to SIS at this time. Details:
[][][][][][][][][][]

The Indexer cannot connect to SIS at this time. This can happen if Tomcat
is restarted for any reason or there are network problems.)
Once connection to SIS is re-established, the Indexer will continue to work
normally.

If connection to SIS cannot be re-established, please contact Scalix.
-------------------------------------------------------------------------------