powered by Jive Software

Can't connect to administrative console

Openfire has been running fine, but now when I try to connect to the administrative console at http://myserver.com:9090, the browser just hangs. I’ve stopped and started Openfire from the Linux command line, but it doesn’t seem to help. Here are some log excerpts:

warn.log:

2009.01.19 15:33:00 Error creating connection to server.
Connection failed. No response from server.:
at org.jivesoftware.smack.PacketReader.startup(PacketReader.java:170)
at org.jivesoftware.smack.XMPPConnection.initConnection(XMPPConnection.java:851)
at org.jivesoftware.smack.XMPPConnection.connectUsingConfiguration(XMPPConnection. java:810)
at org.jivesoftware.smack.XMPPConnection.connect(XMPPConnection.java:1252)
at org.jivesoftware.webchat.ChatManager.createConnection(ChatManager.java:270)
at org.jivesoftware.webchat.FastpathServlet$1.run(FastpathServlet.java:117)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)

nohup.out:

Error creating server listener on port 5269: Address already in use
Openfire 3.6.3 [Jan 19, 2009 3:31:06 PM]
Admin console listening at:
http://myservercom:9090
https://myserver.com:9091
Starting Client Control Plugin
Starting Fastpath Server
Starting Monitoring Plugin

error.log:

java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:2 05)
at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.jav a:304)
at org.mortbay.jetty.security.SslSelectChannelConnector.doStart(SslSelectChannelCo nnector.java:566)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.Server.doStart(Server.java:233)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.jivesoftware.openfire.http.HttpBindManager.start(HttpBindManager.java:97)
at org.jivesoftware.openfire.spi.ConnectionManagerImpl.startHTTPBindListeners(Conn ectionManagerImpl.java:523)
at org.jivesoftware.openfire.spi.ConnectionManagerImpl.startListeners(ConnectionMa nagerImpl.java:136)
at org.jivesoftware.openfire.spi.ConnectionManagerImpl.access$000(ConnectionManage rImpl.java:54)
at org.jivesoftware.openfire.spi.ConnectionManagerImpl$1.pluginsMonitored(Connecti onManagerImpl.java:108)
at org.jivesoftware.openfire.container.PluginManager.firePluginsMonitored(PluginMa nager.java:533)
at org.jivesoftware.openfire.container.PluginManager.access$800(PluginManager.java :47)
at org.jivesoftware.openfire.container.PluginManager$PluginMonitor.run(PluginManag er.java:1042)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101 (Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodi c(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknow n Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

something else on your server is already using the ports when openfire tries to start. was something else installed on the server or was the firewall settings changed blocking those ports.

I don’t know of any changes. How do I check to see what’s using the port? I’m using Centos Linux.

Now when I try to access the admin console, I’m getting a page, but it’s an error page:

HTTP ERROR: 404

NOT_FOUND

RequestURI=/

Powered by jetty://

Also, my users don’t seem to be able to login using the Spark client (or any other client for that matter). It seems to hang on the Authenticating message.

I discovered there were two instances of openfire running. Once I stopped them both and then restarted, all was fine.