[Backgroundrb-devel] logging problem in production

Ezra Zygmuntowicz ezmobius at gmail.com
Tue Feb 6 14:05:23 EST 2007

	Yeah Bill solved his problem, he just needed to set   
RAILS_ENV=production as an env var when starting up backgroundrb.


On Feb 6, 2007, at 9:50 AM, Jacob Robbins wrote:

> Bill,
>    Have you made any progress on your logging issue?
>    From what i've seen on the list this could just as likely be a
> backgroundrb issue as something in your app. Backgroundrb still has  
> many
> corner cases where it doesn't handle the RAILS_ENV variable  
> correctly. I
>   wouldn't be surprised if it is doing this for everybody but nobody
> else has been bothered enough/noticed it to report it to the list.
>   If you do identify the location of the problem and it's in bdrb  
> please
> take the time to add it to the backgroundrb trac.
>   Have you tried creating an empty rails app, adding backgroundrb and
> your worker, then using the bdrb console in production mode?
> -Jacob
> Bill Walton wrote:
>> Oops...  I wasn't done.  Dang fat fingers ;-)
>> Bill Walton wrote
>>> Hi Ezra,
>>> Ezra Zygmuntowicz wrote:
>>>> I'm not sure why it is writing to the development log instead of
>>>> production. But know this, calls to ActiveRecord objects in a  
>>>> worker will
>>>> still write their sql to the normal rails log.
>>> I went to bed last night believing firmly that the problem I'm  
>>> having lay
>>> with my hosted environment and comitted fully to figuring out how to
>>> conclusively demonstrate that to them.
>>> I woke this morning with a plan, but also realizing that I'd  
>>> missed an
>>> important step in my debugging efforts so far.  Everything works  
>>> fine on
>>> my development box in development mode.  But I hadn't tested the  
>>> behavior
>>> on my development box in *production* mode.
>>> There is definitely a problem with Backgroundrb in production mode.
>>> I am seeing *exactly* the same behavior on my local machine that I'm
>>> seeing on my hosted environment.  In development mode, everything  
>>> gets
>>> written to development.log.  In production mode, the web server  
>>> logging
>>> goes to production.log.  But the SQL logging, and not all of it,  
>>> goes to
>>> the development log.
>> The piece of the app that I'm testing is trivial in terms of  
>> size.  I'll
>> send a zip to anyone willing to help by giving it a run on their  
>> system.
>> Along, of course, with my eternal gratitude!
>> Best regards to all,
>> Bill
>> _______________________________________________
>> Backgroundrb-devel mailing list
>> Backgroundrb-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel

-- Ezra Zygmuntowicz 
-- Lead Rails Evangelist
-- ez at engineyard.com
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)

More information about the Backgroundrb-devel mailing list