Bug 4353

Summary: dhcpd service not running after boot. (systemd)
Product: Mageia Reporter: Bit Twister <bittwister2>
Component: RPM PackagesAssignee: Stew Benedict <stewbintn>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: dmorganec
Version: CauldronKeywords: Triaged
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: dhcp CVE:
Status comment:
Bug Depends on:    
Bug Blocks: 2120    
Attachments: logs and configuration information.

Description Bit Twister 2012-01-30 22:25:01 CET
Description of problem:

dhcpd service not running after boot.

# systemctl status dhcpd.service
dhcpd.service - LSB: Start and stop the DHCP server
          Loaded: loaded (/etc/rc.d/init.d/dhcpd)
          Active: inactive (dead)
          CGroup: name=systemd:/system/dhcpd.service

See attachment to prove it will start and run.

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. clean alpha3 install, apply updates
2. configure /etc/dhcpd.conf
3. systemctl enable dhcpd.service
2. /bin/cp /dev/null /var/log/messages
3. reboot
4. grep "DHCP Server" /var/log/messages
Comment 1 Bit Twister 2012-01-30 22:25:49 CET
Created attachment 1467 [details]
logs and configuration information.
Comment 2 Manuel Hiebel 2012-01-31 10:54:43 CET
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Blocks: (none) => 2120
Assignee: bugsquad => stewbintn
Summary: 2_a3: dhcpd service not running after boot. => dhcpd service not running after boot. (systemd)
Source RPM: systemd-39-3.mga2.src.rpm => dhcp

Comment 3 D Morgan 2012-01-31 15:28:10 CET
what is the dhcp version you have installed ?

CC: (none) => dmorganec

Comment 4 D Morgan 2012-01-31 16:03:12 CET
can you test new dhcp rpms ?
Comment 5 Bit Twister 2012-01-31 20:04:40 CET
(In reply to comment #4)
> can you test new dhcp rpms ?

What is the general policy on enable/disable service upon a rpm release?
Or should I create bug reports on each one I dislike?

IIRC, the old method was to en/disable based on current setting, but with systemd it is not. 

I have seen an Apache doc update, re-enable/start httpd, and this dhcp update disabled dhcpd.service which is not funny if node is being managed remotely.

I enabled it, rebooted, and it worked this time.
Comment 6 D Morgan 2012-01-31 22:30:14 CET
yes we have to deal with sysvinit -> systemd migration because for now we only enable systemd services at first install.

We had a script from fedora for this but it required python so this is a nogo as it meant python deps on minimal install, but coling will look at this ( this will be OK for mageia 2 ).

So if after enabling manually it works i close this bugreport.

thank you for your feedback.

Status: NEW => RESOLVED
Resolution: (none) => FIXED