Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Dhcpd failing in 1.2.3-RC3 built on Tue Sep 8 00:18:28 UTC 2009

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    11 Posts 5 Posters 5.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jamesdean
      last edited by

      Dhcpd failing in 1.2.3-RC3 built on Tue Sep 8 00:18:28 UTC 2009.

      Anyone else having this issue.

      Sep 9 14:12:11 dhcpd: Internet Systems Consortium DHCP Server V3.0.7
      Sep 9 14:12:11 dhcpd: Copyright 2004-2008 Internet Systems Consortium.
      Sep 9 14:12:11 dhcpd: All rights reserved.
      Sep 9 14:12:11 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
      Sep 9 14:12:11 dhcpd: vr2: not found
      Sep 9 14:15:53 dhcpd: Internet Systems Consortium DHCP Server V3.0.7
      Sep 9 14:15:53 dhcpd: Copyright 2004-2008 Internet Systems Consortium.
      Sep 9 14:15:53 dhcpd: All rights reserved.
      Sep 9 14:15:53 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
      Sep 9 14:15:53 dhcpd: vr2: not found

      Fixed it by doing an up-grade to built on Tue Sep 8 23:17:53 UTC 2009.

      James

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Looks like it had a config for a network card that was missing from the system at the time it was running.

        A reboot may have fixed that if it was having trouble detecting the NIC, or it could have been something in that update.

        Remember: Upvote with the šŸ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • G
          garg_art2002
          last edited by

          @jimp:

          Looks like it had a config for a network card that was missing from the system at the time it was running.

          A reboot may have fixed that if it was having trouble detecting the NIC, or it could have been something in that update.

          DHCPD is not working in mine. I even used the latest snapshot using automatic update to point to :

          http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/.updaters

          I looked up under Status Services and it says DHCPD is stopped and is in red. Repeated click of start /play is also not able to fix this problem.

          Service

          Description

          Status
          dnsmasq DNS Forwarder
          Running
          [Restart Service] [Stop Service]
          ntpd NTP clock sync
          Running
          [Restart Service] [Stop Service]
          dhcpd DHCP Service
          Stopped

          1 Reply Last reply Reply Quote 0
          • W
            wallabybob
            last edited by

            Anything reported in Status -> System logsĀ  DHCP tab?

            1 Reply Last reply Reply Quote 0
            • G
              garg_art2002
              last edited by

              @wallabybob:

              Anything reported in Status -> System logsĀ  DHCP tab?

              Here is what I found as repetition (a few times):

              Oct 4 23:21:28 dhcpd: Internet Systems Consortium DHCP Server V3.0.7
              Oct 4 23:21:28 dhcpd: Copyright 2004-2008 Internet Systems Consortium.
              Oct 4 23:21:28 dhcpd: All rights reserved.
              Oct 4 23:21:28 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
              Oct 4 23:21:28 dhcpd: Wrote 0 deleted host decls to leases file.
              Oct 4 23:21:28 dhcpd: Wrote 0 new dynamic host decls to leases file.
              Oct 4 23:21:28 dhcpd: Wrote 0 leases to leases file.
              Oct 4 23:21:28 dhcpd: Listening on BPF/fxp1/00:02:b3šŸ’æad:50/192.168.3/24
              Oct 4 23:21:28 dhcpd: Sending on BPF/fxp1/00:02:b3šŸ’æad:50/192.168.3/24
              Oct 4 23:21:28 dhcpd: Sending on Socket/fallback/fallback-net
              Oct 4 23:21:28 dhcpd: There's already a DHCP server running

              1 Reply Last reply Reply Quote 0
              • G
                garg_art2002
                last edited by

                @wallabybob:

                Anything reported in Status -> System logsĀ  DHCP tab?

                Strange, that now DHCPD is up as per Status >> Services

                But it is not serving IP address to any machines on the lan.

                Any suggestions?

                1 Reply Last reply Reply Quote 0
                • W
                  wallabybob
                  last edited by

                  From the shell see if there is really a dhcpd running:

                  # ps ax | grep dhcpd
                  
                  

                  If so, kill every copy..

                  Is there a file containing the pid of a dhcp left over from a previous run of dhcpd?

                   # lsĀ  /var/dhcpd/var/run/dhcpd.pid 
                  

                  If so, delete it:

                  # rm /var/dhcpd/var/run/dhcpd.pid
                  

                  Then restart dhcpd (Uncheck the "Enable" box on the appropriate tab(s) under Services -> DHCP Server then click on Save, then check the box and click on Save)

                  Does dhcp service now work?

                  1 Reply Last reply Reply Quote 0
                  • G
                    garg_art2002
                    last edited by

                    This did the trick. I think this is working now.Ā  Here is the output from issuing those commands (I used pfsense DIAGNOSTICS >> COMMAND to do that):

                    
                    $ ps ax | grep dhcpd
                    39290Ā  ??Ā  IĀ  Ā  Ā  0:00.00 /usr/local/sbin/dnsmasq --all-servers -l /var/dhcpd/v
                    39410Ā  ??Ā  SĀ  Ā  Ā  0:00.00 sh -c ps ax | grep dhcpd
                    39412Ā  ??Ā  SĀ  Ā  Ā  0:00.00 grep dhcpd
                    
                    $ lsĀ  /var/dhcpd/var/run/dhcpd.pid
                    /var/dhcpd/var/run/dhcpd.pid
                    
                    $ rm /var/dhcpd/var/run/dhcpd.pid
                    
                    
                    1 Reply Last reply Reply Quote 0
                    • L
                      liontaur
                      last edited by

                      I'm having the same problem. I rebooted and it still wasn't working right. There were no dhcpd processes running according to ps but the logs said "There's already a DHCP server running." but when I deleted the PID file and unchecked the "Enable DHCP server on LAN interface" box, saved, then rechecked and saved it started working fine again.

                      Mine's a pretty plain installation. I'm using the captive portal, have the nut package installed, use the traffic shaper, have one WAN, one LAN and one OPT interface, use https for accessing pfsense…. that's about all the configuring i've done that I can think of.

                      I'll check it out a bit more tonight when nobody is needing access to the internet and post my findings, if any.

                      Mark

                      Edit: Forgot to mention, i'm using 1.2.3-RC3 built on Tue Oct 6 01:32:12 UTC 2009

                      Second edit: Perhaps the PID file doesn't get removed when the process is killed?

                      1 Reply Last reply Reply Quote 0
                      • W
                        wallabybob
                        last edited by

                        I suspect that if dhcpd is terminated by the operating system due to a programming bug (for instance accessing 'forbidden' memory) or a misdirected kill the .pid file won't be deleted. Then when dhcpd starts again it will see the .pid file and assume there is another copy of the dhcpd process running in the system.

                        Perhaps there is a .core file present which might be able to be used to further diagnose the problem.

                        If dhcpd is stopped through the recommended means it should delete the .pid file allowing it to be restarted such that service is resumed

                        1 Reply Last reply Reply Quote 0
                        • L
                          liontaur
                          last edited by

                          Well, I rebooted again and the problem didn't rear it's ugly head. The PID file was deleted and replaced by the system after reboot. I checked for any core files but there are none. I'm wondering if in my case it was just a glitch. I had updated from 1.2.3 RC2 just before I had this issue so maybe that had something to do with it. Either way i'm going to say that i'm good for now but i'll post again if it crops up again. Thanks guys.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.