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).
If everything checks out on the Manage sensor page, check for network issues.
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.
DigiCert is the world’s premier provider of high—assurance digital certificates—providing trusted SSL, private and managed PKI deployments, and device certificates for the emerging IoT market. Since our founding almost fifteen years ago, we’ve been driven by the idea of finding a better way. A better way to provide authentication on the internet. A better way to tailor solutions to our customer’s needs. Now, we’ve added Symantec’s experience and talent to our legacy of innovation to find a better way to lead the industry forward, and build greater trust in identity and digital interactions.
©2019 DigiCert, Inc. All rights reserved. DigiCert and its logo are registered trademarks of DigiCert, Inc. Symantec and Norton and their logos are trademarks used under license from Symantec Corporation. Other names may be trademarks of their respective owners.