Ooops error in the subject of this topic : they DO WORK in console ;) On Oct 4, 8:05 pm, 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.
