We get this happening in Resque sometimes and restarting the worker seems to
clear it up. Still annoying though. Have you ever gotten this to run
successfully or does it fail immediately?
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To view this
Been getting 404 Nginx Errors on several apps through today. Anyone else
getting this delightful message. Still waiting to here back from Heroku and
their all systems go status at https://status.heroku.com/ is a bit
disheartening. So I thought I'd see if we are the only one.
--
You received
Just moved one of our apps to cedar. Have this in our Procfile:
'mailer: bundle exec rake email:work' which we use for sending out all
sorts of emails. While I can ps:scale mailer=1, I can't seem to get
the output from this task using 'heroku logs -t'. I do see the output
from jobs:work as well as
Thanks for the update.
On Mon, Oct 17, 2011 at 12:25 PM, joshmckin joshmc...@gmail.com wrote:
Looks like they tried something; https://status.heroku.com/
But I'm still getting 404 and somethings heroku restart fails.
--
You received this message because you are subscribed to the Google
No problemo...would be nice to hear from them though...going on 3+ hours
with no replies to my ticket. Is there are higher urgency than urgent?
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To view this discussion on the web visit
You might try putting this at the top of your email:work task:
STDOUT.sync = true
Ruby buffers output by default, which can cause it to delay appearing in the
logs until you have enough output.
Adam
--
You received this message because you are subscribed to the Google Groups
Heroku
Adam, tried that but no worky for me. Here's what I see. On Bamboo,
when I push code, I usually see thin and the bundle exec rake getting
killed with SIGTERM (with full backtrace) and then restarted. With
Cedar, all I get is 'Release v%% created by' message.
If I now do heroku ps;scale worker=0
