Question
How do I enable debugging on the PTA server and collect relevant logs for support?
Answer
Enable debug:
1. Change the log level to 'trace' for all components:
/opt/pta/utility/changeLogLevel.sh -c all -l trace
2. Reproduce the issue and then change the log level back to info level:
/opt/pta/utility/changeLogLevel.sh -c all -l info
Note:
By default, every change will restart the affected component. To disable the restart, the annotation "-norestart" should be added.
Alternatively, you can set the debug level for individual components:
Collect the following logs:
diamond.log:
/opt/tomcat/logs/
exportTool:
/opt/tomcat/utility/exportTool.sh
The exportTool requires number of days of logs that will be exported. It's recommended to add 1-2 days prior to when the issue started. There is no need to export database and dumps unless requested by CyberArk.
DiagTool:
/opt/pta/diag-tool/pta_tool.sh
Note: If diagnostics required, users should run instead RUN_DIAGNOSTICS at a root prompt.
Q: How do I enable debugging on the PTA server and collect relevant logs for support?
A:
Enable debug:
Change the log level to 'trace' for all components:
/opt/pta/utility/changeLogLevel.sh -c all -l trace
Reproduce the issue and then change the log level back to info level:
/opt/pta/utility/changeLogLevel.sh -c all -l info
By default, every change will restart the affected component, to disable the restart, the annotation "-norestart" should be added.
Alternatively, you can set the debug level for individual components:
Collect the following logs:
diamond.log
http://opt/tomcat/logs/
exportTool
/opt/tomcat/utility/exportTool.sh
The exportTool requires number of days of logs that will be exported. It's recommended to add 1-2 days prior to when the issue started. There is no need to export database and dumps unless requested by CyberArk.
DiagTool
/opt/pta/diag-tool/pta_tool.sh
Note: If diagnostics required, users should run instead RUN_DIAGNOSTICS at a root prompt.