[rtg] Traffic is wrapping

[Chris Miller]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I too wish someone could do some cleanup on the way RTG is  
implemented. It works great, but man is it a mess.

What is this RTG-Yahoo patch you speak of?

Thanks,

Chris Miller
ServerMotion
www.servermotion.com



On Apr 1, 2008, at 1:34 PM, Ryan DiRocco wrote:
> And to add to that someone had written a sql based targeting system  
> as a
> patch previously but I could never get that to work. I think the  
> file based
> targets and the forced rehashes are a bad design.
>
> I see no reason why the targets shouldn't be maintained in SQL so  
> they are
> always 'live'
>
>
> -----Original Message-----
> From: rtg-bounces at lists.grdata.com [mailto:rtg- 
> bounces at lists.grdata.com] On
> Behalf Of Ryan DiRocco
> Sent: Tuesday, April 01, 2008 2:31 PM
> To: rtg at lists.grdata.com
> Subject: Re: [rtg] Traffic is wrapping
>
> A combination of people have made enhancements.
>
> I'd like to see some of the work from rtg-yahoo ported into .9 as  
> we're
> running the yahoo patch due to it's enhanced sql handling... we still
> struggle with memory leaks and target rehashes though.
>
>
>
> -----Original Message-----
> From: rtg-bounces at lists.grdata.com [mailto:rtg- 
> bounces at lists.grdata.com] On
> Behalf Of Shaun
> Sent: Tuesday, April 01, 2008 2:20 PM
> To: 'Brandon Ewing'; rtg at lists.grdata.com
> Subject: Re: [rtg] Traffic is wrapping
>
> 0.9? has there been devel work happening again on rtg!?!?!?!  Looks  
> like svn
> on sourceforge was written to back in jan of 2008!  I'm excited :)  Is
> somebody maintaining rtg again, who?
>
> ~Shaun
>
> -----Original Message-----
> From: rtg-bounces at lists.grdata.com [mailto:rtg- 
> bounces at lists.grdata.com] On
> Behalf Of Brandon Ewing
> Sent: Tuesday, April 01, 2008 11:09 AM
> To: rtg at lists.grdata.com
> Subject: Re: [rtg] Traffic is wrapping
>
> On Tue, Apr 01, 2008 at 09:47:12AM -0700, Shaun wrote:
>> What are you using now?  I'm a little disappointed that rtg is no
>> longer being actively maintained.  Even when I tried to get the ball
>> back rolling with a few guys on the lists that have done devel  
>> work on
>> the project nobody wants to take over.  One guy here had done work to
>> 0.8 and said to have it working.  If I was good enough at C I  
>> would do
>> it but I'm more of a perl/php guy.
>>
>> ~Shaun
>>
>
> We currently use RTG 0.8 to monitor ~4000 interfaces across 200  
> devices,
> including a mix of FastE, GigE, and POS interfaces.  Since you're  
> seeing OOR
> values, I think you are using 0.74 still, and do not have an  
> intelligent OOR
> value in your rtg.conf (OOR is what RTG uses to throw out readings  
> that
> don't make sense), and a bug in the old version of rtgtargmkr.pl is
> inserting 0s instead of calculating based on interface speed:
>
> http://lists.grdata.com/pipermail/rtg/2004-February/000832.html
> Set an intelligent OOR value in rtg.conf, and re-run  
> rtgtargmkr.pl / restart
> the poller, to see if the issue persists.
>
> If you're still having problems, let us know some more about your  
> situation,
> such as what version you're running, the contents of rtg.conf, and  
> the entry
> from target.cfg for the GigE interface that's causing the error.
>
> You might consider an upgrade to 0.9 CVS, as the new targetmaker is  
> rather
> robust -- there are various notes on the mailing list on getting it to
> compile correctly.
>
> -- 
> Brandon Ewing                                         
> (nicotine at warningg.com)
>
> _______________________________________________
> RTG mailing list
> RTG at lists.grdata.com
> http://lists.grdata.com/mailman/listinfo/rtg
>
> _______________________________________________
> RTG mailing list
> RTG at lists.grdata.com
> http://lists.grdata.com/mailman/listinfo/rtg
>
> _______________________________________________
> RTG mailing list
> RTG at lists.grdata.com
> http://lists.grdata.com/mailman/listinfo/rtg

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFH8qLpxBwlCB7CRwsRAq3IAJ0cnLlVYXldrJ85KTqQTOsg7Gq4YgCfYzxZ
kNDJez+5F4aorWhrJy5uddo=
=Qvi6
-----END PGP SIGNATURE-----