I had a similar instance on wheezy, twice on the same machine.
the machine has many GRE interfaces, for each of them /etc/network/if-
up.d/ntpdate runs ntpdate, and each take 15-20s.
thanks to a lockfile mechanism, each instance of this script is run
sequentially, so they are all able to use the N
Hi all,
This problem annoys me on my latest minimal sid VM with two interfaces on
VirtualBox.
When I disable one of them on /etc/network/interfaces,
I could circumvent the problem as the timing issue worked in favor of ntpd.
But obviously that's not a strategic solution.
How about removing if-up.
I was able to recreate this without systemd. In my case all it took was
to have a network interface that took a long time to configure/come up.
I'm unsure it is the best way to do it, it currently configures a switch
chip attached to an interface when the interface comes up. This appears
to have
I've also hit this problem of the race condition with ntpdate.
If ntpd dies for whatever reason (port in use, somebody stomping about
with kill to prove the point) systemd thinks that this is fine. System
configuration tools like Puppet won't try to start ntpd again as
"systemctl status ntp" retur
I installed lockfile-progs to try to fix this, and it did not work. I
had no choice but to remove ntpdate on affected systems. Interestingly,
this seems to affect only systems that have been converted to using
systemd. Those not converted still boot happily with both packages
installed, so the
On Mon, Jun 08, 2015 at 09:14:09AM +0200, Evgeni Golov wrote:
> Hi Kurt,
>
> On Sun, Jun 07, 2015 at 11:25:44PM +0200, Kurt Roeckx wrote:
>
> > > Jun 07 21:18:53 genshi.die-welt.net ntpd[650]: unable to bind to wildcard
> > > address 0.0.0.0 - another process may be running - EXITING
> >
> > Th
Hi Kurt,
On Sun, Jun 07, 2015 at 11:25:44PM +0200, Kurt Roeckx wrote:
> > Jun 07 21:18:53 genshi.die-welt.net ntpd[650]: unable to bind to wildcard
> > address 0.0.0.0 - another process may be running - EXITING
>
> This last line is clearly a problem. There are at least 2
> processes that try
On Sun, Jun 07, 2015 at 10:11:41PM +0200, Evgeni Golov wrote:
> Package: ntp
> Version: 1:4.2.6.p5+dfsg-7
> Severity: important
>
> Hi,
>
> after upgrading this machine to jessie, ntpd does not start at boot.
> This might be systemd related.
>
> root@genshi:~# systemctl status ntp
> ? ntp.servic
Package: ntp
Version: 1:4.2.6.p5+dfsg-7
Severity: important
Hi,
after upgrading this machine to jessie, ntpd does not start at boot.
This might be systemd related.
root@genshi:~# systemctl status ntp
● ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp)
Active: active (exi
9 matches
Mail list logo
