Unsure what to tell you, somebody has to fix the issues first. No magic happening here, volunteers doing actual work. Do you have some patches to share?
no, I don’t code, but if so many people has problems, at least halt the release…
If a patch is even doable. You will have to accommodate to every possible starting scenario (upgrading from version x, then do y, from version z, then do w, etc.). Such hotfix will become a messy hack.
I already have a PR for review that should resolve this issue. https://github.com/igniterealtime/Openfire/pull/951
After updating the server (from 4.1.6 to 4.2.0 and then to 4.2.1) the clients (Spark 184.108.40.2060) can’t connect to the server.
¿Can We go back to the OpenFire 4.1.6 without restoring a backup copy?
should be able to, but I suspect we can fix your 4.2.1 issue and make it work. Did openfire fully stop prior to upgrading it?
Yeah. I always stop the service before upgrading.
Are you able to access the Openfire Admin Console?
Yeah. I can access the Admin Console.
if you want to zip up your openfire logs/ folder and email them to me, I can have a look to see what’s up. firstname.lastname@example.org
lots of errors logged, like
2017.12.08 21:29:29 ERROR [pool-4-thread-1]: org.jivesoftware.openfire.container.PluginMonitor - An unexpected exception occurred: java.util.concurrent.ExecutionException: java.lang.NullPointerException: Plugin could not be located: clustering at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at org.jivesoftware.openfire.container.PluginMonitor$MonitorTask.run(PluginMonitor.java:310)
Is this actually a cluster? Did you download updated plugins or are you running updated plugins in an older openfire?
I don’t have a cluster installation. I don’t remember when was the last time I updated the plugins.
can you provide
ls -l output for your
plugins folder? On the admin console, can you view installed plugins and attempt to update any that need it?
I would suggest moving all those files from 2016 out of that folder and restarting Openfire. Then see what happens
Thanks for working with me, you likely found a bug here. OF-1453