Logging
When PROLIN Power Server is running, it produces several files containing information about runtime activities.
- Most of this information can be viewed in the Server Management Console.
- You can also inspect the server.log file, located in the logs subfolder.
- This file contains important details about runtime activities and failures.
- It can be opened with any text editor (e.g., Notepad).
- This file contains important details about runtime activities and failures.
Logging Level
By default, the logging level is set to INFO, which is sufficient for daily usage scenarios.
However, you can change this level to log additional diagnostic messages.
These steps can be performed while PROLIN Power Server is running.
You can also change the logging level at runtime using the Server Management Console (see the Monitoring topic).
However, this method does not allow you to capture DEBUG information during server startup.
Change to DEBUG Level
- In the config subfolder under the installation folder of PowerServer, create a backup of the
log4net.configfile.
- Open the
log4net.configfile in a text editor.
- Locate the following section:
<log4net> ... <logger name="OVSD"> <level value="INFO"/> </logger> <logger name="PROLIN"> <level value="INFO"/> </logger> </log4net>
Change both
<level value="INFO"/>
into:
<level value="DEBUG"/>
Optionally, change the following section:
<appender name="rollingFile" type="log4net.Appender.RollingFileAppender,log4net">
<param name="File" value="logs\server.log" />
<param name="ImmediateFlush" value="false"/>
</appender>
into:
<appender name="rollingFile" type="log4net.Appender.RollingFileAppender,log4net">
<param name="File" value="logs\server.log" />
<param name="ImmediateFlush" value="true"/>
</appender>
Save the file.
Once these changes are made, additional log messages will appear in all logging outputs (including server.log).
Enabling DEBUG logging can generate hundreds of extra messages, causing the log file to grow rapidly and impacting performance. Always revert these changes after completing your diagnostics session.