After upgrade to UCS 5.0-2 I'm getting an alert every night via email saying: Checking NTP time failed: NTP CRITICAL: Offset unknown

UCS - Univention Corporate Server
,
1

Hi all,

since I have upgraded my system from UCS 4.4-9 to 5.0-2 I’m getting an email every night with the following alert:

Cron <root@SERVERNAME> run-parts /usr/share/univention-monitoring-client/scripts/
Checking NTP time failed: NTP CRITICAL: Offset unknown

What I have found out so far is that this script seems to be the culprit for this:
/usr/share/univention-monitoring-client/scripts/check_univention_ntp

The above script is then executing this (Nagios-) plugin:
/usr/lib/nagios/plugins/check_ntp_time

I’m a bit confused … Nagios? is it really still in use with UCS version 5?

Any hint for how to further troubleshoot or fix this would be much appreciated.

Thx and best regards
Thomas

2 Likes
2

Same problem here.

I’m a bit confused … Nagios? is it really still in use with UCS version 5?

The plugins seem to be still used, just the NAGIOS server was dropped.

The script causing the error messages is /usr/share/univention-monitoring-client/scripts/check_univention_ntp

The script checks the clock offset with the ntp of the hostname (saved in UCR). Is it possible that the error just is raised if the clock is perfectly in sync!? Because if I trigger the command manually, the error is not always raised.

You can manually check the output in the konsole by calling /usr/lib/nagios/plugins/check_ntp_time -H $(ucr get hostname)

Output should be something like
NTP OK: Offset -3,933906555e-06 secs|offset=-0,000004s;60,000000;120,000000;
but sometimes it is
NTP CRITICAL: Offset unknown

1 Like