|
2:
Re: problems after upgrating to lams 2.3.1
|
In response to 1
|
07/30/09 06:51 AM |
|
Hi i managed to solve the problem.I had to change the password in the jboss-dir/server/default/deploymysql-ds.xml.But now i have another problem.When i run ./run.sh from jboss-dir/bin, lams works fine.But when i try to start it for init.d(the command i use is sudo /etc/init.d/lams start) it doesn't starts.And when i run sudo /etc/init.d/lams status it says
'Removed stale pid file: /var/run/lams2.pid
LAMS 2 Server is not running.'.
Can someone help me?Thanks
Posted by giannis ioannidis
|
|
|
|
3:
Re: Re: problems after upgrating to lams 2.3.1
|
In response to 2
|
07/30/09 08:45 PM |
|
Inside the /etc/init.d/lams2 script it should look for JAVA_HOME - is your java in a non-standard place? Also if the script was installed by the unix installer then there would be a log file in /path/to/jboss/log/wrapper.log - there might be info there.
Posted by Jun-Dir Liew
|
|
|
|
4:
Re: Re: Re: problems after upgrating to lams 2.3.1
|
In response to 3
|
07/31/09 03:31 AM |
|
The variable java_home is ok but i think the script is wrong. First in function start the option -- $DAEMON_OPTS should be without space. But again it is not running. The variable $DAEMON_OPTS it is not set right(at least to me) it is
DAEMON_OPTS="$JAVA_OPTS \
-Djava.endorsed.dirs=$JBOSS_ENDORSED_DIRS \
-classpath $JBOSS_CLASSPATH \
org.jboss.Main $JBOSS_OPTS"
where JAVA_OPTS ="$JAVA_OPTS -Dprogram.name=$PROGNAME"
and $PROGNAME is not set. What should be the value of the variable?
Also in the start of the script is defined
JBOSS_OPTS=
So this again is null.
Could you please tell me the values?
Finally although i have installed lams with the unix installer there is no log file in /path/to/jboss/log/wrapper.log
Posted by giannis ioannidis
|
|
|
|
5:
Re: Re: Re: Re: problems after upgrating to lams 2.3.1
|
In response to 4
|
08/04/09 01:10 AM |
|
The settings are fine - it's the same steps that the original run.sh does before running jboss. You're right $PROGNAME is missing, but it seems to work without it. JBOSS_OPTS are optional, so if it's empty, that's ok.
What you can do to debug is run your shell with 'bash -x' - and then execute the startup script from there. It might help pinpoint what the script is doing.
Posted by Jun-Dir Liew
|
|
|
6:
Re: Re: Re: Re: problems after upgrating to lams 2.3.1
|
In response to 4
|
08/04/09 01:53 AM |
|
Hello Giannis,
Have you at any stage edited your run.sh?
I could be wrong, but for the wrapper to work, I think in run.sh you need to replace these lines (near the bottom):
$JAVA $JAVA_OPTS \
-Djava.endorsed.dirs=$JBOSS_ENDORSED_DIRS \
-classpath $JBOSS_CLASSPATH \
org.jboss.Main $@"
With these lines
echo "$JAVA $JAVA_OPTS \
-Djava.endorsed.dirs=$JBOSS_ENDORSED_DIRS \
-classpath $JBOSS_CLASSPATH \
org.jboss.Main $@"
Essentially printing the command instead of running it. backup your run.sh first then give this a try.
Jundir is this correct?
Luke
Posted by Luke Foxton
|
|
|
|
7:
Re: Re: Re: Re: Re: problems after upgrating to lams 2.3.1
|
In response to 6
|
08/04/09 12:02 PM |
|
Thanks all very much for your responses.Yes Jun-Dir-Liew the settings are optional, i open the run.sh from jboss and the settings are the same.But i can't understand why it is not running form /etc/init.d/lams while it is running from run.sh.The message that i get when i check the status (sudo /etc/init.d/lams status) is
Removed stale pid file: /var/run/lams2.pid
LAMS 2 Server is not running.
Does anyone knows why i get this message?
I run the script with -x option and i check all the values of variables which are correct.So i guess that the syntax of the start-stop-command in the start function is wrong.When i echo it with the specific values that i have i get this
start-stop-daemon --start --background --make-pidfile --pidfile /var/run/lams2.pid --chuid lams:lams --exec /usr/lib/jvm/java-1.5.0-sun/bin/java -- -server -Xmx512m -XX:MaxPermSize=128m -XX:MaxNewSize=204m -XX:SurvivorRatio=32 -Dprogram.name=lams2 -Djava.endorsed.dirs=/usr/share/jboss-4.0.2/lib/endorsed -classpath /usr/share/jboss-4.0.2/bin/run.jar:/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar org.jboss.Main start
Can someone check it or just post his script ?
As for the log file i will change it in a while(but i have never edited this).
Thanks again.
Posted by giannis ioannidis
|
|
|
|
|
|
|
|
|
|
11:
Re: Re: Re: Re: Re: Re: Re: Re: Re: problems after upgrating to lams 2.3.1
|
In response to 10
|
09/03/09 03:22 AM |
|
Hi sorry for the delayed response.Ok i checked the file and it is almost the same.I am thinking to unistall lams and install the ubuntu version.But as i can see there is not an uninstall script or anything else.What can i do in order to uninstall it properly?I think it is not a good idea just delete or just install the ubuntu version.
Thanks again for any response.
Posted by giannis ioannidis
|
|
|
|
|
|
|
|
|
|
|
|
