On Thursday, September 03, 2015 8:09:02 PM Mike Edenfield wrote: > For some reason, whenever I check the status of my startup scripts, > dhcpd registers as "crashed". However, dhcpd is up and running and > working fine. Normally I don't worry about it, but on those occasions > where dhcpd does stop working, it's hard to tell if it's "fixed" or not. > > What makes rc-status think something is crashed, and how can I fix this? > > basement log # rc-status -v | grep crashed > dhcpd [ crashed ] > basement log # ps aux | grep dhcpd > root 2214 0.0 0.0 8268 876 pts/0 S+ 19:47 0:00 grep > --colour=auto dhcpd > dhcp 2648 0.0 0.6 30028 12136 ? Ss Aug29 0:00 > /usr/sbin/dhcpd -cf /etc/dhcp/dhcpd.conf -q -pf /var/run/dhcp/dhcpd.pid > -lf /var/lib/dhcp/dhcpd.leases -user dhcp -group dhcp -chroot > /chroot/dhcp enp0s7 > >
This is just a guess but it could be the permissions on the pid file on /chroot/dhcp/var/run/dhcp/. So stop the daemon, delete the file, check that the directory is owned by dhcp:dhcp and start the daemon again. -- Fernando Rodriguez
