Cacitd not pulling data

[Linuturk]

This is a continuation of this thread.

http://forums.cacti.net/viewtopic.php?t=19689

Basically, the second hard disk on the original hardware died. I dumped the cacti database, installed cacti on a new server, and imported the entire old cacti database onto the new server. I left the rrd files where on the old server.

Cacti with cmd.php seemed to work fine. I was getting data from all my hosts, and things were peachy, until the load of my server skyrocketed again (as in the previous thread.)

I upped my PHP memory limit, and nothing changed.

This time, I was smart enough to install Ubuntu 6.10 instead of 6.06. 6.06 has a broken cactid package in its repositories. 6.10 has a working cactid package.

I installed the cactid package, and pointed cacti to cactid instead of cmd.php. Now, the poller doesn't pull any data from localhost anymore (and possibly other hosts, I haven't checked all 50+ yet)

I can snmpwalk locally on the machine, and the perl scripts return data if they are ran from the command line.

Adding /usr/bin/perl instead of just perl on the Data Sources page did not resolve the problem.

What do I need to do?

[gandalf]

Let me introduce this by saying, that I don't like rpm installations of cacti. Are you sure, that all path settings are the same as the old install that created the mysql tables? Cacti stores path information in the tables! Those may now be broken.
Yes, you may say that storing absolute paths is not that good of an idea, but nevertheless, this is fact.
Reinhard

[Linuturk]

This is not an RPM. This is a DEB.

The only difference between the two machines is one is running Ubuntu 6.06 and the other is running Ubuntu 6.10. Maybe the paths did change since then, but I don't believe that is the case.

Where can I see those settings?

I can always "whereis <command>" and compare the paths, but I need to know where to find these settings.

Is this the Paths tab under System Settings?

[Linuturk]

I've checked the path settings under the Paths tab under Settings.

all of them match up to what is displayed on the whereis command.

[gandalf]

Yes, but that was not the question.
Table poller_item holds /full/path/to/rrd/file. You may re-create this table by running

Code: Select all

php -q rebuild_poller_cache.php

. You may enable poller verbosity level of DEBUG to find more output at ./log/cacti.log
Reinhard

[TheWitness]

The Debian package is a bit finiky. I did not know their very specific packaging system too well, so when it came to cleaning things up, I was kind of lost. However, once you understand it, things should work as expected.

The Debian distribution changes very many things in Cacti's base setup. Things like scripts are taken from the web path, password containing files are moved to /etc/cacti, rra's are moved to their own directory, ADODB is moved to a system library path, and the log file is moved to /var/log and handled like any other log.

It's actually quite "Linux" centric distribution.

TheWitness

[Linuturk]

Code: Select all

cacti@FAIA-Cacti:~$ sudo php -q /usr/share/cacti/site/rebuild_poller_cache.php

Warning: include_once(./lib/utility.php): failed to open stream: No such file or directory in /usr/share/cacti/site/rebuild_poller_cache.php on line 35

Warning: include_once(): Failed opening './lib/utility.php' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /usr/share/cacti/site/rebuild_poller_cache.php on line 35
WARNING: Do not interrupt this script.  Rebuilding the Poller Cache can take quite some time
.
Fatal error: Call to undefined function update_poller_cache() in /usr/share/cacti/site/rebuild_poller_cache.php on line 95

There is the output from the php file you asked me to run. Obviously, it failed.

I'm guessing this has to do with the moved directories that The Witness is talking about?

[gandalf]

That shows what Larry said already. The cacti distro files do not match. You may contact the distro packager or install cacti from tar.gz
Reinhard

[Linuturk]

I don't want to install from source. I guess I'll drop the current database and reinstall it.