[2.1b2] Service 'ntp' is SERVICE_STATE.ON but not in the expected state of 'running', its current state is 'exited'.

Bug #1631403 reported by Andres Rodriguez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Critical
Unassigned

Bug Description

Oct 7 14:42:36 maas2-integration maas.service_monitor: [WARNING] Service 'ntp' is SERVICE_STATE.ON but not in the expected state of 'running', its current state is 'exited'.
Oct 7 14:43:36 maas2-integration maas.service_monitor: [WARNING] Service 'ntp' is SERVICE_STATE.ON but not in the expected state of 'running', its current state is 'exited'.
Oct 7 14:44:36 maas2-integration maas.service_monitor: [WARNING] Service 'ntp' is SERVICE_STATE.ON but not in the expected state of 'running', its current state is 'exited'.
Oct 7 14:45:36 maas2-integration maas.service_monitor: [WARNING] Service 'ntp' is SERVICE_STATE.ON but not in the expected state of 'running', its current state is 'exited'.
Oct 7 14:46:36 maas2-integration maas.service_monitor: [WARNING] Service 'ntp' is SERVICE_STATE.ON but not in the expected state of 'running', its current state is 'exited'.
Oct 7 14:47:36 maas2-integration maas.service_monitor: [WARNING] Service 'ntp' is SERVICE_STATE.ON but not in the expected state of 'running', its current state is 'exited'.

3 ubuntu@maas2-integration:~⟫ sudo service ntp status
● ntp.service - LSB: Start NTP daemon
   Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
   Active: active (exited) since Fri 2016-10-07 01:52:38 UTC; 12h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 58048 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS)
  Process: 58061 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
    Tasks: 0
   Memory: 0B
      CPU: 0

after a manual restart

Oct 07 01:52:38 maas2-integration systemd[1]: Stopping LSB: Start NTP daemon...
Oct 07 01:52:38 maas2-integration ntp[58048]: * Stopping NTP server ntpd
Oct 07 01:52:38 maas2-integration systemd[1]: Stopped LSB: Start NTP daemon.
Oct 07 01:52:38 maas2-integration ntp[58048]: ...done.
Oct 07 01:52:38 maas2-integration systemd[1]: Starting LSB: Start NTP daemon...
Oct 07 01:52:38 maas2-integration ntp[58061]: * Starting NTP server ntpd
Oct 07 01:52:38 maas2-integration ntpd[28141]: ntpd exiting on signal 15 (Terminated)
Oct 07 01:52:38 maas2-integration ntpd[28141]: 91.189.89.199 local addr 10.244.192.10 -> <null>
Oct 07 01:52:38 maas2-integration ntpd[28141]: 91.189.94.4 local addr 10.244.192.10 -> <null>
Oct 07 01:52:38 maas2-integration ntp[58061]: ...done.
Oct 07 01:52:38 maas2-integration systemd[1]: Started LSB: Start NTP daemon.
Oct 07 01:52:38 maas2-integration ntpd[58073]: proto: precision = 0.054 usec (-24)
Oct 07 01:52:38 maas2-integration ntpd[58073]: unable to bind to wildcard address :: - another process may be running - EXITING
Oct 07 14:48:38 maas2-integration systemd[1]: Stopping LSB: Start NTP daemon...
Oct 07 14:48:38 maas2-integration ntp[38154]: * Stopping NTP server ntpd
Oct 07 14:48:38 maas2-integration ntp[38154]: start-stop-daemon: warning: failed to kill 58073: No such process
Oct 07 14:48:38 maas2-integration ntp[38154]: ...done.
Oct 07 14:48:38 maas2-integration systemd[1]: Stopped LSB: Start NTP daemon.
Oct 07 14:48:38 maas2-integration systemd[1]: Starting LSB: Start NTP daemon...
Oct 07 14:48:38 maas2-integration ntp[38166]: * Starting NTP server ntpd
Oct 07 14:48:38 maas2-integration ntp[38166]: ...done.
Oct 07 14:48:38 maas2-integration systemd[1]: Started LSB: Start NTP daemon.
Oct 07 14:48:38 maas2-integration ntpd[38176]: proto: precision = 0.047 usec (-24)
Oct 07 14:48:38 maas2-integration ntpd[38176]: Listen and drop on 0 v6wildcard [::]:123
Oct 07 14:48:38 maas2-integration ntpd[38176]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Oct 07 14:48:38 maas2-integration ntpd[38176]: Listen normally on 2 lo 127.0.0.1:123
Oct 07 14:48:38 maas2-integration ntpd[38176]: Listen normally on 3 eth0 10.244.192.10:123
Oct 07 14:48:38 maas2-integration ntpd[38176]: Listen normally on 4 eth1 192.168.224.244:123
Oct 07 14:48:38 maas2-integration ntpd[38176]: Listen normally on 5 lo [::1]:123
Oct 07 14:48:38 maas2-integration ntpd[38176]: Listen normally on 6 eth0 [fe80::216:3eff:fe1a:a56f%72]:123
Oct 07 14:48:38 maas2-integration ntpd[38176]: Listen normally on 7 eth1 [fe80::216:3eff:fe57:c27f%74]:123
Oct 07 14:48:38 maas2-integration ntpd[38176]: Listening on routing socket on fd #24 for interface updates
Oct 07 14:48:38 maas2-integration ntpd[38176]: start_kern_loop: ntp_loopfilter.c line 1126: ntp_adjtime: Operation not permitted
Oct 07 14:48:38 maas2-integration ntpd[38176]: set_freq: ntp_loopfilter.c line 1089: ntp_adjtime: Operation not permitted
Oct 07 14:48:39 maas2-integration ntpd[38176]: Soliciting pool server 91.189.89.198

Tags: oil
Changed in maas:
milestone: none → 2.1.0
importance: Undecided → Critical
tags: added: oil
Changed in maas:
status: New → Triaged
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Dear user,

This is an automated message.

We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.

Changed in maas:
status: Triaged → Won't Fix
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.