Debug logging uses two switches, SmsDebug and SmsDebug2, to control the amount of logging. SmsDebug is used to log information about a particular feature, and SmsDebug2 is used to control the level of debug messages required. Although the details of all possible values for these switches are beyond the scope of this document, it is important to note that both these switches must be supplied in the command line to enable debug logging. Novell support might request additional debug logs to be generated for specific features based on the complexity of the problem.
Use the following options to enable or disable debug log on OES Linux and NetWare:
Kill the SMDR process
pkill smdrd
Enable debug and restart SMDR
/opt/novell/sms/bin/smdrd --smsdebug fffffffc --smsdebug2 fffffffc
Perform the tests to reproduce the problem.
The error messages will be logged in the debug log file.
pkill smdrd
Load SMDR
load smdr
Start Debug log
smdr /smsdebug=fffffffc /smsdebug2=fffffffc
Perform the test to reproduce the problem.
The error messages will be logged in the debug log file.
smdr /smsdebug=0 /smsdebug2=0
smsconfig -l tsafs --smsDebug=fffffffc --smsDebug2=fffffffc
Unload TSA
smsconfig -u tsafs
Reload TSA
smsconfig -l tsafs
tsafs /smsDebug=fffffffc /smsDebug2=fffffffc
tsafs /smsDebug=0 /smsDebug2=0
NOTE:On OES NetWare debug logging can be enabled at runtime. On OES Linux, debug logging must be enabled during loading of smdr or tsafs. To ensure that the debug logs have been created and all the information has been flushed to the files, unload the modules before collecting the log files.