  Vyper28
@dccnet.com
| reply to Vyper28 Re: DCCNET/EASLINK - Packet loss/stutter?
The spikes have continued consistently, dropping all teh machines on the network repeatedly. Really getting frustrated. I went into my router settings and turned on all the types of logging, and these are the only messages I'm getting:
Jul 1 19:30:01 ? cron.err crond[31121]: USER root pid 31805 cmd rcheck --cron Jul 1 19:40:01 ? cron.err crond[31121]: USER root pid 31809 cmd ntpsync --cron Jul 1 19:40:12 ? user.info ntpc[31810]: Time Updated: Wed, 01 Jul 2009 19:40:12 -0700 [+11s] Jul 1 19:45:01 ? cron.err crond[31121]: USER root pid 31823 cmd rcheck --cron Jul 1 20:00:01 ? cron.err crond[31121]: USER root pid 31826 cmd logger -p syslog.info -- -- MARK -- Jul 1 20:00:01 ? cron.err crond[31121]: USER root pid 31827 cmd rcheck --cron Jul 1 20:00:01 ? syslog.info root: -- MARK -- Jul 1 20:15:01 ? cron.err crond[31121]: USER root pid 31832 cmd rcheck --cron Jul 1 20:30:01 ? cron.err crond[31121]: USER root pid 31835 cmd rcheck --cron Jul 1 20:45:01 ? cron.err crond[31121]: USER root pid 31839 cmd rcheck --cron Jul 1 20:53:49 ? daemon.info dnsmasq[136]: DHCPREQUEST(br0) 192.168.1.108 04:4b:80:80:80:03 Jul 1 20:53:49 ? daemon.info dnsmasq[136]: DHCPACK(br0) 192.168.1.108 04:4b:80:80:80:03 user-f3045470bf Jul 1 20:53:49 ? daemon.warn dnsmasq[136]: not giving name mom-26452b09508 to the DHCP lease of 192.168.1.106 because the name exists in /etc/hosts.dnsmasq with address 192.168.1.110 Jul 1 20:53:49 ? daemon.warn dnsmasq[136]: not giving name user-e781d77954 to the DHCP lease of 192.168.1.100 because the name exists in /etc/hosts.dnsmasq with address 192.168.1.105 Jul 1 21:00:01 ? cron.err crond[31121]: USER root pid 31842 cmd logger -p syslog.info -- -- MARK -- Jul 1 21:00:01 ? cron.err crond[31121]: USER root pid 31843 cmd rcheck --cron Jul 1 21:00:01 ? syslog.info root: -- MARK -- Jul 1 21:06:59 ? daemon.info dnsmasq[136]: DHCPINFORM(br0) 192.168.1.100 00:1a:92:7d:5a:f0 Jul 1 21:06:59 ? daemon.info dnsmasq[136]: DHCPACK(br0) 192.168.1.100 00:1a:92:7d:5a:f0 user-e781d77954 Jul 1 21:15:01 ? cron.err crond[31121]: USER root pid 31883 cmd rcheck --cron Jul 1 21:30:01 ? cron.err crond[31121]: USER root pid 31885 cmd rcheck --cron Jul 1 21:45:01 ? cron.err crond[31121]: USER root pid 31898 cmd rcheck --cron Jul 1 22:00:01 ? cron.err crond[31121]: USER root pid 31900 cmd logger -p syslog.info -- -- MARK -- Jul 1 22:00:01 ? cron.err crond[31121]: USER root pid 31901 cmd rcheck --cron Jul 1 22:00:01 ? syslog.info root: -- MARK --
Are they any help in finding out what the problem is? |