You can identify the reasons for issues with file system usage and take measures to prevent these issues.
Identify issues with file system usage
To identify issues with file system usage, you can search the /opt partition for large directories.
- Log on to the appliance that you want to identify issues on from a local system console, or remotely using SSH.
- Run the following commands:
du /opt -Dm | sort -n|tail
A search is started for the largest folders in the /opt partition. The results are output in ascending order of size, for example, as follows.
1158 /opt/mwg/plugin/data 1320 /opt/mwg/plugin 5010 /opt/mwg/storage/default 6011 /opt/mwg/storage 7937 /opt/mwg/log/debug/cores
- If you cannot determine the source of an issue, create a listing for support, using the following commands:
du /opt -Dm | sort -n > opt_directory_listing.txt
The command outputs a .txt file with a listing of the directories in the /opt partition.
Preventing excessive utilization of the /opt partition
You can prevent excessive utilization of the /opt partition by taking appropriate measures regarding the files that are stored in this partition.
The following file types often cause the /opt partition to run out of space due to their sizes.
User-defined logs are, for example, the access.log and access_denied.log. You can find these logs under /opt/mwg/log in the user-defined logs directory and its subdirectories.
To prevent utilization issues due to log files, set up appropriate rotation, deletion, and push schedules, using the File System Logging settings.
Make sure that you also compress the log files after rotation using the GZIP log files after rotation setting.
Trace files are, for example, created for connection or rule engine tracing. You can find these files under /opt/mwg/log/ in the debug directory and its subdirectories.
This directory also contains trace files for authentication, quota, PD storage, the log manager, and the Coordinator subsystem of the Web Gateway appliance.
To prevent utilization issues due to trace files, create them only just before your testing or troubleshooting activities and stop tracing immediately after completing these activities. Many tracing options also allow you to restrict the tracing to individual IP addresses.
NOTE: Connection tracing files are by default removed when the appliance is restarted. Do not wait for a restart and manually remove these files as soon as possible.
Temporary files are found under /opt/mwg/ in the temp directory.
Web Gateway usually creates temporary mwg-core files in the temp directory while downloading and scanning files. These files are managed by the mwg-core process and are removed after the download and scanning has completed.
NOTE: Streaming Media files that are scanned for anti-malware filtering can cause very large temp files, as streams have no known end. Let these files bypass scanning.
Support might request you to provide additional troubleshooting files for reviewing. For example, files that you find under /opt/mwg/log in the debug directory. These files include tcpdump, feedback, and core files, as well as some others.
After support has confirmed the receipt of these files, you can remove them from the /opt partition.
Tags recommended by the template: article:topic