1,126
edits
Difference between revisions of "Troubleshooting Content Manager OnDemand"
Jump to navigation
Jump to search
Troubleshooting Content Manager OnDemand (view source)
Revision as of 13:37, 28 November 2017
, 13:37, 28 November 2017Added IBM CMOD troubleshooting with strace.
m (Minor updates to IBM CMOD troubleshooting introduction.) |
(Added IBM CMOD troubleshooting with strace.) |
||
| Line 17: | Line 17: | ||
... 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. | ... 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. | ||
If arssockd doesn't produce a trace file, on platforms that include the strace utility, prefixing your command with: <code> strace -s 256 -f </code> will produce diagnostically valuable output. Search the output for the word 'arslog' in order to find error messages that are unable to be written to the System Log or trace file. | |||
strace -s 256 -f arssockd -I ARCHIVE -S | |||
... then search the output for the word 'arslog', and view the error messages that occur after it, as in the example below: | |||
[pid 900] execve("/opt/ibm/ondemand/V9.5/bin/arslog", ["/opt/ibm/ondemand/V9.5/bin/arslog", "ARCHIVE", "2017-11-27 11:38:06.247480", "0", "ARSMSG", "", "2", "216", "ARS0216E Unable to determine SMS/DMS tablespace type or filesystem is invalid >/arsdb/SMS<. The error number is 2", ""], | |||
== Operating Systems == | == Operating Systems == | ||