Monthly Archive for January, 2006

UNIX Template Set for Cacti

Published
by
alex
on Friday January 27th, 2006
in Unix & Linux
. 0 Comments

Following my first cacti host template (v1.0, see this previous post), which allows to graph some usefull performance metrics of HP-UX boxes, I was missing an equivalent (and somehow homogeneous) host template for Solaris and Linux boxes.

So I’ve reworked and adapted some existing graphs and data templates, basing me on the one available for Net-SNMP compatible hosts, and also creating new ones.

Now my Unix Template Set for Cacti is composed of 2 host templates:
* my HP-UX host template (see changes below),
* a Net-SNMP compatible host template (working well for Solaris and Linux host for example).

Both templates gives the same graphs, using the same colors… They allow graphing of the following metrics:
* CPU Usage: Sys, Nice, User and Idle CPU time
* Jobs Average: 1, 5, and 15min Jobs Average
* Memory occupation,
* Detailled Memory: part of used memory dedicated to buffers, cached and shared (available for Linux only, as neither Solaris nor HP-UX report such detailled information),
* Swap occupation
* Running Processes
* Logged in Users
* Lan traffic: In/Out Traffic and In/Out Errors
* Filesystem occupation

I’ve also apported some minor changes to version 1.0 existing graphs templates:
* CPU graphs now give a total of 100%,
* HP-UX load average is correctly rendered (value divided by 100, as the snmp agent report it multiplied by 100).

Feel free to download version 1.1 of the Unix Template Set for Cacti, and use and/or redistribute it under the terms of the GPL license.

ShareThis / Compartelo

Troubles with WP2 caching feature

Published
by
alex
on Sunday January 15th, 2006
in Internet & Blogging
. 0 Comments

The first time I tryed to upgrade WP to version 2 I already had problem with the new caching feature.

Upgrading on the test host I didn’t have those caching problems, but after replicating the exact same data (files and database) on the production host the troubles are back again!

Let me explain the problem: I have WP2 caching feature enabled (as it is by default) and wp-content/cache/ folder is writable by erb server processes.

* I go to the Admin panel options page,
* I change the tagline option to some random words
* and click the Update options button to save

As the page reload, I can see that the new tagline option is now empty, and that many other options have changed.

It’s weird but it doesn’t happend on my test host (while the production host is running Linux Debian testing, the test host is running HP-UX 11i).

Of course, if I disable the cache feature, it doesn’t happend any more. So the cache seems to be the cause of my troubles.
After searching for some time, I have found some people reporting that WP2 cache is broken, but I couldn’t find anything official about it:

* WordPress 2.0 Cache Is Broken!
* No caching for me
* Odd issue with editing posts

So, until any WP revision solve the cache problems, the only thing I can do for the moment is disabling the cache. This can be done by writting the following line in wp-config.php:

define('DISABLE_CACHE', true);

ShareThis / Compartelo

Upgrade to WP2

Published
by
alex
on Sunday January 15th, 2006
in Internet & Blogging
. 0 Comments

At the end of December 2005 I upgraded my Wordpress blog to version 2 following the official procedure detailled on the codex. Unfortunately, I suppose that I didn’t do it very well, as I had many troubles with the plugins (although I desactivated all of them before perfoming the upgrade), with the new cache system…

So I decided to roll everything back to version 1.5.2 and startover again, this time using another host as a test system – this is a reason why you NEED to do a backup before upgrading!
My test system was an old HP-UX box I own, which I had to adapt into a test system: so I installed Apache+PHP and MySQL. Once this was working fine, I replicated my WP1.5 original blog to that box. This was pretty easy: I just needed to create a mysql database, import the backup of the WP1.5 blog into it. Then I copied all the files from my WP1.5 blog into that box. Finally I had to change options ‘home’ and ’siteurl’ in wp_options to reflect the new host name. That’s all!

There I started again the upgrade procedure, but this time I followed Tamba2’s guide.

This time the upgrade seem to have succeed, so I have replicated the upgraded WP2 data (files and BD) back to the production host. And there it is!

ShareThis / Compartelo

Close
Powered by ShareThis