> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/other-help-articles/debug-logging.md).

# Debug Logging

## Description

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.

### Enable Logging

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.

1. 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: */system/lib/sys/settings.cfg*
   * Release version 7.3.2 or later: */dat/settings.cfg*
2. Search for the setting called *LNLOG\_PROFILE\_DEFAULT*.
3. Change the value to *DEBUG*.
4. 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.

1. Download and install *DebugView* from *SysInternals*: <https://technet.microsoft.com/en-us/sysinternals/debugview.aspx>.
2. Start the DebugView application in administrator mode.
3. Ensure that Global Win32 events are logged by clicking the *Capture* Menu. Check *Capture Global Win32*.
4. Use the LogicNets application.
5. Save the log to a file.
6. 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.

* /etc/httpd/logs/error\_log
* /tmp/lua.log
* /tmp/logicnets.log

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:

1. /tmp/systemd-private-XXXXXXXXXXX-httpd.service-XXXXX/tmp
2. /var/tmp/systemd-private-XXXXXXXXXXX-httpd.service-XXXXX/tmp


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/other-help-articles/debug-logging.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.