Collecting an extended.log, error.log or messages output from the Content Gateway
- Article Number: 000008652
- Products: Forcepoint V10000 Appliance, Forcepoint V20000 Appliance, Forcepoint V5000 Appliance, Forcepoint Virtual Appliance, Forcepoint Web Security, TRITON AP-WEB, Web Security Gateway, Web Security and Web Filter
- Version: 8.5, 8.4, 8.3, 8.2, 8.1, 8.0, 7.8, 7.7
- Last Published Date: June 16, 2020
When troubleshooting issues in relation to the Websense Content Gateway, Technical Support may request specific log files such as extended.log, messages and error.log.
The log files are listed directly in the Content Gateway Manager GUI and can be downloaded onto the computer where the GUI is open for collection.
Log File Locations:
Note Regarding Older logs:
By default, extended.log and error.log files will rollover every 6 hours. If the issue is intermittent, you are unable to replicate it and transaction & error logging was enabled during the time of the incident, you can download older logs by looking for the date/time on the filename. For example:
We recommend attaching the log files to the case, or emailing them as a reply to a case notification. If the log file is especially large, you may want to create a ZIP folder with the case number and contact Technical Support for a Kiteworks (XFR) link for encrypted transfer.
Keywords: troubleshooting; file collection; must gather; support; administration; logs; extended.log; error.log; messages; transaction logs; wcg; content gateway; proxy