3PAR Users Group

A Storage Administrator Community




Post new topic Reply to topic  [ 5 posts ] 
Author Message
 Post subject: Could not check node:unable to convert date-time string
PostPosted: Wed Apr 12, 2017 2:08 am 

Joined: Wed Apr 12, 2017 1:41 am
Posts: 1
Good day for all!

Few days ago its appear some weird (for me) record in 3Par system when client started checkhealth comand:
3pf400-02 cli% checkhealth -svc -detail
Checking alert
Checking cabling
Checking cage
Checking date
Checking file
Checking ld
Checking license
Checking network
Checking node
Could not check node: unable to convert date-time string "2016-11-29 18:17:41 YEKT"
Checking pd
Checking pdch
Checking port
Checking rc
Checking snmp
Checking task
Checking vlun
Checking vv
Checking sp
Component ----------Description----------- Qty
License Licenses which have expired 1
pdch Chunklets on remote disks 1
vlun Hosts not connected to a port 57
vlun Paths not reported by host agent 108
....
....
Honestly i don't have any skills in 3par systems.
Garanty contract for this storage unit already has expired and it is because i can't ask HPE.
If you know what does it means this record (about unable to convert date-time string) please give some reply for me.

Thanks


Top
 Profile  
Reply with quote  
 Post subject: Re: Could not check node:unable to convert date-time string
PostPosted: Fri Jul 26, 2019 6:27 am 

Joined: Fri Jul 26, 2019 6:23 am
Posts: 2
Hi All,

I have a similar problem with: Release version 3.3.1.410 (MU2):
Any suggestion?

cli% checkhealth -svc
Checking alert
Checking ao
Checking cabling
Checking cage
Checking cert
Checking dar
Checking date
Could not check date: input string does not match supplied format
Checking file
Checking fs
Checking host
Checking ld
Checking license
Checking network
Checking node
Checking pd
Checking pdch
Checking port
Checking qos
Checking rc
Checking snmp
Checking task
Checking vlun
Checking vv
Checking sp
Component -Summary Description- Qty
Component Could not check date 1
-----------------------------------
1 total 1
cli%


Top
 Profile  
Reply with quote  
 Post subject: Re: Could not check node:unable to convert date-time string
PostPosted: Fri Jul 26, 2019 7:39 am 

Joined: Mon Sep 21, 2015 2:11 pm
Posts: 931
Location: Europe
what does "showdate" say?

_________________
The views and opinions expressed are my own and do not necessarily reflect those of my current or previous employers.


Top
 Profile  
Reply with quote  
 Post subject: Re: Could not check node:unable to convert date-time string
PostPosted: Fri Jul 26, 2019 8:22 am 

Joined: Fri Jul 26, 2019 6:23 am
Posts: 2
Hi,

It says the correct date time:

cli% showdate
Node Date
0 2019-07-26 15:21:16 CEST (Europe/Budapest)
1 2019-07-26 15:21:16 CEST (Europe/Budapest)
cli%


Top
 Profile  
Reply with quote  
 Post subject: Re: Could not check node:unable to convert date-time string
PostPosted: Sat Jul 27, 2019 6:32 am 

Joined: Fri Jan 20, 2017 9:39 am
Posts: 58
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.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 


Who is online

Users browsing this forum: Google [Bot] and 25 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group | DVGFX2 by: Matt