First let me say I LOVE Widefire / Openfire but I am very upset about how the latest upgrade process.
Today I was prompted to upgrade just like past upgrades. The link pointed me to the new download. I ran the new download only to find out that unlike upgrades in the past my old version was COMPLETLY wiped out!
I REALLY wish during the upgrade a notice would have stated that unlike old upgrades this one would not convert your old database automatically and it would be deleted.
The employee Calls and Emails are starting to come in now asking why they cannot log into Spark. Uuuggghhh… Now I have to re-created each and every single account over again.
I am SHOCKED that during the upgrade process NOWHERE was it stated that your old database would be deleted .
Sorry about that. I still need to post the news about Openfire 3.3.0 including the upgrade guide. But before doing that I need to check that the startup script included in the RPM is working fine.
Were you using the embedded or an external database? In any case the information is not lost. If you were using the embedded then you need to rename the files as explained in the upgrade guide so that Openfire can locate it and use it.
Looks like that worked. YEA! Thanks! Having problems with the service for some reason. It installed just fine but I cannot connect to it (but that problem is for a different thread) at least the standard runfile works for now and I didn’'t have to retype 3,000 names.
Good to hear that it is now working for you. The service in the init.d has to be updated too. You may want to remove the old one and create the new one that will use the bin/extra/openfired script instead of the old one bin/extra/wildfired.
I really like Openfire also, but my first response to all the upgrading is…
Do you backup your databases on a regular bases? If you did, you wouldn’'t be pulling your hair out thinking you had to re-create all your users.
I understand each admin has their own methods, but as a suggestion, the first thing I do before installing the newest version is to stop the service and back-up the entire install folder (I use built in db). That way if something goes wrong, I can revert to that back up and re-install the previous version.
Another question I have is since when does the automatic update force you to install the newest version? I just get a message on the main admin page that says there is a new version available.
I am glad I found this thread, I was searching all day for any documentation for updating from 3.2.4 to 3.3.
Yes I did. The old service was stopped and removed, the new service said it started fine (even in the windows services menu), but I could not connect with any clients or through the admin interface. As soon as I shut it down and then start the normal run file I can connect just fine.