Enabling debugging for remote XPC

You can store the debug information for the remote XPC in an external file.

To enable debugging for the remote XPC for a remote host

1. Access the UNIX OS application menu for the remote host in the Remote Monitoring container as described in Accessing-KM-Commands-and-InfoBoxes.
2. Choose Debug and Diagnostics > PUK Remote XPC Debug Admin.
3. In the PUK Remote Host Debug Admin dialog box, select the Enable XPC Debug check box to start the debugging at XPC level.
4. Select the Enable Libssh2 TRACE check box to start the debugging at library level.
5. Enter the absolute path and name of the log file in which you want the KM to store the debug information. For example,/tmp/PukRemoteDebug.txt.
6. Click Accept.
   The log file will be generated in the following format: /tmp/PukRemoteDebug.txt~pid, where pid is the process ID of the running pukremotexec.xpc.

To enable debugging for the remote XPC using pconfig variable

To enable the debug logs, set the following pconfig variable to 1:
/REMOTE_HOSTS/log_level
The logs are created at $PATROL_HOME/log.
Log file name convention: puk_rem.log~<pid>~#
where, <pid> is the process ID of the running pukremotexec.xpc.
and # is a number starting from 1.

OR

Execute the following PSL command from the PATROL Console system output window:
%PSL pconfig("REPLACE","/REMOTE_HOSTS/log_level",1);