Issue/Introduction

This article describes how to troubleshoot chrony.conf configuration that is reset after it is changed on a host. It applies to the initial diagnosis and resolution of similar issues in ZStack Cloud.

Environment

• Product: ZCF
• Component: Cloud
• Version: 3.x-5.5.30

Possible causes

Reconnecting the host causes the management node to update the chrony.conf configuration file.

Resolution

1. Sign in to the host and run the following commands to stop the management node service:

  # Check whether dual management node services are configured
  [root@localhost ~]# zsha2 status
  # Stop the management service
  [root@localhost ~]# zsha2 stop-node

2. Run the following commands in sequence to modify the dual management node configuration file and set chrony.serverIp.0 = IP:

  # Back up the configuration file
  [root@localhost ~]# cp -a /usr/local/zstack/apache-tomcat/webapps/zstack/WEB-INF/classes/zstack.properties /root/zstack.properties.bak
  # Edit the configuration file
  [root@localhost ~]# vim /usr/local/zstack/apache-tomcat/webapps/zstack/WEB-INF/classes/zstack.properties

3. Run the following command to start the dual management node service:

  [root@localhost ~]# zsha2 start-node

4. Click Resource Center > Hardware Facilities > Compute Facilities > Hosts to open the Hosts page. Select the host, and click Actions > Reconnect.