Troubleshooting

9.1 Troubleshooting Tips

Upon startup, a DGE component connects to the provisioning database located on the provisioning server and downloads all tests that are configured for that DGE. The DGE components continue to maintain a connection to the database at all times. As new devices and tests are added or existing devices and tests are updated or removed, the provisioning server notifies the appropriate DGE (the one responsible for performing the monitoring tasks for the particular device) in real-time of the changes. If this communication link is broken, the DGE will repeatedly attempt to restore the connection. Until the connection is restored, it will continue to carry on monitoring with information available in memory. Once the connection to the provisioning database is restored, the DGE will shutdown. A cron job will restart the DGE shortly after that. The reason for this being while the DGE was not able to communicate with the provisioning server, it may have missed notices about changes to device/test configurations. So by restarting the process, the DGE downloads a fresh copy of the list of tests and proceeds with normal operation.

Several log files can be useful in troubleshooting. All log files are located under NETVIGIL_HOME/logs directory.

Log File	Use By
stderr.log	All startup scripts, monitors
netvigil.error	Any warning, error or critical level messages generated by any component is logged in this file.
monitor.info	Information on monitors are logged to this file as tests are performed, actions triggered, etc.
webapp.info	All user tasks, both in the web application and BVE socket server are logged to this file. Tasks include create, delete, update, suspend and resume tasks performed on devices, Departments, users, etc.
tomcat.log	Any errors generated inside jsp pages in the web application component is logged in this file.
poet.log	Provisioning database specific errors