hiya,

i'll group two replies together here.

On Wed, Sep 22, 2010 at 10:57:10AM +0300, Teodor MICU wrote:
> >  * does the schema seem correct (i.e. a disabled column in the host table)?
> 
> I don't know anything related to a 'schema', so probably not the
> issue. If you can tell me what to check, I'll do.

what i meant was something along the lines of comparing mysqldump
output when the --no-data option was used (i.e. are all the tables/columns
the same between the versions and do the queries look correct).

> >  * does it work if you disable the spine poller and use the cmd.php one
> >   instead?
> 
> Yes, with 'cmd.php' I get the graphs but still at every 5 minutes
> there are SQL errors reported (see attached).
> No, with 'spine' I still get the SQL errors but also only NaN on all graphs.

ok, then my suspicions turn towards spine as the culprit.

> >  * does it start graphing again if you nuke the rrd files or play around
> >   with rrdtool versions?
> 
> I'll try to avoid playing around with rrdtool again. I did it for the
> conversion from 1.2x to 1.3x and this is the main reason I'm using
> cacti from squeeze on a lenny host.

right.  and if cmd.php works and spine doesn't, i don't think we should
focus too hard on the rrdtool goo.

On Wed, Sep 22, 2010 at 11:02:05AM +0300, Teodor MICU wrote:
> > do you get the same problems if you also upgrade spine from the lenny 
> > version
> > to the squeeze version (0.8.7e-2)?  i wouldn't be surprised that the
> > poller from lenny is designed for different sql/schema and thus might not
> > do the right INSERT/UPDATE type statements.
> 
> I didn't upgrade spine because I'll have to upgrade mysql too (and
> probably other packages from backports). The weird thing about these
> SQL errors is that running them manually gives no error but sometimes
> there are no results returned from the query.

okay, this may be where the problem is, though.

> > if upgrading to the squeeze version of spine doesn't solve the problem,
> > you could also try updating to the latest upstream version (i.e. compiling
> > it yourself and replacing the packaged version), but i haven't been lead
> > to believe that the latest version is so different from the squeeze/sid
> > version.
> 
> There are near zero chances of compiling it myself. I'll probably try
> a fresh install on a squeeze host with cacti and spine >=0.8.7e. Until
> them I'll stick with cacti=0.8.7e-4.

i think backporting the package should be fairly straightforward, assuming
your problem is because you don't want to get your hands dirty at least (vs 
some kinda corporate "you can not compile on the web hosts" thing).

the following should be all you need to do:

 * make sure there is a deb-src line for squeeze on your lenny box

        deb-src http://ftp.se.debian.org/debian squeeze main

 * (as root) apt-get update; apt-get install build-essential fakeroot
 * (as root) apt-get build-dep cacti-spine
 * apt-get source -b cacti

packages compiled against your lenny packages (i.e. no mysql upgrade required)
will then have appeared in the current working directory.

i suggest you give it a go before getting to deep into any other 
troubleshooting.  as it should only take a number of minutes to do the
above and then a couple runs of spine after that to see if it works.


        sean

-- 

Attachment: signature.asc
Description: Digital signature

Reply via email to