After upgrading our Hub server to R6.5 from 5.011, we started receiving the following errors: Chronos: Error full text indexing dircat.nsf: Message Queue is full. We also get them for the DirAssis.nsf and Names.nsf. Any ideas what is causing these errors? We have plenty of system resources available. Is there something in the Notes.ini that might cause/cure this problem? Any help would be appreciated. Thanks
Subject: ‘Chronos: Error full text indexing dircat.nsf: Message Queue is full.’ error
I just upgraded from 5.0.11 to 6.5 as well and am getting these errors as well. Did you ever come across the reason for them? or even a solution?
Nelson
Subject: RE: ‘Chronos: Error full text indexing dircat.nsf: Message Queue is full.’ error
I am also getting these errors.
Subject: RE: ‘Chronos: Error full text indexing dircat.nsf: Message Queue is full.’ error
I was Getting the same error for mail file.I opened that email in Client and presses Ctrl+Shift+F9 and it rebulded all views and indexes and error is gone.
Subject: ‘Chronos: Error full text indexing dircat.nsf: Message Queue is full.’ error
We recently upgraded our mail servers from 5.0.11 to 6.5.1. Almost immediately, we began experiencing this problem. So far, I have been able to spot 56 0f our 72 full-text indexed mail files in the server logs with the following error:
“Chronos: Error full text indexing Mail\mailfile.nsf: Message Queue is full.”
I opened a ticket w/ Lotus; and below is what they have suggested. I will be attempting these in the next day or two, and will post my results here.
Fixes(?):
1.) Run “updall -x” on all of the databases (those with full-text indexes, and those that may be full-text indexed in the future).
2.) Add the following to the notes.ini:
UPDATE_IDLE_TIME=1
Subject: RE: ‘Chronos: Error full text indexing dircat.nsf: Message Queue is full.’ error
Well, we tried both of these to no avail. However, we did find one thing on our own (thanks to the forums); and Lotus told us another.
1.) We were getting several messages on the console saying, “Agent is running full text operations on mail\xxx.nsf which is not full text indexed. This is extremely inefficient.” We found that when the indexer ran shortly after one of these messages appeared on the server; that several of our databases were getting the Chronos error. We went through these databases, deleted obsolete agents, and full-text indexed those that still needed to run their agents. This seemed to eliminate both error/warning messages.
2.) Lotus informed us that we should be running one indexer task (Update) per CPU. We only had one task running for our server; although it has 4 CPUs. We added 3 more indexers, and saw them immediately processing, then all 4 going idle.
Hope this helps.
Subject: RE: ‘Chronos: Error full text indexing dircat.nsf: Message Queue is full.’ error
We have the same problem with Chronos with 6.5. I found at the support.lotus.com the following link where the bug is reported:
http://www-1.ibm.com/support/docview.wss?uid=swg21160041
hope this is similar to your problem.