*** This bug is a duplicate of bug 1593907 ***
https://bugs.launchpad.net/bugs/1593907
Hi Everybody,
I looked into this again as a friend asked me. And it turns out there is an
update probably worth it.
Two things to mention:
1. the locking issue of /run/lock/ntpdate vs /var/lock/ntpdate
Hi Heinrich,
thank you for picking up working on this.
I must beg your pardon as I come by this so late (as I'm currently cleaning
bugs too long dormant).
I like the suggestion of a fix by adapting the scripts, but following comments
#22 and #23 that would have to be accepted in Debian instead.
The attachment "ntpdate_HH is a revised version of /etc/network/if-
up.d/ntpdate" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
Please do not blame me too hard if I provided a "patch" not in the
correct format - but the script does the job for me. ntpd is started and
continues to run, ntpdate seems to be invoked twice. The first
invocation is too early and failes. The next one does its job but
doesn't do a very impressive
attached version of ntpdate solves the problem for me and hopefully for
everybody.
I do not mind if comments are removed.
The attached version avoids the conflict between ntpd and ntpdate and also
makes the skript simpler.
** Attachment added: "ntpdate_HH is a revised version of
I don't think -u would be necessary if /etc/network/if-up.d/ntpdate were
using the correct lock file (/var/lock/ntpdate vs /run/lock/ntpdate, as
I pointed out in comment #27).
But I do agree that either adding -u or fixing the lock file path would
be a simple solution to this problem.
--
You
I tested the suggestion from comment #38 by robx. It works for
me.
Deviating from his proposal I only did the following change:
hhl@ILS-AP2:~$ diff ntpdate /etc/network/if-up.d/ntpdate
9a10
> # exit 0 # hh_161120 - ntpdate prevents start ntpd Ubuntu Bug #1577596
42c43,44
< flock -n
Hi,
there is a much easier solution.
"/etc/network/if-up.d/ntpdate" use "/usr/sbin/ntpdate-debian" which read the
configfile "/etc/default/ntpdate" (man ntpdate-debian). If you modify
/etc/default/ntpdate with NTPOPTIONS="-u" then "/usr/sbin/ntpdate-debian" use
an unpriviledge port (>1023) if
The solution suggested in comment #36 works for me, ntpd is running after
reboot.
Actually I did not create ntpdate_bak in the directory, I simply inserted the
exit 0 statement in the script.
= To resolve the bug
= I suggest if-up.d/ntpdate is removed from the system.
=
I hope my comment #35 answered the question raised in comment #32.
I do not fully understand the discussion and I am a newbe in that knowledge
domain however I would like to have the problem solved.
Please let me know if you think the following attempt makes sense.
Grep'ing through /etc I found
hhl@ILS-AP2:~$ which ntpdate
/usr/sbin/ntpdate
hhl@ILS-AP2:~$ dpkg -l | grep ntpdate
ii ntpdate
1:4.2.8p4+dfsg-3ubuntu5.3 i386 client for setting
system time from NTP servers
hhl@ILS-AP2:~$
--
You received this bug
I knew I remembered something about it - so missing sntp is
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1604010
Keep this bug here for the issue starting ntpd when using ntpdate that
has to be viewed under the constraints outlined by rbasak in comment #22
/ #23
--
You received this bug
Paul,
yeah I recently realized as well that sntp is missing in later releases.
Long Term I really look forward to see how it ends up if ntpsec will
replace ntp (that should hopefully fix most open issues by being almost
a full rewrite/cleanup, but as everything new surely needs some
test/fixup).
Heinrich,
to check if that is the same or a different bug - is ntpdate installed for you?
If not that is a "different" issue than what was discussed here, so please
confirm or if not please open a new bug to be discussed separately.
--
You received this bug notification because you are a member
Yes, it looks to me like sntp is a sufficient replacement for ntpdate.
However, sntp is not currently packaged for Debian or Ubuntu:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793837
In addition, prior to that bug being introduced, sntp was included in
the 'ntp' package, so sntp could not
systemctl restart-failed ntp # was no help
# However after
systemctl stop ntp # changes status active (exited) to inactive (dead)
systemctl start ntp # succeeds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am affected too.
Manually starting ntpd using `systemctl start ntp` doesn't work for me.
ps -ef | grep ntpd # shows no started ntpd.
systemctl status ntp # does not change active (excited), only another last line
is added.
root@ILS-AP2:~# systemctl start ntp
root@ILS-AP2:~# ps -ef | grep ntp
According to http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate, it
seems that they expect you to use the sntp client for that
functionality. Is this sufficient?
But yes - given that ntpdate is deprecated upstream, in general it would
make sense to communicate upstream for any lost use cases.
My original issue is definitely a duplicate of Bug #1575572 and the fix
for that bug solves the specific problem described in Comment #8.
The issues described by Lars Kollstedt and others are a separate issue
... My original issue was that systemd would not start ntp.service if
/etc/network/if-up.d/ntpdate executes it's code between ()& starting on line 25.
this is to be able to wait until /usr is mounted, when it isn't already.
If that check is disabled, and the run-in-background ampersand is commented out
(line 46), the ntp daemon starts just fine.
No matter to
Hi Rick,
On Mon, Sep 19, 2016 at 02:17:58PM -, Rick Frey wrote:
> So, if I understand correctly, the ntp package really has no bug (at
> least related to starting at boot). Issue was really due to bug with
> deprecated ntpdate package which should be removed if running ntp
> anyway.
That's
Thanks for the update Robie. I was not aware of ntpdate being
deprecated (appears to have been deprecated years ago).
For those like myself that require ntpd (the suggested alternative
systemd-timesyncd uses sntp which may not suffice in all use cases), I
think the best fix/workaround is to
Sorry, I missed the link:
[1] https://lists.ubuntu.com/archives/ubuntu-
devel/2016-August/039484.html
** Changed in: ntp (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think that this belongs to the class of bugs we discussed on ubuntu-
devel recently[1].
The summary is:
1. ntpdate is deprecated
2. Various patches got polished, tested and provided to Debian but not yet
picked up
3. We are unwilling to add more delta to Debian for a deprecated binary
So if
I'm seeing same behavior as Alex where failure of ntpdate is preventing
ntpd from starting. ntpdate is logging same message indicating failure
due to name resolution (Bind not running yet at boot):
Sep 16 10:40:09 scorpion ntpdate[1033]: name server cannot be used:
Temporary failure in name
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577596
Title:
ntpd not started when using ntpdate
To manage notifications about this bug go to:
Hmm, I also found this line in my log (this time it booted OK):
Jul 12 18:41:47 redacted.example.org ntpdate[2184]: name server cannot
be used: Temporary failure in name resolution (-3)
I'm wondering whether it's either
a) failing to start ntp because ntpdate isn't running because it
couldn't
OK, unduping for now.
** This bug is no longer a duplicate of bug 1575572
apache2 fails to start if installed via cloud config (on Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577596
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
I'm also seeing this still fail with init-system-helpers 1.29ubuntu2,
also suggesting this is not a duplicate of #1575572.
It does not seem to fail reliably, but for what it's worth this was a
clean
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
I don't think this is a duplicate of bug #1575572
I am seeing this problem on an Ubuntu 16.04 machine that has the update "This
bug was fixed in the package init-system-helpers - 1.29ubuntu2" mentioned as
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
Another observation, the ntpdate command is really slow on Ubuntu 14.04
and 16.04. On average it takes about 6.1 seconds to run the ntpdate
command, I am running ntpdate after boot. Our Red hat 6.8 machines
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
I am seeing this on some but not all systems. I can only manually start
after first doing a stop:
root@tophat:~# ps -ef | grep ntp
root 2380 2365 0 11:51 pts/800:00:00 grep --color=auto ntp
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
Send to fast. :-( Tab, Enter wasn't a good idea, in the Bugtrackers
WebGUI. :-( ;-)
The differences between the versions and platforms are probably just
timing. But this happens deterministically on
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
Hi Martin,
the fix for Bug #1575572 released yesterday turns the situation from bad
to worse from my experience. Since I saw this on i686 only before, I am
experiencing this also on amd64 since installing
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: init-system-helpers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
Indeed this is a duplicate of bug 1575572, so marking accordingly.
Thanks Paul for the analysis!
** This bug has been marked a duplicate of bug 1575572
apache2 fails to start if installed via cloud
Paul, that's a really handy analysis - thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577596
Title:
ntpd not started when using ntpdate
To manage notifications about this bug go to:
This reminds me of bug 1575572. invoke-rc.d's behaviour is adjusted
there. I wonder if that fix is related to this problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577596
Title:
ntpd not
Aha! I've found the issue.
/etc/network/if-up.d/ntpdate is called when each network interface comes
up. This happens before network.target is reached, so it happens before
ntp.service would normally be automatically started by systemd.
/etc/network/if-up.d/ntpdate calls `invoke-rc.d ntp stop`,
** Summary changed:
- ntpd not started by systemd
+ ntpd not started when using ntpdate
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577596
Title:
ntpd
40 matches
Mail list logo
