You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
If a DSM has a CHRONY_TRACKING_LOG sensor entry in the XML, the DSM entry can’t be edited with configedit. Throws error:
To fix, add devicename=“/var/log/chrony/tracking.log” to each sensor line in section of XML.
Permanent fix: propagate devicename from sensorCatalog. Be careful to not overwrite devicename below in sensor.
See SPICULE and ASPIRE for examples of this.
The text was updated successfully, but these errors were encountered: