Forum Problems Installing LAMS: Problem installing/running LAMS 2.0.4 on MacOS 10.4.10

Try not setting JAVA_HOME and the PATH - I know that's against instructions but I actually test the Unix installers on a Mac, and it works for me even if I don't set the values.

I have attached a lams.properties file from my Mac.

If LAMS has installed correctly, then there should be a new directory

/usr/local/jboss-4.0.2/server/default/deploy/lams.ear/

and that should have a whole pile of .war and .jar files.

Hope this helps!

Fiona

ps we agree that the MacOSX installer would be awesome. Its on the extremely long todo list.

Posted by Fiona Malikoff

Thanks so much for your response. I restarted my Mac and followed your suggestion.

1. Changed the lams.properties to include JDK_DIR=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/

2. I did not set JAVA_HOME or PATH.

3. Ran the install-lams.sh.

It seems the installation completed successfully (as before).

Here is the contents of /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/:

FCKeditor-2.3.jar lams-tool-lachat11.jar
META-INF lams-tool-lachat11.war
antlr.jar lams-tool-lafrum11.jar
axis-ant.jar lams-tool-lafrum11.war
axis.jar lams-tool-lamc11.jar
cglib-nodep-2.1_2.jar lams-tool-lamc11.war
cglib_jboss404GA.jar lams-tool-lanb11.jar
commons-beanutils.jar lams-tool-lanb11.war
commons-codec-1.3.jar lams-tool-lantbk11.jar
commons-collections.jar lams-tool-lantbk11.war
commons-digester.jar lams-tool-laqa11.jar
commons-discovery-0.2.jar lams-tool-laqa11.war
commons-fileupload.jar lams-tool-larsrc11.jar
commons-lang-2.0.jar lams-tool-larsrc11.war
commons-logging.jar lams-tool-lasbmt11.jar
commons-validator.jar lams-tool-lasbmt11.war
concurrent-1.3.4.jar lams-tool-lascrb11.jar
dom4j-1.5.2.jar lams-tool-lascrb11.war
gnujaxp.jar lams-tool-lasurv11.jar
hibernate3.jar lams-tool-lasurv11.war
jakarta-oro.jar lams-tool-lavote11.jar
jaxrpc.jar lams-tool-lavote11.war
jboss-cache.jar lams-valve.jar
jboss-common.jar lams-www.war
jboss-jmx.jar lams.jar
jboss-system.jar log4j-1.2.13.jar
jcommon-1.0.0.jar mysql-connector-java-3.1.12-bin.jar
jdom.jar odmg-3.0.jar
jfreechart-1.0.1.jar poi-2.5.1-final-20040804.jar
jgroups.jar quartz.jar
jmock-2004-03-19.jar saaj.jar
joda-time-0.98.jar smack.jar
jstl.jar smackx.jar
lams-admin.jar spring.jar
lams-admin.war standard.jar
lams-central.jar stax-1.1.1-dev.jar
lams-central.war stax-api-1.0.jar
lams-contentrepository.jar struts-el.jar
lams-dictionary.jar struts.jar
lams-learning.jar wddx.jar
lams-learning.war wsdl4j-1.5.1.jar
lams-learning.war.bak xml-writer-0.2.jar
lams-monitoring.jar xom-1.0b3.jar
lams-monitoring.war xpp3-1.1.3.4d_b4_min.jar
lams-monitoring.war.bak xstream-1.1.jar
lams-session.jar

Nonetheless I got the same result running lams. Nothing happens. There doesn't seem to be any activity coming from the hard drive after launching the run command. And no logs are created. Any suggestions would be much appreciated.

The best I can do in the way of DEBUG info is a text dump of the contents of Terminal (attached).

(I've got LAMS running on a PC. But I'm one of those crazy Mac people who would rather have root canal treatment than use Windows. So not being able to run LAMS on any of my Macs is doubly frustrating!

Barry

Posted by Barry Kayton

I understand about the crazy Mac bit.First used a Mac 512K as a teenager, had my own SE/30 when I left Uni (now that dates me) and I'm enjoying being back on a Mac this year.

But to the problem. The install log looks fine, and it sounds like all your files are there.

The run-lams.sh is a simple little script that hides the terminal window gumpf that comes up when JBOSS starts. But in this case we need the gumpf so rather than running ./run-lams.sh, can you run

"sudo ./run.sh"

in the same directory ie /usr/local/jboss-4.0.2/bin?

With any luck this will give you an error, and that will tell us why LAMS won't start. Once we have fixed the error, you can go back to using ./run-lams.sh so that LAMS is easier to start.

If it does start up correctly using "sudo ./run.sh" you will need to leave the terminal window running otherwise LAMS should shutdown when you close the window. That's one of the other things run-lams.sh does - it sticks LAMS in the background so that it can keep running even after you have closed the terminal window.

If it does start up correctly and it stays running when you close the window, then how do you stop it? Go back to /usr/local/jboss-4.0.2/bin and do "sudo shutdown.sh -S".

Fiona

Posted by Fiona Malikoff

Thanks for the info. I tried sudo ./run.sh but the command was not found even though I can see it in the directory list.

I then tried the run command as it appears in the run-lams.sh script. Don't know what all the attributes mean, but I figured it might reveal something.

Here's the contents of the terminal window:

MBP17:/usr/local/jboss-4.0.2/bin bazza$ clear

MBP17:/usr/local/jboss-4.0.2/bin bazza$ ls
classpath.sh run.bat shutdown.sh
deployer.bat run.conf twiddle.bat
deployer.sh run.jar twiddle.jar
jboss_init_redhat.sh run.sh twiddle.sh
jboss_init_suse.sh shutdown.bat
run-lams.sh shutdown.jar

MBP17:/usr/local/jboss-4.0.2/bin bazza$ run.sh
-bash: run.sh: command not found

MBP17:/usr/local/jboss-4.0.2/bin bazza$ nohup ./run.sh > /dev/null &
[1] 914

MBP17:/usr/local/jboss-4.0.2/bin bazza$ nohup ./run.sh > /dev/null &
[1] 925

MBP17:/usr/local/jboss-4.0.2/bin bazza$ nohup ./run.sh > /dev/null &
[2] 926

Does this give you any idea of what's happening?

Thanks
Barry

Posted by Barry Kayton

The "> /dev/null" tells the operating system to throw away any messages that would normally appear on the terminal.

The "&" on the end means run in the background ie start running and keep running but give me the prompt back again so I can do something else.

The "nohup" on the front means leave the program running even after I logout/close the shell window.


So you really need to do just "./run.sh"

And "./run.sh" is different to "run.sh" I won't try to explain why, just take it that sometimes "./run.sh" will work when "run.sh" won't.

But you say you tried "sudo ./run.sh" and that gave you command not found. That is really weird. I'm wondering if it is run.sh it can't find, or something in the actual script it can't find.

Can you edit run.sh and add a new line "set -vx" as the second line. It will now look like:

#!/bin/sh
set -vx
### ====================================================================== ###
## ##
## JBoss Bootstrap Script



Then when you try to run it, it will dump out each line of the script as it goes. Then if it is running the script and failing within the script, we will be able to see how far it gets. e.g.

fiona-malikoffs-computer:/usr/local/jboss-4.0.2/bin fiona$ sudo ./run.sh
### ====================================================================== ###
## ##
## JBoss Bootstrap Script ##
## ##
### ====================================================================== ###

### $Id: run.sh,v 1.19.4.2 2004/12/15 16:54:03 starksm Exp $ ###

DIRNAME=`dirname $0`
dirname $0
++ dirname ./run.sh
+ DIRNAME=.
PROGNAME=`basename $0`
basename $0
++ basename ./run.sh
+ PROGNAME=run.sh
GREP="grep"
+ GREP=grep

Posted by Fiona Malikoff

LAMS is now running on my Intel Macbook Pro and on my Powerbook too.

I found the solution here:

http://developer.apple.com/internet/java/enterprisejava.html

Specifically the startup scripts were not executable, a problem fixed by navigating to /usr/local/jboss-4.0.2/bin and entering the following command:

chmod ug+x *.sh

Thanks for all your advice and suggestions, especially your explanations of the Unix commands. Using Terminal is not as challenging or as foreign as it first seems.

Regards
Barry

PS

I've just installed Ubuntu 7.0.4 on my HP laptop and will try to get LAMS running on that too.

Posted by Barry Kayton

I should have thought of that. That will give the exact symptom that you described. My apologies.

Fiona

Posted by Fiona Malikoff