Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DSM sensor with CHRONY_TRACKING_LOG entry without devicename can't be edited #11

Open
janineA opened this issue Dec 23, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@janineA
Copy link
Contributor

janineA commented Dec 23, 2021

If a DSM has a CHRONY_TRACKING_LOG sensor entry in the XML, the DSM entry can’t be edited with configedit. Throws error:

“ads_rack [dsm303]: Invalid parameter: dsm303:/var/log/chrony/tracking.log has same id=196713(dsm id=3,sensor id=105) as dsm303:/var/log/chrony/tracking.log”

To fix, add devicename=“/var/log/chrony/tracking.log” to each sensor line in section of XML.

  • Devicename is already in sensorcatalog, so XML doesn’t need it, but configedit does.
  • Adding a new CHRONY to a DSM adds it as a , but SPICULE and ASPIRE have them as a .
    Permanent fix: propagate devicename from sensorCatalog. Be careful to not overwrite devicename below in sensor.

See SPICULE and ASPIRE for examples of this.

@janineA janineA added the bug Something isn't working label Dec 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant