similar to: time synchronization problem (using NTP)

The time appears to be perfect inside dom0, however all the domU''s tend to have a slightly faster date which gets further out of sync every day. I''m currently using Xen 3.0.3 with Gentoo Linux, under 3.0.2 I had no problems with domU clocks. Are there any known issues which could cause this? I''d strongly prefer not to run ntpd in every domU, having all domU clocks in

Hi, I am facing problem in sync time within DomU with Dom0. After gone through mailing lists, I have set /proc/sys/xen/independent_wallclock to 0. But still DomU are not syncing their time :-S Machine using kernel-xen-2.6.19-1.2911.fc6 xen-3.0.3-3.fc6 xen-libs-3.0.3-3.fc6 Please advice to solve this weird problem, Thanks _______________________________________________ Xen-users mailing list

On 05/02/17 16:15, Richard wrote: > >> Date: Sunday, February 05, 2017 10:26:05 -0500 >> From: Robert Moskowitz <rgm at htt-consult.com> >> >> I have read: >> http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet >> ween-ntpd-and-chronyd/ >> >> My server is up all the time and will serve time to internal >> systems (via

On Sunday, 3 June 2018 16:32:12 CEST Rowland Penny via samba wrote: > On Sun, 3 Jun 2018 17:11:47 +0300 > > Alexei Rozenvaser <alexei.roz at gmail.com> wrote: > > On Sun, Jun 3, 2018 at 4:51 PM Rowland Penny via samba > > > > <samba at lists.samba.org> wrote: > > > On Sun, 3 Jun 2018 16:29:04 +0300 > > > > > > Alexei Rozenvaser

On 16.11.2019 15:17, Sonic wrote: > On Thu, Nov 14, 2019 at 1:56 PM Viktor Trojanovic via samba > <samba at lists.samba.org> wrote: >> I'm running a Samba AD DC v4.9.9 with Windows 10 clients connected to it >> and just noticed that the clients are not synchronizing time with the >> server. I'm not sure why not. >> >> My setup is a bit special in

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.

Hello ! Just a quick question about time synchronization between xen dom0 and domUs... We''re running Xen 3.1 64-bit, with 32 and 64 bits linux guests. It''s up since 89 days and the domU''s time is around 5 minutes behind the dom0, which is updated via ntpdate... Any idea why it doesn''t sync the guests even that /proc/sys/xen/independent_wallclock is 0 ?

After our office upgraded to Windows 10, time sync stopped working with the Windows workstations. This used to work fine with Windows 7 and still works with linux domain members (although that's not surprising). The Windows 10 workstations ended up operating off the CMOS clock. We didn't notice this for a long time since the CMOS clock drift is slow, but after several months users started

Hi Louis, In general, this sounds like the solution I was looking for. But I’m still a bit unclear about the practical implementation. So, the DC can be setup without ntpd as it will work based on the system clock which, in turn, is actually being updated by the container host using NTP. Which means we’ve got the DC itself covered. But if ntpd is not installed, then how can the DC serve time

Hey, I have rather new installation of xen, dom0 is running ntpd and is perfectly in time. All domU''s are ~23s in future. Running ntpd on the domU''s seem to have no effect, /proc/sys/xen/independent_wallclock appears to have no effect. I''m running xen-unstable and 2.6.16-rc4 in AMD64 box. Any tip would be appricated. Thanks, -- ++ytti

Hi all, I am running Scientific Linux 5.1 (rhel 5.1 compatible) 64bit on a 2x4core system with 16 gb ram with 3 Scientific Linux 4.6 (rhel 4.6 compatible) guests an one Scientific Linux 5.1 guest. I do not run ntp on the guests but only on dom0. One specific Scientific Linux 4 domU always looses time synchronization with dom0. All the others SL4 and the SL5 domUs remain synchronized. There

It appears that none of our windows clients are syncing their time with the samba DC.??? From what I can tell they are not able to get a response from the DC.? For example, where the DC is named athena: >w32tm /monitor /computers:athena athena[10.10.1.10:123] ? ICMP: 0ms delay ? NTP: error ERROR_TIMEOUT - no response from server in 1000ms From a Linux machine there is

I’m currently trying to install a new (primary) AD DC in a Linux container. It seems to me that being in a container, the DC is easier to maintain and backup than on bare metal, and I prefer a container over a VM for performance reasons. If the container setup will prove to be too much of hassle, I’ll switch to a VM, though. The first issue I’m facing is time synchronization. An container cannot

Hello, I recently compiled Samba 4.0.6 (as an AD DC) and am running it on Ubuntu 12.04. I followed the instructions on the Samba wiki (https://wiki.samba.org/index.php/Configure_NTP) for how to configure ntp, however the domain clients are rejecting the DCs as being acceptable time sources. Below is my ntp.conf: server 127.127.1.0 fudge 127.127.1.0 stratum 10 server 0.pool.ntp.org iburst

Hallo, what is the standard way to sync time under Centos 7. ntp or chrony. Thanks for a short hint. Ralf

On 5/23/2015 11:22 PM, Luigi Rosa wrote: > Kirk Bocek wrote on 24/05/2015 04:37: >> So I've built my first CentOS 7 host and am learning all the new ways >> of doing >> things. I setup and enabled ntpd but after a reboot I get: > > In CentOS 7 is bettere to use chrony, here's an howto > > http://linoxide.com/linux-command/chrony-time-sync/ > So

Hi, As Centos 7 and Fedora defaults to chronyd [2] , should I use ntpd for some reason [3] ? I based my configurations on [1] which use ntpd ... but I thinking change for chronyd , change ntp deamons could outage the samba service and client computers ? Thanks [1] https://negativo17.org/samba-4-active-directory-with-bind-dlz-zones-dynamic-dns-updates-windows-static-rpc-2/ [2]

On 5/24/2015 12:22 PM, Gordon Messmer wrote: > On 05/24/2015 11:41 AM, Kirk Bocek wrote: >> to activate your selected daemon. I just used the new systemd commands, >> thinking that would be enough. So I tried that and rebooted. Nope, same >> problem: > > chronyd and ntpd both use UDP port 123, so each will terminate the > other when it starts. If both are enabled,

So I've built my first CentOS 7 host and am learning all the new ways of doing things. I setup and enabled ntpd but after a reboot I get: $ systemctl status ntpd ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled) Active: inactive (dead) After issuing: $ systemctl start ntpd Ntpd runs just fine. But why isn't it loading at boot

Hello, It is debian 11, and it is ntp, as you can see below my ntp.conf. Ntp service is running fine . Some , not all, W10/11 clients do not sync with the dc (samba 4.19). What i did on the clients: net stop w32time w32tm /unregister w32tm /register net start w32time But after some time the wrong time shows up again? Greetings Daniel -----Urspr?ngliche Nachricht----- Von: Luis Peromarta