Logging Tab
Previous Topic  Next Topic 

The Logging Tab defines a variety of logging mechanisms. The tab contains two sections: General and Output Capture.

NOTE: Be careful when running batch files and redirecting stdout and stderr. If you use batch file commands such as "timeout" and "pause" that expect stdin then your batch file may crash. We have seen this behaviour on earlier versions of Windows including Server 2008 and 7. Windows 10 and Server 2016 appear immune to this problem. Try using "waitfor" instead.

General Section



Event Logging

Toggle logging by FireDaemon Pro to the Event Log.

Debug Logging

Toggle debugging by FireDaemon Pro to nominated text file. Note that Debug Logging is somewhat verbose and should only be enabled temporarily when attempting to resolve FireDaemon Pro service configuration issues. Ultra-verbose execution tracing can also be included in the debug log. This is enabled globally by setting a system wide environment variable as follows:

Environment Variable Name: FD_TRACELEVEL

Environment Variable Value: DEBUG

Execution tracing will be included in the debug log file once the relevant FireDaemon Pro service(s) have been restarted. This environment variable has no effect if Debug Logging is disabled.

Append Logs

When this option is enabled, entries are always appended to the Debug, Stdout and Stderr log files.  When this option is disabled, the Debug, Stdout and Stderr log files are overwritten when the service starts. If the sub-process crashes and FireDaemon Pro has to restart it, the Stdout and Stderr log files are overwritten when Append Logs is unchecked. Note that if FireDaemon Pro cannot write to the any of the specified log files it will write an error event to the Windows Applicatoin Event Log.

Debug Log File

The full path and name of the file to log to. Environment variables can be used in the name.

Output Capture Section



Capture Stdout in File

Enables the capture of Stdout (Standard Output the console text output stream from the application being run as a service). Nominate the full path and name of the file to log to. Note: Stdout/Stderr capture is unbuffered and cached. Stdout/Stderr is only captured to file when only when the application's output buffer is flushed. Thus, the successful capture of output is dependent upon the application's behavior. Stdout/Stderr capture may be truncated if the application exits suddenly of its own accord. FireDaemon Pro does flush Stdout/Stderr upon application restart and termination.

Capture Stderr in Stdout

Enables Stderr (Standard Error the console text output stream specifically marked as errors from the application being run as a service) to be captured alongside Stdout into the same log file.

Or Capture in File

Enables Stderr to be captured in a separate file from Stdout.