Hey Jason, To get the environment passed in correctly, I use: RAILS_ENV=staging ./script/backgroundrb start
And just to make sure, you're aren't actually calling your staging environment "stage" are you? Or if you are, you have an environment intentionally named that, right? Just had to ask :). stevie On Wed, Apr 30, 2008 at 10:32 AM, Jason Lee <[EMAIL PROTECTED]> wrote: > Ah, that's it, it's still in development env. So neither of these > commands worked for me: > > RAILS_ENV=stage rake backgroundrb:start > > script/backgroundrb start -e stage > > both go to development. Right now I'm kicking them off manually at the > command line. Maybe the rake command is not taking the environment in > to account? > > Now that I know the cause, I guess I have to try to fix it. I saw the > environment issue mentioned in previous postings on the list, but it > didn't look like there was a solution yet (I think). I'm running rev > 234 of BRb. > > If I figure this out or someone else does, please post. Thx. > > - jason > > > > On Wed, Apr 30, 2008 at 4:00 AM, Adam Williams <[EMAIL PROTECTED]> wrote: > > I'm not certain at all about this, but the -e thing was not working well > for > > me. Try spitting out the RAILS_ENV value in your worker, to be sure it is > > the environment your expect. Or, perhaps you could use 'sudo lsof -Pni -a > -c > > ruby' to see what database ruby processes are connecting to. > > > > > > > > On Apr 30, 2008, at 1:16 AM, Jason Lee wrote: > > > > > > > > > > > > > > > > Hello, > > > > > > I'm using just the scheduler with my workers like cron jobs. I have 3 > > > different ones that poll my db for specific object states and do work > > > accordingly. > > > > > > This all works perfectly on my development machine. However, when I > > > deploy to my staging server - with its own staging configuration - the > > > scheduler works, the worker processes, but my ActiveRecord object > > > never returns any data back. > > > > > > I explicitly include the model in the top of the worker and when the > > > worker processes, I can see the query logging in the log file. I can > > > even cut the query, paste into a sql window and get back the expected > > > results. But whenever the query returns in my non-development deployed > > > worker, the result set is empty. > > > > > > My backgroundrb.yml configuration is super simple: > > > > > > --- > > > :backgroundrb: > > > :ip: 0.0.0.0 > > > :port: 11006 > > > > > > Again, the above is only just for scheduling and works perfectly on my > > > local env. I also explicitly executed brb with the env specific > > > setting: > > > > > > script/console backgroundrb -e stage > > > > > > Still no luck. > > > > > > Has anyone see this weird issue with AR not returning back any > > > results, even tho the query has been executed in the db? > > > > > > tia, > > > > > > - jason > > > _______________________________________________ > > > Backgroundrb-devel mailing list > > > [email protected] > > > http://rubyforge.org/mailman/listinfo/backgroundrb-devel > > > > > > > > _______________________________________________ > Backgroundrb-devel mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/backgroundrb-devel > _______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
