The DLQ log file includes measurements about how long calls take and it is a very useful file for troubleshooting purposes. When DLQ logging is turned on, a DLQ file will generate in the location of the TcpSubServer executable. Each time the server is stopped and restarted, a new DLQ file is created and will be named something like this example:
Activating DLQ Logging
When a split server is initialized for the first time, we typically recommend that you turn on DLQ logging. Here are the steps to do this:
- Stop the master server and slave server(s), if applicable. (see Stopping and Starting a SystemWeaver Server)
- In the server directory, open the swServer.ini.
- Add a line for DLQ logging (DLQ=True):
- Save your changes.
- Restart the server(s).
Maintaining DLQ Log Files
The dlq files can become quite large especially if the server is not restarted in a very long time. If the size becomes an issue, you can move or delete a DLQ file. However, if the file is the one currently being written to by the server, you must first stop the server before moving or deleting it. When you restart the server, a new file will generate. If there are multiple DLQ files saved, you can always delete older file versions at any time.
If Systemite requests this file for troubleshooting purposes, make a copy of the dlq file covering the time frame of the reported issue and upload the copy to SystemiteNAS.
Turning off DLQ Logging
To turn off DLQ logging, open the swServer.ini in a text editor and change the setting to DLQ=False. The new setting will not apply until the server is restarted. See Stopping and Starting a SystemWeaver Server.