Hi,
Problem still exists...
<snip>
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /users/0000111/.
Reason: Could not connect to remote machine: Operation timed out
</snip>
regards,
Louis
-----Original Message-----
From: pyds-dev-admin@muenster.westfalen.de
[mailto:pyds-dev-admin@muenster.westfalen.de]On Behalf Of Phillip
Pearson
Sent: Tuesday, October 07, 2003 7:14 AM
To: PyDS Developer List (E-Mail); pycs-devel@lists.sourceforge.net;
Rogers Cadenhead
Subject: [Pyds-dev] Heads-up: pycs.net is all screwed up
Hey guys,
This may be affecting some of you -- just wanted to drop you a line to let
you know that there is some weird shit going on with the code running on
pycs.net. I'm getting segfaults inside the MetaKit (database) code on the
server. I suspect that the database is damaged, but I've already rebuilt
it, so I'm stumped for the moment.
I've put in a supervision script to restart the server when it dies, but if
anybody notices anything weird like rankings or comments not working, please
get in touch ASAP so I can take a look. It should be a bit more reliable
from now on -- no mre several hour outages after crashes.
BTW, that means now if you get a 'proxy failure' error when accessing pages
on pycs.net, something has _really_ gone wrong, so please get in touch
straight away! :-)
Cheers,
Phil