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