Forum Problems Installing LAMS: Re: Re: Re: Re: Re: Re: Re: Re: Problem accessing LAMS after installation


 
Search: 

9: Re: Re: Re: Re: Re: Re: Re: Re: Problem accessing LAMS after installation
In response to 8 12/29/07 09:39 PM
[ Reply | Forward ]
Ernie,

That is correct!

Here is the output:

[root@ip-72-167-46-74 bin]# ps -ef|grep java
jive 1986 1 0 Dec27 ? 00:01:06 /opt/wildfire/jre/bin/java -server -Dinstall4j.jvmDir=/opt/wildfire/jre -Dinstall4j.appDir=/opt/wildfire -Dexe4j.moduleName=/opt/wildfire/bin/wildfire -classpath /opt/wildfire/.install4j/i4jruntime.jar:/opt/wildfire/lib/activation.jar:/opt/wildfire/lib/bouncycastle.jar:/opt/wildfire/lib/commons-el.jar:/opt/wildfire/lib/hsqldb.jar:/opt/wildfire/lib/hsqldbutil.jar:/opt/wildfire/lib/jasper-compiler.jar:/opt/wildfire/lib/jasper-runtime.jar:/opt/wildfire/lib/jdic.jar:/opt/wildfire/lib/jtds.jar:/opt/wildfire/lib/mail.jar:/opt/wildfire/lib/mysql.jar:/opt/wildfire/lib/postgres.jar:/opt/wildfire/lib/servlet.jar:/opt/wildfire/lib/startup.jar:/opt/wildfire/lib/wildfire.jar com.install4j.runtime.Launcher start org.jivesoftware.wildfire.starter.ServerStarter false false /opt/wildfire/bin/../logs/stderror.log /opt/wildfire/bin/../logs/stdoutt.log true true false true true 0 0 20 20 Arial 0,0,0 8 500 version 2.6.2 20 40 Arial 0,0,0 8 500 -1 -DwildfireHome=/opt/wildfire -Dwildfire.lib.dir=/opt/wildfire/lib start
tomcat 2580 1 0 Dec27 ? 00:00:22 /usr/java/jdk1.5.0_13/bin/java -XX:TargetSurvivorRatio=1 -Xverify:none -XX:PermSize=16M -Xms8m -Xmx32m -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/usr/java/tomcat-5.5/conf/logging.properties -Djava.endorsed.dirs=/usr/java/tomcat-5.5/common/endorsed -classpath :/usr/java/tomcat-5.5/bin/bootstrap.jar:/usr/java/tomcat-5.5/bin/commons-logging-api.jar -Dcatalina.base=/usr/java/tomcat-5.5 -Dcatalina.home=/usr/java/tomcat-5.5 -Djava.io.tmpdir=/usr/java/tomcat-5.5/temp org.apache.catalina.startup.Bootstrap start
root 2604 1 0 Dec27 ? 00:00:56 /usr/java/jdk1.5.0_13/bin/java -XX:TargetSurvivorRatio=1 -Xverify:none -XX:PermSize=16M -Xms8m -Xmx48m -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/usr/share/turbopanel/conf/logging.properties -Djava.endorsed.dirs=/usr/share/turbopanel/common/endorsed -classpath :/usr/share/turbopanel/bin/bootstrap.jar:/usr/share/turbopanel/bin/commons-logging-api.jar -Dcatalina.base=/usr/share/turbopanel -Dcatalina.home=/usr/share/turbopanel -Djava.io.tmpdir=/var/turbopanel/temp org.apache.catalina.startup.Bootstrap start
root 18707 18705 2 20:30 ? 00:01:25 /usr/java/jdk1.6.0_03/bin/java -Dprogram.name=run.sh -XX:MaxPermSize=256m -Xms246m -Xmx512m -Djava.library.path=../lib -classpath ../lib/wrapper.jar:../bin/run.jar:/usr/java/jdk1.6.0_03/lib/tools.jar -Dwrapper.key=TDfd1uaT4TB66hmC -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=18705 -Dwrapper.version=3.2.3 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.jboss.Main
root 19038 17079 0 21:26 pts/0 00:00:00 grep java

Posted by Rod Spears

10: Re: Problem accessing LAMS after installation
In response to 9 12/30/07 04:23 AM
[ Reply | Forward ]
Hi Rod,

It seems that you are running another instance of Tomcat (LAMS runs JBoss who also has an embedded Tomcat in it) which seems to collide with LAMS.

Would you know what other application is using Tomcat in this box?

If you do have an application that needs to be running Tomcat and you can't stop it, then here are instructions on how you can get around this. Method 1 seems to be the easiest if your box have multiple IPs. Otherwise Method 2 will require a bit more fiddle with the JBoss configuration files.

If you get stuck, please ask! I've never done this myself, but Jun-Dir, the JBoss King, for sure has.

Thanks,

Ernie

Posted by Ernie Ghiglione

11: Re: Re: Problem accessing LAMS after installation
In response to 10 12/30/07 12:56 PM
[ Reply | Forward ]
Ernie,

I stopped Tomcat and that did not work. Then I tried Option 1 because I have more than one IP address available. Here is a copy of what I did and the results. After I change this IP address, do I need to change my URL in the lams.properties file and use a different URL?

[root@ip-72-167-46-74 bin]# /usr/local/jboss-4.0.2/bin/run.sh -b 72.167.48.28
=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /usr/local/jboss-4.0.2

JAVA: /usr/java/jdk/bin/java

JAVA_OPTS: -server -Xms128m -Xmx128m -Dprogram.name=run.sh

CLASSPATH: /usr/local/jboss-4.0.2/bin/run.jar:/usr/java/jdk/lib/tools.jar

=========================================================================

/usr/java/jdk/bin/java -server -Xms128m -Xmx128m -Dprogram.name=run.sh -Djava.endorsed.dirs=/usr/local/jboss-4.0.2/lib/endorsed -classpath /usr/local/jboss-4.0.2/bin/run.jar:/usr/java/jdk/lib/tools.jar org.jboss.Main -b 72.167.48.28
[root@ip-72-167-46-74 bin]# sudo ./lams2 status
LAMS is not running.
[root@ip-72-167-46-74 bin]# sudo ./lams2 start
Starting LAMS...
[root@ip-72-167-46-74 bin]# sudo ./lams2 status
LAMS is running (4337).
[root@ip-72-167-46-74 bin]#

Posted by Rod Spears

12: Re: Re: Re: Problem accessing LAMS after installation
In response to 11 12/30/07 04:55 PM
[ Reply | Forward ]
Rod,

If you change the IP address, you should change it in the lams.properties in /etc/lams2 for future upgrades. But it won't make any difference to the version of LAMS already installed.

You will need to start using the new IP address when you try to call LAMS ie http://72.167.48.28:8080/lams.

Then if you do get the login screen up then the page may look a little odd, as it may not be loading the stylesheets correctly. Log into LAMS as sysadmin, select the Sys Admin link and go to Edit Configuration Settings. Change the Server URL entry to the new URL.

This highlights an issue with using a numeric IP address, rather than a name for the server. Users will have to use that numeric IP address to access LAMS, or the stylesheets won't load - the url that is specified in the Server URL field is the url used to load the stylesheets and other bits and pieces of rendering bits in LAMS.

Fiona

Posted by Fiona Malikoff

13: Re: Re: Problem accessing LAMS after installation
In response to 10 01/01/08 12:58 AM
[ Reply | Forward ]
Ernie,

I have spent many hours working on a solution over the past several days. While searching for answers, I finally came across something about checking the firewall on my server. When I disabled the firewall, I could access LAMS!!!

During the process, I changed the port to 8180 and it is working on that port after disabling the firewall. Then I changed my firewall to allow access.

Now I am working on integration of LAMS and Moodle.

Posted by Rod Spears

14: Re: Re: Re: Problem accessing LAMS after installation
In response to 13 01/01/08 03:08 PM
[ Reply | Forward ]
Hi Rod,

Great to hear that it was just a firewall issue :-) I can't believe I didn't think about this before!

Anyway, let us know if you have any further problems.

Thanks,

ernie

Posted by Ernie Ghiglione

Reply to first post on this page
Back to Problems Installing LAMS