Does anybody have detailed instructions on the proper way to upgrade Wildfire Server using RPM install on RedHat with MySQL Database?
I have been using jabber/wildfire/openfire for quite a while now on RedHat ES 3 box. I have upgraded twice in the past, both time times with problems and had to revert to backup. (see thread from 3.1.1 upgrade: http://www.igniterealtime.org/forum/thread.jspa?threadID=23823). Upgrade to 3.2.2 was no different.
Before upgrading to 3.2.2 RPM I looked around some and found this:
#########
Upgrading Wildfire on Linux with an RPM can be accomplished by following these steps.
-
Stop Wildfire.
-
Backup the Wildfire installation directory. This step is critical because the data will be overwritten with the new RPM install.
-
Backup the Wildfire database. Note that the embedded database is backed up in step 2.
-
Install the RPM.
-
Copy the conf directory from the backup to the installation directory.
-
Copy the embedded-db directory from the backup to the installation directory.
-
Copy the enterprise directory from the backup to the installation directory, if it exists.
-
Copy the plugins directory from the backup to the installation directory except for plugins/admin.
-
Copy the resources/security/keystore file from the backup to the installation directory.
-
Copy the resources/security/truststore file from the backup to the installation directory if you modified this file.
-
Start Wildfire.
#########
I tried this and it didn’'t work. I got 503 errors trying to get to admin page. I tried removing old PlugIns as those were shown to cause problems in other threads,…not luck. Users could login to the server but were immediately kicked off…so I reverted to backup.
Although these steps give a general overview, they still do not go into any detail. RPM installations have many options; I’‘ve been told in the past that rpm -Uvh wildfire.rpm would do the trick…but it didn’‘t. I’'ve tried the ‘‘Freshen’’ option, rpm -Fvh wildfire.rpm which also resulted in a broken config.
I was under the impression that the Database would also be upgraded during the install but this hasn’‘t worked either…ever (maybe this only applies to embedded db?). Don’'t get me wrong, I love wildfire and it works great. The initial installation was a breeze, but upgrading rpms has always been a mess.
As a result of these past issues, if I run ‘‘rpm -qa |grep wildfire’’ it returns wildfire-3.2.2-1. When I login to my Admin page it displays version 3.1.1 (since I am running from restored backup after failed upgrade), and the crazy part is that I am likely running these on the DB installed with wildfire-2.6.2!!!
After reading through a bunch of posts I went and looked at my jiveVersion table in MySQL and it lists version 6! Yikes…isn’'t the current version 11?
I’'d love to get this install straightened out… Here is what I am “Thinking” I need to do. PLEASE have a look and provide some feedback if possible:
-
service wildfired stop
-
Backup wildfire directory
-
Backup MySQL Jabber DB
-
Upgrade MySQL Jabber DB Tables/Version
a. Since I show version 6 I’'ll need to incrementally upgrade to version 11?
b. cd /opt/wildfire/resources/database/upgrade/7 ‘‘cat wildfire_mysql.sql | mysql -p Jabber;’’
c. cd /opt/wildfire/resources/database/upgrade/8 ‘‘cat wildfire_mysql.sql | mysql -p Jabber;’’
d. cd /opt/wildfire/resources/database/upgrade/9 ‘‘cat wildfire_mysql.sql | mysql -p Jabber;’’
e. cd /opt/wildfire/resources/database/upgrade/10 ‘‘cat wildfire_mysql.sql | mysql -p Jabber;’’
f. cd /opt/wildfire/resources/database/upgrade/11 ‘‘cat wildfire_mysql.sql | mysql -p Jabber;’’
-
Force rpm install of 3.2.2 since the system thinks it’'s installed already? rpm -ivh, -Uvh, -Fvh --force wildfire-3.2.2-1.rpm? (advice here would be great)
-
Now do I copy the old conf directory, resources/security/keystore, and resources/security/trustore into new /opt/wildfire/ ?
-
service wildfired start
-
Install new plugins
Any help would be greatly appreciated!
Thanks in advance,
Claud1e