Directory Agent is not running

Web Security Help | Web Security Solutions | Version 7.8.x

In Websense Web Security Gateway Anywhere deployments, Websense Directory Agent gathers user information from your directory service and sends it to the hybrid service for use in applying policies.

When Directory Agent is not available, the hybrid service's user data may become outdated.

Make sure that Directory Agent is installed (software) or enabled (appliance), and that the service or daemon is running.

Appliance: Go to the Status > General page in Appliance Manager and verify that Websense Directory Agent appears as a running service.

If Directory Agent is listed as a disabled service (in pale gray), go to the Administration > Toolbox > Command Line Utility page and select directory-agent-service, then enable.

If Directory Agent is enabled but not running, restart the Websense Web Security module.

Windows: Use the Windows Services tool to start the service or verify that it is running.

Linux: Use the /opt/Websense/WebsenseDaemonControl command to start the daemon or verify that it is running.

If Directory Agent is running, but the alert message continues to appear, verify that:

The Directory Agent machine can communicate with the Policy Server machine (ports 40000 and 55806).

The Directory Agent machine can communicate with the Sync Service machine (port 55832).

The firewall permits communication on the Directory Agent port (55900).

If the service starts, but does not continue to run:

Check the Administration > Logs page (Appliance), Event Viewer (Windows), or websense.log file (Linux) for errors.

For software installations, navigate to the Websense bin directory (C:\Program Files or Program Files (x86)\Websense\Web Security\bin or /opt/Websense/bin/, by default) and verify that the das.ini file exists, and that it has not been corrupted or truncated.

Make sure that there is enough disk space on the Directory Agent machine to store a full snapshot of your directory. For example, a snapshot of a 200,000 user directory requires about 100 MB of disk space.

Make sure that there is enough available memory for Directory Agent to compare its current snapshot with the previous one. For example, comparing snapshots of a 200,000 user directory requires about 100 MB of memory.