Koozali.org: home of the SME Server
Obsolete Releases => SME Server 8.x => Topic started by: EdelingF on November 29, 2013, 11:26:14 AM
-
Just noticed time on my server was out of sync. It appeared the servertime was stil november 16th.
My server is a virtual server (Virtualbox) and I have read a lot of (old SME7) posts about time being out of sync due to a VMware problem, but nothing about Virtualbox.
Does anyone has experienced time being out of sync on a Virtualbox server? Should I just use mmccarn's solution on: http://forums.contribs.org/index.php/topic,32139.msg139191.html#msg139191 (http://forums.contribs.org/index.php/topic,32139.msg139191.html#msg139191)
I can imagine disabeling the local hardware clock could work?
-
i have many sme server virtualized by virtualbox and i never seen your issue.
what is your current version of virtualbox, i use phpvirtualbox and virtualbox 4.3
-
My current version of Virtualbox is 4.2.18 and phpVirtualBox 4.2-8
I updated the server in october I believe.
I just checked the time on the server and it seems it is still the same as this morning. It doesn't seem to count/refresh, how do you call it
-
It appears the time in Server-Manager and the hardwareclock differ.
The time in Server-Manager doesn't change after refreshing the page, the hardwareclock does.
]# hwclock
vr 29 nov 2013 20:36:41 CET -0.000455 seconden
-
did you try a reconfigure of your server, maybe it can repair your problem as the issue concern only the server-manager
-
I wonder if this has anything to do with this issue:
http://wiki.contribs.org/Virtual_SME_Server#Clock.2Ffrequency
-
I was wrong! Sorry guys, I did hwclock on the server, not the virtual server.
This is what I get now, at this moment:
[root@sme8 ~]# hwclock
zo 17 nov 2013 00:33:06 CET -0.858610 seconden
[root@sme8 ~]# date
vr nov 29 22:03:09 CET 2013
Time on the server in Server-Manager is ok: za 30 nov 2013 11:11:34 CET and it synchronizes with smeserver.pool.ntp.org
Time on the virtual server is : vr 29 nov 2013 22:04:29 CET
I also looked into the clock frequency and this is the result:
[root@sme8 ~]# grep CONFIG_HZ /boot/config-`uname -r`
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
I'll try the suggested solution.
-
The result is:
[root@sme8 ~]# hwclock
vr 29 nov 2013 22:10:23 CET -0.332284 seconden
[root@sme8 ~]# date
za nov 30 11:37:36 CET 2013
-
Apperently syncing stopped again for some reason:
[root@sme8 ~]# hwclock
za 30 nov 2013 16:25:53 CET -0.428388 seconden
[root@sme8 ~]# date
za nov 30 16:28:04 CET 2013
-
Turned off time syncing between server and virtual server:
vboxmanage setextradata [VMname] "VBoxInternal/Devices/VMMDev/0/Config/GetHostTimeDisabled" "1"
Also switched off syncing with NTP-server. Manually put it the time and now time is only about 6 hours out of sync in 24 hours.
Still not solved, but workable for the time being. Still can't figure out why the VM isn't syncing with the NTP-server
-
Still can't figure out why the VM isn't syncing with the NTP-server
-g
Normally, ntpd exits if the offset exceeds the sanity limit, which is 1000 s by default. If the sanity limit is set to zero, no sanity checking is performed and any offset is acceptable. This option overrides the limit and allows the time to be set to any value without restriction; however, this can happen only once. After that, ntpd will exit if the limit is exceeded. This option can be used with the -q option.
I enter this into the 'NTP Server' field in server-manager on virtual hosts:smeserver.pool.ntp.org minpoll 10 maxpoll 11
- Play with the values for minpoll & maxpoll
- Read more in this Bug 5648 (http://bugs.contribs.org/show_bug.cgi?id=5648)
On my SME8 it looks like this might help, too:
config setprop ntpd SupportLargeDrive enabled
signal-event timeserver-update
If all else fails, you could schedule a cronjob to forcefully reset the server's time using ntpdate -d pool.ntp.org
-
Thanks, I'll look into that.
I allready tried to put the smeserver.pool.ntp.org minpoll 10 maxpoll 11
into the 'NTP Server' field in server-manager, but that resulted in an error. SME says it's not a valid serveraddress
The result of signal-event timeserver-update
is:
no connection to syslog available
- /dev/log is not a socket
- /dev/log is not a socket at /usr/lib/perl5/site_perl/esmith/Logger.pm line 42
Did you mean:
config setprop ntpd SupportLargeDrift enabled
expand-template /etc/ntp.conf
?
I tried that allready after reading http://wiki.contribs.org/Virtual_SME_Server#Clock.2Ffrequency (http://wiki.contribs.org/Virtual_SME_Server#Clock.2Ffrequency)
-
I allready tried to put the smeserver.pool.ntp.org minpoll 10 maxpoll 11
into the 'NTP Server' field in server-manager, but that resulted in an error. SME says it's not a valid serveraddress
Hmmm.
That's what I have in server-manager; I must have entered it at the command line:config setprop ntpd NTPServer 'smeserver.pool.ntp.org minpoll 10 maxpoll 11'
(single quotes required)
signal-event timeserver-update
- works fine on my system (no errors). I don't know what it means (if anything) that you're getting an error.
-
Ok, that explanes it. Tried that and the result was an error:
[root@sme8 ~]# config setprop ntpd NTPServer 'smeserver.pool.ntp.org minpoll 10 maxpoll 11'
no connection to syslog available
- /dev/log is not a socket at /usr/lib/perl5/site_perl/esmith/config.pm line 598
That's the second perl error, maybe that's where the problem is?
-
what is the output of this command on the console please?:
'service syslog status'
-
This is the result:
[root@sme8 ~]# service syslog status
syslogd is gestopt
klogd is gestopt
-
Try:
service syslog start
-
They both started without problems:
[root@sme8 ~]# service syslog start
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
-
They both started without problems:
[root@sme8 ~]# service syslog start
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
Try making your time server changes now
-
I made the timeserver changes and
smeserver.pool.ntp.org minpoll 10 maxpoll 11
is now in the 'NTP Server' field in server-manager.
I noticed syslog was down and I had to start it again.
I tried :signal-event timeserver-update
again, but got the same error and syslog went down again.
-
Anything in /var/log/messages that can give a clue?
-
This what I find:
Dec 8 14:04:28 server01 syslogd 1.4.1: restart.
Dec 8 14:04:28 sme8 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Dec 8 14:04:28 sme8 kernel: Inspecting /boot/System.map-2.6.18-371.3.1.el5
Dec 8 14:04:28 sme8 kernel: Loaded 30904 symbols from /boot/System.map-2.6.18-371.3.1.el5.
Dec 8 14:04:28 sme8 kernel: Symbols match kernel version 2.6.18.
Dec 8 14:04:28 sme8 kernel: No module symbols loaded - kernel modules not enabled.
Dec 8 14:04:32 sme8 /sbin/e-smith/db[29971]: /home/e-smith/db/configuration: OLD ntpd=service|NTPServer|smeserver.pool.ntp.org|SupportLargeDrift|enabled|SupportLar
Dec 8 14:04:32 sme8 /sbin/e-smith/db[29971]: /home/e-smith/db/configuration: NEW ntpd=service|NTPServer|smeserver.pool.ntp.org minpoll 10 maxpoll 11|SupportLargeDr
Dec 8 14:05:31 sme8 esmith::event[30009]: Processing event: timeserver-update
Dec 8 14:05:31 sme8 esmith::event[30009]: Running event handler: /etc/e-smith/events/actions/generic_template_expand
Dec 8 14:05:31 sme8 esmith::event[30009]: expanding /var/service/ntpd/env/MEMLIMIT
Dec 8 14:05:31 sme8 esmith::event[30009]: expanding /etc/ntp.conf
Dec 8 14:05:31 sme8 esmith::event[30009]: expanding /etc/ntp/step-tickers
Dec 8 14:05:31 sme8 esmith::event[30009]: generic_template_expand=action|Event|timeserver-update|Action|generic_template_expand|Start|1386507931 528547|End|1386507
Dec 8 14:05:31 sme8 esmith::event[30009]: Running event handler: /etc/e-smith/events/actions/adjust-services
Dec 8 14:05:31 sme8 esmith::event[30009]: adjusting non-supervised crond (restart)
Dec 8 14:05:32 sme8 esmith::event[30009]: Stoppen van crond: ^[60G[^[0;32m OK ^[0;39m]^
Dec 8 14:05:32 sme8 esmith::event[30009]: Starten van crond: ^[60G[^[0;32m OK ^[0;39m]^
Dec 8 14:05:32 sme8 esmith::event[30009]: adjusting supervised ntpd (restart)
Dec 8 14:05:32 sme8 esmith::event[30009]: adjusting supervised ntpd (up)
Dec 8 14:05:32 sme8 esmith::event[30009]: adjusting non-supervised syslog (restart)
Dec 8 14:05:32 sme8 kernel: Kernel logging (proc) stopped.
Dec 8 14:05:32 sme8 kernel: Kernel log daemon terminating.
Dec 8 14:10:06 sme8 ntpd[30028]: ntpd 4.2.2p1@1.1570-o Fri Nov 18 13:21:16 UTC 2011 (1)
Dec 8 14:10:06 sme8 ntpd[30028]: logging to file /dev/stdout
Dec 8 14:10:06 sme8 exiting on signal 15
Dec 8 14:12:07sme8 syslogd 1.4.1: restart.
Dec 8 14:12:07 sme8 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Dec 8 14:12:07 sme8 kernel: Inspecting /boot/System.map-2.6.18-371.3.1.el5
Dec 8 14:12:07 sme8 kernel: Loaded 30904 symbols from /boot/System.map-2.6.18-371.3.1.el5.
Dec 8 14:12:07 sme8 kernel: Symbols match kernel version 2.6.18.
Dec 8 14:12:07 sme8 kernel: No module symbols loaded - kernel modules not enabled.
I can't figure it out, sorry....
-
what is the outcome of this command please?
'lsmod'
and
'uname -a'
-
The outcome of 'lsmod' is:
[root@sme8 ~]# lsmod
Module Size Used by
bonding 97633 0
ipt_REJECT 9537 1
ipt_MASQUERADE 7617 1
xt_state 6209 1
xt_tcpudp 7105 26
ip_nat_ftp 7361 0
ip_conntrack_ftp 11569 1 ip_nat_ftp
iptable_mangle 6849 0
iptable_nat 10949 1
ip_nat 21229 3 ipt_MASQUERADE,ip_nat_ftp,iptable_nat
ip_conntrack 53665 6 ipt_MASQUERADE,xt_state,ip_nat_ftp,ip_conntrack_ ftp,iptable_nat,ip_nat
nfnetlink 10713 2 ip_nat,ip_conntrack
iptable_filter 7105 1
ip_tables 17029 3 iptable_mangle,iptable_nat,iptable_filter
ipt_ULOG 11717 2
x_tables 17349 7 ipt_REJECT,ipt_MASQUERADE,xt_state,xt_tcpudp,ipt able_nat,ip_tables,ipt_ULOG
loop 18761 0
dm_multipath 27213 0
scsi_dh 12481 1 dm_multipath
video 21193 0
backlight 10049 1 video
sbs 18533 0
power_meter 16461 0
hwmon 7365 1 power_meter
i2c_ec 9025 1 sbs
dell_wmi 8401 0
wmi 12137 1 dell_wmi
button 10705 0
battery 13637 0
asus_acpi 19289 0
ac 9157 0
lp 15849 0
sg 36973 0
e1000 120285 0
usb_storage 80929 0
parport_pc 29669 0
parport 37513 2 lp,parport_pc
pcspkr 7105 0
ide_cd 40161 0
serio_raw 10693 0
cdrom 36705 1 ide_cd
i2c_piix4 13133 0
tpm_tis 16713 0
tpm 19041 1 tpm_tis
i2c_core 24897 2 i2c_ec,i2c_piix4
tpm_bios 11073 1 tpm
dm_raid45 67273 0
dm_message 6977 1 dm_raid45
dm_region_hash 15681 1 dm_raid45
dm_mem_cache 9537 1 dm_raid45
dm_snapshot 23653 0
dm_zero 6209 0
dm_mirror 24905 0
dm_log 14785 3 dm_raid45,dm_region_hash,dm_mirror
dm_mod 64889 11 dm_multipath,dm_raid45,dm_snapshot,dm_zero,dm_m irror,dm_log
ata_piix 23749 0
ahci 39245 2
libata 158085 2 ata_piix,ahci
sd_mod 25409 3
scsi_mod 144277 5 scsi_dh,sg,usb_storage,libata,sd_mod
raid1 25537 2
ext3 126281 2
jbd 57705 1 ext3
uhci_hcd 25421 0
ohci_hcd 24937 0
ehci_hcd 34509 0
The outcome of 'uname -a' is:
[root@sme8 ~]# uname -a
Linux server01 2.6.18-371.3.1.el5 #1 SMP Thu Dec 5 12:47:01 EST 2013 i686 i686 i386 GNU/Linux