Random system log messages
-
any reason why i am getting this message every 10-30 seconds?
dhcpd: uid lease 10.0.1.255 for client 00:07:e9:e2:80:93 is duplicate on 10.0.0/22
Subnet: 10.0.0.0
Subnet Mask: 255.255.252.0
Available range: 10.0.0.0 - 10.0.3.255Specified Range: 10.0.1.1 - 10.0.3.254
also i get this message every so often too
Aug 18 18:12:01 kernel: arpresolve: can't allocate route for 10.0.0.1
Aug 18 18:12:01 kernel: arplookup 10.0.0.1 failed: could not allocate llinfoalso also on the opentpd log tab i got this log entry and i do not have ntpd enabled
ntpdate[382]: step time server 128.10.252.1 offset 0.880973 sec
also when you hit clear log on any log tab you get this event in system log
Aug 19 08:44:09 syslogd: exiting on signal 15
Aug 19 08:41:58 syslogd: kernel boot file is /boot/kernel/kernel…
for every carp interface you get this error on startupAug 19 08:53:11 kernel: carp1: INIT -> MASTER (preempting)
Aug 19 08:53:10 kernel: arp_rtrequest: bad gateway [CARP-IP] (!AF_LINK)btw my current build is
1.2.1-RC1
built on Sun Aug 17 23:30:22 EDT 2008 -
any reason why i am getting this message every 10-30 seconds?
dhcpd: uid lease 10.0.1.255 for client 00:07:e9:e2:80:93 is duplicate on 10.0.0/22
That means something is answering ARP or pings (I don't recall which offhand, pretty sure it's pings) on that IP. It's probably one of two things - something has that address statically assigned, or there is a device with a wrong subnet mask on 10.0.1.0/24 that responds to traffic to its broadcast address.
also i get this message every so often too
Aug 18 18:12:01 kernel: arpresolve: can't allocate route for 10.0.0.1
Aug 18 18:12:01 kernel: arplookup 10.0.0.1 failed: could not allocate llinfo"Normal" in some circumstances, it doesn't affect functionality, and for that reason I haven't dedicated much effort to tracking down the cause.
also also on the opentpd log tab i got this log entry and i do not have ntpd enabled
ntpdate[382]: step time server 128.10.252.1 offset 0.880973 sec
ntpdate is what sets the system's time and it logs there, that's normal.
also when you hit clear log on any log tab you get this event in system log
Aug 19 08:44:09 syslogd: exiting on signal 15
Aug 19 08:41:58 syslogd: kernel boot file is /boot/kernel/kernelnormal.
Aug 19 08:53:11 kernel: carp1: INIT -> MASTER (preempting)
Aug 19 08:53:10 kernel: arp_rtrequest: bad gateway [CARP-IP] (!AF_LINK)Also normal, that one's been around for a while. Just log noise.
-
thank you for your time and help ;D