Nope, most definitely not. Actually.. You may be right. I did get an email from sprint, the provider in question saying they were making some changes to the reachability of those IPs.. Now I really have a delima.
Thanks for your help!! _____ From: Bowler, Michael [mailto:[EMAIL PROTECTED] Sent: Friday, March 05, 2004 2:00 PM To: 'James Nelson' Subject: RE: [mrtg] Re: mrtg restart problems Could the IP addresses have changed? or DNS? -----Original Message----- From: James Nelson [mailto:[EMAIL PROTECTED] Sent: Friday, March 05, 2004 1:57 PM To: Bowler, Michael Subject: RE: [mrtg] Re: mrtg restart problems WARNING: Could not match host:'[EMAIL PROTECTED]:' ref:'Ip' key:'x.x.x.a' WARNING: Could not match host:'[EMAIL PROTECTED]:' ref:'Ip' key:'x.x.x.b' Ok, so something is wrong here I assume? Key is naturally our private key, border1 is the router and x.x.x.a/b is the IP address of the specific interface. What's gotten screwed up? _____ From: Bowler, Michael [mailto:[EMAIL PROTECTED] Sent: Friday, March 05, 2004 1:47 PM To: 'James Nelson' Subject: RE: [mrtg] Re: mrtg restart problems <path-to>/mrtg <path-to>/mrtg.cfg --logging <path-to>/<logfile> -----Original Message----- From: James Nelson [mailto:[EMAIL PROTECTED] Sent: Friday, March 05, 2004 1:41 PM To: Bowler, Michael Subject: RE: [mrtg] Re: mrtg restart problems I get logging is an unknown option. Version mrtg-2.9.10. No config has changed. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Bowler, Michael > Sent: Friday, March 05, 2004 1:31 PM > To: 'James Nelson'; [EMAIL PROTECTED] > Subject: [mrtg] Re: mrtg restart problems > > James, > Try checking the log file --logging <path-to>/<logfile>. If the process > is > dying right away, it usually means MRTG ran into something it didn't like. > Bowler > > -----Original Message----- > From: James Nelson [mailto:[EMAIL PROTECTED] > Sent: Friday, March 05, 2004 1:18 PM > To: [EMAIL PROTECTED] > Subject: [mrtg] mrtg restart problems > > > I am running redhat linux. I have been using mrtg and snmpd to monitor > several cisco routers for years. Some time mrtg died, now I can not > restart > it. I am running it as a daemon. > > > I have tried stopping snmpd, which appears to happen normally. It also > restarts normally and can be seen in ps -ax. > > > > Stopping mrtg results in a failure and mrtg.pid and /var/lock/subsys/mrtg > remain. > > > > I remove both and attempt to start mrtg and it appears to start normally > but > immediately is dead again. > > > > Mrtg status results in: > > mrtg dead but subsys locked > > > > I don't get what has happened that I can't restart the darn thing. > > > > Please help. > > > > -- > Unsubscribe mailto:[EMAIL PROTECTED] > Archive http://www.ee.ethz.ch/~slist/mrtg > FAQ http://faq.mrtg.org Homepage http://www.mrtg.org > WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi > > > -------------------------------------------------------------------------- > ----------- > A.G. Edwards & Sons' outgoing and incoming e-mails are electronically > archived and subject to review and/or disclosure to someone other > than the recipient. > > -------------------------------------------------------------------------- > ----------- > > > > -- > Unsubscribe mailto:[EMAIL PROTECTED] > Archive http://www.ee.ethz.ch/~slist/mrtg > FAQ http://faq.mrtg.org Homepage http://www.mrtg.org > WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
