all is working again :)

On 26 nov, 17:18, Marinho Brandão <[EMAIL PROTECTED]> wrote:
> Mine too.
>
> I guess a session function is making requests spend much mcycles.
>
> Since it was'nt being used more, I removed the parts was using it and
> tried to update files into the server, but the following error is
> shown:
>
> 2008-11-26 17:10:44,317 ERROR appcfg.py:1334 An unexpected error
> occurred. Aborting.
> Error 500: --- begin server output ---
>
> Server Error (500)
> A server error has occurred.
> --- end server output ---
>
> Now I don't know what I do, because there is nothing on dashboard nor
> on source files I can do to change this, and my site keeps off :/
>
> On 26 nov, 17:09, ksjun <[EMAIL PROTECTED]> wrote:
>
> > 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 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to