Openfire 3.6.3 + centos 5.3, admin console

Hi,

I have a big problem with openfire :

In a fresh install of centos 5.3 in virtualbox:

  • rpm -ivh openfire-3.6.3-1.i386.rpm : OK
  • /etc/init.d/openfire start : OK
  • debug.log : nothing
  • error.log : nothing
  • warn.log : nothing
  • info.log :
    date Openfire 3.6.3 [date]
    date Admin console listening at http://127.0.0.1:9090
  • nohup.out :
    Openfire 3.6.3 [date]
    Admin console listening at http://127.0.0.1:9090
  • netstat -an | grep 9090 :
    tcp 0 0 :::9090 :::* LISTEN
  • iptables -L
    Chain INPUT (policy ACCEPT)
    target prot opt source destination
    ACCEPT all – anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all – anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all – anywhere anywhere

  • admin console : OK
    In my existing centos 5.3 in a dedicated server :
  • rpm -ivh openfire-3.6.3-1.i386.rpm : OK
  • /etc/init.d/openfire start : OK
  • debug.log : nothing
  • error.log : nothing
  • warn.log : nothing
  • info.log :
    date Openfire 3.6.3 [date]
  • nohup.out :
    Openfire 3.6.3 [date]
  • netstat -an | grep 9090 : nothing
  • iptables -L
    Chain INPUT (policy ACCEPT)
    target prot opt source destination
    ACCEPT all – anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all – anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all – anywhere anywhere

  • admin console : KO

Hi,

try to get the PID of the java process (ps -ef|grep openfire) and then create a javacore (kill -3 Openfire-PID). It should be written to nohup.out.

JVM Settings and Debugging may also be interesting.

LG

double post

This is my nohup.out, but y can’t understand this.
nohup.out (9836 Bytes)

Hi,

are you using the same JDK / JRE for both servers?

If you have the chance to use an older or newer JRE then try using it.

One can see that the thread “pool-1-thread-1” hangs in sun.security.provider.SeedGenerator.getSeedBytes() which means that /dev/random or /dev/urandom blocks. This seems to happen with some JRE’s, maybe it’s an issue with OpenJDK.

LG

jre in 2 case :

/opt/openfire/jre/bin/java

Hi,

so you may want to visit java.sun.com and download jre1.6.0_13 and install it on the server. I have no idea why it works one time and the other time it fails. The JRE could use processor-specific extentions or have problems with multi-core or multiple CPUs.

LG

Setting the java parameter -Djava.security.egd=file:/dev/urandom could also help.

same problem with sun jre and with or without -Djava.security.egd=file:/dev/urandom or /dev/random
nohup.out (6852 Bytes)