Dhcpd crash



  • Pfsense 2.2.6

    keep getting problem on clients that says network not recognized, and after restarting the dhcp server they get fine.
    This is the log at every restart of dhcp server of pfsense:

    php-fpm[61302]: /status_services.php: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid fxp0' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.8 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Wrote 0 deleted host decls to leases file. Wrote 0 new dynamic host decls to leases file. Wrote 18 leases to leases file. Listening on BPF/fxp0/00:12:3f:a7:ef:a9/10.7.218.0/24 Sending on BPF/fxp0/00:12:3f:a7:ef:a9/10.7.218.0/24 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help.

    This is the only dhcp server in the network so what's the problem?



  • Looking at DHCP LOG:

    dhcpd: BOOTREQUEST from MAC via fxp0
    Feb 23 09:01:32	dhcpd: Wrote 19 leases to leases file.
    Feb 23 09:01:32	dhcpd: Wrote 0 new dynamic host decls to leases file.
    Feb 23 09:01:32	dhcpd: Wrote 0 deleted host decls to leases file.
    Feb 23 09:01:27	dhcpd: DHCPACK on X.X.X.20 to MAC via fxp0
    Feb 23 09:01:27	dhcpd: DHCPREQUEST for X.X.X.20 from MAC via fxp0
    Feb 23 08:24:16	dhcpd: DHCPACK on 10.7.218.32 to f4:31:c3:58:68:e4 via fxp0
    Feb 23 08:24:16	dhcpd: DHCPREQUEST for 10.7.218.32 from f4:31:c3:58:68:e4 via fxp0
    Feb 23 08:24:16      dhcpd: uid lease X.X.X.161 for client  MAC is duplicate on X.X.X.0/24
    

    the duplicate mac can be a problem?



  • I'm seeing this too, not often but it just happened last night.  I'm hoping that it's one of those little flukes that goes away with the 2.3 upgrade that should be out any day now.


Log in to reply