Your help is much appreciated! I can confirm I had only one worker running. What scares me the most is that the celery beat was lost (not writing my print stmt to logs), and I could not be alerted nor find why it happened. I am currently building better logs capabilities in my app to better document this case if this occurs again.
I'll update this thread if I find anything interesting. Thanks again Daniel, Julien Le mardi 25 juin 2013 18:58:39 UTC+2, Daniel Farina a écrit : > > On Tue, Jun 25, 2013 at 2:24 AM, julien boucher > <[email protected]<javascript:>> > wrote: > > Thanks for the pointer Daniel, appreciated! > > > > I do not understand why it worked for 5 days with no problem and failed > > since I started and desactivated a web server. > > I think that's because you may be running one web dyno and then the > application went to sleep. > > After reviewing > https://devcenter.heroku.com/articles/dynos#dyno-sleeping I'm left > scratching my head because it says "worker dynos never sleep". If you > do 'heroku ps' does the worker claim to be 'idle'? > > On the other hand, there's an admonition on the right saying that one > needs two web dynos for the application to not sleep, which conflicts > with the last sentence. Looks like a bug in the documentation. My > guess is the admonition is right and the last sentence is wrong, if > your case is any indication. > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
