Multihost boost install issues

gninja · Posted: Wed Jul 16, 2008 4:29 pm Post subject: Multihost boost install issues

Running into a few issues migrating from a single host install, to a multi-host install.

Moving to: 1 database host, 1 update host, 1 poller host, 1 ui host.

update host has the rrds on local disk. ui host mounts the rrd directory read-only over nfs. Most of it's working.

Migrated the database to a new host, worked fine, saw noticeable performance improvements immediately.

Migrated the rrd files to a new host, after setting the boost record size to 250k... Everything worked fine, aside from a small glitch with the path_webroot setting.

The path_webroot setting in the database keeps getting reset, by I think the poller. I want it to be /data/cacti, but it keeps getting set to /usr/local/share/cacti.. Not a big deal since I have symlinks in place now, but still somewhat annoying.

Boost updates are now doing 128k updates in 330 seconds.

Problems are coming up with the migration of the poller.

It's completing everything fairly quickly, but continuing to hang around for 294 seconds. I'm still digging, but figured I'd toss this up in case anyone's seen this and had ideas.

gninja · Posted: Wed Jul 16, 2008 6:22 pm Post subject:

And while fixing what I thought to be unrelated problems... poller time dropped to normal.

gninja · Posted: Fri Jul 18, 2008 1:42 pm Post subject:

Still running into an update problem...

RRDs are being updated properly, if someone goes and views them.

But the update server is not seeming to be called at the normal interval.

I can watch the boost status, and every poller cycle or two it drops the number of records to 0, but the boost process output doesn't actually display any activity, other than the ones that happen when someone hits a graph.

gninja · Posted: Fri Jul 18, 2008 3:22 pm Post subject:

Ok. What seems to be happening, is the poller.php is detecting that boost needs to be run, and starting up a poller_boost.php, on the poller host, which connects to the database and then attempts to update the rrd files locally.

Which, since the poller host doesn't have a copy of the rrds, fails dramatically.

Am I configuring this wrong? I kind of thought poller.php would see that a boost update needs to run, and would either connect to the boost server and say "update everything" or launch the poller_boost.php, which would iterate through everything, connecting to the update server for the updates...

gninja · Posted: Fri Jul 18, 2008 3:41 pm Post subject:

Now it's working the way I want to, but not without me kludging it into place.

I've got a crontab doing a forced poller_boost.php update on the update server, every five minutes. And the default boost settings are such that the automated poller_boost launch on the poller host never happens.

This seems a bit backwards, but so far appears to be working.

TheWitness · Posted: Wed Jul 23, 2008 8:34 am Post subject:

Got it then. So, aside from the webroot issue, we need a way to have the boost updates run from Cron as apposed to by the poller process. Does that sum it up in a nutshell? Also, how many total RRD's?

TheWitness

gninja · Posted: Wed Jul 23, 2008 1:16 pm Post subject:

That pretty much sums it up.

Right now I have about 21k rrds. That should inflate to around 50k over the next 3-6 months.