Skip to main content

How to set FileWave Server components to debug mode

For troubleshooting, you can temporarily increase FileWave Server logging. Debug logging can help with server, Booster, LDAP collection/syncing, and Software Update catalog issues by adding detail that you or FileWave Support can use during investigation.

Before changing Server logging: These steps run on the self-managed Linux or macOS FileWave Server, not on the computer running FileWave Central. Use an administrator account authorized to change the listed files and control services. If FileWave hosts your Server, ask FileWave Technical Support to collect the Server diagnostics; do not attempt these shell steps from Central.

Record the existing logging settings before changing them. Coordinate the service restarts below with other administrators because they interrupt the work those services handle. How to Restart FileWave Components lists the commands for restarting individual services.

Step-by-step guide

To set debug logging for fwxserver.log, fwldap.log, and fwsu.log:

  1. On a Linux or macOS server, use /usr/local/etc/server.lvl.
  2. On Linux or macOS, set the debug level with echo 99 > /usr/local/etc/server.lvl. The server.lvl file may be empty if the debug level has not been set before.

If server.lvl does not exist, create it with a text editor or with echo 99 > /usr/local/etc/server.lvl.

If you only need fwxserver.log in debug mode, no restart is required after changing server.lvl. For LDAP, Software Update, or Booster troubleshooting, restart the relevant FileWave Server services or processes after changing the level.

Set logging back to the standard level after troubleshooting so debug logs do not keep growing unnecessarily.

The logging levels are as follows:

10 : Standard Log Level
99 : Debug Log Level
101: Trace Log Level

To set debug logging for the Django component (filewave_django.log):

  1. On a Linux or macOS server, go to /usr/local/filewave/django/filewave/.
  2. Edit settings_custom.py with sudo nano settings_custom.py.
  3. Remove the # before DEBUG = True.
  4. Save the file.
  5. Restart Apache with sudo fwcontrol apache restart.
  6. Restart Scheduler with sudo fwcontrol scheduler restart.
  7. Restart client_monitor with sudo fwcontrol client_monitor restart.
  8. Restart model_update_service with sudo fwcontrol model_update_service restart.

While debug logging is enabled, reproduce the reported issue and record the time and time zone. Use FileWave Log File Locations to collect the affected component logs for that interval. After troubleshooting, return Django logging to normal by adding the # back before DEBUG = True, then restart the services again. Share logs through your Support case rather than a public forum, and exclude passwords, API tokens, and private keys.