modified in future

[sub3xt1]

MASTER: PVE 1.3
# cat /etc/ntp.conf

driftfile /var/lib/ntp/ntp.drift

# Enable this if you want statistics to be logged.
statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example

# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
# pick a different set every time it starts up. Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
#server 0.debian.pool.ntp.org iburst dynamic
#server 1.debian.pool.ntp.org iburst dynamic
#server 2.debian.pool.ntp.org iburst dynamic
#server 3.debian.pool.ntp.org iburst dynamic


restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery

# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust
# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines. Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient

# date

Mon Oct 6 16:24:34 WIT 2009

NODE: PVE 1.3
# cat /etc/ntp.conf

driftfile /var/lib/ntp/ntp.drift

# Enable this if you want statistics to be logged.
statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example
server ip_of_master

# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
# pick a different set every time it starts up. Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
#server 0.debian.pool.ntp.org iburst dynamic
#server 1.debian.pool.ntp.org iburst dynamic
#server 2.debian.pool.ntp.org iburst dynamic
#server 3.debian.pool.ntp.org iburst dynamic


restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery

# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust
# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines. Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient

# date

Mon Oct 5 16:24:44 WIT 2009

WEB (MASTER)
> SYSLOG

Oct 5 16:05:33 pvedaemon 24068 WARNING: file '/etc/qemu-server/103.conf' modified in future

what i have done??
a. i create centos 5.2, KVM mode on master
b. i migrate 103 (centos 5.2 ) from master to node.
Online migration is done. but when open the console, in the command shows :

[root@centos] shutdown -r now
bash: /sbin/shutdown: Input/Output error

to resolve this issue, i need to stop and start again from console.

c. i migrate back from node to master
Online migration is done. but when open the console, in the command shows :

[root@centos] shutdown -r now
bash: /sbin/shutdown: Input/Output error

to resolve this issue, i need to stop and start again from console.

it looks like time server is important. it demands ntp synchronize with master. could it fixed in the next stable release??

 

[sub3xt1]

i found this link for reference:

http://www.debian.org/doc/manuals/system-administrator/ch-sysadmin-time.html
http://www.crazysquirrel.com/computing/debian/ntp.jspx

 

[dietmar]

it looks like time server is important. it demands ntp synchronize with master. could it fixed in the next stable release??

Proxmox includes ntp, and the installer configure ntp automatically - so I do not understand your suggestion (you want explicit sync with master?).