Issue

Use this article to troubleshoot database startup failures caused by missing NTP configuration on a ZSphere single management node.

Symptoms

• The management interface cannot be accessed, and zstack-ctl status shows that MN is stopped.
• Restarting the service reports Can't connect to MySQL server.
• The system time is abnormal or NTP is not configured.

Environment

• Product: ZVF
• Version: 4.10.17.8
• Component: ZSphere
• Affected object: management node
• Scenario: Management plane and upgrade issues. Confirm the current version, deployment topology, storage type, and operation timeline.

Possible causes

• Time drift on a single management node causes database service or certificate/authentication failures.
• NTP/chrony is not configured or cannot access the time source.
• A system time jump affects database startup and management-service connections.

Resolution

Perform the following checks in sequence, and record the affected objects, occurrence time, complete error messages, and current state.

1. Check the status of date, timedatectl, chronyc tracking, or ntpq.
2. Confirm that the management node can access a reliable NTP source. After correcting the time, restart the database and management services.
3. Check management-server.log and the database logs for time-related exceptions.
4. Include NTP configuration in the implementation checklist to prevent time drift in single-management-node environments.

Remediation

1. Configure the management node to use a reliable NTP time source and synchronize the time.
2. After time calibration, restart the database and management services in dependency order.

Verification

• timedatectl, chronyc tracking, or ntpq shows that time synchronization is normal.
• The database and management services start normally, and the logs no longer contain time-related exceptions.