How to setup NTP on VMTurbo Server to keep time in sync

This article was updated on February 26, 2013

The recommended method of keeping the time in sync on your VMTurbo Ops Manager Server is done using the 3 steps below:

1. Set the timezone properly.   The easiest way to do this is to establish a putty or console session to the VMTurbo server and login as root (default password is vmturbo) and use the yast command.   Here is the command:

    # yast timezone

     ***Note:   Even though you will see an option in yast to set up an NTP service, do *not* use this option and instead set up NTP using step 2 below.

2.  Configure the NTP server to keep the time in sync using the following steps to edit the NTP configuration file:

  •     Edit the configuration file using the 'vi' command

# vi /etc/ntp.conf

  •     Move to the bottom of this file (SHIFT-G) and you will notice these two lines:


  • Change the server names "" and "" to the FQDN of your time servers.    It may be safest to use the IP address of the servers instead.   If you only have one time server then you can delete the second unnecessary time server entry.
  • Restart the ntp service using the following command:

/etc/init.d/ntp restart

3.  Reboot your VMTurbo appliance using the following command:

#  shutdown -r now

Have more questions? Submit a request


  • Avatar
    Jeff Earickson

    webpage out of date for 5.4. You had two files lying around: /etc/ntp.conf and /etc/ntp.conf.local. The local file has entries for The other file had our time server but the syntax was wrong.

    I fixed ntp.conf, and found there is no /etc/init.d/ntp file -- you are now using systemctl.

    systemctl status ntp (it was dead)
    systemctl enable ntp
    systemctl start ntp
    ps -ef | grep ntp (daemon was running)

    Final check:

    ntpq -c peers. It found its peer. Good,

    Then I rebooted per the shutdown command.

    Arrrgh. After the reboot, the GUI put me into the setup wizard. Grrr.

  • Avatar
    Stephen Bartlett

    Jeff the same thing happened to me. I had to put my key in again and wait for the rescan on the environment.