Openshift Event Code: 1038NODE0009

Sommaire: Clock not synchronising.

Cet article s’applique à Cet article ne s’applique pas à Cet article n’est lié à aucun produit spécifique. Toutes les versions de produits ne sont pas identifiées dans cet article.
Consulter d’autres ressources

Symptômes

This alert is critical. It indicates an issue that can lead to the API Server Operator becoming degraded or unavailable. If the API Server Operator becomes degraded or unavailable, this issue can negatively affect other Operators, such as the Cluster Monitoring Operator.

Cause

The NodeClockNotSynchronising alert triggers when a node is affected by issues with the NTP server for that node. For example, this alert might trigger when certificates are rotated for the API Server on a node, and the certificates fail validation because of an invalid time.

Résolution

Diagnosis

To diagnose the underlying issue, start a debug pod on the affected node and check the chronyd service:

oc -n default debug node/<affected_node_name>
systemctl status chronyd

Mitigation

  1. If the chronyd service is failing or stopped, start it:

    systemctl start chonyd

    If the chronyd service is ready, restart it

    systemctl restart chronyd

    If chronyd starts or restarts successfuly, the service adjusts the clock and displays something similar to the following example output:

    Oct 18 19:39:36 ip-100-67-47-86 chronyd[2055318]: System clock wrong by 16422.107473 seconds, adjustment started
Oct 19 00:13:18 ip-100-67-47-86 chronyd[2055318]: System clock was stepped by 16422.107473 seconds
    		 
     

  2. Verify that the chronyd service is running:

    systemctl status chronyd
    		 
     

  3. Verify using PromQL:

    min_over_time(node_timex_sync_status[5m])
node_timex_maxerror_seconds

    node_timex_sync_status returns 1 if NTP is working properly,or 0 if NTP is not working properly. node_timex_maxerror_seconds indicates how many seconds NTP is falling behind.

    The alert triggers when the value for min_over_time(node_timex_sync_status[5m]) equals 0 and the value for node_timex_maxerror_seconds is greater than or equal to 16.

Support

If all the above steps cannot resolve the issue, contact the Dell EMC technical support for further investigation.

Produits touchés

APEX Cloud Platform for Red Hat OpenShift
Propriétés de l’article
Numéro d’article: 000217425
Type d’article: Solution
Dernière modification: 18 sept. 2026
Version:  4
Obtenez des réponses à vos questions auprès d’autre utilisateurs de Dell
Services de soutien
Vérifiez si votre appareil est couvert par les services de soutien.