Skip to main content
The following resources describe a few common issues and the techniques available to analyze and troubleshoot these issues.
The <registry_path> should be considered as one of the existing paths on the device: /etc/sensors/registry/registry/ or /var/cache/sensors/registry/registry/.

​
The ssc_sensor_info tool is unable to list sensors

This error indicates a failure in parsing the sensor registry, rendering the sensor unavailable for listing using the ssc_sensor_info tool. Do the following to resolve this error:
Verify that the read and write permissions for the files are enabled for user mode, and read only permission is enabled for group and others modes. Ensure that the user and group mode names are system system.
  1. Ensure that /etc/sensors/sns_reg_config and /etc/sensors/config/json.lst files are present with the required permissions as shown in the following example:
  1. Ensure that /etc/sensors/config/ directory has the sensor JSON file with the required permissions, as described in the above note.
  1. Ensure that <registry_path> directory is accessible and has the corresponding parsed file, as shown below.

​
SUID lookup failures

This error indicates a custom code failure in retrieving SUID for a specified sensor. Do the following to resolve this error:
  1. Run the ssc_sensor_info tool to check if the specified sensor is available.
    • If the sensor list is empty, see the first debugging method described in The ssc_sensor_info tool is unable to list sensors.
    • If only the specified sensor is unavailable, proceed with the following checks: a. Ensure that the sensor is listed in /etc/sensors/config/json.lst file, as shown in the following example:
b. Verify that the configuration file for the specified sensor is parsed and present in the parsed_file_list.csv file, as shown in the following example:
c. Verify that the configuration file for the specified sensor is parsed and present in the <registry_path> directory as shown in the following example:
  1. If the preceding validations don’t identify any issues, then there may be an issue with your application’s custom code implementation that uses the QSH client APIs. Revisit your code implementation.

​
Sensor is listed but unable to receive sensor data

This error indicates a failure in the sample or custom code. Use the following sensor tool to receive events for a specified sensor. Run the following command to stream the specified sensor: see_workhorse [-sensor=][-sample_rate=] [-batch_period=] [-calibrated=<0 | 1>] [-wakeup=<0 | 1>] For example,
If the tool is able to receive the sensor event, there may be an issue with your application’s custom code implementation that uses the QSH client APIs. Revisit your code implementation. For more information, see Sensor testing tools.