The documentation you're currently reading is for version 2.3.0. Click here to view documentation for the latest stable version.
If a particular sensor is not running or appears to not be working (e.g. triggers are not emitted) usually the best course of action is to follow the steps described below.
1. Verify sensor is registered¶
The first step is verifying that sensor is registered in the database. You can do that by inspecting the output of the command below and making sure your sensor is present:
st2 sensor list
If your sensor is not listed, this means it’s not registered. You can
register it by running the
st2-register-content --register-sensors --register-fail-on-failure -v
This will register sensors for all the packs which are available on the file
system. As you can see, we also use
This will cause the register script to exit with non-zero and print a failure in case registration of a particular sensor fails (e.g. typo in sensor metadata file, invalid YAML, etc).
2. Verify virtual environment for pack to which sensor belongs exists¶
When you have confirmed that the sensor has been registered, you need to confirm that a virtual environment for the pack to which the sensor belongs exists.
You can confirm that by confirming the existence of
/opt/stackstorm/virtualenvs/<pack name> directory. If the directory and
virtual environment doesn’t exist, you can create it using this command:
st2 run packs.setup_virtualenv packs=<pack name>
3. Checking st2sensorcontainer service logs¶
If after checking that the sensor is registered and virtual environment exists, sensor still doesn’t appear to be running or working, you should run sensor container service in the foreground in debug and single sensor mode. In this mode sensor container will only run the sensor you specified and all the log messages with level DEBUG and higher will be printed directly to the console.
st2sensorcontainer --config-file=/etc/st2/st2.conf --debug --sensor-ref=pack.SensorClassName
The log output will usually give you a clue as to what is going on. Common issues include typos and syntax errors in the sensor class code, uncaught exceptions being thrown that causes the sensor to exit, etc.