[google-appengine] Re: Cron jobs silently failing

I did some more digging and found that it was an issue with dotnet and how error reporting differs on local/production. I had already been isolating my /api endpoints from this error handling, and thought I was doing the same with my /cron endpoints, but I was not. On Tuesday, February 15, 202

[google-appengine] Re: Cron jobs not getting executed

Hi Andres, I'd suggest to report the issue on a Public Issue Tracker as this seems to be a technical issue and you'd need to provide additional details such as the error message you are getting. Furthermore, this is very o

[google-appengine] Re: Cron jobs not getting executed

Hi guys, we are experimenting this issue with a cronjob that runs every 30'. It has been running normally up to 2 days ago. Does anybody have the same problem? greetings, Andres. p.d: I apologize for my english. El jueves, 11 de noviembre de 2010 a la(s) 15:53:33 UTC-3, dzwiedziu escribió: > My

Re: [google-appengine] Re: Cron job targeting a specific service returns status 400

Hello, >From redirecting requests, this information would be helpful. You can create a dispatch file to override App Engine's URL-based routing rules and define your own custom routing rules. With a dispatch file, you can send incoming requests to a specific service based on the path or host n

Re: [google-appengine] Re: Cron job targeting a specific service returns status 400

Hello, I’m glad you were able to narrow down the problem to a mismatch. I was able to find a document indicating that the target option is optional. target: Optional. The name of a specific service in y

Re: [google-appengine] Re: Cron job targeting a specific service returns status 400

Hi Elliott, I have been able to narrow down the problem. There is a mismatch between the app URL with a defined service name and the cron job "host" used. I can explain it as follows: if you have an app.yaml file such as this: runtime: python38 handlers: # This configures Google App Engine to ser

[google-appengine] Re: Cron job targeting a specific service returns status 400

Hello, I understand that you have a problem with your application. Although Google Groups is meant for general discussions, we may still be able to guide you, at least a little bit. To move things forward, would you be able to share some redacted logs about the 400 error? I was able to find th

[google-appengine] Re: Cron job permission

Based on this doc [1], and my testing, you need to have Project Editor or Project Owner role to run cron jobs from the console. [1] https://cloud.google.com/appengine/docs/standard/python/config/cron#before_you_begin -- You received this message because you are subscribed to the Google Groups

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

Hello, In an attempt to isolate the issue, would you be able to set "app_start_timeout_sec" to the max? The max is 1800, you may try it again once set. Also, this will help rule out if the issue is due to app initialization or not. You may find further information about this here

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

Hello Daniel , I am trying to deploy appengine-web.xml and cron.yaml together PFB my pom.xml portaldata False true ${java.io.tmpdir}/appengine-staging E:/git_Collection_Portal/Collections-app-server/JavaPortal-1/src/main/webapp/WEB-INF/appe

[google-appengine] Re: Cron jobs stop to work, responding a 404 code

Hi Rodrigo, If the issue still persists, I recommend to raise a report via the Issue Tracker so that we would be able to investigate the root cause of the issue efficiently. - Note that Google Groups are reserved for general Google Cloud

[google-appengine] Re: Cron Jobs failure

Hello Rodrigo! Error 404 means that a resource was not found. Either there is no API method associated with the URL path of the request, or the request refers to one or more resources that were not found. It is worthwhile testing if you have access to the route for Cron, as defined in your app.

[google-appengine] Re: Cron job not start in Standard engine

Hi Guangjie, I tried these steps and could create the cron job with your cron.xml config successfully. Note that your Servlet URL mapping in web.xml should be the same as the cron job URL. If this map

Re: [google-appengine] Re: Cron Job config takes a day to be effective

I see. Didn't know that cron update requires a new deployment. Thanks George. On Sat, Feb 24, 2018 at 11:12 AM, 'George (Cloud Platform Support)' via Google App Engine wrote: > Hello Justin, > > How did you update your cron configuration? One can redeploy the whole > application, or only the

[google-appengine] Re: Cron Job config takes a day to be effective

Hello Justin, How did you update your cron configuration? One can redeploy the whole application, or only the cron configuration, for Java, with: ./appengine-java-sdk/bin/appcfg.sh -A your-app-id -V app-version update_cron [YOUR_APP_DIR] For details and other languages, you may read the "

[google-appengine] Re: cron in microservice url

This issue can often occur due to misconfiguration of your app.yaml handlers, dispatch rules, and endpoints. Google Groups is meant for general product discussions and not for technical support. I

[google-appengine] Re: Cron job runs successfully on local development server but fails after deployed

Thanks George! This is just the problem. 在 2017年9月8日星期五 UTC+8上午1:46:49，George (Cloud Platform Support)写道： > > Hello Zhou, > > None of your two projects seem to have a task queue; no queue is visible > in the Developers' Console. Without a queue, you get the > "UnknownQueueError" error message

[google-appengine] Re: Cron job runs successfully on local development server but fails after deployed

Hello Zhou, None of your two projects seem to have a task queue; no queue is visible in the Developers' Console. Without a queue, you get the "UnknownQueueError" error message. You may try deploying the queue config explicitly

[google-appengine] Re: Cron doesn't start

Worked! Thanks On Thursday, June 1, 2017 at 11:28:27 PM UTC+3, Roxana Ioana Roman wrote: > > Hi, > *appcfg.sh update_cron [YOUR_APP_DIR]. *Try playing with * [YOUR_APP_DIR], > *give it /Users/shachar/server_project/web or move WEB-INF one step > before. My WEB-INF is in src/main/webapp/ WEB-INF.

[google-appengine] Re: Cron doesn't start

Hi, *appcfg.sh update_cron [YOUR_APP_DIR]. *Try playing with * [YOUR_APP_DIR], *give it /Users/shachar/server_project/web or move WEB-INF one step before. My WEB-INF is in src/main/webapp/ WEB-INF. Good luck! On Thursday, 1 June 2017 17:42:53 UTC+3, Shachar Grembek wrote: > > Hi, > > Thanks, W

[google-appengine] Re: Cron doesn't start

Hi, Thanks, We are progressing, but only this time I received the following error when running update_cron: "Bad configuration: Could not find the WEB-INF directory in /Users/shachar/server_project/WEB-INF. The given application file path must point to an exploded WAR directory that contains a

[google-appengine] Re: Cron doesn't start

To update cron: *./appengine-java-sdk/bin/appcfg.sh update_cron [YOUR_APP_DIR]* If you are using maven you can also do inside your project directory: *mvn appengine update_cron* After this you should be able to see a list of your cron jobs under App Engine -> Task Queues -> Cron Jobs and you w

[google-appengine] Re: Cron doesn't start

Hi Roxana, Thanks, I cannot see the cron jobs App Engine -> Task Queues -> Cron Jobs. How do I run update_cron? Please find the web.xml: http://www.w3.org/2001/XMLSchema-instance"; version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"; xsi:schemaLocation="http://java.sun.c

[google-appengine] Re: Cron doesn't start

Are your cron jobs visible in App Engine -> Task Queues -> Cron Jobs? If not, you have to run update_cron. Can you add your web.xml and the Servlet which handles these cron jobs? Your second cron job does not have a which means the job will run on the default service . Roxana On Thursday, 1

[google-appengine] Re: Cron job failed in Google App Engine Flexible environment

Nice to hear that, Dhandapani! - Jun On Friday, May 5, 2017 at 11:44:01 AM UTC-4, Dhandapani Sattanathan wrote: > > Thanks, Jun, Attila-Mihaly Balazs, > > *Cron jobs working fine. I added this in crontest.php file *$_SERVER[ > 'HTTP_X_APPENGINE_CRON'] =true;. > > Then I added this socket mysqli

[google-appengine] Re: Cron job failed in Google App Engine Flexible environment

Thanks, Jun, Attila-Mihaly Balazs, *Cron jobs working fine. I added this in crontest.php file *$_SERVER[ 'HTTP_X_APPENGINE_CRON'] =true;. Then I added this socket mysqli.default_socket= '/cloudsql/CONNECTION_NAME' in php.ini. *After that Cron job working fine using core PHP projects.* On Wedne

Re: [google-appengine] Re: Cron job failed in Google App Engine Flexible environment

Thanks, Jun & Attila. I had issues in Cron job only.I 'll give details in the issue tracker and open defect. *Regards,* *SATTANATHAN DPROJECT MANAGER* *SSOMENS SOFTWARE DEVELOPMENT* *04132333229 /230/231* www.ssomens.com [image: C:\Users\SSOMENS-003_2\Desktop\business development material\cu

[google-appengine] Re: Cron job failed in Google App Engine Flexible environment

Hi Dhandapani, For now, I suggest that you try the suggestion by Attila-Mihaly given the 404 error you're seeing. If it does not resolve the issue, then it is recommended that you open an issue at the Issue Tracker report with your proje

[google-appengine] Re: Cron job failed in Google App Engine Flexible environment

Hello Dhandapani, If you're seeing a 404 error, it means that the given URL (/web/crontest.php) is not accessible. Could you check your setup to confirm that /web/crontest.php can be accessed? Regards, Attila -- You received this message because you are subscribed to the Google Groups "Googl

Re: [google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

thanks a lot for your help man!! now it running !! :-) On Tue, Apr 4, 2017 at 3:43 PM, Daniel Garrido wrote: > I skipped this information from Brian. How to run appcfg from the command > line: > > [1] appcfg.sh is from the App Engine SDK for Java >

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

I skipped this information from Brian. How to run appcfg from the command line: [1] appcfg.sh is from the App Engine SDK for Java and not included in the Google Cloud SDK. But it's a simple wrapper around a jar that is included

Re: [google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

Thanks Daniel!! i ran this appcfg command!! but my cron job is not getting uploded!! i dont know why!! On Tue, Apr 4, 2017 at 3:38 PM, Daniel Garrido wrote: > Hi, > > I ran appcfg from the command line. You will have to use appcfg.cmd > included in the java app engine sdk. It seems that it is no

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

Hi, I ran appcfg from the command line. You will have to use appcfg.cmd included in the java app engine sdk. It seems that it is not included in the cloud sdk. At least, I wasn't able to find it. This point doesn't seem very clear in the documentation. Inside eclipse, I followed the recommenda

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

hi daniel!! same thing is happening with me!! corn job not being uploded!! what to do?? where to run this appcfg command in eclipse?? im using eclipse!! its a gwt project!! please tell me how to make it work? thanx in advance! On Wednesday, March 15, 2017 at 3:05:19 AM UTC+5:30, Daniel Garrido

Re: [google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

hii Brian!! my corn job is not getting uploded! my corn.xml cornservlet.java and web.xml are fine! im not able to get how to trigger corn service?? ! im not getting uploding corn job message in my console page!! what should i do?? i even dont know how to run appcfg.sh command and where to run t

Re: [google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

Jason, This will be fixed in the next release of Cloud Tools for Eclipse. In the meantime you should be able to use the `appcfg.sh` command [1] to upload your cron.xml (`appcfg.sh help update_cron`) and `queue.xml` (`appcfg.sh help update_queues`). You'll need to use the `-A` argument to spec

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

What if you are not using a Maven-based project? I created a non-maven project and it is not uploading my queue.xml or cron.xml either. On Wednesday, March 15, 2017 at 3:23:46 AM UTC-7, Nicola Spreafico wrote: > > If you're using a Maven-based project, by default implementation of the > Maven Pl

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

It seems like the first option does not consult your configuration with specified *deployables*. It is thus likely consulting a different maven goal. On Wednesday, March 15, 2017 at 4:17:12 PM UTC-4, Daniel Garrido wrote: > > Thank you very much Nicola, > > It worked with minor modifications! M

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

Thank you very much Nicola, It worked with minor modifications! My final configuration is as follows: True true ${java.io.tmpdir}/appengine-staging ${java.io.tmpdir}/appengine-staging/app.yaml ${java.io.

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

If you're using a Maven-based project, by default implementation of the Maven Plugin only the app.yaml file (the application itself) is deployed. If you need to deploy the *cron*, *queue *and *index *as well, you need to configure the deployables configuration with all the files Please see this

[google-appengine] Re: cron job via google app engine or via any npm module(node-schedule)

Hey Himanshu, These are two very different methods. One runs *on* the instance, using Node JS to schedule and run events. The other runs in the Cloud Platform infrastructure, sending requests to your application at given intervals, which will then trigger a request handler to run the code. You

[google-appengine] Re: cron job via google app engine or via any npm module(node-schedule)

can anyone please answer it.. i need to complete it. On Monday, September 19, 2016 at 8:36:56 PM UTC+5:30, himanshu kapoor wrote: > > I need to deploy few cron jobs for my nodejs app hosted on google cloud. > > I have 2 options > > > cron-schedule npm package. > cron.yaml provided by app engine. >

[google-appengine] Re: Cron Retries Feature Launched

Hi Udayan, Thanks for the feedback. For max retries, how high would you like to set this number? We can probably bump it up to 10 pretty easily, but anything over that might take us some time. For alerts, have you looked at Stackdriver's Logs-based metrics (https://cloud.google.com/logging/doc

[google-appengine] Re: Cron Retries Feature Launched

Well, I wonder if cron provides some kind of information when it fails after max defined retry so that application or stack driver can send notification for human intervention. We have been looking into this for past couple of days but couldn't find anything we can use. On a side note, We are k

[google-appengine] Re: Cron job retry parameter for Python

Hi Cody, Yes, this is a known bug in the documentation and it should be fixed soon. The documentation should read: cron: - description: retry demo url: /retry schedule: every 10 mins retry_parameters: min_backoff_seconds: 2.5 max_doublings: 5 -Kim On Tuesday, April 19, 2016 at 10

[google-appengine] Re: Cron Retries Feature Launched

A useful addition, thank you! May I take the opportunity and ask you something about cron-jobs? Is there a specific reason why cron-jobs spawn GET requests? Many of my task-handlers are POST methods. Maybe I miss something, but I think it would feel more natural if I could also define the desir

[google-appengine] Re: Cron Retries Feature Launched

Hey, that's very helpful. Thanks for that! -- 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+unsubscr...@googlegroups.com. To post to this gr

[google-appengine] Re: Cron job not running on HTTPS

Hello Akash, Cron jobs are triggered by the App Engine Cron Service over HTTP. If you're forcing HTTPS redirection, consider adding another handler just for the Cron jobs without any redirection. Also, I recommend reading Securing URLs for cron

Re: [google-appengine] Re: cron

*1) so how much time does my "cron task" have to finish?* The cron job/scheduled task, to an autoscaled instance, has 60 seconds to get a response back. However, as you note... *2) if inside my "cron task" I create a DeferredTask and add it to a queue. **how much time does this new task have to

Re: [google-appengine] Re: cron

Hello. Thank you for all these informations. I have a few questions: I am only using "Automatic Scaling". *1) so how much time does my "cron task" have to finish?* --> If we consider that a cron task is just an http request then 60 seconds, if it's a task then 10 minutes. Which is it? *2) if i

Re: [google-appengine] Re: cron

For some additional clarification, a cron task is not necessarily a task queue task. As Alejandro said, it can merely an HTTP request. That means it can be of the following: 1) a request sent to a standard autoscaling instance (F* instances), be subject to a 60 second deadline; or 2) a request s

[google-appengine] Re: cron

Hello Trez, A Cron Task is an scheduled HTTP request. The time it can run, depends on witch instance type receive the request. If you need a long process to run from a cron task, a common approach is to launch a task queue (from the cron request) in a Manual or Basic scaling module. Cheers E

Re: [google-appengine] Re: Cron task has fails without trace in the logs

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 loo

Re: [google-appengine] Re: Cron task has fails without trace in the logs

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 1

[google-appengine] Re: Cron task has fails without trace in the logs

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

[google-appengine] Re: Cron scheduler synchronized is not working as expected.

If the cron job runs longer than the interval it will reset the clock. If you really need the every 2 minutes and your code is running longer than 2 minutes try running 2 crons at 4 minutes staggered 2 minutes apart. On Friday, August 7, 2015 at 11:06:37 PM UTC-4, Creative Cubs wrote: > > I want

[google-appengine] Re: Cron - targeting a particular version of a particular module

to add, my above answer only works for cron.yaml On Wednesday, July 22, 2015 at 3:59:48 PM UTC+1, Paul Canning wrote: > > Wait, I got it. You can target the versions using the format: > > version-dot-module > > e.g. 1-5-dot-main-module > > On Wednesday, July 22, 2015 at 3:53:36 PM UTC+1, Paul Cann

[google-appengine] Re: Cron - targeting a particular version of a particular module

Wait, I got it. You can target the versions using the format: version-dot-module e.g. 1-5-dot-main-module On Wednesday, July 22, 2015 at 3:53:36 PM UTC+1, Paul Canning wrote: > > I am facing a similar issue. > > Firstly, how do you target a specific version of a module in the > dispatch.yaml? T

[google-appengine] Re: Cron - targeting a particular version of a particular module

I am facing a similar issue. Firstly, how do you target a specific version of a module in the dispatch.yaml? The docs only talk about modules. Secondly, is there anyway to use more then 10 dispatch rules? I have already had to use 5 for routing subdomains (unless there is another way to achiev

[google-appengine] Re: Cron - targeting a particular version of a particular module

Hi Dawid. First thing in cron.yaml, you are supposed to use version or module in the target parameter. If you wish to target the cron job for a particular version and module you can use the dispatch.yaml as described by Vinny in the previous messages. On Thursday, February 20, 2014 at 12:29:04

[google-appengine] Re: Cron - targeting a particular version of a particular module

I hit the same issues with tasks today. The documentation states that the target can have the *version.module* value so this sounds like a bug. I filed the issue, please star it. https://code.google.com/p/googleappengine/issues/detail?id=11858 On Thursday, February 20, 2014 at 9:29:04 AM UTC-8,

[google-appengine] Re: Cron failure on 1.8.3

Yes, the message on the Cron Jobs page only says "on time Failed". I put a screenshot at http://www.tiikoni.com/tis/view/?id=eeea7ba. And no, there really was no entry in the logs - there's a screenshot of the logs at http://www.tiikoni.com/tis/view/?id=5cd1594, which has nothing at the schedul

[google-appengine] Re: Cron failure on 1.8.3

On Friday, August 2, 2013 9:09:02 AM UTC-5, john wrote: > My daily cron at 00:15 UTC failed last night, and there is no info for it > in the logs. What does your cron page show you? Does it say something like "On Time Failure", or anything else? (the info text is just below the cron inform

[google-appengine] Re: cron task not running. No errors in log. Huh!?

Might the task queue latency be relevant? Here's the status over the recent interval: Oh, and I found plenty of "Dead Man's Switch" services. But none that can be reset by a URLFetch. And none wit

Re: [google-appengine] Re: Cron jobs auto repeat on failure option?

A fun little gotcha about this. You may not really know why that 10 minute interval was triggered and it is likely destructive. The timeout can be triggered by something else. If any thread on the instance takes too long, the entire instance is killed immediately along with all active requests. We

[google-appengine] Re: Cron jobs auto repeat on failure option?

As you may notice, cron itself is a task that runs on queue __cron, so it seems trivial to implement this functionality. There may or may not be a good reason Google doesn't. I had asked about it before. https://groups.google.com/d/msg/google-appengine/oJ7VBKPt6ak/aF9lZxmfqygJ -- You received

[google-appengine] Re: Cron jobs auto repeat on failure option?

Likely the same as our crons are doing - they just do some key scanning and enqueue tasks to the taskqueue, having their own retry policy. The cron job itself only runs for a few seconds until all tasks are dispatched. Unfortunately from time to time this simple operation fails. When it happens

[google-appengine] Re: Cron jobs auto repeat on failure option?

We always use the (self-named) "cron-task" pattern. That is, our cron jobs do nothing more than queue a task to do the actual work, and the tasks have their own retry policy. Queuing a task is a very high success operation. j On Friday, 19 July 2013 10:06:03 UTC-6, Marcel Manz wrote: > > Somet

Re: [google-appengine] Re: Cron job on backends not run

I implemented the same workaround. For the past two days, it worked. It looks more elegant than I schedule another same job just for fail-over. Thanks, Will On Fri, May 25, 2012 at 8:59 PM, weboo wrote: > I have same problem. > The cron job on dynamic backend instance does not works. > > So I

[google-appengine] Re: Cron job on backends not run

I have same problem. The cron job on dynamic backend instance does not works. So I set the job which responses only "OK" 1 minites before real job, it works. Hidetaka On May 26, 5:59 am, Steve Meyfroidt wrote: > I had the same. I think there's a timeout while the instance is > started. > > I fi

[google-appengine] Re: Cron job on backends not run

I had the same. I think there's a timeout while the instance is started. I fixed it by scheduling a call to _ah/warmup a minute before the first real work job. Now I see those warmups always fail, but the real work gets done, presumably because the instance is up by the time they're scheduled to r

[google-appengine] Re: Cron job every 30 minutes only on work days

The GAE notes are confusing to me for your scenario. Have you tried: 1. Setting up 19 cron jobs of the form every mon,tue,wed,thu,fri HH:MM where HH:MM is: 09:00, 09:30, 10:00, ..., 15:00 1. Setting up 1 cron job of the form every mon,tue,wed,thu,fri 09:00 and using this cro

[google-appengine] Re: Cron job

The answer to question 1 is 10 minutes. I don't know the answer to question 2 I'm afraid! -- 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/-/bBtdQKs

[google-appengine] Re: cron doesn't run the majority of the time and has no logs

Hi Mike, Try this: under the Admin Console -> Main -> Logs, on the top right hand side, you see "Show: All requests Logs with minimum severity: ". Click on "All request". See if you now see log information for your cron jobs. It worked for me when I first didn't see the logs. Hope this helps

[google-appengine] Re: Cron schedule : one day per month ?

20 of month 09:00 worked for me -- 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/-/7t1S3OIxu_QJ. To post to this group, send email to google-appengine

[google-appengine] Re: Cron schedule : one day per month ?

Any progress on "day of month" feature? Is there an issue? I could star it. Thanks! -- 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/-/hMVIoJTrsOoJ.

Re: [google-appengine] Re: Cron job won't stop.

Hi, One small note, you can see the run schedule in your SDK. You might find it helpful for testing cron run schedules. http://localhost:8080/_ah/admin/cron Robert On Tue, Jun 7, 2011 at 09:28, DEbben wrote: > This fix seems to have stopped the job from running daily. I'll still >

[google-appengine] Re: Cron job won't stop.

This fix seems to have stopped the job from running daily. I'll still have to wait until next month to see if it runs the job on the first. Thanks for the help. On Jun 5, 12:24 am, Robert Kluin wrote: > Try: > >    schedule: 1 of month 00:00 > > Robert > > > > On Fri, Jun 3, 2011 at 10:02, DEbben

Re: [google-appengine] Re: Cron deadlines

No prob, done: http://code.google.com/p/googleappengine/issues/detail?id=5085 Jeff On Fri, May 20, 2011 at 8:11 AM, Johan Euphrosine wrote: > Yes since 1.4.0 is deadline for offline cron request has been raised > to 10 minutes: > http://googleappengine.blogspot.com/2010/12/happy-holidays-from-a

Re: [google-appengine] Re: Cron deadlines

Yes since 1.4.0 is deadline for offline cron request has been raised to 10 minutes: http://googleappengine.blogspot.com/2010/12/happy-holidays-from-app-engine-team-140.html Could you fill a documentation bug on: http://code.google.com/p/googleappengine/issues/entry And report it back here ? Than

[google-appengine] Re: Cron deadlines

Cron scripts have 10 minute limits. On May 20, 10:45 am, Jeff Schnitzer wrote: > The documentation for Scheduled Tasks says "A URL invoked by cron is > subject to the same limits and quotas as a normal HTTP request, > including the request time limit." > > Is there a reason for scheduled tasks to

Re: [google-appengine] Re: Cron is 301

You can check os.environ['REMOTE_ADDR'][:2] == '0.' All the internal requests (cron, task queue, xmpp, etc.) IPs start with '0.'. On Fri, May 20, 2011 at 1:23 PM, 筱枫 wrote: > def redirect(app): > >Status = 'Status: 301 Moved Permanently' >HOST = 'www.aregg.com' > >if o

[google-appengine] Re: Cron is 301

def redirect(app): Status = 'Status: 301 Moved Permanently' HOST = 'www.aregg.com' if os.environ.get('HTTP_HOST').endswith(HOST) and os.environ.get('HTTPS') == 'off' and os.environ.get('X-AppEngine- Cron') is None: sys.stdout.write(Status + '\nLocation: htt

[google-appengine] Re: Cron is 301

Help me. On 5月17日, 下午12时39分, 筱枫 wrote: > My application needs to use 301 to my APP domain. > > if not os.environ.get('HTTP_HOST').endswith(domain) and > os.environ.get('HTTPS') == 'off' and os.environ.get('X-AppEngine- > Cron') is None: > > But why Cron is 301? > > os.environ.get('X-AppEngine-Cro

Re: [google-appengine] Re: Cron job Failure

And you have the advantage of a retry in case of a failure, like no writes during maintenance, task are suspended until the maintenance is complete. You can add new tasks but they are put on hold for a while. 2011/1/26 Kaan Soral : > Add the job to a queue instead of running it directly in cron >

Re: [google-appengine] Re: Cron job Failure

Hi Greg, I thought cron-jobs also had 10-minutes to execute, however someone pointed out the cron docs still state that cron jobs are subject to the 'normal' request limit. Are the docs incorrect (or unclear)? "A cron job will invoke a URL, using an HTTP GET request, at a given time of day. A U

Re: [google-appengine] Re: Cron job Failure

Both Taskqueue tasks and Cron tasks get 10minutes to execute. Have you looked at your logs to determine what error is occurring in your code. On 27 January 2011 06:54, Kaan Soral wrote: > Add the job to a queue instead of running it directly in cron > that way it can run for 10 minutes > > On Ja

[google-appengine] Re: Cron job Failure

Add the job to a queue instead of running it directly in cron that way it can run for 10 minutes On Jan 26, 12:24 am, DougW wrote: > I have a cron setup to run a python file on the vizumetricsupdate > application that is constantly failing although there is no error in > the log. When I run this

[google-appengine] Re: Cron jobs not getting executed

My one minutes jobs also doens't work. -- 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 group, send email to google-appengine+unsubscr...@googl

[google-appengine] Re: Cron jobs not getting executed

Thank you for the reports and apologies for the cron problems you saw today. We made some changes yesterday to improve performance for task queues and this negatively impacted cron jobs that are running very frequently, e.g. every minute. We've reverted these changes and confirmed that cron jobs

[google-appengine] Re: Cron jobs not getting executed

Same problem happening on my app. On Nov 11, 3:55 pm, dflorey wrote: > Hi, > one of my customers has problems with his app: trecontacts > > We have cron jobs scheduled for every minute, but they have not run > for the last hours. > Can someone please check? > > Thanks, > > Daniel -- You receive

[google-appengine] Re: Cron jobs not getting executed

I have been having the same problem today. I thought it was something in my code but clearly not. On Nov 11, 3:55 pm, dflorey wrote: > Hi, > one of my customers has problems with his app: trecontacts > > We have cron jobs scheduled for every minute, but they have not run > for the last hours. > C

[google-appengine] Re: Cron jobs not getting executed

I have been having the same problem today. On Nov 11, 3:55 pm, dflorey wrote: > Hi, > one of my customers has problems with his app: trecontacts > > We have cron jobs scheduled for every minute, but they have not run > for the last hours. > Can someone please check? > > Thanks, > > Daniel -- Yo

[google-appengine] Re: Cron jobs not getting executed

Yes, my 5-minute cron job is working. The two 1-minute jobs are not working. On Nov 11, 6:06 pm, Chris Prinos wrote: > I'v had problems as well, 1-minute crons were not being called > starting around 2:26:am EST. They started working again around 5am > EST, then stopped again a couple of hours la

[google-appengine] Re: Cron jobs not getting executed

I'v had problems as well, 1-minute crons were not being called starting around 2:26:am EST. They started working again around 5am EST, then stopped again a couple of hours later. Currently they are not working. I changed my cron config to 2-minutes and those are working. I had other crons that we

[google-appengine] Re: Cron scheduling at runtime

this is easily possible using command script. refer here - http://code.google.com/appengine/docs/java/tools/uploadinganapp.html#Command_Line_Arguments you will just need to create a small script which will run the script and hence upload the updated cron using update_cron optionread the a

[google-appengine] Re: Cron job ran twice today

Yes double check everything if its a critical job like you mentioned, use the datastore for storing temp values for checking job status 2 times in the past few days, my CRON jobs didnt even run at all during 12AM - 1230AM or so timeline So dont rely on the CRON jobs, maybe you can submit a task (

[google-appengine] Re: Cron job ran twice today

Possible solution: Read the documentation on Quartz and somewhere they explain certain situation that can cause Cron expressions to be executed twice. If I remember correctly, when your Cron expression is fired too close to midnight and/or when you mix issues ot timezones Check it out! You migh

[google-appengine] Re: Cron job ran twice today

I have always assumed in design that my scheduled tasks (cron jobs) should be idempotent, since I know that my queued tasks must be. Your experience appears to validate my assumption! On Oct 25, 11:18 am, Lior Harsat wrote: > Hi, > > I have noticed today that on of my cron jobs ran twice !!! >

[google-appengine] Re: Cron Jobs not working and other Issues (Java)

UPDATE: After deploying to a new version several time these NoClassDefFoundError disappeared. I made this the default version to serve and the application is now working. Even in the new version the cronjobs did not work for some time but are now working again. I am wondering what caused this beh

  1   2   3   >