Problem

A BoKS process needs to be debugged on a remote host but you don't have access to log in to the host.

Solution

BoKS has the ability to remotely debug certain BoKS processes. This process works much like a local bdebug, except that it can be executed from the Master.

For example, if we needed to debug bridge_servc_s on hostx, we could issue the following command from the Master:


BoKS# rbdebug -h hostx -x9 bridge_servc_s -f bridge_servc_s-debug.out

Note: If you do not specify a full path after the -f option, the resulting debug file will be placed into $BOKS_var. If you specify a path outside of $BOKS_var or $BOKS_etc, you will not be able to remotely access the file using rbdebug or cadm.

When we're done with the debug, we can stop it using the command:

BoKS# rbdebug -h hostx -x0 bridge_servc_s

We can examine the debug file on the remote host using the command:

BoKS# rbdebug -h hostx -l bridge_servc_s-debug.out

The following processes can be remotely debugged with rbdebug:

clntdbridge_clntd_sbridge_servm_s
hostlookupdservcbridge_servc_r
bridge_servc_sudsqdbkstd
bksdxdcached
httpsrvacedcsspd
authdvcsynchdeventd
autoregisterddbupdate_readeradpswsyncd
loginrloginrshd
rshsuftpd
ftpxdmdtlogin
telnetboksauthxdl
xtdtsessiondesgold

The rdebug utility uses cadm to communicate with the Server Agent, but you can use the cadm utility directly to trigger debugging activity on a remote host. For the examples above, the corresponding cadm commands would be:

Debug bridge_servc_s:

BoKS# cadm -h hostx -s 'bdebug -x9 bridge_servc_s -f bridge_servc_s-debug.out'

Turn off debugging:

BoKS# cadm -h hostx -s 'bdebug -x0 bridge_servc_s'

View debug file:

BoKS# cadm -h hostx -l -f bridge_servc_s-debug.out


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 25, 2018