powered by Jive Software

Openfire migration between servers linux

Hello,

I need to migrate service openfire to another server linux, I’m using the embedded-database db

-Rwxrwxrwx 1 daemon daemon 1.7M Jun 21 18:13 openfire.log
-Rwxrwxrwx 1 daemon daemon 411 Jun 21 18:13 openfire.properties
-Rwxrwxrwx 1 daemon daemon 1.1g Jun 21 18:14 openfire.script

What are the steps required for this change?

Hi,

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.

LG

Performed the procedures, less name resolution in DNS, because I can not let the current openfire unavailable.

On test server I left the / etc / hosts like this:

192.168.15.31 im.dedic im.dedic.corp

im.dedic the server name so I tried that.

Later on the procedure, but unfortunately when I type nothing appears http://192.168.15.37:9090.

and port 9090 is not in LISTEN on Linux

Netstat-natup

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID / Program name
tcp 0 0 0.0.0.0:6051 0.0.0.0: * LISTEN 27471/caagentd
tcp 0 0 0.0.0.0:3306 0.0.0.0: * LISTEN 12565/mysqld
tcp 0 0 0.0.0.0:22 0.0.0.0: * LISTEN 21446/sshd
tcp 0 0 192.168.15.31:44701 ESTABLISHED 10.130.33.9:445 28169/winbindd
tcp 0 0 192.168.15.31:50305 ESTABLISHED 10.130.33.9:389 28170/winbindd
tcp 0 0 192.168.15.31:51671 ESTABLISHED 10.130.33.9:445 28170/winbindd
tcp 0 0 192.168.15.31:22 10.130.34.181:51461 ESTABLISHED 2567 / 0
udp 0 0 0.0.0.0:6051 0.0.0.0: * 27471/caagentd
0.0.0.0:41524 udp 0 0 0.0.0.0: * 27471/caagentd
udp 0 0 0.0.0.0:5353 0.0.0.0: * 21413/avahi-daemon:
0.0.0.0:46718 udp 0 0 0.0.0.0: * 21413/avahi-daemon:
udp 0 0::: 5353::: * 21413/avahi-daemon:
udp 0 0::: 53 487::: * 21413/avahi-daemon:

info.log just the file appears:

cat info.log
06/22/2010 12:52:28 Openfire 3.6.4 [22/06/2010 12:52:28]
22.06.2010 12:52:30 Administration Console hearing in http://127.0.0.1:9090

Thank’s a lot.

Hi,

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.

LG

Hello,

The output of ps-ef is

ps-ef | grep openfire

daemon 3375 January 1999 16:13? 00:00:06 / usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java-server-DopenfireHome = / opt / openfire-Dopenfire.lib.dir = / opt / openfire / lib-classpath / opt / openfire / lib / startup.jar-jar / opt / openfire / lib / startup.jar

#kill -3 3375

ps -ef |grep openfire

daemon 3375 1 99 16:13 ? 00:02:41 /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java -server -DopenfireHome=/opt/openfire -Dopenfire.lib.dir=/opt/openfire/lib -classpath /opt/openfire/lib/startup.jar -jar /opt/openfire/lib/startup.jar
root 3422 2569 0 16:15 pts/0 00:00:00 grep openfire

This daemon not die !!

Thank’s

Hi,

do you use the same JDK on both servers? Some users did report problems with OpenJDK.

“kill -3 pid” does not kill the process, the JVM writes a javacore to STDOUT, maybe somwhere in the /opt/openfire/logs/ directory.

LG

Hello,

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.

I appreciate your help

Hi,

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.

LG