Hi all,
I want to monitor the status of an ntp server. So I add a new item whose key is check_service[service.ntp]. The Zabbix Release Notes for v1.1beta 2 says that this item "checks availability of NTP service on agent side. It returns time returned by NTP server". I first checked telnetting to the ntp server port 10050 and ask the agentd to show the value for check_service[service.ntp]. I got something like '1131189313.000000' which should be the number of seconds from the NTP base epoch. I added this item from the web interface and when I looked at the Latest data from the Monitoring section I read that the value for the item [service.ntp] is 35y10m17d11h46m1s which is correct for the time part but is not for the date part. Is there a bug in the ntp_time -> human_readable_time? Just curious because for my purpose 0|1 is enough (0 service not available, 1 service is running).
TIA
Maurizio Firmani
I want to monitor the status of an ntp server. So I add a new item whose key is check_service[service.ntp]. The Zabbix Release Notes for v1.1beta 2 says that this item "checks availability of NTP service on agent side. It returns time returned by NTP server". I first checked telnetting to the ntp server port 10050 and ask the agentd to show the value for check_service[service.ntp]. I got something like '1131189313.000000' which should be the number of seconds from the NTP base epoch. I added this item from the web interface and when I looked at the Latest data from the Monitoring section I read that the value for the item [service.ntp] is 35y10m17d11h46m1s which is correct for the time part but is not for the date part. Is there a bug in the ntp_time -> human_readable_time? Just curious because for my purpose 0|1 is enough (0 service not available, 1 service is running).
TIA
Maurizio Firmani