Location:
<WorkspaceDirectory>\LogFiles\nxaOPCSystem.35.log
Within this log file, all relevant event and system messages that are logged by the server application are stored. During server start up, a new, empty system log file is created by the server. However, the old system log files are not lost – after each server start up, the old system log file is renamed to "nxaOPCSystem.35.<timestamp>.log" where <timestamp> is the time of the current server start up.
If an unexpected server behaviour or other problems during runtime are observed, this server log file is a good starting point for analysing the reason of the problem. Since almost all information of the server is logged within this file, analyzing this file helps to solve the issue in most cases.
Example:
INFO;05/03/12 08:11:35.234;SERVER_ENGINE;Licensed Gateway Number: 32;0
INFO;05/03/12 08:11:35.249;SERVER_ENGINE;Option 'OPC.GroupAddressType' = '2Level';0
INFO;05/03/12 08:11:35.249;SERVER_ENGINE;Option 'OPC.AsyncReadFromDevice' = 'FALSE';0
INFO;05/03/12 08:11:35.249;SERVER_ENGINE;Option 'OPC.AsyncWriteConfirmation' = 'FALSE';0
INFO;05/03/12 08:11:35.249;SERVER_ENGINE;Option 'OPC.AsyncRefreshFromDevice' = 'FALSE';0
INFO;05/03/12 08:11:35.249;SERVER_ENGINE;Option 'OPC.AsyncTimeout' = '10';0
INFO;05/03/12 08:11:35.249;SERVER_ENGINE;Option 'KNX.Timeout' = '3';0
INFO;05/03/12 08:11:35.249;SERVER_ENGINE;Option 'SYS.EnableDeviceManager' = 'TRUE';0 INFO;05/03/12 08:11:35.249;SERVER_ENGINE;Option 'SYS.GatewayConnectionTimeout' = '100';0
Each line corresponds to one logging entry.
<tr> <td>1</td> <td>LogLevel</td> <td></td> <td>
| 1 | LogLevel | This column defines the log level of the event. This can be "INFO", "WARNING", or "ERROR". |
...
| 2 | Timestamp | This column specifies the point in time when the event occurred. |
...
| 3 | ModuleName | This column defines the module name that causes the event. |
...
| 3 | Message | This column shows the text of the event message. |
...