Description of problem: If configured dhcpd to start at boot. But it never starts, automatically nor manually. ● dhcpd.service - DHCPv4 Server Daemon Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; enabled; vendor preset: disabled) Active: failed (Result: timeout) since Mon 2020-12-14 09:03:42 CET; 32min ago Docs: man:dhcpd(8) man:dhcpd.conf(5) Process: 2147 ExecStart=/usr/sbin/dhcpd -f -cf /etc/dhcp/dhcpd.conf -user dhcpd -group dhcpd --no-pid $DHCPDARGS (code=killed, signal=TERM) Main PID: 2147 (code=killed, signal=TERM) CPU: 62ms déc. 14 09:02:13 localhost dhcpd[2147]: Source compiled to use binary-leases déc. 14 09:02:13 localhost dhcpd[2147]: Wrote 0 class decls to leases file. déc. 14 09:02:13 localhost dhcpd[2147]: Wrote 0 leases to leases file. déc. 14 09:02:13 localhost dhcpd[2147]: Listening on LPF/enp0s3/08:00:27:0c:1b:5f/192.168.1.0/24 déc. 14 09:02:13 localhost dhcpd[2147]: Sending on LPF/enp0s3/08:00:27:0c:1b:5f/192.168.1.0/24 déc. 14 09:02:13 localhost dhcpd[2147]: Sending on Socket/fallback/fallback-net déc. 14 09:02:13 localhost dhcpd[2147]: Server starting service. déc. 14 09:03:42 localhost systemd[1]: dhcpd.service: start operation timed out. Terminating. déc. 14 09:03:42 localhost systemd[1]: dhcpd.service: Failed with result 'timeout'. déc. 14 09:03:42 localhost systemd[1]: Failed to start DHCPv4 Server Daemon.
Created attachment 12077 [details] Configuration file This file is generated with a patched drakwizard-dhcp, to allow detecting used interface. Note that drakwizard writes this file in /etc/dhcpd.conf, although dhcp is launched using /etc/dhcp/dhcpd.conf. Is this a wanted change? How users have to manage that in migrating from 7 to 8?
See also https://www.mageialinux-online.org/forum/topic-28180+assistant-dhcp.php
(In reply to papoteur from comment #1) > Note that drakwizard writes this file in > /etc/dhcpd.conf > although dhcp is launched using > /etc/dhcp/dhcpd.conf ******** > Is this a wanted change? How users have to manage that in migrating > from 7 to 8? $ urpmf /etc/dhcp/dhcpd.conf yields nothing, so that path seems not to be provided. $ urpmf /etc/dhcpd.conf dhcp-server:/etc/dhcpd.conf $ urpmq -l dhcp-server | grep /etc /etc/dhcpd.conf It seems worth resolving this path difference at least. Can the customer try linking (should not need to be symbolic) the two: # ln /etc/dhcpd.conf /etc/dhcp/dhcpd.conf to see whether that sorts the problem?
Source RPM: dhcp-server-4.4.2-6.mga8 => dhcp-4.4.2-6.mga8.src.rpmCC: (none) => lewyssmithSummary: dhcpd.service doesn't start, ends with timeout => dhcpd.service doesn't start, ends with timeout. Is dhcpd.conf in the wrong place?
Silly me. I imagine there is a need to create /etc/dhcp/ first.
Someone made a mess out of the service files in a recent commit. Should be fixed in dhcp-4.4.2-7.mga8
Should be available now.
Resolution: (none) => FIXEDStatus: NEW => RESOLVEDCC: (none) => luigiwalser
still persists on 4.2.2-8
CC: (none) => pim7djEver confirmed: 1 => 0Status: RESOLVED => UNCONFIRMEDResolution: FIXED => (none)
We know. *** This bug has been marked as a duplicate of bug 28358 ***
Resolution: (none) => DUPLICATEStatus: UNCONFIRMED => RESOLVED
dhcpd itself is okay The problem is within systemd / systemctl script.
Status: RESOLVED => REOPENEDEver confirmed: 0 => 1Resolution: DUPLICATE => (none)
Resolution: (none) => DUPLICATEStatus: REOPENED => RESOLVED