Sensor troubleshooting

When a sensor isn't working, the first place to go is the Manage sensor page and check the status of the sensor (in the sidebar menu, click Discovery > Manage Discovery. On the Scan page, click Manage sensor).

• Has the sensor been activated? (see Activate a sensor)
• Has the sensor been started? (see Activate a sensor)
• Has the sensor been shut down?
• Have you tried restarting the sensor? (Restart a sensor)
• Any error messages on sensor start up?

If everything checks out on the Manage sensor page, check for network issues.

• Can the sensor access the internet?
• Are the cloud URLs reachable from the sensor? (Sensor diagnostic tool)
• Is a proxy server required? (Configure a sensor to use a proxy server for communications)
• Have you checked the sensor log?

Each sensor has a diagnostic tool to check for connectivity to the URLs configure in the license properties file.

Go to the installation directory and run ./diag.sh to check connectivity to the URLs configured in the license.properties file. Make sure you have root or admin permissions to the server where the sensor is installed.

Go to the installation directory and run diag.bat to check connectivity to the URLs configured in the license.properties file. Make sure you have admin permissions to the server where the sensor is installed.

If you still haven't pinpointed the problem, check the sensor log. You'll also want a copy of the sensor log to share with DigiCert support if you end up needing their help.

The sensor logs are located in the logs directory: '<install_dir>/logs'. Note that sensor.log file is the most recent log.