Fedora Linux Support Community & Resources Center

Home Forums Posting Rules Linux Help Fedora Set-Up Guides Ask Fedora Fedora Project
Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
Reload this Page dhcpd wont start at reboot but runs fine when service dhcpd restart
FedoraForum Search
Forgot Password? Join Us!
Register All Albums FAQ Search Today's Posts Mark Forums Read

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 8th June 2010, 07:44 PM
fireater Offline
Registered User
  
Join Date: Jun 2010
Posts: 2
linuxfedorafirefox
Smile dhcpd wont start at reboot but runs fine when service dhcpd restart
ok
odd problem ..dhcpd fails in bootup but runs fine when i start it manually
heres the problem i see in messages log
Jun 8 11:41:23 sphincter3 ntpd[1540]: Listening on routing socket on fd #21 for interface updates
Jun 8 11:41:23 sphincter3 ntpd[1540]: 0.0.0.0 c016 06 restart
Jun 8 11:41:23 sphincter3 ntpd[1540]: 0.0.0.0 c012 02 freq_set kernel -1.232 PPM
Jun 8 11:41:23 sphincter3 dhcpd: Internet Systems Consortium DHCP Server 4.1.1
Jun 8 11:41:23 sphincter3 dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Jun 8 11:41:23 sphincter3 dhcpd: All rights reserved.
Jun 8 11:41:23 sphincter3 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Jun 8 11:41:23 sphincter3 dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Jun 8 11:41:23 sphincter3 dhcpd: Wrote 1 leases to leases file.
Jun 8 11:41:24 sphincter3 avahi-daemon[1350]: Registering new address record for fe80::290:27ff:fe13:be28 on eth0.*.
Jun 8 11:41:24 sphincter3 dhcpd:
Jun 8 11:41:24 sphincter3 dhcpd: No subnet declaration for eth1 (no IPv4 addresses).
Jun 8 11:41:24 sphincter3 dhcpd: ** Ignoring requests on eth1. If this is not what
Jun 8 11:41:24 sphincter3 dhcpd: you want, please write a subnet declaration
Jun 8 11:41:24 sphincter3 dhcpd: in your dhcpd.conf file for the network segment
Jun 8 11:41:24 sphincter3 dhcpd: to which interface eth1 is attached. **
Jun 8 11:41:24 sphincter3 dhcpd:
Jun 8 11:41:24 sphincter3 dhcpd:
Jun 8 11:41:24 sphincter3 dhcpd: Not configured to listen on any interfaces!
Jun 8 11:41:24 sphincter3 dhcpd:
Jun 8 11:41:24 sphincter3 dhcpd: This version of ISC DHCP is based on the release available
Jun 8 11:41:24 sphincter3 dhcpd: on ftp.isc.org. Features have been added and other changes
Jun 8 11:41:24 sphincter3 dhcpd: have been made to the base software release in order to make
Jun 8 11:41:24 sphincter3 dhcpd: it work better with this distribution.
Jun 8 11:41:24 sphincter3 dhcpd:
Jun 8 11:41:24 sphincter3 dhcpd: Please report for this software via the Red Hat Bugzilla site:
Jun 8 11:41:24 sphincter3 dhcpd: http://bugzilla.redhat.com
Jun 8 11:41:24 sphincter3 dhcpd:
Jun 8 11:41:24 sphincter3 dhcpd: exiting.
Jun 8 11:41:24 sphincter3 NetworkManager[1339]: <info> (eth0): device state change: 7 -> 8 (reason 0)
Jun 8 11:41:24 sphincter3 NetworkManager[1339]: <info> Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS.
Jun 8 11:41:24 sphincter3 NetworkManager[1339]: <info> Activation (eth0) successful, device activated.
Jun 8 11:41:24 sphincter3 NetworkManager[1339]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 8 11:41:24 sphincter3 abrtd: Registered Analyzer plugin 'Kerneloops'
Jun 8 11:41:24 sphincter3 abrtd: Registered Analyzer plugin 'CCpp'
Jun 8 11:41:24 sphincter3 abrtd: Registered Reporter plugin 'Logger'
Jun 8 11:41:24 sphincter3 abrtd: Registered Analyzer plugin 'Python'
Jun 8 11:41:24 sphincter3 abrtd: Registered Reporter plugin 'KerneloopsReporter'
Jun 8 11:41:24 sphincter3 abrtd: Registered Action plugin 'KerneloopsScanner'
Jun 8 11:41:24 sphincter3 abrtd: Registered Reporter plugin 'Bugzilla'
Jun 8 11:41:24 sphincter3 abrtd: Init complete, entering main loop
Jun 8 11:41:25 sphincter3 kernel: e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> (eth1): carrier now ON (device state 2)
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> (eth1): device state change: 2 -> 3 (reason 40)
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) starting connection 'System eth1'
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> (eth1): device state change: 3 -> 4 (reason 0)
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jun 8 11:41:25 sphincter3 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> (eth1): device state change: 4 -> 5 (reason 0)
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) successful.
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> (eth1): device state change: 5 -> 7 (reason 0)
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) started...
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) complete.
Jun 8 11:41:25 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Jun 8 11:41:25 sphincter3 avahi-daemon[1350]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.3.1.
Jun 8 11:41:25 sphincter3 avahi-daemon[1350]: New relevant interface eth1.IPv4 for mDNS.
Jun 8 11:41:25 sphincter3 avahi-daemon[1350]: Registering new address record for 192.168.3.1 on eth1.IPv4.
Jun 8 11:41:26 sphincter3 smbd[1672]: [2010/06/08 11:41:26.067978, 0] smbd/server.c:500(smbd_open_one_socket)
Jun 8 11:41:26 sphincter3 smbd[1672]: smbd_open_once_socket: open_socket_in: Address already in use
Jun 8 11:41:26 sphincter3 smbd[1672]: [2010/06/08 11:41:26.068474, 0] smbd/server.c:500(smbd_open_one_socket)
Jun 8 11:41:26 sphincter3 smbd[1672]: smbd_open_once_socket: open_socket_in: Address already in use
Jun 8 11:41:26 sphincter3 NetworkManager[1339]: <info> Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS.
Jun 8 11:41:26 sphincter3 NetworkManager[1339]: <info> (eth1): device state change: 7 -> 8 (reason 0)
Jun 8 11:41:26 sphincter3 NetworkManager[1339]: <info> Activation (eth1) successful, device activated.
Jun 8 11:41:26 sphincter3 NetworkManager[1339]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
Jun 8 11:41:26 sphincter3 ntpd[1540]: Listen normally on 5 eth1 192.168.3.1 UDP 123
Jun 8 11:41:26 sphincter3 ntpd[1540]: Listen normally on 6 eth0 fe80::290:27ff:fe13:be28 UDP 123



Note dhcpd is trying to run before eth1 is up
why is network manager not waiting for the interfaces before allowing the next thing to run in init? I read its because ivp6 returns a default address so it skips ahead... is there a fix or do i just put in a delay?..and by the way not sure how to put in a delay...

---------- Post added at 01:44 PM CDT ---------- Previous post was at 12:12 PM CDT ----------

added a line "NETWORKWAIT=yes in /etc/sysconfig/network"

fixed
Reply With Quote
Reply

Tags
dhcpd, fine, reboot, restart, runs, service, start

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
DHCPD service not starting on boot erasmix Using Fedora 2 20th January 2010 01:41 AM
Help,Why the dhcpd service always not start? bear Fedora Focus 2 5th December 2005 01:52 AM


Current GMT-time: 21:25 (Saturday, 25-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.
Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

 FedoraForum is Powered by RedHat