<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Sun, Jan 12, 2020, at 06:15, František Šumšal wrote:<br></div><blockquote type="cite" id="qt"><div>Hello!<br></div><div><br></div><div>After recent struggles with compilation under Vagrant over NFS, I'd like to ask<br></div><div>if it would be possible to automatically sync all machines provided by Duffy using<br></div><div>NTP.<br></div><div><br></div><div>We encountered several nasty race conditions caused by system time discrepancies<br></div><div>between a Duffy host and a VM, which I managed to mitigate by installing & enabling<br></div><div>chrony. Unfortunately, it's not perfect, as the time synchronization apparently takes<br></div><div>some time, so the race condition is present, but it's much less probable.<br></div><div><br></div><div>Going through Jenkins logs it looks that all machines have their time significantly off:<br></div><div><br></div><div>● chronyd.service - NTP client/server<br></div><div> Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)<br></div><div> Active: active (running) since Sun 2020-01-12 16:06:53 GMT; 5h 51min left<br></div><div> Docs: man:chronyd(8)<br></div><div> man:chrony.conf(5)<br></div><div>Main PID: 1992 (chronyd)<br></div><div> CGroup: /system.slice/chronyd.service<br></div><div> └─1992 /usr/sbin/chronyd<br></div><div><br></div><div>Jan 12 16:06:53 n15.pufty systemd[1]: Starting NTP client/server...<br></div><div>Jan 12 16:06:53 n15.pufty chronyd[1992]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG)<br></div><div>Jan 12 16:06:53 n15.pufty systemd[1]: Started NTP client/server.<br></div><div>Jan 12 16:07:01 n15.pufty chronyd[1992]: Selected source xx.xx.xx.xx<br></div><div>Jan 12 16:07:01 n15.pufty chronyd[1992]: System clock wrong by -21251.336765 seconds, adjustment started<br></div><div>Jan 12 10:12:50 n15.pufty chronyd[1992]: System clock was stepped by -21251.336765 seconds<br></div><div><br></div><div>I suspect waiting for the synchronization to fully complete using chrony's CLI utilities would<br></div><div>help, but having this to be handled automatically by each machine would be much better.<br></div><div><br></div><div>Thanks!<br></div><div><br></div><div>Frantisek<br></div><div><br></div><div>-- <br></div><div>PGP Key ID: 0xFB738CE27B634E4B<br></div><div><br></div><div><br></div><div>_______________________________________________<br></div><div>CI-users mailing list<br></div><div>CI-users@centos.org<br></div><div>https://lists.centos.org/mailman/listinfo/ci-users<br></div><div><br></div><div><br></div><div><b>Attachments:</b><br></div><ul><li>signature.asc<br></li></ul></blockquote><div><br></div><div><br></div><div>Chronyd *should* be enabled by default. Unfortunately the system clocks on this hardware are not very reliable.<br></div><div><br></div><div>If your builds are sensitive to time shifts, it may make sense for you to put some guards/checks in place, but we'll look into a job that resets the system clocks on a regular basis.<br></div><div><br></div><div>--Brian<br></div></body></html>