Wildfire server crash thrice in a day

Hello,

Recently i installed wildfire_3_0_1.rpm but after installation, Wildfire server crashes twice or thrice in a day unexpectedly.

suseserver:/opt/wildfire/logs # tail -f error.log

2006.09.27 03:50:01 org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java:1 04) Connection closed before session established

Socket[addr=/192.168.1.16,port=41298,localport=5269]

2006.09.27 03:59:08 org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java:1 04) Connection closed before session established

Socket[addr=/192.168.1.16,port=34328,localport=5269]

2006.09.27 03:59:08 org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java:1 04) Connection closed before session established

Socket[addr=/192.168.1.16,port=34329,localport=5269]

2006.09.27 08:23:22 org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java:1 04) Connection closed before session established

Socket[addr=/192.168.1.16,port=52535,localport=5269]

2006.09.27 08:23:22 org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java:1 04) Connection closed before session established

Socket[addr=/192.168.1.16,port=52536,localport=5269]

suseserver:/opt/wildfire/logs # tail -f warn.log

2006.09.26 08:42:07 Closing session due to incorrect hostname in stream header. Host: 192.168.1.16. Connection: org.jivesoftware.wildfire.net.SocketConnection@d5146d socket: Socket[addr=/192.168.1.16,port=58212,localport=5269] session: null

2006.09.26 08:42:26 Closing session due to incorrect hostname in stream header. Host: 192.168.1.16. Connection: org.jivesoftware.wildfire.net.SocketConnection@1eae6fb socket: Socket[addr=/192.168.1.16,port=58214,localport=5269] session: null

2006.09.26 08:45:26 Closing session due to incorrect hostname in stream header. Host: 192.168.1.16. Connection: org.jivesoftware.wildfire.net.SocketConnection@142fb92 socket: Socket[addr=/192.168.1.16,port=47612,localport=5269] session: null

2006.09.26 12:56:10 Closing session due to incorrect hostname in stream header. Host: 192.168.1.16. Connection: org.jivesoftware.wildfire.net.SocketConnection@1b2f057 socket: Socket[addr=/192.168.1.16,port=52960,localport=5269] session: null

2006.09.26 12:58:55 Closing session due to incorrect hostname in stream header. Host: 192.168.1.16. Connection: org.jivesoftware.wildfire.net.SocketConnection@197e57c socket: Socket[addr=/192.168.1.16,port=52962,localport=5269] session: null

2006.09.26 10:06:54 Closing session due to incorrect hostname in stream header. Host: 192.168.1.16. Connection: org.jivesoftware.wildfire.net.SocketConnection@8b6c39 socket: Socket[addr=/192.168.1.16,port=40629,localport=5269] session: null

2006.09.26 10:37:13 Closing session due to incorrect hostname in stream header. Host: server.arpatech. Connection: org.jivesoftware.wildfire.net.SocketConnection@15291cd socket: Socket[addr=/192.168.1.16,port=39239,localport=5269] session: null

2006.09.27 03:50:01 Closing session due to incorrect hostname in stream header. Host: 192.168.1.16. Connection: org.jivesoftware.wildfire.net.SocketConnection@1493995 socket: Socket[addr=/192.168.1.16,port=41298,localport=5269] session: null

2006.09.27 03:59:08 Closing session due to incorrect hostname in stream header. Host: 192.168.1.16. Connection: org.jivesoftware.wildfire.net.SocketConnection@718e31 socket: Socket[addr=/192.168.1.16,port=34328,localport=5269] session: null

2006.09.27 08:23:22 Closing session due to incorrect hostname in stream header. Host: 192.168.1.16. Connection: org.jivesoftware.wildfire.net.SocketConnection@1ba0281 socket: Socket[addr=/192.168.1.16,port=52535,localport=5269] session: null

suseserver:/opt/wildfire/logs # tail -f admin-console.log

10:16:46.734 WARN!! [Update Manager] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >04> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

10:16:48.069 WARN!! [Update Manager] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >04> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

10:37:31.739 ERROR! [SocketListener0-0] uk.ltd.getahead.dwr.util.CommonsLoggingOutput.error(CommonsLoggingOutput.java:7 5) >40> Line=19 The content of element type “dwr” must match “(init?,allow?,signatures?)”.

06:16:39.167 ERROR! [SocketListener0-2] uk.ltd.getahead.dwr.util.CommonsLoggingOutput.error(CommonsLoggingOutput.java:7 5) >40> Line=19 The content of element type “dwr” must match “(init?,allow?,signatures?)”.

06:16:59.225 WARN!! [SocketListener0-1] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >31> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

06:17:00.477 WARN!! [SocketListener0-1] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >31> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

06:17:19.112 WARN!! [SocketListener0-2] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >31> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

06:17:23.259 WARN!! [SocketListener0-2] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >31> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

06:17:27.103 WARN!! [SocketListener0-2] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >31> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

06:17:28.267 WARN!! [SocketListener0-2] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >31> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

Thanks in advance.

Hi,

do you see errors in nohup.out, stdout.log or stderr.log?

Do you see something in /var/log/messages?

LG