budai8 wrote:
Could not check date: input string does not match supplied format
I think this is the same error I had about a month ago and just like you a showdate was fine. In my case the hardware clock on one node was in a messed up state and I was told the solution was to reboot the node. I asked if this was a major issue or if I can run like this for a while without issue and was told I can run like that without issue. I think I was applying patches with HPE which is when I saw the checkhealth error; we still applied the patches without issue and I opened a new case for this problem.
This is what HPE support told me about the error after their initial analysis:
Code:
This error indicates that the HW clock on the nodes is not the same and we did logged into array and found that Node 3 has issues.
root@... Thu Jun 27 12:16:09:~# onallnodes "/sbin/hwclock"
Node 0:
Thu Jun 27 12:17:14 2019 -0.515942 seconds
Node 1:
Thu Jun 27 12:17:15 2019 -0.968927 seconds
Node 2:
Thu Jun 27 12:17:15 2019 -0.047120 seconds
Node 3:
hwclock: select() to /dev/rtc to wait for clock tick timed out: Success
I rebooted the node but checkhealth still reported an error:
Code:
Node 3 time and hwclock are not same
Support logged in again and ran the same command and said everything was fine (node 3 returned a date this time) but I noticed the time and date were way off which is what triggered the warning about time and hwclock not being the same. After they adjusted the date/time (when logged in as root I assume) the error went away and I've been ok since.