[suggest] cacti rpm on rpmforge

[Stefan Radman]

> That's interesting, I've experienced exactly the first two 
> bugs that they say were fixed there.
Did the patches fix the problems you experienced?

> I didn't realise that patch link existed.
http://www.cacti.net -> "Downloads" -> "Official Patches"

Stefan

> -----Original Message-----
> From: Michael Mansour [mailto:mic at npgx.com.au] 
> Sent: Monday, 30 April, 2007 13:10
> To: Stefan Radman; suggest at lists.rpmforge.net
> Cc: Dries Verachtert
> Subject: RE: [suggest] cacti rpm on rpmforge
> 
> Hi Stefan,
> 
> > Hi,
> > 
> > Attached is a patch against the current cacti-0.8.6j-1 spec.
> > 
> > It essentially includes the logrotate script Dries proposed and the
> > official patches for 0.8.6j
> >   http://www.cacti.net/download_patches.php
> > They contain several important bug fixes.
> 
> That's interesting, I've experienced exactly the first two 
> bugs that they 
> say were fixed there.
> 
> I'm currently in the process of building a new clustered 
> cacti environment, 
> I didn't realise that patch link existed.
> 
> Thanks.
> 
> Michael.
> 
> > Please consider updating the repo to cacti-0.8.6j-2.
> > 
> > Thanks and Regards
> > Stefan
> > 
> > > -----Original Message-----
> > > From: suggest-bounces at lists.rpmforge.net 
> > > [mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of 
> > > Michael Mansour
> > > Sent: Monday, 16 April, 2007 12:43
> > > To: Dries Verachtert; suggest at lists.rpmforge.net
> > > Subject: Re: [suggest] cacti rpm on rpmforge
> > > 
> > > Hi Dries,
> > > 
> > > > > Hi,
> > > > >
> > > > > I've been running cacti for a couple of days now, using 
> > > the cacti rpm on
> > > > > rpmforge, and I noticed that the 
> > > /var/www/cacti/log/cacti.log file is ever
> > > > > increasing in size and doesn't seem to be properly 
> > > managed by logrotate
> > > > > (although I haven't checked whether cacti has an internal 
> > > mechanism for
> > > > > this - but I can't see one).
> > > > >
> > > > > Maybe it's an idea to include a logrotate script in 
> the RPM too?
> > > > >
> > > > > Michael.
> > > > 
> > > > Something small like the following, would that be ok?
> > > > 
> > > > cat > %{buildroot}%{_sysconfdir}/logrotate.d/cacti <<EOF
> > > > %{_localstatedir}/www/cacti/log/*.log {
> > > > 	missingok
> > > > 	compress
> > > > }
> > > > EOF
> > > 
> > > Yeah that would be perfect and technically should be part of 
> > > the RPM since
> > > cacti definately doesn't manage it's own log by itself. My 
> > > log file size is
> > > over 20mb already after just one week.
> > > 
> > > Personally though, since running cacti for the short time I 
> > > have, I've come to
> > > the realisation that it's not very functional when using it 
> > > as a packaged
> > > solution. This has nothing to do with rpmforge per se, as you 
> > > guys are doing
> > > an excellent job for at least supplying it, but I'll explain 
> > > why I say this.
> > > 
> > > Cacti itself has very basic functionality, querying devices 
> > > via scripts and
> > > snmp, whether packaged in RPM or supplied in a tarball by the 
> > > cacti developers
> > > off their main cacti website, that's basically all Cacti does.
> > > 
> > > What I've found since starting to use it, is I really needed other
> > > functionality like killspike, RRD cleaner, syslog monitoring, 
> > > report creator,
> > > Thresholds (alerts), cycle graphs, device tracking, etc. 
> > > 
> > > These are all available as plugins and require the Plugin 
> > > Architecture to be
> > > installed (patches on top of "official" cacti release). The Plugin
> > > Architecture was not developed by Cacti developers but by 
> > > cactiusers.org,
> > > people that needed to extend the core functionality with plugins.
> > > 
> > > These plugins are what make cacti a very useful and powerful 
> > > product, without
> > > them it's just a standard rrd graphing tool, like most others.
> > > 
> > > I'll take the killspike plugin as an example. One doesn't 
> realise how
> > > important this tool is until a spike occurs and completely 
> > > ruins a graph.
> > > Spikes in the graph are easy to produce yet quite difficult 
> > > to fix without
> > > third party tools or some indepth knowledge of rrdtool and 
> > > rrddump, yet the
> > > killspike plugin cleans these problems up automatically.
> > > 
> > > The cacti developers have promised the next official release 
> > > will support
> > > plugins, possibly with their own architecture, but the 
> > > cactiusers.org guys
> > > already have this today with hundreds of plugins already 
> > > programmed by third
> > > parties and available immediately.
> > > 
> > > This effectively means that the cacti tarball supplied by 
> the cacti
> > > developers, and in effect the RPM (graciously) supplied by 
> > > rpmforge, is only
> > > of use for basic graphing, and in the case of killspike 
> > > above, requires the
> > > use of the admin to constantly monitor the environment and 
> > > fix problems.
> > > 
> > > For anything serious one must move to the standard 
> tarball and plugin
> > > architecture patches on top, then installation of the various 
> > > plugins one needs.
> > > 
> > > Regards,
> > > 
> > > Michael.
> > > 
> > > > kind regards,
> > > > Dries
> > > > 
> > > > _______________________________________________
> > > > suggest mailing list
> > > > suggest at lists.rpmforge.net
> > > > http://lists.rpmforge.net/mailman/listinfo/suggest
> > > ------- End of Original Message -------
> > > 
> > > _______________________________________________
> > > suggest mailing list
> > > suggest at lists.rpmforge.net
> > > http://lists.rpmforge.net/mailman/listinfo/suggest
> > >
> ------- End of Original Message -------
> 
>