Cannot update OpenSUSE VM image from 3.0 to 3.1 release

[Sancho]

Like it

Up

0

Down

Drop it

::

Have you checked this documentation ?

http://www.openideas.info/wiki/index.php?title=Pandora_3.0:Documentation_en:Anexo_Upgrade

Talks about the upgrade process. You need to RE-INSTALL the new RPM packages AND make the database migration, using the .sql files from your mysql command line client.

[summa_sp]

Like it

Up

0

Down

Drop it

::

I receive an error when I run the upgrade script.

host1:/srv/www/htdocs/pandora_console # cat extras/pandoradb_migrate_v3.0_to_v3.1.sql | mysql -u pandora -p pandora -D pandora
Enter password:
ERROR 1054 (42S22) at line 306: Unknown column ‘id_group’ in ‘where clause’

[Sancho]

Like it

Up

0

Down

Drop it

::

You probably comes from a rc version of 3.0, let’s do the SQL transformation progress step by step.

Open a mysql client, connect to pandora database and enter each SQL sentence from .sql file, separately, to see where is the problem exactly.

[suzdal]

Like it

Up

0

Down

Drop it

::

i got this error time ago.
it comes from this line:

UPDATE talert_actions SET id_group = 0 WHERE id_group = 1;

and you should have more errors, after that if you fix this.

all of that comes from a prior version 2x and an upgrade of pandora but not the bdd.

my advice, make a backup
run pandoradb_migrate_v2.x_to_v3.0.sql, located at /pandora/branches/pandora_3.0/pandora_console/extras  (i use svn)
after that, run again the pandoradb_migrate_v3.0_to_v3.1.sql

[summa_sp]

Like it

Up

0

Down

Drop it

::

I ran the 2.x to 3.x script first, but got an error.
ERROR 1060 (42S21) at line 4: Duplicate column name ‘priority’

I ran the 3.0 to 3.1 script, and got the same error.

[summa_sp]

Like it

Up

0

Down

Drop it

::

I downloaded a clean VM and started it up.  I did not install any agents or create any modules or alerts.  I booted the VM connected with a browser to make sure Pandora worked correctly, and logged in with ssh.  Here is the VM i downloaded.

Pandora_FMS_3.0_OpenSource.i686-3.0.1229.vmdk

Here are the results:

testhost1:/var/tmp # /etc/init.d/pandora_server stop
Stopping Pandora FMS Server
testhost1:/var/tmp # /etc/init.d/apache2 stop
Shutting down httpd2 (waiting for all children to terminate)
testhost1:/var/tmp # rpm -iv –force pandorafms_console-3.1-1.noarch.rpm
Preparing packages for installation…
pandorafms_console-3.1-1
testhost1:/var/tmp # rpm -iv –force pandorafms_server-3.1-1.noarch.rpm
Preparing packages for installation…
useradd: Account `pandora’ already exists.
pandorafms_server-3.1-1
Don’t forget to start Tentacle Server daemon if you want to receive
data using tentacle
testhost1:/var/tmp # cd /srv/www/htdocs/pandora_console/
testhost1:/srv/www/htdocs/pandora_console # cat extras/pandoradb_migrate_v3.0_to_v3.1.sql | mysql -u pandora -p -D pandora
Enter password:
ERROR 1054 (42S22) at line 306: Unknown column ‘id_group’ in ‘where clause’

So, the problem isn’t with a 2.x version of my database.  The migration script doesn’t work with your configured virtual machine. 

I don’t want to have to rebuild all the alerts and modules to get to version 3.1, and I really need the flip flop threshold fix for my ping modules.

Can you fix the script?