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 02:28, 27 February 2024
, 02:28, 27 February 2024Updated links to ODWEK Tracing & CMOD tracing.
(Updated links to ODWEK Tracing & CMOD tracing.) |
|||
| Line 48: | Line 48: | ||
There are a lot of articles on the IBM CMOD support portal for enabling tracing: | There are a lot of articles on the IBM CMOD support portal for enabling tracing: | ||
[ | [https://www.ibm.com/support/pages/how-do-i-enable-tracing-content-manager-ondemand-web-enablement-kit-odwek Enabling ODWEK Tracing] [https://www.ibm.com/support/pages/how-enable-trace-ibm-content-manager-ondemand-server 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. | ||