View Issue Details

IDProjectCategoryView StatusLast Update
0007990CentOS-7dhcppublic2014-12-13 06:22
Reporterrlj4214 Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status newResolutionopen 
PlatformAMD 64 bit X86 Asus SabertoothOSCentos 7OS VersionCurrent 12/12/14
Product Version7.0-1406 
Summary0007990: DHCP fils to start
DescriptionFailed to start dhcpd :
Redirecting to /bin/systemctl start dhcpd.service
Job for dhcpd.service failed. See 'systemctl status dhcpd.service' and 'journalctl -xn' for details.
[root@wopr ~]# systemctl status dhcpd.service
dhcpd.service - DHCPv4 Server Daemon
   Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; disabled)
   Active: failed (Result: exit-code) since Fri 2014-12-12 18:23:01 CST; 1min 2s ago
     Docs: man:dhcpd(8)
           man:dhcpd.conf(5)
  Process: 12960 ExecStart=/usr/sbin/dhcpd -f -cf /etc/dhcp/dhcpd.conf -user dhcpd -group dhcpd --no-pid (code=exited, status=1/FAILURE)
 Main PID: 12960 (code=exited, status=1/FAILURE)

Dec 12 18:23:01 wopr dhcpd[12960]: have been made to the base software release in order to make
Dec 12 18:23:01 wopr dhcpd[12960]: it work better with this distribution.
Dec 12 18:23:01 wopr dhcpd[12960]: Dec 12 18:23:01 wopr dhcpd[12960]: Please report for this software via the CentOS Bugs Database:
Dec 12 18:23:01 wopr dhcpd[12960]: http://bugs.centos.org/
Dec 12 18:23:01 wopr dhcpd[12960]: Dec 12 18:23:01 wopr dhcpd[12960]: exiting.
Dec 12 18:23:01 wopr systemd[1]: dhcpd.service: main process exited, code=exited, status=1/FAILURE
Dec 12 18:23:01 wopr systemd[1]: Failed to start DHCPv4 Server Daemon.
Dec 12 18:23:01 wopr systemd[1]: Unit dhcpd.service entered failed state.
[root@wopr ~]# journalctl -xn
-- Logs begin at Fri 2014-12-12 02:06:33 CST, end at Fri 2014-12-12 18:24:01 CST. --
Dec 12 18:23:01 wopr dhcpd[12960]: Please report for this software via the CentOS Bugs Database:
Dec 12 18:23:01 wopr dhcpd[12960]: http://bugs.centos.org/
Dec 12 18:23:01 wopr dhcpd[12960]: Dec 12 18:23:01 wopr dhcpd[12960]: exiting.
Dec 12 18:23:01 wopr systemd[1]: dhcpd.service: main process exited, code=exited, status=1/FAILURE
Dec 12 18:23:01 wopr systemd[1]: Failed to start DHCPv4 Server Daemon.
-- Subject: Unit dhcpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dhcpd.service has failed.
--
-- The result is failed.
Dec 12 18:23:01 wopr systemd[1]: Unit dhcpd.service entered failed state.
Dec 12 18:24:01 wopr systemd[1]: Starting Session 1561 of user root.
-- Subject: Unit session-1561.scope has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-1561.scope has begun starting up.
Dec 12 18:24:01 wopr systemd[1]: Started Session 1561 of user root.
-- Subject: Unit session-1561.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-1561.scope has finished starting up.
--
-- The start-up result is done.
Dec 12 18:24:01 wopr CROND[13015]: (root) CMD (/usr/local/ispconfig/server/server.sh &> /dev/null)
Steps To ReproduceI had it running a few of days ago but didn't have DNS set-up.
There was a system update and requested that a reboot
After the reboot I had like 6 or 7 "Auto Ethernet" instances all of which failed. It took a reboot to get to the point where I could delete them and go back to my known hardware set-up and make it work. It is a static IP address and this has cause much anger. Additionally there is a bridge vibr0. after the update there were several of them and all were junk.

I finally got the REAL HARDWARE NETWORK WORKING without all the BS.

Then I went in to set up DNS. After that was done I got the above failure and can't get rid of it AND THE DAMN AUTO ETHERNET BS IS BACK.
Additional InformationFailed to start dhcpd :
Redirecting to /bin/systemctl start dhcpd.service
Job for dhcpd.service failed. See 'systemctl status dhcpd.service' and 'journalctl -xn' for details.
[root@wopr ~]# systemctl status dhcpd.service
dhcpd.service - DHCPv4 Server Daemon
   Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; disabled)
   Active: failed (Result: exit-code) since Fri 2014-12-12 18:23:01 CST; 1min 2s ago
     Docs: man:dhcpd(8)
           man:dhcpd.conf(5)
  Process: 12960 ExecStart=/usr/sbin/dhcpd -f -cf /etc/dhcp/dhcpd.conf -user dhcpd -group dhcpd --no-pid (code=exited, status=1/FAILURE)
 Main PID: 12960 (code=exited, status=1/FAILURE)

Dec 12 18:23:01 wopr dhcpd[12960]: have been made to the base software release in order to make
Dec 12 18:23:01 wopr dhcpd[12960]: it work better with this distribution.
Dec 12 18:23:01 wopr dhcpd[12960]: Dec 12 18:23:01 wopr dhcpd[12960]: Please report for this software via the CentOS Bugs Database:
Dec 12 18:23:01 wopr dhcpd[12960]: http://bugs.centos.org/
Dec 12 18:23:01 wopr dhcpd[12960]: Dec 12 18:23:01 wopr dhcpd[12960]: exiting.
Dec 12 18:23:01 wopr systemd[1]: dhcpd.service: main process exited, code=exited, status=1/FAILURE
Dec 12 18:23:01 wopr systemd[1]: Failed to start DHCPv4 Server Daemon.
Dec 12 18:23:01 wopr systemd[1]: Unit dhcpd.service entered failed state.
[root@wopr ~]# journalctl -xn
-- Logs begin at Fri 2014-12-12 02:06:33 CST, end at Fri 2014-12-12 18:24:01 CST. --
Dec 12 18:23:01 wopr dhcpd[12960]: Please report for this software via the CentOS Bugs Database:
Dec 12 18:23:01 wopr dhcpd[12960]: http://bugs.centos.org/
Dec 12 18:23:01 wopr dhcpd[12960]: Dec 12 18:23:01 wopr dhcpd[12960]: exiting.
Dec 12 18:23:01 wopr systemd[1]: dhcpd.service: main process exited, code=exited, status=1/FAILURE
Dec 12 18:23:01 wopr systemd[1]: Failed to start DHCPv4 Server Daemon.
-- Subject: Unit dhcpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dhcpd.service has failed.
--
-- The result is failed.
Dec 12 18:23:01 wopr systemd[1]: Unit dhcpd.service entered failed state.
Dec 12 18:24:01 wopr systemd[1]: Starting Session 1561 of user root.
-- Subject: Unit session-1561.scope has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-1561.scope has begun starting up.
Dec 12 18:24:01 wopr systemd[1]: Started Session 1561 of user root.
-- Subject: Unit session-1561.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-1561.scope has finished starting up.
--
-- The start-up result is done.
Dec 12 18:24:01 wopr CROND[13015]: (root) CMD (/usr/local/ispconfig/server/server.sh &> /dev/null)
TagsNo tags attached.
abrt_hash
URL

Activities

rlj4214

rlj4214

2014-12-13 01:25

reporter  

DHCP fail.odt (22,541 bytes)
Evolution

Evolution

2014-12-13 03:35

reporter   ~0021931

You haven't provided any steps to reproduce this issue.

Off hand it sounds like you have both the network and Network Manager services conflicting, as well as a possible error in your dhcpd.conf

Please provide the dhcpd.conf you're using, as well as more details (with less emotion please, it doesn't help in a bug report).
Evolution

Evolution

2014-12-13 03:36

reporter   ~0021932

The last line of your log shows a reference to ispconfig. Have you installed this on your system?
rlj4214

rlj4214

2014-12-13 06:22

reporter   ~0021933

My apologies for the emotion. Frustration had set in.

After going nuts for what seems like a lifetime I went back and redid the entire system from an image I made before this happened and have configured it manually.

I guess we'll see what happens when it updates.

The scenario is as follows.

I wanted to try Webmin had it set up and had gone through the system and I ran across ISPConfig and thought it looked interesting so I tried it.

DHCP was working fine but DNS was not set up so I disabled DHCP.
I played with the programs mentioned above and decided that I did not like ISPConfig that much and chose Webmin for some say to day stuff. ISPConfig is now removed.

I set up the DNS server and found a couple of errors in the config file and while I was researching them the system apparently downloaded an update. When I went to reboot it asked if I wanted to install the updates so I figured sure.

I rebooted and everything was totaled apparently due to the network interfaces. There were several, literally several, bridges and and Automatic Ethernet interfaces listed, some seemed persistent.

I tried to get is all running again and failed. If frustration I imaged the system again.

I went through the configuration again manually and it seems to be working again for now.

But recall it was working before the system was updated.

I think something got jumbled in the download but obviously that is a really ignorant guess.

After this next update I will pursue this further if necessary.

Again I apologize. This has been one of those weeks and it felt like Friday the 13th all day. Thank you for your help. Take care.

There are others that have reported similar problems starting DHCP elsewhere but I don't think it was their network interfaces.

You can close this if you like and I'll add later after another update and of course after I image it again.

Issue History

Date Modified Username Field Change
2014-12-13 01:25 rlj4214 New Issue
2014-12-13 01:25 rlj4214 File Added: DHCP fail.odt
2014-12-13 03:35 Evolution Note Added: 0021931
2014-12-13 03:36 Evolution Note Added: 0021932
2014-12-13 06:22 rlj4214 Note Added: 0021933