# Beta - Manager servers - Monitors - Gone since

**URL:** <https://community.ntppool.org/t/beta-manager-servers-monitors-gone-since/2466>\
**Category:** Uncategorized\
**Tags:** beta\
**Created:** [June 27, 2022, 4:19pm UTC](https://community.ntppool.org/t/beta-manager-servers-monitors-gone-since/2466 "2022-06-27T16:19:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![twekkel](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@twekkel](https://community.ntppool.org/u/twekkel)\
**Post date:** [June 27, 2022, 4:19pm UTC](https://community.ntppool.org/t/beta-manager-servers-monitors-gone-since/2466/1 "2022-06-27T16:19:56Z")

</div>

syslog shows no errors

```auto
# systemctl status ntppool-monitor
● ntppool-monitor.service - NTP Pool Monitor ()
     Loaded: loaded (/etc/systemd/system/ntppool-monitor.service; disabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-06-27 18:09:43 CEST; 10min ago
   Main PID: 220704 (ntppool-monitor)
      Tasks: 6 (limit: 973)
     CGroup: /system.slice/ntppool-monitor.service
             └─220704 /usr/bin/ntppool-monitor --config /etc/ntpmon/nlams1-hm79d5.test.mon.ntppool.dev.json monitor

Jun 27 18:19:23 pia ntppool-monitor[220704]: 2022/06/27 18:19:23 Failure for "ntp.ripe.net" "2001:67c:2e8:14:ffff::229": offset too large: -9.382>
Jun 27 18:19:23 pia ntppool-monitor[220704]: 2022/06/27 18:19:23 Failure for "ntp.stupi.se" "2001:440:1880:1000::20": offset too large: -10.80754>
Jun 27 18:19:24 pia ntppool-monitor[220704]: 2022/06/27 18:19:24 Failure for "uslax1-ntp-001.aaplimg.com" "2620:149:a1a:3000::1f2": offset too la>
Jun 27 18:19:24 pia ntppool-monitor[220704]: 2022/06/27 18:19:24 Failure for "jptyo5-ntp-001.aaplimg.com" "2403:300:a0c:3000::1f2": offset too la>
Jun 27 18:19:24 pia ntppool-monitor[220704]: 2022/06/27 18:19:24 Failure for "ntp.nict.jp" "2001:ce8:78::2": offset too large: -30.581347ms
Jun 27 18:19:26 pia ntppool-monitor[220704]: 2022/06/27 18:19:26 Failure for "defra1-ntp-002.aaplimg.com" "2a01:b740:a04:4000::1f2": offset too l>
Jun 27 18:19:27 pia ntppool-monitor[220704]: 2022/06/27 18:19:27 Failure for "time.nist.gov" "2610:20:6f97:97::4": offset too large: -10.794598ms
Jun 27 18:19:35 pia ntppool-monitor[220704]: 2022/06/27 18:19:35 Failure for "ntp1.net.berkeley.edu" "2607:f140:ffff:8000:0:8006:0:a": read udp [>
Jun 27 18:19:35 pia ntppool-monitor[220704]: 2022/06/27 18:19:35 failures: 8, threshold: 4, hosts: 9
Jun 27 18:19:35 pia ntppool-monitor[220704]: 2022/06/27 18:19:35 Local clock might not be okay, waiting 2m0s

```

ntppool-monitor process is still running

restarting the services → ‘active’ temporary and becomes ‘Last seen’ very soon

any ideas?

---

<div class="post-metadata">

**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\
**Post date:** [June 28, 2022, 1:26pm UTC](https://community.ntppool.org/t/beta-manager-servers-monitors-gone-since/2466/2 "2022-06-28T13:26:02Z")

</div>

Have you ever updated the monitor via apt?

Look in the monitor-page, does it state this: Agent version: v3.0.2-69

If it’s older, you might want to upgrade it.

---

<div class="post-metadata">

**Author:** ![twekkel](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@twekkel](https://community.ntppool.org/u/twekkel)\
**Post date:** [June 28, 2022, 4:56pm UTC](https://community.ntppool.org/t/beta-manager-servers-monitors-gone-since/2466/3 "2022-06-28T16:56:53Z")

</div>

Yep latest version and I even used a fresh pair of API keys, but I’m “gone” again.

Everything seems so work well, but it is odd.

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [June 29, 2022, 4:16am UTC](https://community.ntppool.org/t/beta-manager-servers-monitors-gone-since/2466/4 "2022-06-29T04:16:21Z")

</div>

What’s the status of the ntpd peers or chrony sources? When the monitor runs it tries some “well known” servers and if too many of those have a too large offset the monitor basically waits and doesn’t do any work until it’s better. From the log you posted it looks like that might be happening.

---

<div class="post-metadata">

**Author:** ![twekkel](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@twekkel](https://community.ntppool.org/u/twekkel)\
**Post date:** [June 29, 2022, 2:43pm UTC](https://community.ntppool.org/t/beta-manager-servers-monitors-gone-since/2466/5 "2022-06-29T14:43:18Z")

</div>

ntp peer… like none.

Chrony is my server, but using htpdate as the ‘ntp client’. Accuracy will be around 10 to 15ms… that explains the ‘gone’. Should I retract from this beta?