how to deal with VRM System Time Offset Exceeds 1 Minute alarm on FusionCompute V1R5C00 version

The system checks its time every minute. This alarm is generated when the system detects that the time offset exceeds 1 minute
Handle the alarm.

On FusionCompute, choose Monitoring > Alarm. On the Alarm page, click the alarm object name.
The Service and Management Node page is displayed.

On the Service and Management Node page, view the management node information and obtain the management IP address of the alarm object viewed in Step 1.
Click System Configuration on the System Management page, select Time Management, and obtain the IP address of the NTP server.
Use PuTTY to log in to the node for which the alarm is generated.
Ensure that the management IP address and username gandalf are used to establish the connection.

Run the following command and enter the password of user root to switch to user root:

su - root


Check whether the NTP server is configured.

If yes, go to Step 7.
If no, go to Step 11.

Have the administrator check whether the NTP server is available. If available, obtain the NTP server IP address of the NTP server and run the following command to check whether the heartbeat communication between the node and the upper-layer NTP server is normal:
ntpq -p NTP server IP address or domain name

Determine the NTP server status according to the command output and check whether Request timed out or ntpq: read: Connection refused is contained in the command output.

If yes, the heartbeat communication of the server is abnormal. Go to Step 8.

If no, the heartbeat communication of the server is normal. Go to Step 9.


Have the administrator check whether the node can properly communicate with the NTP server and whether the NTP server runs properly. After the heartbeat communication between the node and the NTP server is restored, go to Step 9.
Run the sh /usr/sbin/ntpdate NTP server IP address or domain name&& /sbin/hwclock -w -u command to synchronize time.
Check whether sntp: not enough valid responses received in time is contained in the command output.


If yes, go to Step 14.
If no, go to Step 11.

Run the following command to restart all processes on the node:

sh /opt/galax/gms/common/config/restartPorcess.sh

NOTE:
The restart of all processes takes about 3 minutes. During the restart, you cannot log in to the FusionStack portal.


Check whether the following information is displayed:

restart all process success.

If yes, go to Step 13.
If no, go to Step 14.

After 3 minutes, log in to the FusionCompute again, locate the row that contains the alarm to be cleared, click Manually clear, and clear this alarm. Check whether the alarm is cleared.

If yes, no further action is required.
If no, go to Step 14.

Contact technical support.
Handle the alarm impact.

The alarm generation and processing involve time adjustment. If the time is adjusted to the past time, some alarms cannot be cleared automatically. For example, if the time is adjusted from T1 09:00 a.m. to T2 08:00 a.m., some alarms generated from T0 08:00 a.m. (original 08:00 a.m.) to T1 cannot be cleared automatically. These alarms need to be cleared manually. After the time reaches T3 09:00 a.m., check whether the alarms generated from T2 to T3 on the Monitoring page are automatically cleared based on the online help information. If not, choose Monitoring > Alarms to manually clear the alarms.

Scroll to top