maas-dhcp upgrade to 1.9.5+bzr4599-0ubuntu1~14.04.1 fails to start installed isc-dhcp-server

Bug #1679322 reported by Jamon Camisso
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
maas (Ubuntu)
New
Undecided
Unassigned

Bug Description

An automatic update of maas-dhcp via landscape triggered alerts that DHCP was down on all controller nodes. The update appeared to stop any running dhcpd process, and failed to start the installed isc-dhcp-server dhcp.

Logs show messages like this:

Apr 3 13:40:18 kernel: [17717361.075006] init: isc-dhcp-server main process (15092) killed by TERM signal
Apr 3 13:40:28 maas.dhcp: [ERROR] DHCPv4 server failed to stop: 'maas-dhcpd' is unknown to upstart.
Apr 3 13:40:28 maas.dhcp: [ERROR] DHCPv4 server failed to stop: 'maas-dhcpd' is unknown to upstart.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi There,

Can you confirm that both your MAAS Region and Cluster controller are working as expected?
Can you attach logs? /var/log/maas/*.log
Can you restart your services? sudo service maas-regiond restart && sudo service maas-rackd restart
Can you attach the upstart job log?

Changed in maas (Ubuntu):
milestone: ubuntu-14.04.5 → none
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for maas (Ubuntu) because there has been no activity for 60 days.]

Changed in maas (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Alexandre Gomes (alejdg) wrote :

Here are the logs from the last occurrence.

/var/log/upstart/maas-dhcpd.log:

/var/lib/maas/dhcpd.conf does not exist. Aborting.
maas-dhcpd stop/pre-start, process 9058

/var/log/maas/maas.log: https://pastebin.canonical.com/207799/

/var/log/maas/clusterd.log: https://pastebin.canonical.com/207800/

Changed in maas (Ubuntu):
status: Expired → New
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Please att h logs from apt both the term and the history.

Changed in maas (Ubuntu):
status: New → Incomplete
Revision history for this message
Jamon Camisso (jamon) wrote :

Sure, here's term.log:

Log started: 2018-01-08 14:59:40
Log ended: 2018-01-08 15:00:02

Log started: 2018-01-10 14:53:41
Log ended: 2018-01-10 14:53:52

Log started: 2018-01-17 18:01:43
Log ended: 2018-01-17 18:01:59

And here's history.log from the same host:

Start-Date: 2018-01-17 18:01:43
Upgrade: python-maas-provisioningserver:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), maas-common:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), maas-cli:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), maas-dhcp:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), maas-cluster-controller:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), python-maas-client:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3)
End-Date: 2018-01-17 18:01:59

Junien F (axino)
Changed in maas (Ubuntu):
status: Incomplete → New
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.