[Backgroundrb-devel] A fix for bdrb crash when running in background
webmaster at wolniartysci.pl
Wed Jun 18 09:04:05 EDT 2008
I just spent way too much time trying to figure out why the fsck bdrb
wouldn't run in background (while it worked perfecly in foreground), so
I figured I'll share my unimpressive solution to save others the trouble.
So the problem was that bdrb, when started with `script/backgroundrb
start`, would exit, with this error msg:
`log': PGError: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
: SELECT tablename
WHERE schemaname IN (E'"$user"',E'public')
Starting it with `script/backgroundrb` didn't cause that problem,
everything worked fine.
This happened exactly the same way on a G5/OSX/Postgres 8.2.4/Rails
2.0.2 workstation and a Xeon/Gentoo/Postgres 8.3.1/Rails 2.0.2 server.
Considering the different setups and the complete lack of complaints
from Postgres, even with highest logging verbosity AND the smoothly
working rails app, I figured it must be a problem with backgroundrb, but
whatever changes I tried, nothing worked. So fast forward (to spare you
the story of the cursing and the hopeless googling) - here's the
solution - line 32 of script/backgroubdrb:
29 case ARGV
30 when 'start'
31 if fork
Apparently leaving the child on it's own too early is not a good thing :-o
So there. Here's my good deed for the day.
PS. Thanks guys for bdrb!
More information about the Backgroundrb-devel