Using SafeLinx Server logs

The SafeLinx Server stores troubleshooting information in message, account, and trace logs.

SafeLinx Server logs are stored in files or, in the case of accounting and billing information, a relational database or a file. All SafeLinx Server logs stored in files are viewed by using the SafeLinx Administrator. Each log is viewable separately. An administrator can view logs only if the administrator ID has an additional access enabled by an ACL profile. The ACL profile needs at least Read-only access to the SafeLinx Server.

The log files and their default file names are:

The trace log contains a trace of all packet data for SafeLinx Clients that have the trace turned on. The message log can be filtered to contain specific levels of logging information or specific devices or user IDs.

Maintain your message, account, and trace logs regularly. Your business needs dictate whether you keep historical records in addition to how often you start new records. For database records, this process means archiving and purging records. To purge accounting and billing records, use the -p parameter with the wg_acct command. For more information, see Account log After purging records, you can reclaim disk space.

For log files, reset (rename the old files and begin new ones) them regularly using SafeLinx Administrator:

Alternatively, you can use the SafeLinx Server command line to reset all log files. Enter chwg -r acct | trace | log | all

If message, account, or trace information is not stored in a file, as expected, there might not be sufficient storage available in the file system.

Check the /var file system. If it is full, make space available to allow the SafeLinx Server to write to the log file.

If necessary, compress or back up the old files before deleting them. If active processes open the files, terminate the processes to release the files. For example, if you are using the tail command to display the log file, terminate the tail process before you work with the file.