Migrate db from 0.8.7b to 0.8.7e

[smlick]

I used BSOD2600 windows installer to create a new cacti test environment.
Now I like to import the production db into the new test environment and I read the document http://www.cacti.net/downloads/docs/html/upgrade.html
but I'm not sure about the correct db migration procedure.
I made a diff from the db of 0.8.7b and 0.8.7.e version and there are some difference in the db so if I made a db backup of the old version and a restore in the new environment I think that this is not right due to different structure.


This is the difference between the two db:

able `cacti`.`manage_admin_link` was dropped
Table `cacti`.`manage_alerts` was dropped
Table `cacti`.`manage_groups` was dropped
Table `cacti`.`manage_host` was dropped
Table `cacti`.`manage_poller_output` was dropped
Table `cacti`.`manage_process` was dropped
Table `cacti`.`manage_services` was dropped
Table `cacti`.`manage_sites` was dropped
Table `cacti`.`manage_tcp` was dropped
Table `cacti`.`manage_templates` was dropped
Table `cacti`.`manage_uptime_method` was dropped
Table `cacti`.`plugin_aggregate_color_templates` was dropped
Table `cacti`.`plugin_aggregate_color_template_items` was dropped
Table `cacti`.`plugin_camm_keys` was dropped
Table `cacti`.`plugin_camm_rule` was dropped
Table `cacti`.`plugin_camm_snmptt_stat` was dropped
Table `cacti`.`plugin_camm_snmptt_unk` was dropped
Table `cacti`.`plugin_camm_snmptt` was dropped
Table `cacti`.`plugin_camm_syslog` was dropped
Table `cacti`.`plugin_camm_temp` was dropped
Table `cacti`.`plugin_camm_tree2` was dropped
Table `cacti`.`plugin_thold_contacts` was dropped
Table `cacti`.`plugin_thold_log` was dropped
Table `cacti`.`plugin_thold_template_contact` was dropped
Table `cacti`.`plugin_thold_threshold_contact` was dropped
Table `cacti`.`superlinks_auth` was dropped
Table `cacti`.`superlinks_pages` was dropped
Table `cacti`.`syslog_alert` was dropped
Table `cacti`.`syslog_incoming` was dropped
Table `cacti`.`syslog_remove` was dropped
Table `cacti`.`syslog_reports` was dropped
Table `cacti`.`syslog` was dropped
Table `cacti`.`thold_data` was dropped
Table `cacti`.`thold_template` was dropped
Table `cacti`.`uptime_data` was dropped
Table `cacti`.`uptime` was dropped
Table `cacti`.`weathermap_auth` was dropped
Table `cacti`.`weathermap_data` was dropped
Table `cacti`.`weathermap_maps` was dropped
Table `cacti`.`data_input_fields` was modified
Table `cacti`.`data_template_rrd` was modified
Table `cacti`.`graph_local` was modified
Table `cacti`.`graph_templates_graph` was modified
Table `cacti`.`host` was modified
Table `cacti`.`host_snmp_cache` was modified
Table `cacti`.`poller_item` was modified
Table `cacti`.`poller_time` was modified
Table `cacti`.`snmp_query_graph_rrd` was modified
Table `cacti`.`snmp_query_graph_rrd_sv` was modified
Table `cacti`.`user_auth` was modified
Table `cacti`.`data_input_fields` was modified
indices:
- added index type_code with columns: type_code
__
Table `cacti`.`data_template_rrd` was modified
indices:
- added index local_data_template_rrd_id with columns: local_data_template_rrd_id
- removed index data_source_name
__
Table `cacti`.`graph_local` was modified
indices:
- added index snmp_query_id with columns: snmp_query_id
__
Table `cacti`.`graph_templates_graph` was modified
columns:
- modified column scale_log_units
__
Table `cacti`.`host` was modified
columns:
- removed column manage
- removed column monitor_text
- removed column monitor
- removed column telnet_flag
- removed column uptime
- modified column availability_method
- modified column status_last_error
__
indices:
- removed index hostname
__
Table `cacti`.`host_snmp_cache` was modified
indices:
- added index field_name with columns: field_name
- added index field_value with columns: field_value
- added index snmp_query_id with columns: snmp_query_id
__
Table `cacti`.`poller_item` was modified
columns:
- modified column snmp_auth_protocol
- modified column snmp_priv_passphrase
- modified column snmp_priv_protocol
- modified column rrd_step
__
Table `cacti`.`poller_time` was modified
columns:
- modified column pid
__
Table `cacti`.`snmp_query_graph_rrd` was modified
indices:
- added index data_template_rrd_id with columns: data_template_rrd_id
__
Table `cacti`.`snmp_query_graph_rrd_sv` was modified
indices:
- added index data_template_id with columns: data_template_id
__
Table `cacti`.`user_auth` was modified
columns:
- modified column enabled

As you can see there are some difference (except the plugin).

Could someone tell me the correct procedure to import the data of the old db into the new one?

Regards
Alessio

[BSOD2600]

I used BSOD2600 windows installer to create a new cacti test environment.

The latest installer is 0.8.7e -- why did you create it with b?

...but I'm not sure about the correct db migration procedure.

1) backup the mysql database.
mysqldump -l --add-drop-table cacti > mysql.cacti

2) backup the cacti files/rrd files.

3) download/extract the cacti 0.8.7g files over the existing installation.

4) download/extract PIA 2.8 files over the existing installation.

5) make the appropriate changes to config.php for the mysql user/pass.

6) open http://localhost/cacti/ and follow the upgrade guide.

[smlick]

Tnx BSOD2600 for your reply.
I create it with 0.8.7.b because I build the production environment in April 2008
Now is time to migrate and test a more recent version
I didn't know there was an automated procedure to update the database (upgrade guide after logging in).

Thank's now I'll try

Regards
Alessio

[smlick]

But with a new installation in a new hardware how to import the db ?
The rra is a simple copy into the rra folder but what to do with the backup of the old 0.8.7b into the old machine?
A simple restore like mysql < mysql.cacti -uroot -pXXXX into the new cacti db of the new machine I think that is not the correct procedure.
Can you explain more the upgrade process of a Cacti system from 0.8.7.b (or any previous version) to a new one with different hardware and a new fresh install of recent Cacti.

Tnx again

Alessio

[BSOD2600]

But with a new installation in a new hardware how to import the db ?

Treat it as a quasi-new install.

The rra is a simple copy into the rra folder but what to do with the backup of the old 0.8.7b into the old machine?

Restore all of the 0.8.7b stuff to the new hardware. Then follow the cacti upgrade guide (after making sure the install works correctly on the new hardware).

A simple restore like mysql < mysql.cacti -uroot -pXXXX into the new cacti db of the new machine I think that is not the correct procedure.

That works just fine, assuming you backed up the database using the procedure documented in the upgrade guide.

[smlick]

Sorry but no import db procedure started when I logged into the new Cacti.
This is what I did.

1) make a db backup from old 0.8.7b machine (shell> mysqldump -l --add-drop-table cacti > mysql.cacti)

2)copy RRA folder and any relevant thing such script resource from old 0.8.7b machine

3)make a new fresh install of yours windows installer 1.94 (cacti 0.8.7e) into the new machine

4)copied the old file into RRA, scripts and resource into the new folder without overwrite the existing one file

5)logged into the new machine (admin, cactipw) but no import procedure for old db import started.

I missed something?

Regards
Alessio

[BSOD2600]

Sorry but no import db procedure started when I logged into the new Cacti.

You have to manually import the database.

[smlick]

Something doesn't go in the right way
No problem with the import procedure, all the device, graphs and data are in the right place.
In settings paths I made some adjustments and now all green and ok but the poller doesn't go.
No data in the log, I tried spine and also cmd.php.
I tried to reboot the machine and also from the cli a poller_reindex_hosts and also rebuild_poller_cache but with no success.

In the log there are only the line of auth login.

Any idea?

An additional info: when I did the upgrade procedure the system display a correct import from 0.8.7.b to 0.8.7.c but I used BSOD2600 windows installer 1.4 with cacti 0.8.7.e so why displaied an upgrade from 0.8.7.b to 0.8.7.c?

Regards
Alessio

[BSOD2600]

The installer should NOT be used to upgrade an existing installation.

The cacti technical support page show any issues?

With the cacti logging level set to debug, manually run: php poller.php. Does anything get spit out in the logs/screen?

[smlick]

I tried running php poller.php but nothing split out from clog.
However this is not an upgrade of a preinstalled version.
As I told before this is a new fresh install of your installer in a test environment (new hardware) and an import of the db from a production environment (old hardware) to test the improvement of the new version of cacti.
So new installation and import of the only db and RRA to repopulate the new machine with device and graph.
Any idea of what happened?

Regards
Alessio

A little update :
Now something split out...whenever I click a graph clog display something like that:

09/06/2010 08:32:05 AM - WEBLOG: Poller[0] CACTI2RRD: d:/rrdtool/rrdtool.exe graph - --imgformat=PNG --start=1283668325 --end=1283754725 --title="Imperia_Server_208 (128.69.239.2)-Traffic-e1-Up_Rete " --rigid --base=1000 --height=120 --width=500 --alt-autoscale-max --lower-limit=0 COMMENT:"From 2010/09/05 08\:32\:05 To 2010/09/06 08\:32\:05\c" COMMENT:" \n" --vertical-label="bits per second" --slope-mode --font TITLE:10: --font AXIS:8: --font LEGEND:8: --font UNIT:8: DEF:a="D\:/Apache2/htdocs/cacti/rra/imperia_server_208_traffic_in_899.rrd":traffic_in:AVERAGE DEF:b="D\:/Apache2/htdocs/cacti/rra/imperia_server_208_traffic_in_899.rrd":traffic_out:AVERAGE CDEF:cdefa=a,8,* CDEF:cdefe=b,8,* AREA:cdefa#00CF00FF:"Inbound" GPRINT:cdefa:LAST:" Cur\:%8.2lf %s" GPRINT:cdefa:AVERAGE:"Avg\:%8.2lf %s" GPRINT:cdefa:MAX:"Max\:%8.2lf %s\n" LINE1:cdefe#002A97FF:"Outbound" GPRINT:cdefe:LAST:"Cur\:%8.2lf %s" GPRINT:cdefe:AVERAGE:"Avg\:%8.2lf %s" GPRINT:cdefe:MAX:"Max\:%8.2lf %s"

but nothing more!!!

[smlick]

I tried running php poller.php but nothing split out from clog.
However this is not an upgrade of a preinstalled version.
As I told before this is a new fresh install of your installer in a test environment (new hardware) and an import of the db from a production environment (old hardware) to test the improvement of the new version of cacti.
So new installation and import of the only db and RRA to repopulate the new machine with device and graph.
Any idea of what happened?

Regards
Alessio

A little update :
Now something split out...whenever I click a graph clog display something like that:

09/06/2010 08:32:05 AM - WEBLOG: Poller[0] CACTI2RRD: d:/rrdtool/rrdtool.exe graph - --imgformat=PNG --start=1283668325 --end=1283754725 --title="Imperia_Server_208 (128.69.239.2)-Traffic-e1-Up_Rete " --rigid --base=1000 --height=120 --width=500 --alt-autoscale-max --lower-limit=0 COMMENT:"From 2010/09/05 08\:32\:05 To 2010/09/06 08\:32\:05\c" COMMENT:" \n" --vertical-label="bits per second" --slope-mode --font TITLE:10: --font AXIS:8: --font LEGEND:8: --font UNIT:8: DEF:a="D\:/Apache2/htdocs/cacti/rra/imperia_server_208_traffic_in_899.rrd":traffic_in:AVERAGE DEF:b="D\:/Apache2/htdocs/cacti/rra/imperia_server_208_traffic_in_899.rrd":traffic_out:AVERAGE CDEF:cdefa=a,8,* CDEF:cdefe=b,8,* AREA:cdefa#00CF00FF:"Inbound" GPRINT:cdefa:LAST:" Cur\:%8.2lf %s" GPRINT:cdefa:AVERAGE:"Avg\:%8.2lf %s" GPRINT:cdefa:MAX:"Max\:%8.2lf %s\n" LINE1:cdefe#002A97FF:"Outbound" GPRINT:cdefe:LAST:"Cur\:%8.2lf %s" GPRINT:cdefe:AVERAGE:"Avg\:%8.2lf %s" GPRINT:cdefe:MAX:"Max\:%8.2lf %s"

but nothing more!!!

Sorry for the double post but I'm not able to delete this one.

[BSOD2600]

As I told before this is a new fresh install of your installer in a test environment (new hardware) and an import of the db from a production environment (old hardware) to test the improvement of the new version of cacti.

Do the versions of the databases match? i.e. what was the restored db cacti version and what cacti version did you install?

Validated the ntfs permissions are correct on cmd.exe, rrdtool.exe, etc per the installation guide? A lack of anything being generate in the cacti.log typically is permission issues.

[smlick]

I think that the problem is for Apache/Tomcat NTFS permissions instead IIS.
Have you tried in your installer the install option of Apache does it work right for permission issue?
I'll try the same procedure with IIS install to understand if this is the problem.

The migration is from 0.8.7b to 0.8.7e.

Regards
Alessio

[BSOD2600]

Have you tried in your installer the install option of Apache does it work right for permission issue?

It does on a clean windows install... I've got VM's for XP, 2003, and 2008 I test against.

[smlick]

I did the same procedure with a new fresh install (windows 2003 and IIS) but with no success!!!
Probably I did something wrong.
This is what I did step by step:

1) I did a backup of the db (mysqldump -uroot -ppwdroot -l --add-drop-table cacti > mysql.cacti) and the rra folder from my old machine with cacti 0.8.7b.
2)Installed your 1.94 installer on a new fresh windows 2003 machine with all install option enabled.
The installer works flawlessy with no errors. I put the old rra into the new rra cacti folder.
3)I restored the old db into the new machine (mysql -uroot -ppwdroot cacti < mysql.cacti).
4)I logon into the new cacti (0.8.7e from your installer) and the upgrade procedure started automatically with no errors (all green and ok) but it displaied an import from 0.8.7b to 0.8.7c (instead 0.8.7b --> 0.8.7e).

After the import procedure I make a restart of the machine and then a new logon all the graphs and devices are in the correct place but there is no poller activities.
I tried cmd.php and also spine with no success. I checked the file permissions and all seems ok.

I did something wrong?

Regards
Alessio