MrCoffee
09-03-2010, 09:00 PM
Hi,
I've just installed Resin Professional 4.0.10 on my Linux server, and I'm unable to start it as a daemon. When I try starting it up (logged in a root) like this:
/usr/local/jdk1.6.0_21/bin/java -jar /usr/local/resin/lib/resin.jar -root-directory /var/www -conf /etc/resin/resin.xml -log-directory /var/log/resin/ start
... nothing happens for about a minute, and then the following message is displayed:
Resin/4.0.10 can't start -server '' for watchdog at 127.0.0.1:6600.
java.lang.NullPointerException
When I try running "/etc/init.d/resin start", the same thing happens, except the failure message is:
Starting resin: failed!
However, when I start Resin in console mode, like this:
/usr/local/jdk1.6.0_21/bin/java -jar /usr/local/resin/lib/resin.jar -root-directory /var/www -conf /etc/resin/resin.xml -log-directory /var/log/resin/ console
... it starts up and runs fine.
Any idea why Resin would be working in console mode, but not as a daemon? Is there any way I can obtain more verbose failure messages, or is there a log I could look at?
Thanks!
I've just installed Resin Professional 4.0.10 on my Linux server, and I'm unable to start it as a daemon. When I try starting it up (logged in a root) like this:
/usr/local/jdk1.6.0_21/bin/java -jar /usr/local/resin/lib/resin.jar -root-directory /var/www -conf /etc/resin/resin.xml -log-directory /var/log/resin/ start
... nothing happens for about a minute, and then the following message is displayed:
Resin/4.0.10 can't start -server '' for watchdog at 127.0.0.1:6600.
java.lang.NullPointerException
When I try running "/etc/init.d/resin start", the same thing happens, except the failure message is:
Starting resin: failed!
However, when I start Resin in console mode, like this:
/usr/local/jdk1.6.0_21/bin/java -jar /usr/local/resin/lib/resin.jar -root-directory /var/www -conf /etc/resin/resin.xml -log-directory /var/log/resin/ console
... it starts up and runs fine.
Any idea why Resin would be working in console mode, but not as a daemon? Is there any way I can obtain more verbose failure messages, or is there a log I could look at?
Thanks!