Clock skew detected after building OEL5.3 in vSphere 4.1 environment
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Clock skew detected after building OEL5.3 in vSphere 4.1 environment
When booting, the system sticks at a warning
Starting sendmail: make: Warning: File 'sendmail.cf'has modification time 2.3e+04 s in the future
make: warning: Clock skew detected. Your build may be incomplete.
System just sits here for a good 20min spinning it's wheels. Don;t see any resource usage or network traffic on the virtual machine, it doing nothing as far as I can tell. It eventually moves on to "Starting sm-client:" and sits there for a about 10minutes before completing the boot process.
Never worked with Oracle Enterprise Linux before and I am in the process of creating templates in vSphere with a group of developers who need the vm's to develop an application on. The VM specs chosen by the devs is OEL 5.3 with no update subscription (so it is just fresh off the install CD) with 2 cpu, 16GB of ram, 40GB vmdk (100mb /boot, 8gb /tmp, 16gb swap, remaining space to /). The system was built with no IP information entered (this is prep for a template). At first, things seemed fine with the system. VMTools installed with out issue and all things worked with the exception of network. I setup the VM with a DHCP setup, and the vlan the vm is attached to does not offer DHCP. During the install I did input the fqdn of the two internal NTP servers, though I did get the error that they could not be reached since no IP address was provided to the system.
Before I found out the devs do not have a subscription for updates, I put in a static IP address on the nic so I can download current updates. I put in the IP address info and DNS info. After doing this and restarting the vm, I ran into this clock skew, hang around and wait issue.
For my time configuration, my ESXi servers are set to UTC time in the BIOS, and ESX servers are in the PST time zone. The VM I normally do not alter the VM bios and let it stay with the default PST time it gets from ESX. The OEL setup is configured to use local time to match what the BIOS is set to.
In searching, I can not find much reference to this machine other than configuring NTP server, which I have. But none of the info I do find references anything to this huge boot delay I am getting.
Does anyone know why I get such a large boot delay? or where I can look to figure this out?
Unfortunately this kind of thing happens from time to time in vSphere. My ESX box sitting under my desk is now so far out of time, it won't even sync with ntpdate, even though it was set to run a regular sync with my NTP servers. You could create a new VM and build it... but honestly just sync it once with ntpdate and quickly make your template. After you deploy your templates, make sure you set the boxes to sync with an NTP source and off you go.
There are several reasons to respond -- positive or negative -- to a suggested solution:
It's polite. -- Just replying is a form of thank you.
You confirm to your helper(s) & the rest of LQ that a given solution does or doesn't work for a given problem. This furthers the LQ objective of creating an archive of answers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.