Failure in ntpd start on bootstrap

Bug #1385627 reported by Mike Scherbakov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
High
Fuel Library (Deprecated)

Bug Description

I used vbox scripts to run ISO
VERSION:
  feature_groups:
    - experimental
  production: "docker"
  release: "6.0"
  api: "1.0"
  build_number: "176"
  build_id: "2014-10-24_03-28-01"
  astute_sha: "97eea90efe0a1f17b4934919d6e459d270c10372"
  fuellib_sha: "cf39a7503c5a6006ed7a4f2b46b2ef43d7d4dda8"
  ostf_sha: "de177931b53fbe9655502b73d03910b8118e25f1"
  nailgun_sha: "dcf7f0de85364b8d059bcd30015b37ec8d6da36d"
  fuelmain_sha: "7b34d04edb929659dad5fa4ddb224346d4e74ec3"

When bootstrap nodes started, ntpd service didn't start and I saw "FAILED" on console screen. See attachment. As this is the first thing which users see after they try Fuel with VirtualBox scripts, it significantly affects User Experience too.

In /var/log/messages of that bootstrap node:
2014-10-24T17:44:13Z notice ntpdate-log: /usr/sbin/ntpdate -U ntp -s -b 10.20.0.2
2014-10-24T17:44:13Z notice ntpdate-log: /usr/sbin/ntpdate -U ntp -s -b 10.20.0.2
2014-10-24T17:44:13Z notice ntpdate[891]: ntpdate 4.2.6p5@1.2349-o Sat Nov 23 18:21:48 UTC 2013 (1)
2014-10-24T17:44:13Z err ntpdate[891]: no server suitable for synchronization found
2014-10-24T17:44:14Z err ntpdate[892]: no server suitable for synchronization found
2014-10-24T17:44:24Z err ntpdate[894]: no server suitable for synchronization found
2014-10-24T17:44:44Z err ntpdate[896]: no server suitable for synchronization found
2014-10-24T17:44:44Z notice ntpd[899]: ntpd 4.2.6p5@1.2349-o Sat Nov 23 18:21:48 UTC 2013 (1)
2014-10-24T17:44:44Z notice ntpd[900]: proto: precision = 0.058 usec
2014-10-24T17:44:44Z info ntpd[900]: 0.0.0.0 c01d 0d kern kernel time sync enabled
2014-10-24T17:44:44Z info ntpd[900]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
2014-10-24T17:44:44Z info ntpd[900]: Listen and drop on 1 v6wildcard :: UDP 123
2014-10-24T17:44:44Z info ntpd[900]: Listen normally on 2 lo 127.0.0.1 UDP 123
2014-10-24T17:44:44Z info ntpd[900]: Listen normally on 3 eth0 10.20.0.131 UDP 123
2014-10-24T17:44:44Z info ntpd[900]: Listen normally on 4 lo ::1 UDP 123
2014-10-24T17:44:44Z info ntpd[900]: Listen normally on 5 eth1 fe80::a00:27ff:fec5:4e60 UDP 123
2014-10-24T17:44:44Z info ntpd[900]: Listen normally on 6 eth2 fe80::a00:27ff:fe11:6397 UDP 123
2014-10-24T17:44:44Z info ntpd[900]: Listen normally on 7 eth0 fe80::a00:27ff:fe4d:fc5c UDP 123
2014-10-24T17:44:44Z info ntpd[900]: peers refreshed
2014-10-24T17:44:44Z info ntpd[900]: Listening on routing socket on fd #24 for interface updates
2014-10-24T17:44:44Z info ntpd[900]: 0.0.0.0 c016 06 restart
2014-10-24T17:44:44Z info ntpd[900]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM
2014-10-24T18:20:36Z info ntpd[900]: 0.0.0.0 c61c 0c clock_step +2145.461993 s
2014-10-24T18:20:36Z info ntpd[900]: 0.0.0.0 c614 04 freq_mode
2014-10-24T18:20:37Z info ntpd[900]: 0.0.0.0 c618 08 no_sys_peer

Tags: ntp
Revision history for this message
Mike Scherbakov (mihgen) wrote :
Revision history for this message
Mike Scherbakov (mihgen) wrote :
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.