dhcp3-server automatically starts ignoring startup rules on package update

Bug #513749 reported by lordcerber
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dhcp3 (Ubuntu)
Expired
Low
Unassigned

Bug Description

recent security upgrade started dhcp3-server even it was forbidden to start. It caused troubles in local network. As the network-important service it must do status checks if it is allowed to start or not.

more of all - it was a security update so it was installed automatically- at night time, and troubles came in the morning already network-wide

the log
Log started: 2010-01-28 07:46:12
(Reading database ... 199239 files and directories currently installed.)
Preparing to replace dhcp3-server 3.1.1-5ubuntu8.1 (using .../dhcp3-server_3.1.1-5ubuntu8.2_i386.deb) ...
 * Stopping DHCP server dhcpd3
   ...fail!
Unpacking replacement dhcp3-server ...
Preparing to replace dhcp3-client 3.1.1-5ubuntu8.1 (using .../dhcp3-client_3.1.1-5ubuntu8.2_i386.deb) ...
Unpacking replacement dhcp3-client ...
Preparing to replace dhcp3-common 3.1.1-5ubuntu8.1 (using .../dhcp3-common_3.1.1-5ubuntu8.2_i386.deb) ...
Unpacking replacement dhcp3-common ...
Processing triggers for man-db ...
Setting up dhcp3-common (3.1.1-5ubuntu8.2) ...
Setting up dhcp3-server (3.1.1-5ubuntu8.2) ...
 * Reloading AppArmor profiles ...
   ...done.
 * Starting DHCP server dhcpd3
   ...done.

Setting up dhcp3-client (3.1.1-5ubuntu8.2) ...
 * Reloading AppArmor profiles ...
   ...done.

Log ended: 2010-01-28 07:47:02

Revision history for this message
Mathias Gug (mathiaz) wrote :

How did you forbid dhcp3-server to start?

Changed in dhcp3 (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
lordcerber (lordcerber) wrote :

as in manual by renaming link S10dhcp3-server to K10dhcp3-server in proper /etc/rc*/ dir and running update-rc.d script defaults

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in dhcp3 (Ubuntu):
status: Incomplete → Expired
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.