Cron task has fails without trace in the logs
46 views
Skip to first unread message
PK
Oct 16, 2015, 1:14:19 PM10/16/15
to Google App Engine
I have many periodic tasks scheduled by cron. Today I noticed that one of them that is supposed to run at 4:00AM Pacific every day had not run for two days. Next to the task in the console, in the status column, it had a yellow warning sign and the word Failed. I looked at the logs I could not find the invocation of this task for the past two days but I can see the invocation on the 13th and the 14th.
I just kicked it off manually pressing “Run Now” and it run fine. Nothing has changed in that part of my system.
Can somebody help me with this behavior? How can I find out why it failed? I assume the system tried both the 14 & the 15th and failed in both cases??
Nick (Cloud Platform Support)
Oct 16, 2015, 5:30:07 PM10/16/15
to Google App Engine
Hey PK,
This forum isn't the right place to look for specific issue technical support, and is meant for more general discussion of the platform and services. If you'd like, you could post a clarified version of this post to stackoverflow, where you will be more likely to find users who can help. We monitor both here and there, along with the public issue tracker, so not to worry whether you'll be visible to Googlers who support the community.
Best wishes,
Nick
Best wishes,
Nick
PK
Oct 16, 2015, 5:40:06 PM10/16/15
to google-a...@googlegroups.com
Nick,
what further clarification do you need? This is very clear and most likely something Google needs to fix, you cannot fail our requests without any trace. I want to see whether others in the community have seen this before I decide what route to take (support call, etc).
Thanks
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/479d99f6-a0e5-4adc-b47e-a22a50b64201%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Nick (Cloud Platform Support)
Oct 16, 2015, 5:59:36 PM10/16/15
to Google App Engine
Hey PK,
The problem is, it's not entirely clear whether the issue is yours or the platform's. If you'd like, you can post to the public issue tracker, but that would also require more information and code to reproduce, or at the very least an app id and affected timeframe, so that it can be looked-into and determined to be an issue rather than your own issue. This doesn't come from any kind of lack of trust directed towards you or any user, it's just that issue reports on any software project will need to have some minimal guarantee that the issue is actually existing in the code which the project you report to is able to fix, rather than your own project / code / configuration.
The kind of information I think might be relevant:
1. the cron task configuration data
The problem is, it's not entirely clear whether the issue is yours or the platform's. If you'd like, you can post to the public issue tracker, but that would also require more information and code to reproduce, or at the very least an app id and affected timeframe, so that it can be looked-into and determined to be an issue rather than your own issue. This doesn't come from any kind of lack of trust directed towards you or any user, it's just that issue reports on any software project will need to have some minimal guarantee that the issue is actually existing in the code which the project you report to is able to fix, rather than your own project / code / configuration.
The kind of information I think might be relevant:
1. the cron task configuration data
2. the code of the handler
3. description of steps you've taken to ensure possible alternate causes aren't at fault (is your log-level set correctly in the logs viewer?)
You can certainly check using google whether others have had issues like yours using a combination of keywords, and while it's true that making a post to a forum to ask others might be useful, the way you phrased your question wasn't indicating that, and seems to look for an individual solution, which isn't the purpose of the forum.
I wish you the best in finding a solution by posting to either stackoverflow or the public issue tracker. I'll leave this thread open to replies, of course, if anybody happens to see this thread and also have input, although be advised that specific resolution of this issue should occur on stackoverflow or the public issue tracker, if investigation and work on the issue is needed, rather than just +1 comments from other users.
Best wishes,
Nick
You can certainly check using google whether others have had issues like yours using a combination of keywords, and while it's true that making a post to a forum to ask others might be useful, the way you phrased your question wasn't indicating that, and seems to look for an individual solution, which isn't the purpose of the forum.
I wish you the best in finding a solution by posting to either stackoverflow or the public issue tracker. I'll leave this thread open to replies, of course, if anybody happens to see this thread and also have input, although be advised that specific resolution of this issue should occur on stackoverflow or the public issue tracker, if investigation and work on the issue is needed, rather than just +1 comments from other users.
Best wishes,
Nick
On Friday, October 16, 2015 at 5:40:06 PM UTC-4, PK wrote:
Nick,what further clarification do you need? This is very clear and most likely something Google needs to fix, you cannot fail our requests without any trace. I want to see whether others in the community have seen this before I decide what route to take (support call, etc).Thanks
On Oct 16, 2015, at 2:30 PM, Nick (Cloud Platform Support) <pay...@google.com> wrote:
Hey PK,This forum isn't the right place to look for specific issue technical support, and is meant for more general discussion of the platform and services. If you'd like, you could post a clarified version of this post to stackoverflow, where you will be more likely to find users who can help. We monitor both here and there, along with the public issue tracker, so not to worry whether you'll be visible to Googlers who support the community.
Best wishes,
Nick
On Friday, October 16, 2015 at 1:14:19 PM UTC-4, PK wrote:I have many periodic tasks scheduled by cron. Today I noticed that one of them that is supposed to run at 4:00AM Pacific every day had not run for two days. Next to the task in the console, in the status column, it had a yellow warning sign and the word Failed. I looked at the logs I could not find the invocation of this task for the past two days but I can see the invocation on the 13th and the 14th.I just kicked it off manually pressing “Run Now” and it run fine. Nothing has changed in that part of my system.Can somebody help me with this behavior? How can I find out why it failed? I assume the system tried both the 14 & the 15th and failed in both cases??--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscribe@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/479d99f6-a0e5-4adc-b47e-a22a50b64201%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages