LogicNets offers logging options for use in troubleshooting, and LogicNets can also offer some assistance with log review in some cases. By default, logging is disabled on a production system. The following sections explain how to enable logging and how to retrieve the files from Windows and Linux-systems.
Use the following steps to enable debug logging. The updated configuration will be active for all LogicNets sessions started after the change. It will not affect existing sessions.
- Open the LogicNets configuration file in a text editor, such as Notepad. The configuration file is is located in the following location:
- Releases prior to version 7.3.2: <installation>/system/lib/sys/settings.cfg
- Release version 7.3.2 or later: <installation>/dat/settings.cfg
- Search for the setting called LNLOG_PROFILE_DEFAULT.
- Change the value to DEBUG.
- Save the configuration file.
View Logging on a Windows Machine
The logging on a Windows machine is not saved in log files, but files can be accessed via an external tool by using the following steps.
- Download and install DebugView from SysInternals: https://technet.microsoft.com/en-us/sysinternals/debugview.aspx.
- Start the DebugView application in administrator mode.
- Ensure that Global Win32 events are logged by clicking the Capture Menu. Check Capture Global Win32.
- Use the LogicNets application.
- Save the log to a file.
- Send the log file to LogicNets.
View Logging on a Linux Machine
The system saves logging on a Linux machine in three different files. For help with troubleshooting, please send all three files to LogicNets.
Note: RHEL Apache can make use of the “private-tmp”-feature. Depending on your RHEL setup the log files may be located somewhere else, but typical locations include the following: