Ad Widget

Collapse

How to configure ntpdate.service in Zabbix 3.4

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pratheek
    Junior Member
    • Jan 2020
    • 2

    #1

    How to configure ntpdate.service in Zabbix 3.4

    I need to monitor ntpdate.service in Zabbix.

    Application is running in the server-side

    service ntpdate status
    Redirecting to /bin/systemctl status ntpdate.service
    ● ntpdate.service - Set time via NTP
    Loaded: loaded (/usr/lib/systemd/system/ntpdate.service; disabled; vendor preset: disabled)
    Active: active (exited) since Thu 2019-03-14 04:31:04 EDT; 10 months 18 days ago
    Main PID: 20326 (code=exited, status=0/SUCCESS)
    CGroup: /system.slice/ntpdate.service

    But PS output shows nothing

    [xxxxxxxx zabbix]# ps aux | grep ntpdate
    root 7933 0.0 0.0 112708 984 pts/0 S+ 00:51 0:00 grep --color=auto ntpdate

    [xxxxxxxx zabbix]# ps aux | grep ntp
    root 7960 0.0 0.0 112708 980 pts/0 S+ 00:52 0:00 grep --color=auto ntp

    [xxxxxxxx zabbix]# ps aux | grep ntpd
    root 7975 0.0 0.0 112708 984 pts/0 S+ 00:52 0:00 grep --color=auto ntpd

    [xxxxxxxx zabbix]# ps aux | grep ntpdate.service
    root 7990 0.0 0.0 112708 996 pts/0 S+ 00:52 0:00 grep --color=auto ntpdate.service


    should I use this configuration

    {xxxxxxroc.num[ntpdate].last(0)}=0

    or

    proc.num[ntpdate]





    Last edited by pratheek; 03-02-2020, 06:33.
  • Markku
    Senior Member
    Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
    • Sep 2018
    • 1781

    #2
    Hi, ntpdate is not a service that stays in the memory. It is only run once during the system startup I believe, maybe in some other situations as well. But it does not make any sense to try to monitor its process continuously.

    If you want to monitor ntpd (the daemon that continuously syncs the time), your system is apparently not having it enabled at the moment. Try to install or enable it first, and the continue with your Zabbix item configurations.

    Markku

    Comment


    • tim.mooney
      tim.mooney commented
      Editing a comment
      100% agree with Markku.

      Also, on RHEL or RHEL-derived hosts, the default for timekeeping since RHEL 7.0 is chronyd, so unless you've disabled that and enabled ntpd, you probably want to look at monitoring that instead.
  • pratheek
    Junior Member
    • Jan 2020
    • 2

    #3
    Thanks for the update , But in this cause i need to monitor only ntpdate . Previously itwork with proc.num[ntpdate].last(0)}=0 , But after server reboot ( yum update) its shows Failed to process ntpdate .

    We need not to enable ntpd in our servers.

    Comment

    • Markku
      Senior Member
      Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
      • Sep 2018
      • 1781

      #4
      Ok, so you still want to monitor the number of ntpdate processes, let's try. Can you show us your configurations related to this?

      Also, where exactly do you see the "Failed to process ntpdate" output? Is that the full output related to this?

      Markku

      Comment

      Working...