Up to Discussions in Openfire Support

This Question is Answered (go to answer)

1 "helpful" answer available (5 pts)
2,858 Views 17 Replies Last post: Nov 18, 2007 10:10 AM by James Rome RSS
Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated

Nov 16, 2007 1:19 PM

Cannot connect to admin console

 

I just installed OpenFire on my MacPro running Leopard. The server claims to be started, but I cannot connect to the Admin Console in System Prerences. I tried

 

 

http://127.0.0.1:9090 manually, but that did not connect either. I see nothing in the firewall logs.

 

 

So how do I administer the server?

 

 

Tags: openfire
LG KeyContributor
LG
5,452 posts since
Dec 13, 2005
Currently Being Moderated
Nov 16, 2007 1:43 PM in response to: James Rome
Re: Cannot connect to admin console

Hi James,

 

I guess that also on MacPro Openfire writes log files, maybe you can take a look at them and verify whether Openfire opens port 9090 or not. info.log should contain a line with "Admin console listening at: http://hostname:9090/"

 

LG

Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated
Nov 16, 2007 2:12 PM in response to: LG
Re: Cannot connect to admin console

 

2007.11.16 15:49:33 Admin console listening at http://127.0.0.1:9090

 

 

But it does not answer

 

 

The error log is empty.

 

 

 

 

 

LG KeyContributor
LG
5,452 posts since
Dec 13, 2005
Currently Being Moderated
Nov 16, 2007 2:17 PM in response to: James Rome
Re: Cannot connect to admin console

Hi James,

 

are the server and your browser are on the same computer?

Do you have something like a "shell" on Mac where you can enter "netstat -an | grep 9090" to verify that port 9090 is open?

 

LG

Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated
Nov 16, 2007 2:30 PM in response to: LG
Re: Cannot connect to admin console

 

It seems to be listening:

 

 

sh-3.2# netstat -an | grep 9090

tcp4       0      0  127.0.0.1.9090         127.0.0.1.54750        ESTABLISHED

tcp4       0      0  127.0.0.1.54750        127.0.0.1.9090         ESTABLISHED

tcp46      0      0  *.9090            & nbsp;    .             &n bsp;      LISTEN

tcp4       0      0  *.9090            & nbsp;    .             &n bsp;      LISTEN

c58bc38 stream      0      0        0  c690908        0        0 /var/run/mDNSResponder

c690908 stream      0      0        0  c58bc38        0        0

 

 

LG KeyContributor
LG
5,452 posts since
Dec 13, 2005
Currently Being Moderated
Nov 16, 2007 2:48 PM in response to: James Rome
Re: Cannot connect to admin console

Hi James,

 

it looks like you are connected with your browser.

tcp4 0 0 127.0.0.1.9090 127.0.0.1.54750 ESTABLISHED

tcp4 0 0 127.0.0.1.54750 127.0.0.1.9090 ESTABLISHED

So I wonder if Openfire has a bug and does not send any data to the browser.

 

You could try again in the shell:

telnet 127.0.0.1 9090

and then enter completely blind:

GET /login.jsp HTTP/1.0

 

 

press enter a few times and wait for a response. If a lot of HTML code is displayed then it could be a problem with your browser.

 

LG

Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated
Nov 16, 2007 3:55 PM in response to: LG
Re: Cannot connect to admin console

Its the app:

 

sh-3.2# telnet 127.0.0.1 9090

Trying 127.0.0.1...

Connected to ad.doubleclick.net.

Escape character is '^]'.

GET /login.jsp HTTP/1.0

GET %2Flogin.jsp HTTP%2F1.0

 

 

 

 

 

 

 

 

 

 

and that is all it writes out

 

 

 

 

 

(I have ad.doubleclick.net routed to localhost to stop any connections to it, but that should not affect this since localhost:9000 works)

LG KeyContributor
LG
5,452 posts since
Dec 13, 2005
Currently Being Moderated
Nov 17, 2007 3:00 AM in response to: James Rome
Re: Cannot connect to admin console

Hi James,

 

I hope that David brings up some more details, for me this looks like an "echo service" and not like Openfire responding. You could also try to connect to your network IP (192.168.1.1 or something like this) with http://192.168.1.1:9090/ - but you may get the same result as on localhost.

 

LG

Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated
Nov 17, 2007 5:34 AM in response to: LG
Re: Cannot connect to admin console

Same none response with the ip number.

Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated
Nov 17, 2007 6:35 AM in response to: James Rome
Re: Cannot connect to admin console

Hmmm. I turned OpenFire off, and get the same response to Telnet. How can this be?

 

 

How do I uninstall OpenFire, by the way. If we cannot figure this out, it is doing me no good.

 

 

Thanks,

 

 

Jim

LG KeyContributor
LG
5,452 posts since
Dec 13, 2005
Currently Being Moderated
Nov 17, 2007 6:50 AM in response to: James Rome
Re: Cannot connect to admin console

Hi Jim,

 

are you sure that Openfire is really stopped, or is it possible that you have inetd running?

Did you try https://127.0.0.1:9091/ ? Can you try to connect to any other port (like 12345)? If you do not get a response there then you may want to edit conf/openfire.xml and adjust the port to one which is not used.

 

LG

Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated
Nov 17, 2007 7:05 AM in response to: LG
Re: Cannot connect to admin console

 

I stopped it using the Mac System Preferences for OpenFire. It would be good for users if you told people where OpenFire was installed. I was not able to find it easily.

 

 

Switching it to 9099 worked!  Maybe Leopard has something else running on 9090?

 

 

Aznidin KeyContributor
Aznidin
508 posts since
Jul 5, 2006
Currently Being Moderated
Nov 17, 2007 7:09 AM in response to: James Rome
Re: Cannot connect to admin console

Hi Jim,

 

 

 

I don't know much about Mac shell. As root, can you do something like the following?

 

sh-3.2# lsof -i :9090

 

In Linux that shows who owns the listening port. If it's Openfire application, it should show something like:

 

COMMAND   PID   USER   FD   TYPE DEVICE SIZE NODE NAME

java    24381 daemon   46u  IPv6  89917       TCP *:9090(LISTEN)

 

Otherwise, it could be some other application.

David Smith KeyContributor
David Smith
189 posts since
Jan 11, 2007
Currently Being Moderated
Nov 16, 2007 2:20 PM in response to: James Rome
Re: Cannot connect to admin console

It's possible that there is a bug in the installer when running on Leopard. I have tested upgrade installs thoroughly, but only did cursory initial installation testing. I'll try to get to that soon and let you know what I find.

Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated
Nov 16, 2007 6:54 PM in response to: David Smith
Re: Cannot connect to admin console

Thanks. It could be the new Leopard application firewall too. It is impossible to set it for a new system service. But there is nothing in the firewall logs.

 

I can connect to my slimserver on 9000 though, but since it is a .app, I can put it into the firewall.

 

 

 

 

 

I tried connecting from another PC to it, and got

 

 

 

Nov 16 17:36:15 jarmac Firewall[56]: Allow perl connecting from 192.168.1.49:1195 uid = 0 proto=6

 

 

 

Is this app written in perl? But still does not connect. I think the server must be screwed up.

 

 

Its not the firewall because the above tcp test worked.

Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated
Nov 17, 2007 8:05 AM in response to: James Rome
Re: Cannot connect to admin console

 

So now the server is running, but I get errors. In the warning log, I get:

 

<span class="date">2007.11.17 10:18:46 Error when trying to update to new name

             &n bsp; java.sql.SQLException: Table not found in statement

             &n bsp; at org.hsqldb.jdbc.Util.throwError(Unknown Source)

             &n bsp; at org.hsqldb.jdbc.jdbcPreparedStatement.&lt;init&gt;(Unknown Source)

             &n bsp; at org.hsqldb.jdbc.jdbcConnection.prepareStatement(Unknown Source)<span class="hilite">at org.jivesoftware.database.AbstractConnection.prepareStatement(AbstractConnectio n.java:36)<span class="hilite">at org.jivesoftware.database.SchemaManager.updateToOpenfire(SchemaManager.java:298 )<span class="hilite">at org.jivesoftware.database.SchemaManager.checkOpenfireSchema(SchemaManager.java: 66)<span class="hilite">at org.jivesoftware.database.DbConnectionManager.setConnectionProvider(DbConnectio nManager.java:467)<span class="hilite">at

             &n bsp; org.jivesoftware.openfire.admin.setup.setup_002ddatasource_002dsetting s_jsp._jspService(setup_002ddatasource_002dsettings_jsp.java:155)

             &n bsp; at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)

             &n bsp; at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

             &n bsp; at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)

             &n bsp; at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1093)

             &n bsp; at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:11 8)

             &n bsp; at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)

             &n bsp; at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1084)<span class="hilite">at org.jivesoftware.util.LocaleFilter.doFilter(LocaleFilter.java:65)

             &n bsp; at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1084)<span class="hilite">at org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingF ilter.java:41)

             &n bsp; at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1084)<span class="hilite">at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)

             &n bsp; at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1084)<span class="hilite">at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

             &n bsp; at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1084)

             &n bsp; at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

             &n bsp; at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

             &n bsp; at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)

             &n bsp; at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)

             &n bsp; at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)

             &n bsp; at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollect ion.java:211)

             &n bsp; at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

             &n bsp; at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)

             &n bsp; at org.mortbay.jetty.Server.handle(Server.java:313)

             &n bsp; at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)

             &n bsp; at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.j ava:830)

             &n bsp; at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)

             &n bsp; at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)

             &n bsp; at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)

             &n bsp; at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)

             &n bsp; at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) <span class="date">2007.11.17 10:20:32 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.<span class="date">2007.11.17 10:20:32 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

 

I also get errors:

 

<span class="hilite"><span class="date">2007.11.17 10:57:35

             &n bsp; org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSessi on(LocalOutgoingServerSession.java:258)

             &n bsp; Error trying to connect to remote server: conference.jarmoc.local(DNS

             &n bsp; lookup: conference.jarmoc.local:5269)

             &n bsp; java.net.UnknownHostException: conference.jarmoc.local

             &n bsp; at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)

             &n bsp; at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)

             &n bsp; at java.net.Socket.connect(Socket.java:520)<span class="hilite">at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)<span class="hilite">at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:143)<span class="hilite">at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:205)<span class="hilite">at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:185)

             &n bsp; at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 650)

             &n bsp; at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)

             &n bsp; at java.lang.Thread.run(Thread.java:613)<span class="hilite"><span class="date">2007.11.17 10:57:35

             &n bsp; org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSessi on(LocalOutgoingServerSession.java:258)

             &n bsp; Error trying to connect to remote server: jarmoc.local(DNS lookup:

             &n bsp; jarmoc.local:5269)

             &n bsp; java.net.UnknownHostException: jarmoc.local

             &n bsp; at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)

             &n bsp; at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)

             &n bsp; at java.net.Socket.connect(Socket.java:520)

 

jarmac.local is defined in /etc/hosts:

 

 

127.0.0.1       localhost jarmac.local

 

 

 

 

 

LG KeyContributor
LG
5,452 posts since
Dec 13, 2005
Currently Being Moderated
Nov 17, 2007 1:12 PM in response to: James Rome
Re: Cannot connect to admin console

Hi,

 

I assume that you did a fresh installation and that the warning "Error when trying to update to new name" did occur exactly one time. Or did you connect this server to an existing, old Wildfire or Openfire database?

 

You may want to add conference.jarmoc.local to your /etc/hosts file if you want to manage s2s via the /etc/hosts file. An alternative and maybe better solution is to handle this within Openfire by setting a "System Property", see Openfire Properties

 

LG

Bronze
James Rome
21 posts since
Nov 8, 2007
Currently Being Moderated
Nov 18, 2007 10:10 AM in response to: James Rome
Re: Cannot connect to admin console

Thanks everyone for the help. It would be good to know what else runs on 9090 on a Mac. Switching the port to 9099 fixed it.

More Like This

  • Retrieving data ...

Bookmarked By (0)