Hardware Clock having wrong time on cluster node
This document (7011375) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 11 Service Pack 1
SUSE Linux Enterprise High Availability Extension 11 Service Pack 2
Situation
The server has been fenced and not shutdown in a normal way.
Resolution
## Type: boolean
## Default: "no"
#
# Force time synchronization befor start ntpd
#
NTPD_FORCE_SYNC_ON_STARTUP="no"
## Type: boolean
## Default: "no"
#
# Force time synchronization of hwclock befor start ntpd
# This works only if NTPD_FORCE_SYNC_ON_STARTUP is set
# to yes.
#
NTPD_FORCE_SYNC_HWCLOCK_ON_STARTUP="no"
By default these are set to "no". When set to "yes", the time will be set to the hardware clock when ntpd starts.
Cause
In addition, the hardware clock will only be updated when the difference between hardware time and Kernel is 15 minutes or less. In case of daylight saving time switch the difference is bigger and due to that the hardware clock will not be updated by the kernel itself.
Additional Information
SYSTOHC="yes"
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7011375
- Creation Date: 15-Nov-2012
- Modified Date:16-Mar-2021
-
- SUSE Linux Enterprise High Availability Extension
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com