Technical Library | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Network Agent issues > Network Agent is not running
Network Agent is not running
Web Security Help | Web Security Solutions | Version 7.8.x
Network Agent is required to enable full management of protocols other than HTTP, HTTPS, and FTP. With some integrations, Network Agent is also used to provide more accurate logging.
For standalone installations, Network Agent must be running to monitor and manage network traffic.
To troubleshoot this problem:
1.
Look for low memory problems on the Network Agent machine that may be preventing the service or daemon from starting.
2.
Check the status of the Network Agent service or daemon:
*
Windows: Use the Windows Services tool to see if the Websense Network Agent service has started.
*
Linux: Use the /opt/Websense/WebsenseDaemonControl command to check the status of Network Agent.
*
Appliance: Use the Appliance Manager to check the status of the Network Agent module.
3.
Make sure all administrators are logged off of the TRITON console, then restart the Websense Policy Broker and Websense Policy Server services (see Stopping and starting Websense services).
4.
Start or restart the Websense Network Agent service.
5.
Wait 1 minute, and then log on to the TRITON console again.
If that does not fix the problem:
*
Check the Windows Event Viewer for error messages from Network Agent (see The Windows Event Viewer).
*
Check the Websense.log file for error messages from Network Agent (see The Websense log file).

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Network Agent issues > Network Agent is not running
Copyright 2016 Forcepoint LLC. All rights reserved.