Documentation | Support

Go to the table of contents Go to the previous page You are at the end of the document View or print as PDF
Content Gateway Troubleshooting : Content Gateway is running but no log files are created
Content Gateway is running but no log files are created
Content Gateway Troubleshooting | Forcepoint Web Security | v8.4.x, v8.5.x | 29-Apr-2022
Content Gateway writes event log files only when there is information to record.
*
If Content Gateway is idle, there may be no log files.
*
Confirm that you are looking in the correct directory.
By default, Content Gateway creates log files in its logs directory. Check the location of the log files in the Content Gateway manager by examining the Log Directory field on the Configure > Subsystems > Logging > General tab.
*
Check that the log directory has read/write permissions for the Content Gateway user account. If the log directory does not have the correct permissions, the content_gateway process is unable to open or create log files.
*
Check that logging is enabled. In the Content Gateway manager, examine the Logging area on the Configure > Subsystems > Logging > General tab.
*
Check that a log format is enabled. In the Content Gateway manager, check that a standard format is enabled on the Configure > Subsystems > Logging > Formats tab or that the custom format is enabled on the Custom tab.
 
©2022 Forcepoint. Forcepoint and the FORCEPOINT logo are trademarks of Forcepoint. All other trademarks used in this document are the property of their respective owners.

Go to the table of contents Go to the previous page You are at the end of the document View or print as PDF
Content Gateway Troubleshooting : Content Gateway is running but no log files are created
Copyright 2022 Forcepoint. All rights reserved.