I have seen this in the past, not just when deploying a new version,
but even redeploying the same version, first few requests always
500'd. But I have noticed it not happening any more.
On Mar 30, 12:03 pm, Simon Knott wrote:
> Ha, I've no idea then :) Whenever I've had a server 500 error, it'
Ha, I've no idea then :) Whenever I've had a server 500 error, it's usually
been my fault and I've been able to see the appropriate logs. Just to
reiterate though, I've been redeploying to the same version for a long time
now (maybe 4-5 months) without any issues.
--
You received this messag
There was an issue where Python instances would fail while importing
modules, and then that instance would be screwed until it got recycled.
This seemed to happen more often around deploying new version. I remember
this being claim-fixed in the release notes of a recent version.
I think your
The sort that say 500. :) When google's servers throw these errors, there is
never any explanation of what the problem is, and they don't show up in the
logs.
On Mar 30, 2011, at 12:07 PM, Simon Knott wrote:
> Hi,
>
> I very rarely update the version number and have never run into server
>
Hi,
I very rarely update the version number and have never run into server
issues, unless I've changed the underlying structure of a serialized object
which is cached in MemCache. What sort of 500 errors were you getting
before?
Cheers,
Simon
--
You received this message because you are sub
