Please enter search query.
Search <product_name> all support & community content...
Under certain conditions if a content router is stopped during rerouting, the content router can fail to start up.
Article: 100020115
Last Published: 2010-01-13
Ratings: 0 0
Product(s): Appliances
Problem
GENERAL ERROR: Under certain conditions if a content router is stopped during rerouting, the content router can fail to start up.Solution
Overview:
The PureDisk 6.5.1 Content Router has an extra safe-guard built in. This safeguard performs a consistency check on theCR queue (which consists of the files /Storage/queue/*.tlog). During rerouting, the Content Router can put an entry with type "MARKER" in its queue.This entry may have an uninitialized "task id" value. This field is not used by the Content Router, but the consistency check may consider this uninitializedvalue to be an error. If the Content Router is stopped during rerouting while the "MARKER" entry is present in its queue, it will not start because the consistency check detects the error.
Log files:
The ContentRouter logs an event with severity "critical" to the Storage Pool Authority(SPA): "Failed to Start the Spooler Cache Manager. Please check the server log for additional information and probable cause of this error. The application hasbeen terminated.".
Error messages will be present in /Storage/log/spoold/spoold.log.
The PureDisk 6.5.1 Content Router has an extra safe-guard built in. This safeguard performs a consistency check on theCR queue (which consists of the files /Storage/queue/*.tlog). During rerouting, the Content Router can put an entry with type "MARKER" in its queue.This entry may have an uninitialized "task id" value. This field is not used by the Content Router, but the consistency check may consider this uninitializedvalue to be an error. If the Content Router is stopped during rerouting while the "MARKER" entry is present in its queue, it will not start because the consistency check detects the error.
Log files:
The ContentRouter logs an event with severity "critical" to the Storage Pool Authority(SPA): "Failed to Start the Spooler Cache Manager. Please check the server log for additional information and probable cause of this error. The application hasbeen terminated.".
Error messages will be present in /Storage/log/spoold/spoold.log.
February02 21:45:16 ERR [47655040622928]: 25032: Spooler Cache Manager:
Truncatedoffset 68828 for tlogid 285: We found a task ID (1077952848) that is
higherthan any we've handed out so far (256). This indicatescorruption.
Pleasecontact support. Content router will not start as aprecaution.
February02 21:45:16 ERR [47655040622928]: 25032: Spooler Cache Manager: failed
toinitialize global spooler cache. There are probably more objects in the
queuethan fit in the cache. Cannot continue. (data corrupt)
February02 21:45:16 ERR [47655040622928]: 26016: Spooler Cache Manager: Start
failure.
Formal Resolution:
This issue is currently being considered by Veritas Corporation to be addressed in a forthcomingversion of the product. As Puredisk patches are released, please visit thefollowing link for download and readme information for a fix on this issue(Etrack1514990).
https://www.veritas.com/business/support/overview.jsp?pid=52672
If this error is encountered prior to a Formal Resolution being available, please contact Technical Support and reference this Etrack ID(1514990).
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.