--- title: "Upgrade to AppGate SDP v6.0.1 Fails and Rolls Back to Previous Version When Upgrading from v5.0.2, v5.0.1 or v5.0.0" slug: "warning-ntpd-is-not-running-or-system-clock-synchronized-no-is-showing-in-the-appgate-dashboard" description: "Ensure accurate time synchronization for AppGate operation to avoid connection issues. Learn how to resolve NTP errors and maintain system health." updated: 2025-11-23T14:32:19Z published: 2025-11-23T14:32:19Z canonical: "support.appgate.com/warning-ntpd-is-not-running-or-system-clock-synchronized-no-is-showing-in-the-appgate-dashboard" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Upgrade to AppGate SDP v6.0.1 Fails and Rolls Back to Previous Version When Upgrading from v5.0.2, v5.0.1 or v5.0.0 Accurate time synchronization is an extremely important requirement of successful AppGate operation. Inaccurate time can cause issues with Clients connecting to AppGate servers or AppGate servers connecting to other servers in the collective. AppGate appliances rely on an NTP Server for accurate time synchronization. If there is an issue with the NTP services setting accurate time across appliances, appliances can go into a warning or unhealthy state and errors can be seen including: "Warning: ntpd is not running" "System clock synchronized: no" ## **Observed Behaviors and Errors** ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/warning-ntpd-is-not-running-or-system-clock-synchronized-no-is-showing-in-the-appgate-dashboard-image-g15i9d6b.png?sv=2026-02-06&spr=https&st=2026-10-27T06%3A05%3A39Z&se=2026-10-27T07%3A05%3A39Z&sr=c&sp=r&sig=oI%2B%2BW1ynNED8wbZ4zDa3zvr2MWhd0NS6N8d8ZVMPXVM%3D)![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/warning-ntpd-is-not-running-or-system-clock-synchronized-no-is-showing-in-the-appgate-dashboard-image-0wp2op9i.png?sv=2026-02-06&spr=https&st=2026-10-27T06%3A05%3A39Z&se=2026-10-27T07%3A05%3A39Z&sr=c&sp=r&sig=oI%2B%2BW1ynNED8wbZ4zDa3zvr2MWhd0NS6N8d8ZVMPXVM%3D)If you find these errors on the AppGate dashboard it is likely due to an inability to reach NTP servers and the NTP Client daemon has stopped. ## **Resolution / Suggested Actions** Navigate to System -> Appliances. Select the Appliance with the warning, review the NTP Server settings... ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/warning-ntpd-is-not-running-or-system-clock-synchronized-no-is-showing-in-the-appgate-dashboard-image-22e6xu26.png?sv=2026-02-06&spr=https&st=2026-10-27T06%3A05%3A39Z&se=2026-10-27T07%3A05%3A39Z&sr=c&sp=r&sig=oI%2B%2BW1ynNED8wbZ4zDa3zvr2MWhd0NS6N8d8ZVMPXVM%3D)SSH into the appliance and query the NTP server shown to see if there is a response. The -q flag for the ntpdate command only queries the server, and does not make any changes. ntpdate -q If the command results with "no server suitable for synchronization found". ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/warning-ntpd-is-not-running-or-system-clock-synchronized-no-is-showing-in-the-appgate-dashboard-image-c93qj3l4.png?sv=2026-02-06&spr=https&st=2026-10-27T06%3A05%3A39Z&se=2026-10-27T07%3A05%3A39Z&sr=c&sp=r&sig=oI%2B%2BW1ynNED8wbZ4zDa3zvr2MWhd0NS6N8d8ZVMPXVM%3D)Determine what could be causing the connection issue. This could be caused by... - NTP port blockage by the firewall or security group - Inability to resolve the hostname - Routing issues - Invalid NTP server Once you have determined the connection issue, execute the same command again and you should get results from the server(s) showing the offset and delay of the system date compared to the NTP server. ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/warning-ntpd-is-not-running-or-system-clock-synchronized-no-is-showing-in-the-appgate-dashboard-image-luqwya3p.png?sv=2026-02-06&spr=https&st=2026-10-27T06%3A05%3A39Z&se=2026-10-27T07%3A05%3A39Z&sr=c&sp=r&sig=oI%2B%2BW1ynNED8wbZ4zDa3zvr2MWhd0NS6N8d8ZVMPXVM%3D)If the NTP server hostnames should be changed this should be done in the AppGate Admin UI under the System->Appliance settings. This may take a while for the NTP client to retry the new server; To force the NTP client to refresh, run these commands: sudo systemctl stop ntp sudo ntpdate sudo systemctl start ntp