ntpdate[634]: no servers can be used, exiting

Bug #1422125 reported by dino99
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ntp (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

desktop booted with systemd-sysv

from journalctl:

 networking[439]: ...done.
systemd[1]: Started LSB: Raise network interfaces..
systemd[1]: Stopped LSB: Start NTP daemon.
apparmor_parser[594]: <audit-1400> apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=594 comm="apparmor_pa
apparmor_parser[594]: <audit-1400> apparmor="STATUS" operation="profile_load" profile="unconfined" name="chromium" pid=594 comm="apparmor_parser"
kernel: audit: type=1400 audit(1423979133.654:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=594 co
kernel: audit: type=1400 audit(1423979133.654:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="chromium" pid=594 comm="apparmor_parser"
ntpdate[634]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2)
ntpdate[634]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2)
ntpdate[634]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2)
ntpdate[634]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2)
ntpdate[634]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
ntpdate[634]: no servers can be used, exiting

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ntpdate 1:4.2.6.p5+dfsg-3ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
Uname: Linux 3.19.0-5-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
CurrentDesktop: GNOME
Date: Sun Feb 15 15:38:14 2015
NtpStatus: ntpq: read: Connection refused
SourcePackage: ntp
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :

oem@u32:~$ ntpq -pn
     remote refid st t when poll reach delay offset jitter
==============================================================================
+195.154.71.176 193.79.237.14 2 u 23 64 377 15.006 -0.106 2.678
-195.83.66.158 193.50.27.66 3 u 12 64 377 20.668 4.701 0.578
-194.57.169.1 145.238.203.14 2 u 16 64 377 24.269 0.446 1.963
*78.194.78.49 213.251.128.249 2 u 21 64 377 15.981 0.270 1.894
+91.189.89.199 192.93.2.20 2 u 32 64 377 37.263 0.417 1.216

oem@u32:~$ ntptrace
localhost: stratum 3, offset 0.000211, synch distance 0.010676
78.194.78.49: timed out, nothing received
***Request timed out

Revision history for this message
dino99 (9d9) wrote :

78.194.78.49 IP adress is know to fall
http://iptrace.in/All-IPv4-IP-Addresses/78.194.78.0-78.194.78.255.html

/etc/ntp.conf needs to be upgraded
get better config examples on: http://en.linuxreviews.org/NTP_-_Howto_make_the_clock_show_the_correct_time

Revision history for this message
dino99 (9d9) wrote :

Warning: The system is configured to read the RTC time in the local time zone. This
         mode can not be fully supported. It will create various problems with time
         zone changes and daylight saving time adjustments. The RTC time is never updated,
         it relies on external facilities to maintain it. If at all possible, use
         RTC in UTC by calling 'timedatectl set-local-rtc 0'.

Revision history for this message
dino99 (9d9) wrote :

Get the same error if some other servers are added

Revision history for this message
dino99 (9d9) wrote :

Latest systemd upgrade has fixed that issue:

systemd (219-4ubuntu8) vivid; urgency=medium

  * force ifup@ to run after systemd-tmpfiles-setup as ifupdown
    operations require /run/network which is being created by tmpfiles
    (LP: #1434020).

 -- Scott Moser <email address hidden> Fri, 20 Mar 2015 09:48:23 -0400

Changed in ntp (Ubuntu):
status: New → Fix Released
Revision history for this message
Alexander Adam (7ql6) wrote :

Should this issue be fixed on current Ubuntu 15.04?
Having systemd 219-7ubuntu6 installed, this issue still appears.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.