0

so I was playing around with capistrano and a local dummy raring vm in vbox. everything was fine and my attention shifted to deployments on real machines. A couple of days later I want to deploy to my vm again and the script succeeds but afterwards no tomcat is running.

From all the messages that capistrano plays back to me, it looks like everything, including tomcat startup, went smoothly. Even the PID file was wirtten, but when you look at ps aux, the process doesn't exist. There is nothing in catalina.out but it's timestamp is updated, which is the only evidence, together with the PID file, that something happened on the vm at all.

Next thing I did was take the whole tomcat startup command as logged by capistrano and execute it "manually" with ssh. That gives me the exact same log messages but this time, the tomcat instance is actually up and running.

So, something that capistrano is doing with that command before it gets sent over via ssh must mess it up, but understanding the capistrano source of the run command is giving me a hard time, so any pointers would be appreciated.

2 Answers 2

0

Do you have logs from the tomcat under capistrano (catalina.out)

Something to check quickly is if you have a display (DISPLAY) variable set.

The link below explains about DISPLAY:

http://mail-archives.apache.org/mod_mbox/tomcat-users/200808.mbox/%3CF58E0AE5D219DE4DB2646B2199A4F5DD02B74EE3@exsgmb16.apac.nsroot.net%3E

A fix is:

-Djava.awt.headless=true

Update: Saw the bit about catalina.out being empty.

1
  • hi, thx for your support. I figured it out, though... see my answer Aug 5, 2013 at 14:36
0

turns out it was a nohup that got lost in a refactoring and several factors contributed to me not seeing it as the root reason. Ultimately just a mistake, though...

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .