Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMichal Sekletar
2014-03-18 11:40:25 UTC
Description of problem:
Syntax and semantics of dhcpd configuration file is quite complex and it is easy to make a typo or mistake. Unfortunately dhcpd.service doesn't include Type= configuration option hence it is run by systemd as default service type (Type=simple).
If admin issues "systemctl start dhcpd.service" command and dhcpd is *miscofigured* then systemd will spawn the new process and doesn't care anymore. However dhcpd will fail microseconds after that because of errors in config file. Administrator is not presented with any information whatsoever and without checking dhcpd status he has no clue that service is not running.
Version-Release number of selected component (if applicable):
dhcp-4.2.5-27.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. make an error in /etc/dhcp/dhcpd.conf
2. systemctl start dhcpd.service
Actual results:
No output. Return code of systemctl command is 0.
Expected results:
Error is reported.
Additional info:
In order to achieve expected result one can use sd_notify() facilities provided by systemd. This way daemon can notify init system that it is really able to serve incomming requests. See attached patch.