1,126
edits
Difference between revisions of "Troubleshooting Content Manager OnDemand"
Jump to navigation
Jump to search
m
Troubleshooting Content Manager OnDemand (view source)
Revision as of 10:40, 3 May 2016
, 10:40, 3 May 2016Moved CMOD to the top.
m (Added errpt.) |
m (Moved CMOD to the top.) |
||
| Line 7: | Line 7: | ||
These are the components of CMOD, and the functionality they provide. | These are the components of CMOD, and the functionality they provide. | ||
== Content Manager OnDemand == | |||
Content Manager OnDemand has a built-in 'System Log' that you can query for information. As almost every action is logged into the OnDemand System Log, it can be difficult to find what you're looking for. By choosing from the pop up list for the 'Severity' field, you can quickly find the most important error messages stored in the System Log. | |||
Also, in the most recent versions of Content Manager OnDemand, almost all command-line utilities (arssockd, arsload, arsadmin) have 'tracing' features that can be turned on by specifying the '''-1''' and '''-2''' parameters. | |||
arssockd -I ARCHIVE -S -1 /tmp/arssockd.trace -2 ALL=15 | |||
... specifies maximal tracing for arssockd. It's highly recommended that you only run in this mode while specifically doing debugging, as enabling tracing in Content Manager OnDemand reduces performance of the server. | |||
== Operating Systems == | == Operating Systems == | ||
| Line 80: | Line 90: | ||
... and after entering a valid User ID and password, you will see all messages in TSM, as they happen. To exit from Console Mode, simply press Control-C. | ... and after entering a valid User ID and password, you will see all messages in TSM, as they happen. To exit from Console Mode, simply press Control-C. | ||