FYI, I solved my problem using psionides' Resque (with multi-json support); though workers goes on only with ruby 1.8.7 and not 1.9.2.
http://github.com/psionides/resque/ Thanks, Clément On Oct 4, 8:32 pm, James Bracy <[email protected]> wrote: > Clément, > > Looks like something is up with the DJ's but I can't really tell. > > It works when you run the rake task on heroku, but not the workers? > > My AIM / gTalk is waratuman. Probably easier to debug if you get a > hold of me that way. I'll also be on Heroku IRC in a sec. > > - James > > > > On Mon, Oct 4, 2010 at 11:05 AM, Clément <[email protected]> wrote: > > Hi all, > > I'm using Resque workers on Heroku with Rails 2.3.9, Ruby 1.9.2. > > I followed this nice guide > > :http://blog.redistogo.com/2010/07/26/resque-with-redis-to-go/ > > All works great localy. > > > However, I have a stange problem when deploying on Heroku : > > > If I do > > $ heroku rake jobs:work --trace --app my-app > > And all works as expected with Resque. > > $ heroku ps --app my-app > > UPID Slug Command State Since > > ------- ------------ -------------------------- ---------- > > --------- > > 2458746 7940b53_99b0 rake jobs:work --trace up 1m > > ago > > 1676789 0c1293b_0e00 cron idle 8h > > ago > > 1485310 7940b53_99b0 dyno up 12m > > ago > > > But when I turn one or more workers with > > $ heroku workers 2 --app my-app > > Nothing happens, even if I restart my app. > > > I've got no crash in the log file, and > > $ heroku ps --app my-app > > nicely tells me : > > UPID Slug Command State Since > > ------- ------------ -------------------------- ---------- > > --------- > > 2458625 7940b53_99b0 dj idle 8m > > ago > > 2458624 7940b53_99b0 dj idle 8m > > ago > > 1676789 0c1293b_0e00 cron idle 8h > > ago > > 1485310 7940b53_99b0 dyno up 7m ago > > > I can simultaneously run remote rake & worker, in this case I got > > $ heroku ps --app my-app > > UPID Slug Command State Since > > ------- ------------ -------------------------- ---------- > > --------- > > 2458770 7940b53_99b0 dj idle 5s > > ago > > 2458769 7940b53_99b0 dj idle 6s > > ago > > 2458746 7940b53_99b0 rake jobs:work --trace up 1m > > ago > > 1676789 0c1293b_0e00 cron idle 8h > > ago > > 1485310 7940b53_99b0 dyno up 12m > > ago > > > Any idea ? > > Thanks ! > > Clément -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
