Page 1 of 1
Somewhat stuck
PostPosted:Fri Jul 23, 2010 2:39 pm
by uii
I installed the JDK 6u21 on a Suse 11.1, then the OpenKM4.1 up to the ./run.sh with the following result
Code: Select alleseem8:/opt/OpenKM-4.1_JBoss-4.2.3.GA # ./run.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/OpenKM-4.1_JBoss-4.2.3.GA
JAVA: /usr/lib64/jvm/java/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=128m -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true
CLASSPATH: /opt/OpenKM-4.1_JBoss-4.2.3.GA/bin/run.jar:/usr/lib64/jvm/java/lib/tools.jar
=========================================================================
Then I started the browser with
http://localhost:8080/OpenKM/ to no avail, and then with
http://localhost:8100/OpenKM/ after I realized the run.sh contains port 8100. But even this to no avail. There should be a $JBOSS_HOME/server/default/log/server.log
file, which is not there.
Meaning the login screen for the OpenKM doesn't appear.
Are there requirements for an apache ? It just wasn't mentioned.
TIA
Re: Somewhat stuck
PostPosted:Fri Jul 23, 2010 3:57 pm
by jllort
The url must be
http://localhost:8080/OpenKM/ don't try with other ... can you take a look at server.log while starting .... there's some error there ? is
http://localhost:8080/ available ?
Do you have some tomcat or similar running there ... you can not use both applications with same ports
Re: Somewhat stuck
PostPosted:Fri Jul 23, 2010 8:32 pm
by uii
There is no "server.log" for whatever reason. There is no tomcat. If there was something on port 8080, then I should get an answer, from localhost:8080, I guess. There is none. However, the file run.sh mentions a port 8100 in the last command "soffice .... ". I doubt to have this soffice, I fear. Where should it be located ?
Re: Somewhat stuck
PostPosted:Mon Jul 26, 2010 8:11 am
by jllort
where have you seen soffice into run.sh ? have you put there, because in our OpenKM sourceforge distribution soffice into run.sh is not present.
Re: Somewhat stuck
PostPosted:Wed Jul 28, 2010 10:10 am
by uii
The content of /opt/OpenKM-4.1_JBoss-4.2.3.GA/run.sh :
Code: Select all#!/bin/bash
rm -rf server/default/tmp
rm -rf server/default/work
rm -rf server/default/log
soffice -headless -accept="socket,host=127.0.0.1,port=8100;urp;" -nofirststartwizard
./bin/run.sh -b 0.0.0.0
Re: Somewhat stuck
PostPosted:Wed Jul 28, 2010 1:19 pm
by jllort
I'll remove from there
soffice -headless -accept="socket,host=127.0.0.1,port=8100;urp;" -nofirststartwizard
and make a script to run as service it, separately
Re: Somewhat stuck
PostPosted:Thu Jul 29, 2010 6:13 am
by uii
Thanks this far. I just figured, that I should have run the /opt/OpenKM-4.1_JBoss-4.2.3.GA/bin/run.sh, instead of the /opt/OpenKM-4.1_JBoss-4.2.3.GA/run.sh, what I did. For whatever reason, the files are also there in the second directory. They are not identical though. So I eventually did run the .... JBoss-4.2.3.GA/bin/run.sh, to no avail. The log file that should be there is still not there. The screen looks like :
Code: Select alleseem8:/opt/OpenKM-4.1_JBoss-4.2.3.GA/bin # ./run.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/OpenKM-4.1_JBoss-4.2.3.GA
JAVA: /usr/lib64/jvm/java/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=128m -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true
CLASSPATH: /opt/OpenKM-4.1_JBoss-4.2.3.GA/bin/run.jar:/usr/lib64/jvm/java/lib/tools.jar
=========================================================================
Hmm... any hint on this ?
Re: Somewhat stuck
PostPosted:Thu Jul 29, 2010 11:09 am
by jllort
curious java path /usr/lib64/
Do you have java jdk 1.6 version installed ?
Re: Somewhat stuck
PostPosted:Thu Jul 29, 2010 3:47 pm
by uii
I installed the latest from Sun, JDK 6u10 or so, for 64bit. But whether exactly this is running or a previous preinstalled version is beyond my scope. They should have a version command to check which version is running. Since this stuff is running on a server I cannot simply reboot, as I would a desktop machine. The next reboot is perhaps months away. The only thing I may do is perhaps start and stop a single service.
Re: Somewhat stuck
PostPosted:Fri Jul 30, 2010 11:07 am
by jllort
You can set JAVA_HOME into run.sh
Re: Somewhat stuck
PostPosted:Tue Aug 03, 2010 8:33 am
by uii
Thanks, it took a while until I figured how to set JAVA to /usr/java/jdk1.6.0_21/bin/java. Now, for an unknown reason the process complains that port 8080 is in use. And some process called coyote tries to have it. However, there is little response when trying to connect to 127.0.0.1:8080 - the connection to the server was reset while the page was loading.
Is there a tool to uncover what process is listening to what port ? Or should I try to change the 8080 to something else ? And if so where in the scripts ?
TIA
Re: Somewhat stuck
PostPosted:Tue Aug 03, 2010 4:54 pm
by jllort
to change jboss port, must edit a file called server.xml into some subfolder in deploy folder ( something like tomcat or web ... I don't remember exactly ) take a look at google "jboss change server port server.xml"