Yes, there's a job in the cron tab, I posted it above:

scheduled_process
Run processing of scheduled uploads every 1 minutes      every 1
minutes
(UTC)
2011/12/20 09:53:17 on time Success

but how did it get there and how do I kill it?

As to the other questions, I'm not the only person who has worked on
this project, so I can't say for sure. I wrote the original
application and someone else deployed it. Now I'm doing some upgrades
and only now have access to this particular installation of the
project. It may be that an older version started a cron job as you
say. For one thing, there a few entities in the datastore that are not
in either the current model or the original model. I don't have full
access so I can't download the code for the older versions. I'll have
to wait for the admin to do that.

Thanks for the tip. I didn't realize that a cron job from an older
version would keep going, but I guess it might make sense in some
cases.

David

On Dec 21, 3:54 am, "Greg Darke (Google)" <[email protected]>
wrote:
> The datastore admin job does not use cron.
>
> Have you checked the cron tab in the admin-console to see if there are any
> cron tasks enabled in your app?
>
> Have you recently performed a migration from Master/Slave to High
> Replication and had cron enabled on the application? If so, you will need
> to disable the cron job on the old version of your application (or just
> delete the old version).
>
> On 20 December 2011 21:09, David Lindsey <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > There's a cron job that runs every minute spamming up my logs which I
> > think is an orphan of Datastore Admin delete job. That particular
> > delete request completed in that it deleted all the entities it was
> > supposed to but it said 2 jobs completed 1 active. It seemed hung like
> > that. Another post mentioned deleting the Datastore Admin entity so I
> > did, although I was skeptical, and that didn't have any effect. As far
> > as I know (I'm not the only person who can upload to the app) this app
> > has never had cron.yaml. I know it doesn't have one right now.
>
> > Here's the Cron Jobs listing:
>
> > /scheduled_process
> > Run processing of scheduled uploads every 1 minutes      every 1 minutes
> > (UTC)
> > 2011/12/20 09:53:17 on time Success
>
> > Here's what the logs show:
>
> > 2011-12-20 02:05:23.477 /scheduled_process 200 31ms 3kb AppEngine-
> > Google; (+http://code.google.com/appengine)
> > 0.1.0.1 - - [20/Dec/2011:02:05:23 -0800] "GET /scheduled_process HTTP/
> > 1.1" 200 3459 - "AppEngine-Google; (+http://code.google.com/
> > appengine)" "<APP_URL_OMITTED>" ms=32 cpu_ms=0 api_cpu_ms=0
> > cpm_usd=0.000419 queue_name=__cron
> > task_name=0b7f457ee2ee7ab4fe9e71fcb34667fe
> > instance=00c61b117ccc5309d8c89143086451a9ded1d58f
>
> > Does anyone know how to get rid of this?
>
> > Thanks for reading,
> > David
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected].
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to