[google-appengine] Re: Deadline exceeded error when deploying GAE flex app

['Aref Amiri (Cloud Platform Support)' via Google App Engine]

Hi Jeff,

I have reported this issue to the App Engine engineering team for further 
investigation. I have also created a Public Issue Tracker 
 to follow the progress of the 
issue. You can star the page to be notified of the latest updates on the 
issue, as future communication will be shared on that thread.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a7b7c962-6537-4ad2-a3d1-275b56cf241d%40googlegroups.com.

[google-appengine] Re: Deadline exceeded error when deploying GAE flex app

[Jeff O'Neill]

I figured it out finally, and it is an ugly bug...

About 6 months ago, I set a location policy of US only.  The policy 
included US locations that existed at that time, but I think the policy did 
not update with new US locations as they became available.

My GAE app was being deployed to "us-central1-f" (I did not specifically 
pick this location; I had previously picked us-central).  This location was 
not in my location policy because I presume it did not exist then.  I 
removed my location policy, and I can now deploy my app.

I never got a meaningful error message in deploying my own app.  For a 
sanity check, I tried deploying Google's "hello world" GAE flex app, and 
that app gave an error message that included this:

> Location ZONE:us-central1-f violates constraint 
constraints/gcp.resourceLocations

So I was able to figure it out.

Could a Google Engineer please make an official bug report of this?


On Friday, September 6, 2019 at 7:57:05 AM UTC-4, Jeff O'Neill wrote:
>
> I've been using GAE flex for about six months, and starting yesterday, I 
> get this error when deploying with gcloud app deploy:
>
> > ERROR: (gcloud.app.deploy) Error Response: [4] Flex operation
> > projects/MY-PROJECT/regions/us-central1/operations/xxx
> > error [DEADLINE_EXCEEDED]: An internal error occurred while processing
> > task
> > 
> /appengine-flex-v1/insert_flex_deployment/flex_create_resources>2019-09-04T21:29:03.412Z8424.ow.0:
> > Gave up polling Deployment Manager operation
> > MY-PROJECT/operation-xxx.
>
> I don't see any helpful info in my logs.
>
> The app runs fine locally and I haven't done any major code changes since 
> the a successful deploy a few days ago.
>
> I wonder if I have somehow inadvertently changed a setting.  I did turn 
> on Cloud Web Security Scanner, but I wouldn't expect that to cause the 
> problem.
>
> I set cloud_build_timeout to 600 (what I think is the default anyway) but 
> that didn't help.
>
> Any ideas how to fix this?  Should I set custom values for 
> initial_delay_sec or app_start_timeout_sec?
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/03a3d38f-14bd-45b4-a9da-b5b11ed2639d%40googlegroups.com.

[google-appengine] Re: Deadline exceeded error when deploying GAE flex app

[Jeff O'Neill]

I've been trying everything I can think of to fix this with no luck.  Here 
are some things I tried:

   - deploying the exact code that previously deployed successfully
   - deployed into a new app engine project
   - increased cloud_build_timeout to 1200 (though I've read elsewhere that 
   >600 doesn't work)
   - maxed out all deadlines I could find and added the stuff below to my 
   app.yaml

My app doesn't do anything out of the ordinary.  The build requires 
compiling C code (e.g., Spacy, Numpy) but nothing too complicated.

Any advice would be greatly appreciated.

=

readiness_check:
  check_interval_sec: 300
  timeout_sec: 299
  failure_threshold: 2
  success_threshold: 2
  app_start_timeout_sec: 1800

liveness_check:
  check_interval_sec: 300
  timeout_sec: 299
  failure_threshold: 2
  success_threshold: 2


On Friday, September 6, 2019 at 7:57:05 AM UTC-4, Jeff O'Neill wrote:
>
> I've been using GAE flex for about six months, and starting yesterday, I 
> get this error when deploying with gcloud app deploy:
>
> > ERROR: (gcloud.app.deploy) Error Response: [4] Flex operation
> > projects/MY-PROJECT/regions/us-central1/operations/xxx
> > error [DEADLINE_EXCEEDED]: An internal error occurred while processing
> > task
> > 
> /appengine-flex-v1/insert_flex_deployment/flex_create_resources>2019-09-04T21:29:03.412Z8424.ow.0:
> > Gave up polling Deployment Manager operation
> > MY-PROJECT/operation-xxx.
>
> I don't see any helpful info in my logs.
>
> The app runs fine locally and I haven't done any major code changes since 
> the a successful deploy a few days ago.
>
> I wonder if I have somehow inadvertently changed a setting.  I did turn 
> on Cloud Web Security Scanner, but I wouldn't expect that to cause the 
> problem.
>
> I set cloud_build_timeout to 600 (what I think is the default anyway) but 
> that didn't help.
>
> Any ideas how to fix this?  Should I set custom values for 
> initial_delay_sec or app_start_timeout_sec?
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b76f0119-2acb-465b-b670-89a4c4d05947%40googlegroups.com.

[google-appengine] Re: Deadline exceeded error when deploying GAE flex app

[Jeff O'Neill]

Now I tried building my own docker image, pushed the image to us.gcr.io and 
deployed from there.

I get the same error from my original email.

Hopefully, this is enough info for someone to give me some advice.


On Friday, September 6, 2019 at 7:57:05 AM UTC-4, Jeff O'Neill wrote:
>
> I've been using GAE flex for about six months, and starting yesterday, I 
> get this error when deploying with gcloud app deploy:
>
> > ERROR: (gcloud.app.deploy) Error Response: [4] Flex operation
> > projects/MY-PROJECT/regions/us-central1/operations/xxx
> > error [DEADLINE_EXCEEDED]: An internal error occurred while processing
> > task
> > 
> /appengine-flex-v1/insert_flex_deployment/flex_create_resources>2019-09-04T21:29:03.412Z8424.ow.0:
> > Gave up polling Deployment Manager operation
> > MY-PROJECT/operation-xxx.
>
> I don't see any helpful info in my logs.
>
> The app runs fine locally and I haven't done any major code changes since 
> the a successful deploy a few days ago.
>
> I wonder if I have somehow inadvertently changed a setting.  I did turn 
> on Cloud Web Security Scanner, but I wouldn't expect that to cause the 
> problem.
>
> I set cloud_build_timeout to 600 (what I think is the default anyway) but 
> that didn't help.
>
> Any ideas how to fix this?  Should I set custom values for 
> initial_delay_sec or app_start_timeout_sec?
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f862b6a3-bd7a-4407-8d0e-6866eb779c67%40googlegroups.com.

[google-appengine] Re: deadline errors for pages which normally load fast

[James Gilliam]

I believe this problem was fixed about 10 hours ago.  None of these errors 
occurred overnight and I have had them day after day for a week or longer. 
 Also, pages which were loading in 18 secs to greater than 60 are back to 
loading in 2 seconds when they are not cached.

Also, something significant changed with memcache at the same time.

I typically have about 98% hits but for the last week or so it was 67% 
hits.  I suspected a memcache issue but it was hard to prove.  Now that the 
hit ratio is back up for normal ranges I am convinced there has been a 
memcache issue.

In any case, I am grateful these problems appear to have been fixed.

I wonder if it was version 1.8.7 ???



On Monday, November 4, 2013 4:19:41 PM UTC-8, James Gilliam wrote:

 I am seeing deadline failures such as the one below -- 61 secs.  Using 
 python 2.7, appid ogeekcom.  Notice it doesn't say deadline error -- it 
 appears that somebody is broken in the GAE logging code but based on the 61 
 seconds I have come to believe it is a deadline failure.

 Just loaded the same page in 208 ms.

 Many times they are associated with a memcache set failure, but sometimes 
 other failures, e.g. blob url_serving error.

 I use the 1 gig premium memcache even though I don't need nearly that much 
 cache and hate the cost at $90 a month.

 I saw almost 40 of these errors overnight ... clustered around a couple of 
 times.  When that happens, instances are created for each URL because the 
 request takes so long to finish  ouch.


1. 2013-11-04 14:04:27.457 /viking-international-llc 500 61941ms 0kb 
 Mozilla/5.0 
(compatible; Googlebot/2.1; +http://www.google.com/bot.html)

66.249.66.180 - - [04/Nov/2013:14:04:27 -0800] GET 
 /viking-international-llc HTTP/1.1 500 0 - Mozilla/5.0 (compatible; 
 Googlebot/2.1; +http://www.google.com/bot.html) www.goobafoo.com ms=61941 
 cpu_ms=3850 app_engine_release=1.8.6 
 instance=00c61b117c74a9c539d5b4ef839de2da2a3a8a3f 
 https://appengine.google.com/instances?app_id=s~ogeekcomversion_id=1383584138-1576.371403051099549606key=00c61b117c74a9c539d5b4ef839de2da2a3a8a3f#00c61b117c74a9c539d5b4ef839de2da2a3a8a3f

2. E2013-11-04 14:04:27.361

[data.cacheSave, except, memcache set failed, goobafoo, 
 goobafoo-goobafoo-landingview-landingid=viking-international-llc, 
 {p-landingid:1, p-offset:1, t-gallerys:1, t-landings:1}]

3. E2013-11-04 14:04:27.454

Traceback (most recent call last):

4. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/app_logging.py,
  line 78, in emit

5. E2013-11-04 14:04:27.454

logservice.write(message)

6. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 348, in write

7. E2013-11-04 14:04:27.454

logs_buffer().write(message)

8. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 237, in write

9. E2013-11-04 14:04:27.454

return self._lock_and_call(self._write, line)

10. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 158, in _lock_and_call

11. E2013-11-04 14:04:27.454

return method(*args)

12. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 254, in _write

13. E2013-11-04 14:04:27.454

self._autoflush()

14. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 322, in _autoflush

15. E2013-11-04 14:04:27.454

self._flush()

16. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 308, in _flush

17. E2013-11-04 14:04:27.454

apiproxy_stub_map.MakeSyncCall('logservice', 'Flush', request, 
 response)

18. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py,
  line 94, in MakeSyncCall

19. E2013-11-04 14:04:27.454

return stubmap.MakeSyncCall(service, call, request, response)

20. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py,
  line 328, in MakeSyncCall

21. E2013-11-04 14:04:27.454

rpc.CheckSuccess()

22. E2013-11-04 14:04:27.454

  File 
 

[google-appengine] Re: deadline errors for pages which normally load fast

[James Gilliam]

Spoke too soon ... just had another rash of these errors ... also GAE 
flushed all the memcache again for my app ... second time today ... and 
there is a PYTHON investigation reported as well.

On Monday, November 4, 2013 4:19:41 PM UTC-8, James Gilliam wrote:

 I am seeing deadline failures such as the one below -- 61 secs.  Using 
 python 2.7, appid ogeekcom.  Notice it doesn't say deadline error -- it 
 appears that somebody is broken in the GAE logging code but based on the 61 
 seconds I have come to believe it is a deadline failure.

 Just loaded the same page in 208 ms.

 Many times they are associated with a memcache set failure, but sometimes 
 other failures, e.g. blob url_serving error.

 I use the 1 gig premium memcache even though I don't need nearly that much 
 cache and hate the cost at $90 a month.

 I saw almost 40 of these errors overnight ... clustered around a couple of 
 times.  When that happens, instances are created for each URL because the 
 request takes so long to finish  ouch.


1. 2013-11-04 14:04:27.457 /viking-international-llc 500 61941ms 0kb 
 Mozilla/5.0 
(compatible; Googlebot/2.1; +http://www.google.com/bot.html)

66.249.66.180 - - [04/Nov/2013:14:04:27 -0800] GET 
 /viking-international-llc HTTP/1.1 500 0 - Mozilla/5.0 (compatible; 
 Googlebot/2.1; +http://www.google.com/bot.html) www.goobafoo.com ms=61941 
 cpu_ms=3850 app_engine_release=1.8.6 
 instance=00c61b117c74a9c539d5b4ef839de2da2a3a8a3f 
 https://appengine.google.com/instances?app_id=s~ogeekcomversion_id=1383584138-1576.371403051099549606key=00c61b117c74a9c539d5b4ef839de2da2a3a8a3f#00c61b117c74a9c539d5b4ef839de2da2a3a8a3f

2. E2013-11-04 14:04:27.361

[data.cacheSave, except, memcache set failed, goobafoo, 
 goobafoo-goobafoo-landingview-landingid=viking-international-llc, 
 {p-landingid:1, p-offset:1, t-gallerys:1, t-landings:1}]

3. E2013-11-04 14:04:27.454

Traceback (most recent call last):

4. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/app_logging.py,
  line 78, in emit

5. E2013-11-04 14:04:27.454

logservice.write(message)

6. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 348, in write

7. E2013-11-04 14:04:27.454

logs_buffer().write(message)

8. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 237, in write

9. E2013-11-04 14:04:27.454

return self._lock_and_call(self._write, line)

10. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 158, in _lock_and_call

11. E2013-11-04 14:04:27.454

return method(*args)

12. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 254, in _write

13. E2013-11-04 14:04:27.454

self._autoflush()

14. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 322, in _autoflush

15. E2013-11-04 14:04:27.454

self._flush()

16. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 308, in _flush

17. E2013-11-04 14:04:27.454

apiproxy_stub_map.MakeSyncCall('logservice', 'Flush', request, 
 response)

18. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py,
  line 94, in MakeSyncCall

19. E2013-11-04 14:04:27.454

return stubmap.MakeSyncCall(service, call, request, response)

20. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py,
  line 328, in MakeSyncCall

21. E2013-11-04 14:04:27.454

rpc.CheckSuccess()

22. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_rpc.py,
  line 133, in CheckSuccess

23. E2013-11-04 14:04:27.454

raise self.exception

24. E2013-11-04 14:04:27.454

CancelledError: The API call logservice.Flush() was explicitly cancelled.

25. E2013-11-04 14:04:27.454

Logged from file common.py, line 573




-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop 

[google-appengine] Re: deadline errors for pages which normally load fast

[James Gilliam]

more failures and another memcache flush at 4:28 PT ...

here's an idea GAE ... why don't you test your shit before pushing it out !

On Monday, November 4, 2013 4:19:41 PM UTC-8, James Gilliam wrote:

 I am seeing deadline failures such as the one below -- 61 secs.  Using 
 python 2.7, appid ogeekcom.  Notice it doesn't say deadline error -- it 
 appears that somebody is broken in the GAE logging code but based on the 61 
 seconds I have come to believe it is a deadline failure.

 Just loaded the same page in 208 ms.

 Many times they are associated with a memcache set failure, but sometimes 
 other failures, e.g. blob url_serving error.

 I use the 1 gig premium memcache even though I don't need nearly that much 
 cache and hate the cost at $90 a month.

 I saw almost 40 of these errors overnight ... clustered around a couple of 
 times.  When that happens, instances are created for each URL because the 
 request takes so long to finish  ouch.


1. 2013-11-04 14:04:27.457 /viking-international-llc 500 61941ms 0kb 
 Mozilla/5.0 
(compatible; Googlebot/2.1; +http://www.google.com/bot.html)

66.249.66.180 - - [04/Nov/2013:14:04:27 -0800] GET 
 /viking-international-llc HTTP/1.1 500 0 - Mozilla/5.0 (compatible; 
 Googlebot/2.1; +http://www.google.com/bot.html) www.goobafoo.com ms=61941 
 cpu_ms=3850 app_engine_release=1.8.6 
 instance=00c61b117c74a9c539d5b4ef839de2da2a3a8a3f 
 https://appengine.google.com/instances?app_id=s~ogeekcomversion_id=1383584138-1576.371403051099549606key=00c61b117c74a9c539d5b4ef839de2da2a3a8a3f#00c61b117c74a9c539d5b4ef839de2da2a3a8a3f

2. E2013-11-04 14:04:27.361

[data.cacheSave, except, memcache set failed, goobafoo, 
 goobafoo-goobafoo-landingview-landingid=viking-international-llc, 
 {p-landingid:1, p-offset:1, t-gallerys:1, t-landings:1}]

3. E2013-11-04 14:04:27.454

Traceback (most recent call last):

4. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/app_logging.py,
  line 78, in emit

5. E2013-11-04 14:04:27.454

logservice.write(message)

6. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 348, in write

7. E2013-11-04 14:04:27.454

logs_buffer().write(message)

8. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 237, in write

9. E2013-11-04 14:04:27.454

return self._lock_and_call(self._write, line)

10. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 158, in _lock_and_call

11. E2013-11-04 14:04:27.454

return method(*args)

12. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 254, in _write

13. E2013-11-04 14:04:27.454

self._autoflush()

14. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 322, in _autoflush

15. E2013-11-04 14:04:27.454

self._flush()

16. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 308, in _flush

17. E2013-11-04 14:04:27.454

apiproxy_stub_map.MakeSyncCall('logservice', 'Flush', request, 
 response)

18. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py,
  line 94, in MakeSyncCall

19. E2013-11-04 14:04:27.454

return stubmap.MakeSyncCall(service, call, request, response)

20. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py,
  line 328, in MakeSyncCall

21. E2013-11-04 14:04:27.454

rpc.CheckSuccess()

22. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_rpc.py,
  line 133, in CheckSuccess

23. E2013-11-04 14:04:27.454

raise self.exception

24. E2013-11-04 14:04:27.454

CancelledError: The API call logservice.Flush() was explicitly cancelled.

25. E2013-11-04 14:04:27.454

Logged from file common.py, line 573




-- 
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] Re: deadline errors for pages which normally load fast

[James Gilliam]

GAE ... can you please stop flushing the cache during the middle of the day 
... !

I am pay $90 a month for the premium memcache and you flushed it three 
times today !

Come on !

On Monday, November 4, 2013 4:19:41 PM UTC-8, James Gilliam wrote:

 I am seeing deadline failures such as the one below -- 61 secs.  Using 
 python 2.7, appid ogeekcom.  Notice it doesn't say deadline error -- it 
 appears that somebody is broken in the GAE logging code but based on the 61 
 seconds I have come to believe it is a deadline failure.

 Just loaded the same page in 208 ms.

 Many times they are associated with a memcache set failure, but sometimes 
 other failures, e.g. blob url_serving error.

 I use the 1 gig premium memcache even though I don't need nearly that much 
 cache and hate the cost at $90 a month.

 I saw almost 40 of these errors overnight ... clustered around a couple of 
 times.  When that happens, instances are created for each URL because the 
 request takes so long to finish  ouch.


1. 2013-11-04 14:04:27.457 /viking-international-llc 500 61941ms 0kb 
 Mozilla/5.0 
(compatible; Googlebot/2.1; +http://www.google.com/bot.html)

66.249.66.180 - - [04/Nov/2013:14:04:27 -0800] GET 
 /viking-international-llc HTTP/1.1 500 0 - Mozilla/5.0 (compatible; 
 Googlebot/2.1; +http://www.google.com/bot.html) www.goobafoo.com ms=61941 
 cpu_ms=3850 app_engine_release=1.8.6 
 instance=00c61b117c74a9c539d5b4ef839de2da2a3a8a3f 
 https://appengine.google.com/instances?app_id=s~ogeekcomversion_id=1383584138-1576.371403051099549606key=00c61b117c74a9c539d5b4ef839de2da2a3a8a3f#00c61b117c74a9c539d5b4ef839de2da2a3a8a3f

2. E2013-11-04 14:04:27.361

[data.cacheSave, except, memcache set failed, goobafoo, 
 goobafoo-goobafoo-landingview-landingid=viking-international-llc, 
 {p-landingid:1, p-offset:1, t-gallerys:1, t-landings:1}]

3. E2013-11-04 14:04:27.454

Traceback (most recent call last):

4. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/app_logging.py,
  line 78, in emit

5. E2013-11-04 14:04:27.454

logservice.write(message)

6. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 348, in write

7. E2013-11-04 14:04:27.454

logs_buffer().write(message)

8. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 237, in write

9. E2013-11-04 14:04:27.454

return self._lock_and_call(self._write, line)

10. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 158, in _lock_and_call

11. E2013-11-04 14:04:27.454

return method(*args)

12. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 254, in _write

13. E2013-11-04 14:04:27.454

self._autoflush()

14. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 322, in _autoflush

15. E2013-11-04 14:04:27.454

self._flush()

16. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/logservice/logservice.py,
  line 308, in _flush

17. E2013-11-04 14:04:27.454

apiproxy_stub_map.MakeSyncCall('logservice', 'Flush', request, 
 response)

18. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py,
  line 94, in MakeSyncCall

19. E2013-11-04 14:04:27.454

return stubmap.MakeSyncCall(service, call, request, response)

20. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py,
  line 328, in MakeSyncCall

21. E2013-11-04 14:04:27.454

rpc.CheckSuccess()

22. E2013-11-04 14:04:27.454

  File 
 /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_rpc.py,
  line 133, in CheckSuccess

23. E2013-11-04 14:04:27.454

raise self.exception

24. E2013-11-04 14:04:27.454

CancelledError: The API call logservice.Flush() was explicitly cancelled.

25. E2013-11-04 14:04:27.454

Logged from file common.py, line 573




-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving 

[google-appengine] Re: deadline errors for pages which normally load fast

[Robert King]

A few hours ago most of our python app went down  all requests were timing 
out. (Our app has never been down before).
I checked https://code.google.com/status/appengine/ and it said 
investigating for Memcache  Python so they must have been having some 
issues.
I'm not sure why there is a green tick there now.

-- 
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 group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: deadline errors for pages which normally load fast

[Janusz Skonieczny]

Same here, up until yesterday our app was doing fine, and now it has high 
timeout rate.

Regards. Janusz.

-- 
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 group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Deadline Exceeded Exception on loading requests leaves bad instance running

[bob.hitching]

Hi Anand, 

Some instances of our app (incoming-api) are suffering from abnormal warmup 
times of over 100 seconds, resulting in Error code 104.

I raised a production 
issue http://code.google.com/p/googleappengine/issues/detail?id=8240
two days ago but it has not been Acknowledged yet.

Please can you provide an update on this -

Many thanks, 

Bob


On Wednesday, October 3, 2012 8:27:45 PM UTC-7, Anand Mistry wrote:

 Hi Jason,

 The engineering team is aware of this issue of instances being in a wacky 
 state, however, I can't give you any more information.

 On Thursday, 4 October 2012 06:06:45 UTC+10, Jason Collins wrote:

 We've seen some Deadline Exceeded Exceptions cropping up on loading 
 requests again. This used to be commonplace (a couple of years ago), but I 
 haven't seen it for a long time... until recently.

 Has anyone else seen this lately? We're seeing it on Py2.7. Normally, 
 these apps warmup in a couple of seconds, so 60-70s startup times are 
 completely abnormal.

 Worse, when this occurs during a loading request, the instance is left in 
 a partially inflated state - in our case, basically all subsequent 
 requests fail with import/pythonpath issues. Our recourse, once we discover 
 this is happening, is to manually kill the instance. This really, really 
 sucks.

 Can anyone make an argument why you would *want* to keep an instance 
 that Deadline Exceeded Exceptions on a loading request? I can't. I think an 
 instance that hits a Deadline Exceeded Exception during a loading request 
 should be thrown away as suspect.

 j



-- 
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/-/am-KwJ9DnC8J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline Exceeded Exception on loading requests leaves bad instance running

[Sam]

Is there any update on this? In addition to instance time increases, we are 
also seeing huge datastore latency past few days and lot 
of DeadlineExceededExceptions. 

Our app id: textyserver

On Wednesday, October 3, 2012 8:27:45 PM UTC-7, Anand Mistry wrote:

 Hi Jason,

 The engineering team is aware of this issue of instances being in a wacky 
 state, however, I can't give you any more information.

 On Thursday, 4 October 2012 06:06:45 UTC+10, Jason Collins wrote:

 We've seen some Deadline Exceeded Exceptions cropping up on loading 
 requests again. This used to be commonplace (a couple of years ago), but I 
 haven't seen it for a long time... until recently.

 Has anyone else seen this lately? We're seeing it on Py2.7. Normally, 
 these apps warmup in a couple of seconds, so 60-70s startup times are 
 completely abnormal.

 Worse, when this occurs during a loading request, the instance is left in 
 a partially inflated state - in our case, basically all subsequent 
 requests fail with import/pythonpath issues. Our recourse, once we discover 
 this is happening, is to manually kill the instance. This really, really 
 sucks.

 Can anyone make an argument why you would *want* to keep an instance 
 that Deadline Exceeded Exceptions on a loading request? I can't. I think an 
 instance that hits a Deadline Exceeded Exception during a loading request 
 should be thrown away as suspect.

 j



-- 
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/-/joJCKS4A9xEJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline Exceeded Exception on loading requests leaves bad instance running

[Anand Mistry]

Hi Jason,

The engineering team is aware of this issue of instances being in a wacky 
state, however, I can't give you any more information.

On Thursday, 4 October 2012 06:06:45 UTC+10, Jason Collins wrote:

 We've seen some Deadline Exceeded Exceptions cropping up on loading 
 requests again. This used to be commonplace (a couple of years ago), but I 
 haven't seen it for a long time... until recently.

 Has anyone else seen this lately? We're seeing it on Py2.7. Normally, 
 these apps warmup in a couple of seconds, so 60-70s startup times are 
 completely abnormal.

 Worse, when this occurs during a loading request, the instance is left in 
 a partially inflated state - in our case, basically all subsequent 
 requests fail with import/pythonpath issues. Our recourse, once we discover 
 this is happening, is to manually kill the instance. This really, really 
 sucks.

 Can anyone make an argument why you would *want* to keep an instance that 
 Deadline Exceeded Exceptions on a loading request? I can't. I think an 
 instance that hits a Deadline Exceeded Exception during a loading request 
 should be thrown away as suspect.

 j


-- 
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/-/qi0vpUoJ2usJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline exceeded during warm-up

[Karl Rosaen]

Is happening on our app a lot too.  Seeming more and more like the 
Master/Slave datastore is not a reliable place to be...

-- 
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/-/3CYqFYkW7_0J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline exceeded during warm-up

[Scott Murphy]

I have been having major problems lately. I am on Master/Slave.  I have 
Always On and only the middle (2nd) instance always fails out of 3.  It just 
keeps recycling.  

http://code.google.com/p/googleappengine/issues/detail?id=4921

http://code.google.com/p/googleappengine/issues/detail?id=5253


-- 
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/-/PcUQ3a_jtQgJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline exceeded during warm-up

[Owen Wiggins]

We've been having similar issues (predominantly during warm up requests) 
running on Master/Slave for the past several days. This is with always on 
enabled, if it makes a difference.

AppID: gardenmind-beta

-- 
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/-/N6svmFVbzjgJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline exceeded during warm-up

[JH]

I used to get these when running Master/Slave, since moving to HRD I
haven't gotten them.

I know that the datastore should not affect startup but some people
have suggested that HRD apps are hosted in another environment.  I
don't know if this is true or not but I know I haven't had this issue
since migrating.

On Jul 1, 11:15 am, Bert robertbcur...@gmail.com wrote:
 Hi,

 Is anyone else experiencing deadline exceeded errors on warm up? Its
 been happening for the last hour or so on my app.
 My app is running on master-slave datastore. System status says
 everything is fine, so perhaps its just me!
 On the last instance that just started, the latency was 9 seconds. On
 subsequent requests it dropped to 11ms.
 Instance...
 1 total 0.050    9033.0 ms       28.4 MBytes

 Thanks
 Rob

-- 
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-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline exceeded during warm-up

[Bert]

Thanks,

Looking to move soon, just haven't taken the step yet.

Thanks
Rob

On Jul 1, 8:35 pm, JH ja...@mhztech.com wrote:
 I used to get these when running Master/Slave, since moving to HRD I
 haven't gotten them.

 I know that the datastore should not affect startup but some people
 have suggested that HRD apps are hosted in another environment.  I
 don't know if this is true or not but I know I haven't had this issue
 since migrating.

 On Jul 1, 11:15 am, Bert robertbcur...@gmail.com wrote:







  Hi,

  Is anyone else experiencing deadline exceeded errors on warm up? Its
  been happening for the last hour or so on my app.
  My app is running on master-slave datastore. System status says
  everything is fine, so perhaps its just me!
  On the last instance that just started, the latency was 9 seconds. On
  subsequent requests it dropped to 11ms.
  Instance...
  1 total 0.050    9033.0 ms       28.4 MBytes

  Thanks
  Rob

-- 
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-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline exceeded during warm-up

[todu]

I am seeing a surprising slow response recently and this is with multiple 
instances showing running in administration dashboard.  

Something has changed in the back-end  hopefully not a permanent thing else 
my app will become un-usable.

  

-- 
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/-/2kSR5ES99oEJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline Exceeded Errors

[Dan]

The problem cleared up at 08:45:00 then started recurring at 11:00:00
and is continuing now at 11:48:00.

Anyone else seeing this problem?

Dan

On May 9, 11:31 am, Dan dan.c.hoo...@gmail.com wrote:
 Anyone else start experiencing Deadline Exceeded Errors around
 2011-05-09 08:12:00?  My application mind-well started around that
 time and is still failing around 08:30:00.

 Dan

-- 
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-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline Exceeded Errors

[Francois Masurel]

I'm getting quite a lot of 500 errors on traffic increase since the last 
update.

Check this 
: https://groups.google.com/d/topic/google-appengine/2PuwNpACBus/discussion

It might be related.

Francois

-- 
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-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline errors better today, Wed Nov 3rd, but still happening

[Sean Lynch (Google)]

What is your Application ID?

-- 
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...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline errors better today, Wed Nov 3rd, but still happening

[Kenneth]

Alad dinScho ols

On Nov 3, 4:29 pm, Sean Lynch (Google) sly...@google.com wrote:
 What is your Application ID?

-- 
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...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline?

[Mike Wesner]

The ones that fail right at 10 seconds are usually due to the
simultaneous dynamic request limit.

Do the logs show this?

Request was aborted after waiting too long to attempt to service your
request because you have reached your simultaneous dynamic request
limit. This is almost always due to excessively high latency in your
app. Please see http://code.google.com/appengine/kb/general.html#activerequests
for more details.



-mike

On Jun 7, 2:20 pm, Patrick Twohig patr...@namazustudios.com wrote:
 I was under the impression that the deadline for requests was 30 seconds,
 but my app is routinely throwing deadline exceptions after 10 seconds or so.
  Is there a reason for this?

 --
 Patrick H. Twohig.

 Namazu Studios
 P.O. Box 34161
 San Diego, CA 92163-4161

-- 
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...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Deadline?

[Patrick Twohig]

Ah, that would make sense.

On Mon, Jun 7, 2010 at 1:17 PM, Mike Wesner mike.wes...@webfilings.comwrote:

 The ones that fail right at 10 seconds are usually due to the
 simultaneous dynamic request limit.

 Do the logs show this?

 Request was aborted after waiting too long to attempt to service your
 request because you have reached your simultaneous dynamic request
 limit. This is almost always due to excessively high latency in your
 app. Please see
 http://code.google.com/appengine/kb/general.html#activerequests
 for more details.



 -mike

 On Jun 7, 2:20 pm, Patrick Twohig patr...@namazustudios.com wrote:
  I was under the impression that the deadline for requests was 30 seconds,
  but my app is routinely throwing deadline exceptions after 10 seconds or
 so.
   Is there a reason for this?
 
  --
  Patrick H. Twohig.
 
  Namazu Studios
  P.O. Box 34161
  San Diego, CA 92163-4161

 --
 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...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.




-- 
Patrick H. Twohig.

Namazu Studios
P.O. Box 34161
San Diego, CA 92163-4161

Office: 619.862.2890 x100
Cell: 619.453.5075
Twitter: @svm_invictvs
IRC: svm_invic...@irc.freenode.net ##java, #android-dev, #iphonedev,
#appengine

http://www.namazustudios.com/

This communication, and any attachments, shall be considered confidential
and proprietary information of Namazu Studios LLC.  This message, and
attachments, are intended for the listed recipients only.  If you are not
one of the intended recipients, please destroy all copies of this
communication.

-- 
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...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Deadline Exceeded, but not in my app code?

[Marzia Niccolai]

Hi,

This same message is discussed in this thread:
http://groups.google.com/group/google-appengine/browse_thread/thread/fc589cb2247c2806/4c8ec6aacc80873b

It's basically the warm up cost of loading a non-standard Django
edition.  Brett C. seems to have had with trimming the Django Zip file
and using 1.0.2.

-Marzia

On Mon, Jan 19, 2009 at 7:34 PM, tauz...@gmail.com tauz...@gmail.com wrote:

 I'm seeing this error message:

 class 'google.appengine.runtime.DeadlineExceededError':
 Traceback (most recent call last):
  File /base/data/home/apps/minitracker/4.3/main.py, line 29, in
 module
InstallAppengineHelperForDjango()
  File /base/data/home/apps/minitracker/4.3/appengine_django/
 __init__.py, line 329, in InstallAppengineHelperForDjango
PatchDjangoSerializationModules()
  File /base/data/home/apps/minitracker/4.3/appengine_django/
 __init__.py, line 165, in PatchDjangoSerializationModules
from appengine_django.serializer.python import Deserializer
  File /base/data/home/apps/minitracker/4.3/appengine_django/
 serializer/python.py, line 35, in module
from django.utils.encoding import smart_unicode
 class 'google.appengine.runtime.DeadlineExceededError':

 It appears that the deadline exceeded error is happening during an
 import of some sort, but not in the application code that I wrote.

 Any ideas?

 -Dave
 


--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---

[google-appengine] Re: DEADLINE Exceeded Messages ?!

[Brett C.]

Sticking with a svn copy of google-app-engine-django and moving over
to a zip file of Django 1.0.2 with stuff removed as specified by the
App Engine article (http://code.google.com/appengine/articles/
django10_zipimport.html) and what app-engine-patch suggested (http://
code.google.com/p/app-engine-patch/wiki/ManualInstallation) worked for
me.

On Dec 29, 12:21 pm, Brett C. bcan...@gmail.com wrote:
 On Dec 19, 12:02 pm, Marzia Niccolai ma...@google.com wrote:

  Hi,

  Most all of the DeadlineExceededErrors seem to be coming from the module
  loading of InstallAppEngineHelperForDjango().

  I'm not intimately familiar with what could be causing the loading of this
  module to always timeout, but perhaps another user has some valuable
  insight?  The only advice I can give is that if you can trim down the number
  of imports being done on these requests you'll probably stop seeing this
  error.

 It's from the loading of google-app-engine-django. I have been getting
 this as well for my project as the loading of the helper also leads to
 the importing of a lot of django code. In my situation I am using a
 fresh checkout of the helper and Django 1.0.2 directly from source in
 my app's directory. I am going to try to see if using a zip file helps
 at all.

 If not it will either require using Django 0.96 as included in the
 SDK, switching to app-engine-patch if it can work under the deadline
 limit, or simply not using any of the Django helper projects.

 -Brett
--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---

[google-appengine] Re: DEADLINE Exceeded Messages ?!

[Tzakie]

I'm not entirely sure that app engine hasn't occasionally been
throwing a time out here on even on the most simplistic queries. I
can't be sure as I can't see the timing data in the log. I think got a
couple the other day even though it's the same call that's worked
thousands of times. E.G.:

DataRows = db.GqlQuery(SELECT * FROM Table WHERE R=%i AND X='%s' AND
Y=%i AND Z=%i % (a,b,c,d))

Now I'm going to convert this to a key lookup, but I can't see how
something like this should time out.

Some ideas to help us out:
1)
The log viewer now scrolls off the screen so that if the url is a 'log
get query' you can't see the timeout data on the log. Since it's on
the end. Can you move the timing to the start of the line?
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.4) Gecko/
2008102920 Firefox/3.0.4
2)
DeadlineExceededError. Can we break this down into specific errors of
each type of timeout? Also can the error that comes back spit out
profiling data to the console. E.G. a specific count for each of the
deadline counts we are up against the current value and the total
available?


--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---

[google-appengine] Re: DEADLINE Exceeded Messages ?!

[Marzia Niccolai]

Hi,

Most all of the DeadlineExceededErrors seem to be coming from the module
loading of InstallAppEngineHelperForDjango().

I'm not intimately familiar with what could be causing the loading of this
module to always timeout, but perhaps another user has some valuable
insight?  The only advice I can give is that if you can trim down the number
of imports being done on these requests you'll probably stop seeing this
error.

-Marzia

On Fri, Dec 19, 2008 at 12:36 AM, Derrick derrickrbu...@gmail.com wrote:


 I continue to be plagued by deadline exceeded messages, even when
 requesting a jpg file from within a zip file.  I find it hard to
 believe that the individual request is responsible for the deadline
 exceeded.  What circumstances could cause this error?

 #

   1.
  12-18 03:35PM 36.823 /Photos/P200512048/2277/Benchmark315br.jpg/
 500 8769ms 23782ms-cpu 1kb
  See details

  76.14.31.214 - derrickrburns [18/Dec/2008:15:35:45 -0800] GET /
 Photos/P200512048/2277/Benchmark315br.jpg/ HTTP/1.1 500 1323 http://
 vhac.appspot.com/search?location=angel+fire%2C
 +nmbedrooms=bathrooms=http://vhac.appspot.com/search?location=angel+fire%2C+nmbedrooms=bathrooms=
 -

   2.
  E 12-18 03:35PM 45.589

  class 'google.appengine.runtime.DeadlineExceededError':
  Traceback (most recent call last):
File /base/data/home/apps/vhac/1.330078475388282125/main.py,
 line 29, in module
  InstallAppengineHelperForDjango()
File /base/data/home/apps/vhac/1.330078475388282125/
 appengine_django/__init__.py, line 373, in
 InstallAppengineHelperForDjango
  InstallAuthentication()
File /base/data/home/apps/vhac/1.330078475388282125/
 appengine_django/__init__.py, line 393, in InstallAuthentication
  from appengine_django.auth import models as helper_models
File /base/data/home/apps/vhac/1.330078475388282125/
 appengine_django/auth/__init__.py, line 24, in module
  from django.template import Node
File /base/data/home/apps/vhac/1.330078475388282125/django/
 template/__init__.py, line 51, in module
  import re
File /base/python_dist/lib/python2.5/py_zipimport.py, line
 104, in __init__
  if not os.path.isfile(archive):
File /base/python_dist/lib/python2.5/posixpath.py, line 208,
 in isfile
  st = os.stat(path)


 


--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---

[google-appengine] Re: DEADLINE Exceeded Messages ?!

[Marzia Niccolai]

Hi Derrick,

What DeadlineExceedError message are you getting, there are a few different
deadlines you can run in to with App Engine.

The most common would be the request deadline.  Any given request with App
Engine must be completed within 10 seconds.  This is the runtime
DeadlineExceededError

Various APIs, like the datastore and URLFetch also have deadlines to ensure
that those calls return within the overall request deadline. If you are
running in to this deadline, you will get the
apiproxy_errors.DeadlineExceededError.

The problem shouldn't have anything to do with indexing, since simple
queries indexes are automatically generated, there is no need specify them
in the index.yaml (see this article:
http://code.google.com/appengine/articles/index_building.html)

From your description I can imagine the problem is either you are requesting
too much information from the datastore (running in to
apiproxy_errors.DeadlineExceededError) in one request.  The amount of data
you can return in a query will depend on the size and shape of your data,
but you can test this by reducing the amount of data you query for in one
call.

The other issue I can see is that you are just taking too long to return the
entire request.  This probably happens because it takes too long to process
all of your results before the request deadline.

Generally in such a case we'd suggest profiling your application which will
indicate on which calls, and for how long, your app spends it's time.  Some
good information on profiling can be found in our FAQ:
http://code.google.com/appengine/kb/commontasks.html#profiling
Screencast:
Optimizing Your App: Profiling and Memcache
http://www.youtube.com/watch?v=Zip1G6-NiMM
And the Google I/O talk 'Building a Production Quality Application on Google
App Engine:
http://sites.google.com/site/io/best-practices---building-a-production-quality-application-on-google-app-engine

-Marzia

On Thu, Dec 18, 2008 at 10:39 AM, Derrick derrickrbu...@gmail.com wrote:


 I am consistently getting Deadline exceeded messages.  The problem is
 that my individual requests are trivial: do a query or two to
 BigTable, serialize the results, and return them.

 So, what could be causing these messages.  How are deadlines actually
 measured on app engine?

 In my case, I am sending a number (10-50) of requests in parallel.
 Each individual request retrieves a single row in a table plus one or
 two rows in related tables.

 I would guess that that CPU time usage is measured by interrupting the
 thread serving a request at regular intervals.   The question is, how
 does this interrupt ascertain whether a CPU deadline has been
 exceeded.

 I hypothesize that when the poller wakes up, it checks to see which
 application has the cpu, and adds a tick to the count for that user.
 If the same application is using the CPU as the previous  time the
 poller awoke, then the poller checks to see if the tick count exceeds
 the deadline. If so, it initiates a deadline exceeded message and
 terminates the request.

 If this is the algorithm, then it is very problematic for me. Will
 someone from the Google App Engine team explain to us the workings of
 the Deadline measuring algorithm so that we can adjust our application
 for work on the platform.

 Also, could the problem have anything to do with indexing?  Our
 queries are dirt simple: a single query parameter, so we do not
 generate indices for them manually.
 


--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---

[google-appengine] Re: DEADLINE Exceeded Messages ?!

[Derrick]

I am getting class 'google.appengine.runtime.DeadlineExceededError'

On Dec 18, 12:12 pm, Marzia Niccolai ma...@google.com wrote:
 Hi Derrick,

 What DeadlineExceedError message are you getting, there are a few different
 deadlines you can run in to with App Engine.

 The most common would be the request deadline.  Any given request with App
 Engine must be completed within 10 seconds.  This is the runtime
 DeadlineExceededError

 Various APIs, like the datastore and URLFetch also have deadlines to ensure
 that those calls return within the overall request deadline. If you are
 running in to this deadline, you will get the
 apiproxy_errors.DeadlineExceededError.

 The problem shouldn't have anything to do with indexing, since simple
 queries indexes are automatically generated, there is no need specify them
 in the index.yaml (see this 
 article:http://code.google.com/appengine/articles/index_building.html)

 From your description I can imagine the problem is either you are requesting
 too much information from the datastore (running in to
 apiproxy_errors.DeadlineExceededError) in one request.  The amount of data
 you can return in a query will depend on the size and shape of your data,
 but you can test this by reducing the amount of data you query for in one
 call.

 The other issue I can see is that you are just taking too long to return the
 entire request.  This probably happens because it takes too long to process
 all of your results before the request deadline.

 Generally in such a case we'd suggest profiling your application which will
 indicate on which calls, and for how long, your app spends it's time.  Some
 good information on profiling can be found in our 
 FAQ:http://code.google.com/appengine/kb/commontasks.html#profiling
 Screencast:
 Optimizing Your App: Profiling and 
 Memcachehttp://www.youtube.com/watch?v=Zip1G6-NiMM
 And the Google I/O talk 'Building a Production Quality Application on Google
 App 
 Engine:http://sites.google.com/site/io/best-practices---building-a-productio...

 -Marzia

 On Thu, Dec 18, 2008 at 10:39 AM, Derrick derrickrbu...@gmail.com wrote:

  I am consistently getting Deadline exceeded messages.  The problem is
  that my individual requests are trivial: do a query or two to
  BigTable, serialize the results, and return them.

  So, what could be causing these messages.  How are deadlines actually
  measured on app engine?

  In my case, I am sending a number (10-50) of requests in parallel.
  Each individual request retrieves a single row in a table plus one or
  two rows in related tables.

  I would guess that that CPU time usage is measured by interrupting the
  thread serving a request at regular intervals.   The question is, how
  does this interrupt ascertain whether a CPU deadline has been
  exceeded.

  I hypothesize that when the poller wakes up, it checks to see which
  application has the cpu, and adds a tick to the count for that user.
  If the same application is using the CPU as the previous  time the
  poller awoke, then the poller checks to see if the tick count exceeds
  the deadline. If so, it initiates a deadline exceeded message and
  terminates the request.

  If this is the algorithm, then it is very problematic for me. Will
  someone from the Google App Engine team explain to us the workings of
  the Deadline measuring algorithm so that we can adjust our application
  for work on the platform.

  Also, could the problem have anything to do with indexing?  Our
  queries are dirt simple: a single query parameter, so we do not
  generate indices for them manually.
--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---

[google-appengine] Re: DEADLINE Exceeded Messages ?!

[Derrick]

Here is what I get from the profile of a query that does not exceed
the deadline, but comes close:

ncalls  tottime  percall  cumtime  percall filename:lineno(function)
15/130.2990.0201.0180.078 {__import__}
   160.2170.0140.2350.015
{google3.apphosting.runtime._apphosting_runtime___python__apiproxy.Wait}

Does this mean that I am making 16 datastore requests and that I need
to cut down on the number of such requests?

On Dec 18, 1:13 pm, Marzia Niccolai ma...@google.com wrote:
 This means your app is taking more than 10 seconds to respond to a request.
 Try processing less data per request, or work on streamlining the way that
 you process the data during a request.

 -Marzia

 On Thu, Dec 18, 2008 at 12:48 PM, Derrick derrickrbu...@gmail.com wrote:

  I am getting class 'google.appengine.runtime.DeadlineExceededError'

  On Dec 18, 12:12 pm, Marzia Niccolai ma...@google.com wrote:
   Hi Derrick,

   What DeadlineExceedError message are you getting, there are a few
  different
   deadlines you can run in to with App Engine.

   The most common would be the request deadline.  Any given request with
  App
   Engine must be completed within 10 seconds.  This is the runtime
   DeadlineExceededError

   Various APIs, like the datastore and URLFetch also have deadlines to
  ensure
   that those calls return within the overall request deadline. If you are
   running in to this deadline, you will get the
   apiproxy_errors.DeadlineExceededError.

   The problem shouldn't have anything to do with indexing, since simple
   queries indexes are automatically generated, there is no need specify
  them
   in the index.yaml (see this article:
 http://code.google.com/appengine/articles/index_building.html)

   From your description I can imagine the problem is either you are
  requesting
   too much information from the datastore (running in to
   apiproxy_errors.DeadlineExceededError) in one request.  The amount of
  data
   you can return in a query will depend on the size and shape of your data,
   but you can test this by reducing the amount of data you query for in one
   call.

   The other issue I can see is that you are just taking too long to return
  the
   entire request.  This probably happens because it takes too long to
  process
   all of your results before the request deadline.

   Generally in such a case we'd suggest profiling your application which
  will
   indicate on which calls, and for how long, your app spends it's time.
   Some
   good information on profiling can be found in our FAQ:
 http://code.google.com/appengine/kb/commontasks.html#profiling
   Screencast:
   Optimizing Your App: Profiling and Memcachehttp://
 www.youtube.com/watch?v=Zip1G6-NiMM
   And the Google I/O talk 'Building a Production Quality Application on
  Google
   App Engine:
 http://sites.google.com/site/io/best-practices---building-a-productio...

   -Marzia

   On Thu, Dec 18, 2008 at 10:39 AM, Derrick derrickrbu...@gmail.com
  wrote:

I am consistently getting Deadline exceeded messages.  The problem is
that my individual requests are trivial: do a query or two to
BigTable, serialize the results, and return them.

So, what could be causing these messages.  How are deadlines actually
measured on app engine?

In my case, I am sending a number (10-50) of requests in parallel.
Each individual request retrieves a single row in a table plus one or
two rows in related tables.

I would guess that that CPU time usage is measured by interrupting the
thread serving a request at regular intervals.   The question is, how
does this interrupt ascertain whether a CPU deadline has been
exceeded.

I hypothesize that when the poller wakes up, it checks to see which
application has the cpu, and adds a tick to the count for that user.
If the same application is using the CPU as the previous  time the
poller awoke, then the poller checks to see if the tick count exceeds
the deadline. If so, it initiates a deadline exceeded message and
terminates the request.

If this is the algorithm, then it is very problematic for me. Will
someone from the Google App Engine team explain to us the workings of
the Deadline measuring algorithm so that we can adjust our application
for work on the platform.

Also, could the problem have anything to do with indexing?  Our
queries are dirt simple: a single query parameter, so we do not
generate indices for them manually.
--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en

[google-appengine] Re: DEADLINE Exceeded Messages ?!

[Marzia Niccolai]

Hi,

Seems like you are also doing some heavy module importing.  You could be
able to trim that down as well.

-Marzia

On Thu, Dec 18, 2008 at 1:57 PM, Derrick derrickrbu...@gmail.com wrote:


 Here is what I get from the profile of a query that does not exceed
 the deadline, but comes close:

 ncalls  tottime  percall  cumtime  percall filename:lineno(function)
15/130.2990.0201.0180.078 {__import__}
   160.2170.0140.2350.015
 {google3.apphosting.runtime._apphosting_runtime___python__apiproxy.Wait}

 Does this mean that I am making 16 datastore requests and that I need
 to cut down on the number of such requests?

 On Dec 18, 1:13 pm, Marzia Niccolai ma...@google.com wrote:
  This means your app is taking more than 10 seconds to respond to a
 request.
  Try processing less data per request, or work on streamlining the way
 that
  you process the data during a request.
 
  -Marzia
 
  On Thu, Dec 18, 2008 at 12:48 PM, Derrick derrickrbu...@gmail.com
 wrote:
 
   I am getting class 'google.appengine.runtime.DeadlineExceededError'
 
   On Dec 18, 12:12 pm, Marzia Niccolai ma...@google.com wrote:
Hi Derrick,
 
What DeadlineExceedError message are you getting, there are a few
   different
deadlines you can run in to with App Engine.
 
The most common would be the request deadline.  Any given request
 with
   App
Engine must be completed within 10 seconds.  This is the runtime
DeadlineExceededError
 
Various APIs, like the datastore and URLFetch also have deadlines to
   ensure
that those calls return within the overall request deadline. If you
 are
running in to this deadline, you will get the
apiproxy_errors.DeadlineExceededError.
 
The problem shouldn't have anything to do with indexing, since simple
queries indexes are automatically generated, there is no need specify
   them
in the index.yaml (see this article:
  http://code.google.com/appengine/articles/index_building.html)
 
From your description I can imagine the problem is either you are
   requesting
too much information from the datastore (running in to
apiproxy_errors.DeadlineExceededError) in one request.  The amount of
   data
you can return in a query will depend on the size and shape of your
 data,
but you can test this by reducing the amount of data you query for in
 one
call.
 
The other issue I can see is that you are just taking too long to
 return
   the
entire request.  This probably happens because it takes too long to
   process
all of your results before the request deadline.
 
Generally in such a case we'd suggest profiling your application
 which
   will
indicate on which calls, and for how long, your app spends it's time.
Some
good information on profiling can be found in our FAQ:
  http://code.google.com/appengine/kb/commontasks.html#profiling
Screencast:
Optimizing Your App: Profiling and Memcachehttp://
  www.youtube.com/watch?v=Zip1G6-NiMM
And the Google I/O talk 'Building a Production Quality Application on
   Google
App Engine:
  http://sites.google.com/site/io/best-practices---building-a-productio.
 ..
 
-Marzia
 
On Thu, Dec 18, 2008 at 10:39 AM, Derrick derrickrbu...@gmail.com
   wrote:
 
 I am consistently getting Deadline exceeded messages.  The problem
 is
 that my individual requests are trivial: do a query or two to
 BigTable, serialize the results, and return them.
 
 So, what could be causing these messages.  How are deadlines
 actually
 measured on app engine?
 
 In my case, I am sending a number (10-50) of requests in parallel.
 Each individual request retrieves a single row in a table plus one
 or
 two rows in related tables.
 
 I would guess that that CPU time usage is measured by interrupting
 the
 thread serving a request at regular intervals.   The question is,
 how
 does this interrupt ascertain whether a CPU deadline has been
 exceeded.
 
 I hypothesize that when the poller wakes up, it checks to see which
 application has the cpu, and adds a tick to the count for that
 user.
 If the same application is using the CPU as the previous  time the
 poller awoke, then the poller checks to see if the tick count
 exceeds
 the deadline. If so, it initiates a deadline exceeded message and
 terminates the request.
 
 If this is the algorithm, then it is very problematic for me. Will
 someone from the Google App Engine team explain to us the workings
 of
 the Deadline measuring algorithm so that we can adjust our
 application
 for work on the platform.
 
 Also, could the problem have anything to do with indexing?  Our
 queries are dirt simple: a single query parameter, so we do not
 generate indices for them manually.
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google 

[google-appengine] Re: DEADLINE Exceeded Messages ?!

[Derrick]

Thanks.

On Dec 18, 5:17 pm, Marzia Niccolai ma...@google.com wrote:
 Hi,

 Seems like you are also doing some heavy module importing.  You could be
 able to trim that down as well.

 -Marzia

 On Thu, Dec 18, 2008 at 1:57 PM, Derrick derrickrbu...@gmail.com wrote:

  Here is what I get from the profile of a query that does not exceed
  the deadline, but comes close:

  ncalls  tottime  percall  cumtime  percall filename:lineno(function)
     15/13    0.299    0.020    1.018    0.078 {__import__}
        16    0.217    0.014    0.235    0.015
  {google3.apphosting.runtime._apphosting_runtime___python__apiproxy.Wait}

  Does this mean that I am making 16 datastore requests and that I need
  to cut down on the number of such requests?

  On Dec 18, 1:13 pm, Marzia Niccolai ma...@google.com wrote:
   This means your app is taking more than 10 seconds to respond to a
  request.
   Try processing less data per request, or work on streamlining the way
  that
   you process the data during a request.

   -Marzia

   On Thu, Dec 18, 2008 at 12:48 PM, Derrick derrickrbu...@gmail.com
  wrote:

I am getting class 'google.appengine.runtime.DeadlineExceededError'

On Dec 18, 12:12 pm, Marzia Niccolai ma...@google.com wrote:
 Hi Derrick,

 What DeadlineExceedError message are you getting, there are a few
different
 deadlines you can run in to with App Engine.

 The most common would be the request deadline.  Any given request
  with
App
 Engine must be completed within 10 seconds.  This is the runtime
 DeadlineExceededError

 Various APIs, like the datastore and URLFetch also have deadlines to
ensure
 that those calls return within the overall request deadline. If you
  are
 running in to this deadline, you will get the
 apiproxy_errors.DeadlineExceededError.

 The problem shouldn't have anything to do with indexing, since simple
 queries indexes are automatically generated, there is no need specify
them
 in the index.yaml (see this article:
   http://code.google.com/appengine/articles/index_building.html)

 From your description I can imagine the problem is either you are
requesting
 too much information from the datastore (running in to
 apiproxy_errors.DeadlineExceededError) in one request.  The amount of
data
 you can return in a query will depend on the size and shape of your
  data,
 but you can test this by reducing the amount of data you query for in
  one
 call.

 The other issue I can see is that you are just taking too long to
  return
the
 entire request.  This probably happens because it takes too long to
process
 all of your results before the request deadline.

 Generally in such a case we'd suggest profiling your application
  which
will
 indicate on which calls, and for how long, your app spends it's time.
 Some
 good information on profiling can be found in our FAQ:
   http://code.google.com/appengine/kb/commontasks.html#profiling
 Screencast:
 Optimizing Your App: Profiling and Memcachehttp://
   www.youtube.com/watch?v=Zip1G6-NiMM
 And the Google I/O talk 'Building a Production Quality Application on
Google
 App Engine:
   http://sites.google.com/site/io/best-practices---building-a-productio.
  ..

 -Marzia

 On Thu, Dec 18, 2008 at 10:39 AM, Derrick derrickrbu...@gmail.com
wrote:

  I am consistently getting Deadline exceeded messages.  The problem
  is
  that my individual requests are trivial: do a query or two to
  BigTable, serialize the results, and return them.

  So, what could be causing these messages.  How are deadlines
  actually
  measured on app engine?

  In my case, I am sending a number (10-50) of requests in parallel.
  Each individual request retrieves a single row in a table plus one
  or
  two rows in related tables.

  I would guess that that CPU time usage is measured by interrupting
  the
  thread serving a request at regular intervals.   The question is,
  how
  does this interrupt ascertain whether a CPU deadline has been
  exceeded.

  I hypothesize that when the poller wakes up, it checks to see which
  application has the cpu, and adds a tick to the count for that
  user.
  If the same application is using the CPU as the previous  time the
  poller awoke, then the poller checks to see if the tick count
  exceeds
  the deadline. If so, it initiates a deadline exceeded message and
  terminates the request.

  If this is the algorithm, then it is very problematic for me. Will
  someone from the Google App Engine team explain to us the workings
  of
  the Deadline measuring algorithm so that we can adjust our
  application
  for work on the platform.

  Also, could the problem have anything to do with indexing?  Our
  queries are dirt simple: a single query parameter, so we do not
  generate indices 

[google-appengine] Re: deadline exceeded errors

[Y]

Any update on this?

I'm getting theres errors right now (Nov 10, 2008 at 6:45am EST)

On Nov 9, 12:43 pm, Marzia Niccolai [EMAIL PROTECTED] wrote:
 Hi Joey,

 Our engineering team is currently looking in to these issues, we'll post
 more information to the downtime-notify group when it is available.

 -Marzia



 On Sun, Nov 9, 2008 at 9:30 AM, jhurstus [EMAIL PROTECTED] wrote:

  This morning my application has been receiving deadline exceeded
  errors for many requests, including some that usually take very
  little time to process.  My code has not been updated recently, so I
  suspect this is an environmental issue.

  Also, the app engine dashboard is currently down (Application
  statistics are currently unavailable.).  Anybody experiencing similar
  problems?

  -Joey- Hide quoted text -

 - Show quoted text -
--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
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
-~--~~~~--~~--~--~---

[google-appengine] Re: deadline exceeded errors

[Y]

Just to be more specific, I am getting these errors when sending
email.

On Nov 10, 6:46 am, Y [EMAIL PROTECTED] wrote:
 Any update on this?

 I'm getting theres errors right now (Nov 10, 2008 at 6:45am EST)

 On Nov 9, 12:43 pm, Marzia Niccolai [EMAIL PROTECTED] wrote:



  Hi Joey,

  Our engineering team is currently looking in to these issues, we'll post
  more information to the downtime-notify group when it is available.

  -Marzia

  On Sun, Nov 9, 2008 at 9:30 AM, jhurstus [EMAIL PROTECTED] wrote:

   This morning my application has been receiving deadline exceeded
   errors for many requests, including some that usually take very
   little time to process.  My code has not been updated recently, so I
   suspect this is an environmental issue.

   Also, the app engine dashboard is currently down (Application
   statistics are currently unavailable.).  Anybody experiencing similar
   problems?

   -Joey- Hide quoted text -

  - Show quoted text -- Hide quoted text -

 - Show quoted text -
--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
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
-~--~~~~--~~--~--~---

[google-appengine] Re: deadline exceeded errors

[Marzia Niccolai]

Hi Joey,

Our engineering team is currently looking in to these issues, we'll post
more information to the downtime-notify group when it is available.

-Marzia

On Sun, Nov 9, 2008 at 9:30 AM, jhurstus [EMAIL PROTECTED] wrote:


 This morning my application has been receiving deadline exceeded
 errors for many requests, including some that usually take very
 little time to process.  My code has not been updated recently, so I
 suspect this is an environmental issue.

 Also, the app engine dashboard is currently down (Application
 statistics are currently unavailable.).  Anybody experiencing similar
 problems?

 -Joey

 


--~--~-~--~~~---~--~~
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-appengine@googlegroups.com
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
-~--~~~~--~~--~--~---