# New Server Add issue

**URL:** <https://community.ntppool.org/t/new-server-add-issue/4380>\
**Category:** Server operators\
**Tags:** monitoring\
**Created:** [April 27, 2026, 5:56pm UTC](https://community.ntppool.org/t/new-server-add-issue/4380 "2026-04-27T17:56:55Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [April 29, 2026, 10:09am UTC](https://community.ntppool.org/t/new-server-add-issue/4380/6 "2026-04-29T10:09:45Z")

</div>

Thanks everyone. This was pretty puzzling. I don’t think even it’s a new bug. There [was a race condition](https://github.com/ntppool/monitor/commit/8614dccba9ff0b8ee8557be7e31048edb36af043) in the code where the sub-system talking to the MQTT clients (the ntppool-agents) for ad-hoc checks could lock-up.

The relevant code hasn’t changed for 3 years, so I’m not entirely sure if something in the new cluster triggered it or if it’s just a co-incidence.

---

_[View the full topic](https://community.ntppool.org/t/new-server-add-issue/4380)._