Hi Kesava,
It's just a guess, I assume that the cron entry in question was
supposed to run on dynamic backend instance.
If that's the case, the cron execution can be a single point of
failure, because the cron never retries.
I'd suggest directing all the cron execution to FE, and for the task
Hi,
We have many cron jobs that run as part of our application. Some crons run
on FE instances and some hit our Backend instances for execution. Since
this morning, teh crons are NOT running at regular intervals. I opened 2
production issues and attached screenshots. It's our production app
My site is back up after today's outage but cron jobs have not been
run since about 15:47 UTC.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this
One of my sites has a cron job that is scheduled to run on Wednesdays at
11AM.. (it of course, did not run at 11 when GAE was in its death throes)..
It successfully ran at 1:30 PM EST (about 9 minutes ago, but 3.5 hours
late.).
On Wed, Feb 24, 2010 at 1:36 PM, Chris L clun...@gmail.com wrote:
Is anyone else having a problem with cron today? None of my cron jobs
have run for several hours (task queues are working fine).
Note to Google: you should include information about cron, and task
queues in the status page.
--~--~-~--~~~---~--~~
You received this
Hi.
I have noticed that several cron jobs associated with my app have not
run for several hours (they are on schedules ranging from 1 to 10
minutes. I have not changed the scripts or the cron.yaml file
Is there an issue with the cron service? (it should be included in the
system status
I added new cron jobs couple of hours back, and now neither the new
nor the existing jobs are running. All the jobs either have the
schedule of every 5 minutes (UTC) or every 1 minutes (UTC) . Any
idea what might be the issue here?
--~--~-~--~~~---~--~~
You
