Provisioning Reference Guide › Provisioning Maintenance › View and Maintain Log Files › Diagnostic Logging › Provisioning Manager Logging

Provisioning Manager Logging

To diagnose problems communicating with the server, you can set logging to record events that transpire between the Provisioning Manager and the Provisioning Server to which it is connected. Use the Logging tab under File, Preferences to trace all requests sent to any server from the Provisioning Manager.

This logging is actually logging within the C/C++ client library used by the Provisioning Manager and some other clients (batch utility, password manager, csfconfig, bindeta, pingeta). Once logging is enabled and configured using Provisioning Manager, those log settings apply for these other clients as well. Each client logs its command name as it logs messages so you can identify which log messages are specific to which client.

However, for this to work the client being run must reside in the same file system folder as the Provisioning Manager’s etadmin.exe program. When this is not the case (such as when running on Solaris where there is no Provisioning Manager install, or even on Windows when you run utilities from the Provisioning Server’s installation), the client library consults registry settings specific to the Provisioning Server instead of specific to the Provisioning Manager. Set these other registry settings by running these eta-env commands using the eta-env program included in the Provisioning Server installation:

eta-env
    action=set
    name=Manager/LogMaster
    type=int
    value=1

eta-env
    action=set
    name=Manager/LogDestinations
    type=int
    value=16

eta-env
    action=set
    name=Manager/LogSevFile
    type=int
    value=31

These have the effect of configuring the C/C++ client library for the provisioning server’s installation, setting the destination to “text file” and logging all message severities.

Finally, the csfconfig command has a “debug=yes” command-line parameter you can specify to turn this logging on for one command invocation overriding any registry settings configured with Provisioning Manager or eta-env.