| 1 |
Fernando Rodriguez wrote: |
| 2 |
> On Thursday, September 03, 2015 8:09:02 PM Mike Edenfield wrote: |
| 3 |
>> For some reason, whenever I check the status of my startup scripts, |
| 4 |
>> dhcpd registers as "crashed". However, dhcpd is up and running and |
| 5 |
>> working fine. Normally I don't worry about it, but on those occasions |
| 6 |
>> where dhcpd does stop working, it's hard to tell if it's "fixed" or not. |
| 7 |
>> |
| 8 |
>> What makes rc-status think something is crashed, and how can I fix this? |
| 9 |
>> |
| 10 |
>> basement log # rc-status -v | grep crashed |
| 11 |
>> dhcpd [ crashed ] |
| 12 |
>> basement log # ps aux | grep dhcpd |
| 13 |
>> root 2214 0.0 0.0 8268 876 pts/0 S+ 19:47 0:00 grep |
| 14 |
>> --colour=auto dhcpd |
| 15 |
>> dhcp 2648 0.0 0.6 30028 12136 ? Ss Aug29 0:00 |
| 16 |
>> /usr/sbin/dhcpd -cf /etc/dhcp/dhcpd.conf -q -pf /var/run/dhcp/dhcpd.pid |
| 17 |
>> -lf /var/lib/dhcp/dhcpd.leases -user dhcp -group dhcp -chroot |
| 18 |
>> /chroot/dhcp enp0s7 |
| 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 |
|
| 27 |
I don't know if this will help or not but don't forget the zap option. |
| 28 |
|
| 29 |
root@fireball / # /etc/init.d/dhcpcd <tab twice> |
| 30 |
broken ineed iuse needsme pause restart start status |
| 31 |
stop usesme zap |
| 32 |
root@fireball / # /etc/init.d/dhcpcd |
| 33 |
|
| 34 |
It's been a long time since I used it but if I recall correctly that |
| 35 |
resets the status. I think it stops and deletes any files that stores |
| 36 |
its run status. |
| 37 |
|
| 38 |
If that doesn't apply, just ignore me. Heck, a lot of people ignore |
| 39 |
me. lol |
| 40 |
|
| 41 |
Dale |
| 42 |
|
| 43 |
:-) :-) |
Archives