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
As such, journalctl is being spammed by owstats even though the system clocks remain in sync (thanks to chronyd) when pscheduler-runner.service service is (re)started:
[root@host ~]# owstats
owstats: NTP: STA_NANO should be set. Make sure ntpd is running, and your NTP configuration is good.
[root@host ~]# timedatectl
Local time: Thu 2024-08-01 02:01:39 UTC
Universal time: Thu 2024-08-01 02:01:39 UTC
RTC time: Thu 2024-08-01 02:01:39
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
[root@host ~]# systemctl status chronyd
● chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; preset: enabled)
Active: active (running) since Thu 2024-07-11 21:14:22 UTC; 2 weeks 6 days ago
Docs: man:chronyd(8)
man:chrony.conf(5)
Main PID: 936 (chronyd)
Tasks: 1 (limit: 52428)
Memory: 1.4M
CPU: 1min 395ms
CGroup: /system.slice/chronyd.service
└─936 /usr/sbin/chronyd -F 2
If possible, could you please review adding chronyd support? .. or potentially update the spec files to enforce ntpsec package dependencies if you decide against adding chronyd support?
Thanks!
The text was updated successfully, but these errors were encountered:
With more users migrating away from EL7 over to EL8 or EL9, a lot of users will have the choice to use chronyd or ntpd (via ntpsec package).
While the perfSONAR 5.1.0 docs mentions that we can configure chronyd by hand, the pitfall is that there's no mention of 'owstats' tool having a dependency on ntpd as it simply does not support chronyd. See: https://github.com/perfsonar/owamp/blob/master/owamp/owamp/owamp/time.c#L114-L139
In addition, the rpm spec file doesn't have dependencies https://github.com/perfsonar/owamp/blob/master/owamp/owamp/unibuild-packaging/rpm/owamp.spec (it may be ideal to add package ntpsec deps here?)
As such, journalctl is being spammed by owstats even though the system clocks remain in sync (thanks to chronyd) when
pscheduler-runner.service
service is (re)started:If possible, could you please review adding chronyd support? .. or potentially update the spec files to enforce ntpsec package dependencies if you decide against adding chronyd support?
Thanks!
The text was updated successfully, but these errors were encountered: