My application has same problem today.
APP-ID: momonote-api
On 2월8일, 오후7시54분, Filip wrote:
> Hi,
> I have the same problem today. My app is throwing
> ApiDeadlineExceededException for last 10 hours because of
> file.create()! It seems that blobstore service is down because the
> app works wit
At least, I want 'email support'. The only offical support is this
forum.
If I have a problem, I must post it here with some sensitive data.
On Jul 3, 3:05 am, Brian wrote:
> You really need to deal with your uptime problems. My experience has
> been that App Engine is less reliable than some
But how can I modify my code to handle the capability disabled
exceptions?
Now we can't upload updated code to server.
On Jul 3, 2:38 am, "Jeff S (Google)" wrote:
> Hi all,
>
> As many of you have noticed, App Engine has been experiencing elevated
> datastore latency and error rates and we swi
Here comes yet another timeout errors again. It's started before
2hours ago.
My app raises about 300 datastore put errors - timeout or internal
error. And I can't see http://code.google.com/status/appengine . And
dashboard of my apps is broken too.
I'm tired of too many errors of AppEngine - sch
I made app id 'lifography' at App Engine and I added 'lifography' app
domain to my 'momolog.com' Google Apps.
As I transfered 'lifography'-'momolog.com' domain link to 'momolog-
com' app id - 'www.momolog.com', I clicked 'Google Apps for
momolog.com' -> 'lifography' App Engine - Active -> 'Disab
All my indexes are cleaned up now after12 hours deleting or error
status. My commercial live service have been downed 12 hours by this
indexing broken & rebuild.
On Jun 8, 10:23 pm, ksjun wrote:
> After adding some new indexes, my old indexes were broken. So I
> deleted all
After adding some new indexes, my old indexes were broken. So I
deleted all indexes at index.yaml and update them to app engine.
I hope they are gone, but two are 'deleting...' status forever and
other five are 'Error' status. Although I run 'vacuum_indexes' with
empty 'index.yaml', they still be
Yet another datastore timeout.
It seems that system status page is ok but almost my datastore
operations are failed with timeout errors.
My application id is lifography.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gro
I submited this issue at
http://code.google.com/p/googleappengine/issues/detail?id=1472
--~--~-~--~~~---~--~~
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
With following conditions, a connection is closed immediately and 400
error is occured. An application can't receive this request at all.
- The application has a custom domain like http://www.example.com
- A large file over than 1MB is submitted using a form POST.
I tested several A
They said that it will be less than 30 minutes(5 minute target?), but
it's over than 50 minutes and nothing is changed - Datastore writes
are temporarily disabled.
No one at Google say what's going on and when it will finish.
--~--~-~--~~~---~--~~
You received th
http://code.google.com/p/googleappengine/issues/detail?id=1019
On 3월9일, 오후1시55분, yucc wrote:
> As mentioned
> athttp://code.google.com/appengine/docs/python/users/userobjects.html,
> I just can't figure out what's the exactly situation for "While an
> email address is unique to an account at a
Right now every put operations of my application make errors -
'Timeout: datastore timeout: operation took too long.'
What's wrong on the datastore? my application id is 'lifography'
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
I am also. Just single put operation somtimes caused 'datastore
timeout: operation took too long.'
- my application id : lifography
My application doesn't exceed to any quota. (<1%)
One of this error was occured at Nov 26,2008 AM 12:06 (PST).
File "/base/python_lib/versions/1/goo
14 matches
Mail list logo
