How to set FileWave Server components to debug mode

For troubleshootingtroubleshooting, purposes,you itcan maytemporarily be useful to set theincrease FileWave serverServer tologging. debugDebug mode.logging Whencan troubleshooting issueshelp with the FileWave server, booster,Booster, LDAP collectioncollection/syncing, and syncing, as well as Software Update catalog issues,issues debugby loggingadding will give you extra informationdetail that may help you or the FileWave supportSupport teamcan resolveuse aduring technical problem. investigation.

Step-by-step guide

In order toTo set debug logging for fwxserver.log,log, fwldap.log,log, and fwsu.log:log:

1. Linux/MacOn servera -Linux navigateor tomacOS server, use /usr/local/etc/server.lvl.
   
2. UsingOn aLinux simpleor "macOS, set the debug level with echo 99 > /usr/local/etc/server.lvl"lvl. onThe Mac / Linux, the debug log level can be set. Keep in mind that initially, theserver.lvl file "server.lvl" may be an empty file if you have not set the debug level inhas thenot past.been set before.

If youserver.lvl dodoes not see the server.lvl file at the location on your server you are able toexist, create theit file on the server inwith a text editor or with "echo 99 > /usr/local/etc/server.lvl" on macOS and Linux servers.lvl.

If you are troubleshooting issues with the FileWave server andonly need the fwxserver.log to be in debug mode, no restart is required after settingchanging the level in the server.lvl. file.For If you are troubleshooting an issue with any other process (LDAP, Software update,Update, or Booster issues), then you will need totroubleshooting, restart the relevant FileWave serverServer services /or processes.processes after changing the level.

PleaseSet remember to set the debug log levellogging back to the Standard logstandard level once you have completedafter troubleshooting theso issuedebug atlogs hand.do not keep growing unnecessarily.

The logging levels are as follows:

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

In order toTo set debug logging for the djangoDjango component (filewave_django.log)log):

1. Linux/MacOn servera -Linux navigateor macOS server, go to /usr/local/filewave/django/filewave/.
   
2. Linux/MacEdit - edit the settings_custom.py file with the command "sudo nano settings_custom.py" to open the file with the vi editor. .
   
3. Remove the "#" just# before "DEBUG = True"True.
4. Save the file file.
5. Restart apacheApache with the command "sudo fwcontrol apache restart".
6. Restart schedulerScheduler with the command "sudo fwcontrol scheduler restart".
7. Restart client_monitor with the command "sudo fwcontrol client_monitor restart".
8. Restart model_update_service with the command "sudo fwcontrol model_update_service restart".

PleaseAfter remembertroubleshooting, return Django logging to set the debug log level back to the normal by adding the hash (#)# back tobefore the "DEBUG = True"True, line.then Restartrestart the services again once you have completed troubleshooting the issue at hand.again.