[Backgroundrb-devel] Backgroundrb-devel Digest, Vol 21, Issue 7
orion at mh2o.com
Fri Feb 15 13:13:19 EST 2008
Yeah the exception appears there is I start the server from the server.
If use Capistrano it does not.
So the good news is that I found the exception, and I can now track down
the problem (something with working directories in another gem). The
bad news is that when the server is started via Capistrano it does not
appear in the backgroundrb_server.log
From: George Feil [mailto:gfeil at realgirlsmedia.com]
Sent: Friday, February 15, 2008 12:25 PM
To: Orion Delwaterman; backgroundrb-devel at rubyforge.org
Subject: RE: [Backgroundrb-devel] Backgroundrb-devel Digest, Vol 21,
Did you look in the log/backgroundrb_server.log file? I've noticed that
exceptions thrown by the server often wind up there.
> -----Original Message-----
> From: backgroundrb-devel-bounces at rubyforge.org
> bounces at rubyforge.org] On Behalf Of Orion Delwaterman
> Sent: Friday, February 15, 2008 8:13 AM
> To: backgroundrb-devel at rubyforge.org
> Subject: Re: [Backgroundrb-devel] Backgroundrb-devel Digest, Vol 21,
> Hello All,
> I am using backgroundrb from the trunk of devjavu and I am unable to
> start the script with Capistrano. This is really annoying because it
> means I have to ssh into the server everytime I deploy something
> of letting Capistrano do the work me.
> I am starting the script using the command 'ruby script/backgroundrb
> start'. When I execute via Capistrano the pid file is created but the
> process does not exist. There are no errors in any of the
> logs. When I execute directly on the server it works fine. If I rub
> backgroundrb console via Capistrano it works properly
> So my question is when backgroundrb starts up where is it supposed to
> write any errors it may encounter during startup. Otherwise it seems
> impossible to debug the issue.
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
More information about the Backgroundrb-devel