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