How to solve the time synchronization problem when the Xen Virtual Machine joins the Puppet Environment

Puppet's automated distributed environment has strict time requirements, and the following errors may easily occur during routine operations:

Triggering test.cn7788.comHost test.cn7788.com failed: certificate verify failed.  This is often because the time is out of sync on the server or clienttest.cn7788.com finished with exit code 2Failed: test.cn7788.com

You can follow the error message "This is often because the time is out of sync on the server or client". Generally, if a similar word appears, this is basically a problem caused by inaccurate time. You can solve this problem by using ntpdate.

Multiple groups of Xen virtual machines are added in the work, and the Puppet server is also required for automated management. The initialization environment has been handled by the Xen model machine. The environment is as follows:

192.168.11.26 test1.cn7788.com  puppet-client192.168.11.27 test2.cn7788.com  puppet-client192.168.11.28 test3.cn7788.com  puppet-client

The above error is reported for the same reason:

The hardware clock synchronization between the Xen Virtual Machine and the host machine is very convenient. However, because the simulation interruption of the software will cause a delay when the load changes, it will gradually become slower than the normal time. We will modify the kernel file/etc/sysctl of the xen virtual machine. conf. Add the following code:

xen.independent_wallclock = 1

Run the following command to make the kernel change take effect:

sysctl -p

Finally, we use the ntpdate command on the three Xen machines to synchronize the time, so that the Xen virtual machine will not report an error due to time issues. The command is as follows:

ntpdate ntp.api.bz

This article from the "fuqin liquor" blog, please be sure to keep this source http://andrewyu.blog.51cto.com/1604432/1301516