I thought maybe I had this issue resolved when I performed some mysql database repairs ( a few tables had issues showing up in the logs), but it appears not. After a couple of days of operation, the server stopped responding again this morning. I looked at the error and warn logs and noticed this:
at org.apache.lucen2015.08.17 08:41:36 org.jivesoftware.openfire.filetransfer.proxy.ProxyConnectionManager - Error creating server socket
java.net.BindException: Address already in use
This is followed by other errors such as:
2015.08.17 08:41:36 org.jivesoftware.openfire.FlashCrossDomainHandler - Could not listen on port: 5229
java.net.BindException: Address already in use
At the point when this occurred, the server had been running for a little over 3 days and had already been used this morning for a couple of hours. When this occurred, no one’s messages were being processed by the server any more.
I attempted to resolve this by performing a “service openfire stop” followed by a “service openfire start”. I was surprisingly met by a message stating it was already running. The next step was a server restart.
On the first restart, the server hung starting mysqld. I restarted again and mysqld started correctly. Openfire also appeared to start, but when trying to access the management portal, I was met by the setup wizard. I checked /opt/openfire/conf and saw that openfire.xml and security.xml were now owned by root rather than daemon, so I used chown to set them back to daemon. I restarted openfire again, this time using /etc/init.d/openfire stop and /etc/init.d/openfire start. It again said that openfire was already running after successfully stopping it.
At this point, messages appear to be flowing and the archiving plugin is showing conversations and traffic. I’m at a loss as to what is going on with this server all of a sudden though. It seems like the security.xml and openfire.xml permissions change to root on restart, which causes some issues. It also seems like multiple instances of openfire are trying to startup for some reason. I don’t know if this is a new issue with 3.10.2 or not, but I suspect it is. Prior to that we had a cpu utilization issue, but this is something different entirely.
What’s my best course of action at this point? Can this be repaired fairly easily? Am I better off building a new, clean, Openfire server and migrating mysql database and openfire settings somehow (I’m not an expert with this)? Rollback to 3.9.3 (how would I do this)?
Thanks for your help with this!