I have 2 questions related to the same issue.
We have an hyperscale with 3 nodes. When we look at the mountpath we have 3 shares of which 2 are online and the 3th offline. If you validate this share it comes with the following message:
Failed to check cloud server status, error = [[Cloud] The request time is too skewed. Message: The difference between the request time and the server's time is too large. Resource: /*******?delimiter=%2F&prefix=*******%2F Extra Details: RequestId 1643106149072049 ]
When I gave the command timedatectl we found out that the node was a litte bit over15minutes behind and the other 13min behind. I think 15min is reason to take the share offline for that node.
My questions are:
- Can/may I set the time with the command “date --set”<correct time>”
Does this come with a risk? Do I need to stop the CV services first for example?
- Are Hyperscale nodes not default configured with a NTP server, same as Commserve for example?
All my Linux knowledge is from Google, so please treat me like a dummy in this case
Best answer by HenkRView original