Troubleshooting the sensor
This topic describes common problems that occur with the custom template sensor and presents solutions for those problems.
The custom template sensor does not start or fails
- Problem
- There are a number of potential situations that can prevent the sensor from starting or cause it to fail.
- Solution
- Verify that the following conditions exist:
- The custom template sensor is enabled in the discovery profile.
- The custom template sensor template and scripts are located in the correct directory.
- The name of the directory that stores the template matches the name that is specified in the template.xml file.
- The format of the template.xml file is valid.
- The result-class that is specified in the template.xml file exists and, if required, the plugin-id is specified.
- The scripts (matcher-script.py and sensor-script.py) are in the correct directory and are defined correctly in the template.xml file.
- The scripts contain no syntax errors. Unhandled errors for the matcher-script.py script are recorded in the log file but no seed file is created. Unhandled errors for the sensor-script.py script are recorded in the log file and displayed in the Discovery Management Console.
- The templates directory and associated files must have the correct access rights. You require read access rights to the directory and associated files.
- The sensor that collects the data must complete its discovery with no errors.
- The syntax of the matcher and sensor scripts must comply with the version of Jython used, as defined by the engine-id tag in the template.xml.