RRD files not being created

[vertigo23]

Is the distribution of adodb that comes with cacti broken with php5 and mysql5?

No it isn't - i'm having identical problems with mysql 4.1.15

[vertigo23]

Well, after lots of fighting, I installed the pre-packaged version available from the Ubuntu universe archive, and it's working fine. After this experience, I really can't recommend anyone ever try to use the 1st-party tarball. All I saw from this forum were lots of people with the same problem, and no solutions.

[hickey]

At this point, I'm seriously running out of patience with this tool. I appreciate that it's free and I don't have the right to any expectations, I'm just frustrated that it's not working, and that all of the information I've received hasn't really related to the problems I (and it seems like other people) have been having.

Well, you are not the only one that is getting totally frustrated! I have spent 3 days trying to figure out what the problem is and why the rrd files are not getting created. There does not seem to be any consistent information on what the code should be doing and what code has the responsibility to create the files. Is it when the data source gets create through the website or is it at the first poll? I am getting pretty irate that I have wasted so much time on this, there are a lot of people complaining about it, the developers seem to be ignoring the issue and friggin' gandalf keeps referencing a link in his signature that really does not have any useful information in this case.

It is really a shame. It looks like this package has really good potential and I would like to contribute to it, but not if it doesn't friggin' work. Especially when it wastes my time when I could be doing more productive work.

Just for the record, here are some things that I notice. I am running the cronjobs as apache given that is the user that is running the web server. In fact, I just created a cactiuser and attempted to make the polling work with this user just in case there was a problem with apache (and yes, I did change the owner ship of the existing rrd and log files.) Still no effect.

I have pulled down the FC5 RPM and installed it. I get the same thing. Actually a little worse now. It will not even create the rrd files for localhost now. So DAMN frustrating. The localhost just stays in the unknown state. Hmmm, this sounds vaguely familiar. Maybe I should go check the forums.......

Before I started using the code that came from the RPM, I would get the following when I executed the poller.php:

% sudo -u cactiuser /usr/bin/php /local/cacti/poller.php (3:54)
Content-type: text/html
X-Powered-By: PHP/4.3.9

Waiting on 1/1 pollers.
OK u:0.00 s:0.00 r:0.12
OK u:0.00 s:0.00 r:0.12
OK u:0.00 s:0.01 r:0.12
OK u:0.00 s:0.01 r:0.12
OK u:0.00 s:0.01 r:0.12
OK u:0.00 s:0.01 r:0.12
OK u:0.00 s:0.01 r:0.12
Waiting on 1/1 pollers.
Waiting on 1/1 pollers.
Waiting on 1/1 pollers.
Waiting on 1/1 pollers.
Waiting on 1/1 pollers.

You can see that the rrdtool update is occuring for some rrd files. These are actually the rrd files for localhost. I had several more rrd files that I created by hand (which I should not ever have to do) which would not get updated during a poll cycle. Yes, the permissions would just fine and the files should have been written to. Then of course the additional rrd files that should have been created never were. The waiting statement would continue for the next 5 mins until the poller.php would kill itself off.

Now on the code that came from the RPM, I would get the following when I executed the poller.php:

% sudo -u cactiuser /usr/bin/php /var/www/html/cacti/cmd.php
Content-type: text/html
X-Powered-By: PHP/4.3.9

05/12/2007 04:02:52 AM - CMDPHP: Poller[0] ERROR: Either there are no items in the cache or polling is disabled

This is when just the local host is created as a device. Everything looks fine from the front end interface, yet there are just as bad of problems using the RPM distribution.

Well I think I am about done. I refuse to continue wasting my time. It truly is a shame that a cacti is being released with probably no QA testing. I don't know what the developers are thinking. Do they really believe that after leaving such a bad taste in people's mouth that they can really convince people to use their package again?

Sorry, I don't smoke crack (which is about the only reason I could foresee why I would even play with this crap any more).

Good luck to anyone else that is trying to make the 0.8.6j release work.