Sep 08

written by phi.mic \\ tags: ,

Apr 16

I use VMware VirtualCenter 2.5.0 Build 147697 and VMware ESX 3.5.0 143128 and it was not possible to configure the timeserver of the ESX hosts through the VirtualCenter (VC). Normally you should ajdust the timeserver settings for the ESX hosts in VC by clicking on the ESX Server –> Configuration –> Software: timeserver configuration –> Preferences. But this does not work for me, so i had to adjust the timesever directly on the ESX hosts.

First login to your ESX with ssh and become super-user.

$ ssh -l user esx-server1.your.domain
$ su -
$ ln -sf /usr/share/zoneinfo/Europe/Berlin /etc/localtime
$ cp /etc/ntp.conf /etc/ntp.bak
$ vi /etc/ntp.conf
 
restrict default ignore
restrict 127.0.0.1 
restrict 132.230.1.9 mask 255.255.255.255 nomodify notrap noquery
server 132.230.1.9
driftfile /var/lib/ntp/drift

You have to set the timeserver to your needs (my timeserver has the IP 132.230.1.9) before saving the file. Then put the same IP in the file /etc/ntp/step-tickers.

$ cp /etc/ntp/step-tickers /etc/ntp/step-tickers.bak
$ echo "132.230.1.9" >/etc/ntp/step-tickers

To see the offset in seconds you can run the command ntpdate -q 132.230.1.9 as super-user. Now it’s time to restart the ntpd daemon and enable it for autostart. The last command set the hardware clock to the synchronized local time.

$ esxcfg-firewall -e ntpClient
$ service ntpd restart
$ chkconfig --level 345 ntpd on
$ hwclock --systohc

Finally reboot the ESX server through the VC (don’t forget to migrate running virtual machines to another ESX node) so that the timeserver configuration will be visible in VC.

written by phi.mic \\ tags: ,

Apr 08

Links for 2009-02-02

Links Kommentare deaktiviert

written by phi.mic \\ tags: ,

Nov 13

Today i did a upgrade of my Ubuntu 8.04 (Hardy) to the new release Ubuntu 8.10 (Intrepid). The upgrade procedure was really easy, you only need two commands and about 30 minutes

sudo apt-get update
sudo apt-get install update-manager-core
sudo do-release-upgrade

You should modify the file /etc/update-manager/release-upgrades, so that the update-manager allows you to upgrade to a non-lts release:

[DEFAULT]
# default prompting behavior, valid options:
#  never  - never prompt for a new distribution version
#  normal - prompt if a new version of the distribution is available
#  lts    - prompt only if a LTS version of the distribution is available
Prompt=normal

I had an old VirtualBox OSE 1.6.2 installation which should not seems to work with the recent 2.6.27 kernel modules. So i first delete the old VirtualBox release and installed the recent stable release from Sun.

sudo apt-get remove virtualbox-ose
sudo echo "deb http://download.virtualbox.org/virtualbox/debian intrepid non-free" >> /etc/apt/sources.list
wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | sudo apt-key add -
sudo apt-get update
sudo apt-get install virtualbox-2.0

written by phi.mic \\ tags: , ,