Page 1 of 2

Unable to connect

PostPosted:Fri Apr 09, 2010 8:28 am
by mulerdesign
I coudn't open openkm without terminal configuration

it displays the followiging message
Unable to connect

Firefox can't establish a connection to the server at localhost:8080.

* The site could be temporarily unavailable or too busy. Try again in a few
moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

Re: Unable to connect

PostPosted:Fri Apr 09, 2010 7:36 pm
by jllort
I don't understand it "I coudn't open openkm without terminal configuration".

Tell me something:
1- On which OS are you running OpenKM
2- Have you started jboss server ( in windows probably opens a terminal, you must not close it )
3- You're trying to login - browser - in same server no ?

Give me more information to understand what are you doing

Re: Unable to connect

PostPosted:Mon Apr 12, 2010 6:09 am
by mulerdesign
ok thank you
I am using unix 'Obuntu' OS and installed jboss server, when I am trying to login on Firefox browser the Terminal must be run to work openkm. when close the Terminal and refresh my browser OpenKM stop works and the following error displays

HTTP Status 503 - This application is not currently available
type Status report
message This application is not currently available
description The requested service (This application is not currently available) is not currently available.


"AND NEW BROWSER OPENS THESE ERROR DISPLAY"

Unable to connect
Firefox can't establish a connection to the server at localhost:8080.

* The site could be temporarily unavailable or too busy. Try again in a few
moments.
* If you are unable to load any pages, check your computer's network
connection.
* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

Re: Unable to connect

PostPosted:Mon Apr 12, 2010 5:43 pm
by jllort
Of course, because when you execute in terminal de /bin/run.sh you're not starting a service, you're starting an application, if you close terminal you kill all terminal childs including the jboss running applciation.

You might configure jboss as a service, in wiki it's explained and you can take a look to in google looking for "configuring jboss linus as service"

Re: Unable to connect

PostPosted:Mon Nov 29, 2010 3:08 am
by cinto_qq
Hi,

I just installed OpenKM, and I get the same error even though I did not close the terminal. This happened to all the servers that I installed on, and as I am installing within intranet, there is no firewall blocking.

I am not able to access OpenKM at all. Is there any other settings that I need to change in order to access it?


Cinto

Re: Unable to connect

PostPosted:Mon Nov 29, 2010 6:36 pm
by jllort
I think you're not doing what you're saying. When you've got running on console you can not make CTRL+C or similar ) for example. If it gets a 503 error that means application is not running.

There's no mistery, specially on ubuntu, it's the most easiest place to install OpenKM. Better if you instaling on a fresh OS, because if you're on a testing environment with a lot of installed / uninstalled applications ... all is possible.

Installing OpenKM is so easy. Extract to some folder. Have java installed and then run ( with -b 0.0.0.0 option if you want to binding to all network interfaces ). There's nothing else ...

Re: Unable to connect

PostPosted:Tue Nov 30, 2010 3:24 am
by cinto_qq
Hi Jllort,

While starting the JBoss server and the application, I saw this error:

"java.lang.IllegalArgumentException: Namespace not registered: http://www.openkm.org/1.0"

What does this error mean? I am also not able to shutdown the server with the usual "./shutdown.sh -S". When I do that, I got these errors:
Code: Select all
Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]]
        at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1562)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at org.jboss.Shutdown.main(Shutdown.java:214)
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]
        at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274)
        at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533)
        ... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]
        at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248)
        ... 5 more
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at java.net.Socket.connect(Socket.java:469)
        at java.net.Socket.<init>(Socket.java:366)
        at java.net.Socket.<init>(Socket.java:267)
        at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
        at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
        at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:244)
        ... 5 more
I did not start as a service yet as I just wanted to try it first. Did I do anything wrong?

Cinto

Re: Unable to connect

PostPosted:Tue Nov 30, 2010 10:22 am
by jllort
it's a non relevant warning ( really it's not an error ). First time creation repository show's it ... it's not important.

Re: Unable to connect

PostPosted:Thu Dec 02, 2010 12:53 am
by cinto_qq
Hi Jllort,

Thanks, I am able to get OpenKM to run properly.


Cinto

Re: Unable to connect

PostPosted:Wed Jan 05, 2011 10:21 am
by robshim
Hi,

I would like to test Open KM as a replacement DMS for our hospital but get the same error:

"Firefox can't establish a connection to the server at localhost:8080."

Please advise what to do,

Thanks,

Rob

Re: Unable to connect

PostPosted:Wed Jan 05, 2011 6:40 pm
by jllort
you must stablish connection to your http://serverip:8080/OpenKM

You must run to binding in all network interfaces of server as: run.sh -b 0.0.0.0 take a look a wiki http://wiki.openkm.com/index.php/Basic_ ... _knowledge the section "Making OpenKM accesible to other computers "

Re: Unable to connect

PostPosted:Fri Jan 14, 2011 7:43 pm
by khawley
Thank you for the note about adding the -b 0.0.0.0 switch to the run.sh call. I'm running cPanel/WHM on Cent OS and OpenKM couldn't connect without that switch. I highly recommend putting it in the Quick Install instructions.

Re: Unable to connect

PostPosted:Thu Jan 20, 2011 8:40 pm
by pavila
Added to Quick Install Guide as suggested.

Re: Unable to connect

PostPosted:Fri Feb 04, 2011 2:29 pm
by uii
The installation guide is somewhat incomplete. I was only able to get it running after having JRE, the java runtime library, not the JDK, the developper library, installed. I had to change the rights of the /usr/java to wwwrun:www (user:group). Then after unzipping the JBoss into /opt, I also had to change the rights of the lot to wwwrun:www (user:group). In addition, I had to make the JBoss directory executable. Thanks for considering.

Re: Unable to connect

PostPosted:Sat Feb 05, 2011 11:25 am
by jllort
Hi uui,

It's not incomplete, but must considering we can not specifiying all possible issues must be done in any linux server configuration. It's suposed some administrator skills on their own server environments. Obviously user who executes application server must have right to execute it. If you install in /opt must propagate it, if you install in some /home/user are setting by default.

About jdk, you're wrong, java sun jdk is enought to running application server ( and better that simply jre, really jdk has upper library collection that jre, and includes jre and something more ). About java folder java privileges, that depends how installing in your OS. For exemple on ubuntu with simply command it's installed ( java aptitude install java sun-java6-jdk ) in other linux distribution could be needed some extra job ( sorry for it, but we can not comment all scenarios, althought it, if you give to us your distribution and the commands you've used, well post in our wiki, and it'll be usefull for other user ).