/var/log/messages
--
I told you this was going to happen.
/var/log/messages
--
/dev/null
Odd....from what I can tell in there it seems as if dhcpd is working
just fine. Is there a way to narrow the search, or look elsewhere? I'm
running this command: cat messages|grep dhcpd|more. Nothing dhcpd
related shows up in there stating that the service stopped for any
reason. Maybe I should broaden the search for dhcp without the "d"?
try: grep -i dhcp /var/log/messages
Well, you could also check /var/log/daemon.log and /var/log/syslog
--
/dev/null
There's no daemon.log in there, and no syslog in /var/log/syslog.
Odd...
> Hello all, I'm new at Linux administration. Anyway, my dhcp keeps
> needing to be restarted. Where is the first place I could look to find
> out why?
Did you list the connection as a dialup? Problem with the connectors,
wiring or wireless connection?
More information would help.
The connected is ethernet. The machine is an Linux based Asterisk PBX.
It dynamically assigns IP addresses to the phone units. However, at
certain times throughout the week it just decides it doesn't want to
assign addresses via DHCP anymore. The logs don't seem to show any
errors. Now I'm not so sure if it's a DHCP with Asterisk problem, or
just Asterisk, or just DHCP. I'm new to all this, but I really want to
learn where to look to resolve the issue.
Thanks for the replies, btw.
Hmmm, DHCP server. Does it stop around the same time each week? No power
failures or max cpu utlization? Could the number of leases exceed the
range because expired leases aren't reclaimed fast enough, ie, you run
out of leases. Could your system delete or lock the dhcp.lease files?