D’oh! I had forgotten to upgrade the plugins before starting the server. That, however, was only half the battle and the battle doesn’t seem to be complete.
I noticed that on the first openfire start after untarring the upgrade, the stdoutt.log file still said 3.5.2 and all my plugins would fail (they require 3.6.0). I stopped openfire and started it again, and stdoutt.log then noted 3.6.0 and some database upgrades. Sweet!
However, when it finished all that it tries to start up the plugins and never quite makes it all the way through - the last line of output in my stdoutt.log file is
Starting Monitoring Plugin
I’m not sure if it’s getting stuck on the monitoring plugin or the whichever plugin it goes to next, but I cannot get openfire to start or get past this point.
My total list of plugins is: broadcast, clientControl, gateway, monitoring, search, and userimportexport (userimportexport is probably not needed since it didn’t do what I was hoping to trick it in to doing).
Is it possible to remove the plugin .jar files, add them in after the upgrade and the console is running, and still have them pull old date (like old archives for the monitoring plugin…)???
edit: it looks like the monitoring plugin is the one stalling…
edit2: I removed the monitoring plugin, as well as some others, and the 503 error is still there. sigh
edit3: VICTORY
I tried one more time…
From 3.5.2 I untared 3.6.0a on top. Restored the exodus.xml file and resources/security directory. Moved in the brand new versions of each plugin I have that had a brand new version.
Started openfire and let it spit out “plugin whatever: requires server version 3.6.0” into stdoutt.log for about 15 minutes.
Stopped and restarted openfire. Let it update the database (took just a few seconds) and sit for another few minutes.
Then everything started working.
All the old archives and rosters seem to be there… I will probably wait to hear more about this user-disconnect issue, but everything looks good so far.