Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Debug and verbose log levels

Troubleshooting often requires additional, more detailed information about a specific service. You can change the log level of a specific service to enable more detailed logging. For more information, refer to Log files.

Only increase the log level temporarily when you are doing troubleshooting or you were asked by support. Leaving the log level on Debug/Verbose level can have an adverse effect on system performance which could lead to data loss in critical situations.

Debug command line output

Debug output shows messages about the operation of the internal activities and algorithms of the services. It could be especially useful when troubleshooting service startup issues, e.g. when a service cannot be started. In order to run a component in debug mode, first, you have to stop the desired service through the Web Application under System / Servers / Service Control and Activation or through Windows Service Control application (Start Menu / Settings / Control Panel / Administrative Tools / Services).

If Verba System Monitor is enabled for a given service, make sure that you stop the Verba System Monitor service too, unless it will automatically restart the given service.

The following table lists the services and their command line debug options:


  • No labels