ntpd local clock not immediately usable at boot
When you encounter the message "ntpd local clock not immediately usable at boot" while using the Network Time Protocol daemon (`ntpd`), it typically means that `ntpd` is starting up but hasn't yet synchronized with a time source. This is a common message during the initial startup of the NTP service. Here's what you can do: 1. **Wait for Synchronization**: In most cases, `ntpd` will eventually synchronize with a time source. It may take a few moments or even minutes, depending on your system and network conditions. After synchronization, the local clock becomes usable. 2. **Check NTP Configuration**: Ensure that your NTP configuration is correctly set up to access NTP servers or a time source. Review your NTP configuration file, typically located at `/etc/ntp.conf`, and verify the server settings. You should have a list of NTP servers or sources that `ntpd` can use for time synchronization. 3. **Network Connectivity**: Ensure that your server has network connectivity