Fresh pve 1.5 install, wrong ntp time

M

m.ardito

Famous Member
Feb 17, 2010
1,473
18
103
Torino, Italy
Hi, i had a previous pve server 1.5, with test vms, and so on: (pve on full lenny)
debian:~# pveversion -v
pve-manager: 1.5-7 (pve-manager/1.5/4660)
running kernel: 2.6.26-2-amd64
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-1-pve: 2.6.18-4
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5

Now i just installed a new pve server 1.5, bare ISO:
proxmox1:~# pveversion -v
pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-8
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5

I created a cluster on the new server and added the old as new cluster member (wait, but it has already vms, is this a problem, btw?). the sync fails, due to... different timing on the two servers.

on the old server i get Tue Mar 30 13:58:13 CEST 2010
on the new server i get Tue Mar 30 14:58:06 CEST 2010

and from the web gui, both are set on the same timezone: "Europe/Rome", but the box on the left shows just one hour more on the new server i.e: 14.58 (time has shifted to daylight saving last week, now it is 13.58, but really is 12.58)...

i checked both /etc/ntp.conf and they look identical
both systems are pinging 0.debian.pool.ntp.org

and also done /etc/init.d/ntp restart

but nothing changed...

Any hints?
Should i udate pve on the new server (or both) to make the pve versions match?
Is there any problem if (when sync succeed) join the old (with vms) server to the new cluster (empty)?

Thanks, Marco
 
Well, i also cheched

/etc/default/rcS on both and found that
the old server (right ntp time) had UTC=no
the new server (wrong ntp time) had UTC=yes

then changed UTC=yes to UTC=no on that machine, rebooted but nothing changed...

then went in BIOS settings and ... surprise surprise, the BIOS time was wrong.
changed -1h that bios time, rebooted and time was right, and cluster sync is proceeding now...

now i am still left with this doubts:
* should i have UTC=yes to UTC=no? any concerns about this setting?
* Is there any problem if (when sync succeed) join the old (with vms) server to the new cluster (empty)?

i have another identical "new" server to install, wil check if any other time sync issue will happen...

and waiting for cluster sync to complete


Marco
 
Last edited:
...and still i have to reply myself (read: should think and read more TFM before posting...)
wiki clearly explains that join a non-empty member won't work as expected. (http://pve.proxmox.com/wiki/Proxmox_VE_Cluster)
so i
- removed the nonempty cluster member from the cluster
- then removed the cluster (see wiki page)
- recreated the cluster on the nonempty server

then i will try to
- join the empty server to the new cluster
- promote the new server as cluster master, but before i have to learn how iscsi storage, and backup space etc works in a pve cluster

Marco
 
ok, i have to guess how is the bios set, at a first glance i can't see any reference to how it is, i can only change time and date (IBM X3650M2)
however, as i said in the post before, <<changed UTC=yes to UTC=no on that machine, rebooted but nothing changed...>>, so maybe it was not that important in that case.

Thanks, Marco
 
m.ardito said:
ok, i have to guess how is the bios set, at a first glance i can't see any reference to how it is, i can only change time and date
Click to expand...

Yes, that is the point - the bios does not have a timezone setting. This is why you have to tell the OS if the time you have set in the bios is UTC or local time. Got it?
 
You must log in or register to reply here.
Top Bottom