Category: System configuration issue
Context: NTP Client
Invalid NTP configuration detected
This error is reported by the health evaluation system when the NTP client configuration is invalid.
An invalid NTP client configuration will prevent the NTP client daemon from starting, which will cause the system clock to become incorrect.
The only cause for this error is for the System Configuration File (/etc/firemon/config.yml) to contain invalid definitions for the NTP client configuration. Some examples of common problems include:
The mode property of the ntp object is set to an invalid value. Valid values are limited to none, manual, and dhcp.
The servers property of the ntp object is not a list. This property must be set to a list of one or more objects that define the NTP servers with which this machine should synchronize its clock. Even if only one NTP server is used, the property must still be defined as a list.
To resolve this issue, the System Configuration File needs to be corrected to include proper definitions for the NTP client. This can be accomplished by using the FMOS Server Control Panel web UI:
Navigate to https://servername:55555 (replacing servername with the fully-qualified domain name or IP address of the machine)
Log in using FMOS user credentials
Browse to OS → NTP
Set Configuration Mode to the desired value
If necessary (i.e. Configuration Mode is set to manual), add one or more items to the NTP Servers list, and populate the Host field for each one.
Alternatively, the System Configuration File can be edited manually using the fmos config --edit command. This command will launch an editor allowing the file to be modified. Any invalid values should be removed or corrected. After saving the changes and closing the editor, the new values will be used by the configuration policy, which must be applied using the command fmos redeploy fmos.