I assume that you need to change the DNS record unless you use the same IP. Copy the rc scripts and the whole Openfire directory to the other server or install it and copy then the certificates, plugins and the whole embedded-db and conf folder to the new server.
that’s odd. Does ps -ef show that the Openfire process is running?
A “kill -3 openfire-pid” should write a javacore to STDOUT of the Openfire process (not sure where it will be written to) or if you have a jdk installed you can run “jstack -l openfire-pid” to get a javacore. This should show whether or where Openfire is hanging during startup.
I decided to delete and redo the entire installation, unfortunately I could not migrate the database, but I believe it is because the server name it, that is not the same as the original one.
just in case that you want to change the server name another time (there are also some threads about this):
“cat openfire.script | sed ‘s#oldname#newname#g’>openfire.script.new” - do this also with the openfire.log file if it does exist and use then the new files. There’s a small risk that you change too much entries, especially if one user did register a JID “oldname@oldname” or a stored message contains “oldname”. And if one has added remote users (s2s) these will of course no longer work correctly as the remote server does not know about your server name change.