Finding the logs for failed cron jobs and failed tasks

[N. Rosencrantz]

If a cron job or a task fails, I sometimes can't find the corresponding log file part. Wouldn't it be good if there was a link from the failed job to the relevant log part so that I don't have to scan the logs looking for the error message? I now for instance have a failed task that I want to debug and I can't find where it is in the logfile.

Thanks
Nick Rosencrantz

[Robert Kluin]

Hi Niklas,
I've had similar feelings in the past. Some cross-linking would be
very nice. Does filtering by path and return code help you at all?
That usually helps me quite a bit.

Robert

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/fqRrYlDoEMgJ.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

[Dave Loomer]

I've seen cases where the reason for the failure just plain isn't in the log. I think his happens when cron isn't able to find an available backend instance (kind of rare, but can happen when things are busy or if you configure a limited number of instances). It will keep trying for a few minutes, then eventually give up and not log anything.

On the same topic, I've seen cron jobs initially marked as "failed", then a couple minutes marked as successful. These seem to be the cases where it couldn't initially find an available instance, then eventually finds one.