Difference between revisions of "Troubleshooting Content Manager OnDemand"

Added IBM CMOD Trace arstfmt
(Added IBM CMOD Trace arstfmt)
Line 18: Line 18:
... 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.


There are a lot of articles on the IBM CMOD support portal for enabling tracing:
[http://www-01.ibm.com/support/docview.wss?uid=swg21240220 Enabling ODWEK Tracing]   [http://www-01.ibm.com/support/docview.wss?uid=swg21330810 Enabling tracing in Content Manager OnDemand server]   [http://www.ibm.com/support/docview.wss?uid=swg21661918 Formatting trace files on Windows]   [https://www.ibm.com/support/knowledgecenter/SSEPCD_10.1.0/com.ibm.ondemand.ir.doc/dodig089.htm Trace Facility for PDF indexer]


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.
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.