After Cacti Upgrade..

[TFC]

Hi,
İf I decided to upgrade cacti, what should I do for plugin arch. and plugins? Anybody did arrange this procedure step by step??

[cigamit]

Upgrading is just as simple as installing for the first time. Override your old cacti files with the new files, rename config.php.dist to config.php, and then patch it with the plugin architecture. Re-edit the config.php file with the proper info (Cacti will then ask you to update the database). And your done!

[TFC]

So according to say, after upgrade cacti, I have to copy cacti/plugins directory into new cacti?

[cigamit]

So according to say, after upgrade cacti, I have to copy cacti/plugins directory into new cacti?

Yes, the plugins are pretty much Cacti version independent.

[TFC]

Hey thanks
first time I catch an user online at the same time

[cigamit]

Hey thanks
first time I catch an user online at the same time

Heh, I'm just up late programming. Getting ready to release a new beta of the Cacti CD tomorrow. Lots of fun!

[sini]

Hi,

I am planning to upgrade my cacti-0.8.6g > cacti-0.8.6i
I have no plugin arch installed on cacti-0.8.6g but I plan to use it with 0.8.6i.
Is it possible and if yes what is the suggested procedure to do that?

As I think:
0. backup
1st. upgrade cacti.
2nd. patch with plugin arch cacti-0.8.6i

thx

[fmangeant]

As I think:
0. backup
1st. upgrade cacti.
2nd. patch with plugin arch cacti-0.8.6i

Hi

this is how I proceed. Once your upgraded Cacti works fine, install the plugin architecture, and then enable plugins one by one.

[sini]

Ok, thx!

1st. Upgrade done well less than 10 min and cacti works fine.

2nd. I did a dry patch and got the following output:
No *.rej file created for more detail...
Do I apply the pre-patched files or not?
Do I have to worry about FAILED lines?
------
/opt/cacti# patch -p1 -N --dry-run < cacti-plugin-0.8.6i.diff
patching file auth_login.php
Hunk #1 FAILED at 111.
Hunk #2 succeeded at 180 (offset 18 lines).
1 out of 2 hunks FAILED -- saving rejects to file auth_login.php.rej
patching file data_sources.php
Hunk #1 FAILED at 1043.
Hunk #2 succeeded at 1112 (offset 29 lines).
1 out of 2 hunks FAILED -- saving rejects to file data_sources.php.rej
patching file graph_image.php
patching file graph.php
Hunk #1 succeeded at 94 with fuzz 1.
Hunk #2 FAILED at 208.
1 out of 3 hunks FAILED -- saving rejects to file graph.php.rej
patching file graphs_new.php
patching file include/auth.php
patching file include/config_arrays.php
Hunk #2 succeeded at 452 (offset 22 lines).
patching file include/config_form.php
Hunk #2 succeeded at 1001 (offset 1 line).
patching file include/config.php
Hunk #1 succeeded at 32 with fuzz 1.
patching file include/config_settings.php
Hunk #1 succeeded at 928 (offset 81 lines).
patching file include/plugins.php
patching file include/top_graph_header.php
Hunk #1 FAILED at 81.
Hunk #2 FAILED at 103.
Hunk #3 succeeded at 136 with fuzz 2 (offset 18 lines).
Hunk #4 succeeded at 148 (offset 18 lines).
Hunk #5 FAILED at 156.
3 out of 5 hunks FAILED -- saving rejects to file include/top_graph_header.php.rej
patching file include/top_header.php
Hunk #1 FAILED at 24.
Hunk #2 FAILED at 42.
Hunk #3 succeeded at 59 (offset 5 lines).
Hunk #4 succeeded at 71 (offset 5 lines).
Hunk #5 succeeded at 79 (offset 5 lines).
Hunk #6 succeeded at 92 (offset 5 lines).
2 out of 6 hunks FAILED -- saving rejects to file include/top_header.php.rej
patching file index.php
patching file lib/api_device.php
patching file lib/functions.php
Hunk #2 succeeded at 618 (offset 56 lines).
Hunk #3 succeeded at 1323 (offset 60 lines).
Hunk #4 succeeded at 1336 (offset 60 lines).
Hunk #5 succeeded at 1411 (offset 62 lines).
patching file lib/html_form.php
patching file lib/html.php
Hunk #2 FAILED at 102.
Hunk #5 succeeded at 534 (offset 100 lines).
Hunk #6 succeeded at 545 (offset 100 lines).
Hunk #7 succeeded at 574 (offset 100 lines).
Hunk #8 succeeded at 595 (offset 100 lines).
1 out of 8 hunks FAILED -- saving rejects to file lib/html.php.rej
patching file lib/poller.php
Hunk #1 succeeded at 289 (offset 1 line).
patching file lib/variables.php
patching file plugins/index.php
patching file poller.php
patching file utilities.php
Hunk #1 succeeded at 122 (offset 34 lines).
Hunk #2 succeeded at 974 (offset 617 lines).
--------

thx

[cigamit]

Is Cacti installed from Source, package, or from SVN? There are way too many errors in there for something to not be broken somewhere.

[sini]

Cacti installed from source.
I also tried the pre-patched files without sucess...

[Tomeq]

Same here, I can't get plugin architecture working on 0.8.6i. I have overwritten the original files with prepatched ones. No change in cacti behavior at all.

I've installed Cacti from source, using standard upgrade procedure. Everything is working fine, with or without plugin architecture, but I see no difference anywhere!

Greets,
Tomek

[Tomeq]

Upgrading is just as simple as installing for the first time. Override your old cacti files with the new files, rename config.php.dist to config.php, and then patch it with the plugin architecture. Re-edit the config.php file with the proper info (Cacti will then ask you to update the database). And your done!

Ok it is clear but when Cacti should ask about database update? After which particular changes in config.php? username, password and database name?

Cacti is not asking me about anything and seems to work without any significant difference after applying plugin architecture.

Greets,
Tomek

[cigamit]

First, I will assume that you actually added a Plugin.

http://cactiusers.org/wiki/PluginsInstall

If that is the case, which plugin is it? Have you followed the tips? Particularly the first one.

http://cactiusers.org/wiki/PluginTips

Cacti only asks you about an upgrade if your database version (Cacti stores it own version in the database) is different than the one in the config_arrays.php file. If the one in the file is newer, then you will be prompted for an update.

[Tomeq]

First, I will assume that you actually added a Plugin.

http://cactiusers.org/wiki/PluginsInstall

If that is the case, which plugin is it? Have you followed the tips? Particularly the first one.

http://cactiusers.org/wiki/PluginTips

Cacti only asks you about an upgrade if your database version (Cacti stores it own version in the database) is different than the one in the config_arrays.php file. If the one in the file is newer, then you will be prompted for an update.

Thanks for help. Seems to work now. Anyway it is not clear if installing the plugin architecture standalone will do anything. I have suggestion - any indicator with some self-checking routine? even a short text displayed anywhere in the Cacti window similar to "Plugin architecture enabled, and working." would do the trick.

Greets,
Tomek