Disappointing. Can you please send a traceback for the PKE and any earlier errors that look like they may be related? Out of curiositity, how do you know the POSKeyErrors didn't happen before you switched to the new branch? - C On Wed, 2004-09-15 at 23:39, Richard Jones wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 16 Sep 2004 01:20 pm, Richard Jones wrote:
On Wed, 15 Sep 2004 12:22 pm, Chris McDonough wrote:
I'm afraid I still don't know whether that means you have or haven't seen the errors under the latest 2.7 branch.
Well, that settles it. The errors are alive and kickin' in the 2.7 branch too. Within *moments* of the server going back up, I got the first POSKeyError report.
Make that the first of *many*. I've now backed-out the 2.7 branch and am running 2.7.2 again.
Richard, weeping in the corner
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBSQr0rGisBEHG6TARAuaUAKCF8ve27iBI9+5SBUj52L80/t59ggCcDARE k9aKi/yIeTjBoQSGq9mNRUs= =1H1i -----END PGP SIGNATURE-----