It seems that there is some problematic proxy server involved in puredata.info and it pretty regularly freaks out, bringing puredata.info down with it for extended periods of time. Since I can now ssh to that server,I can see that its running fine when the proxy server freaks out. I was wondering:
1) whether this is a known issue 2) whether there is anything any of us can do to help resolve it
Here's what I'm seeing right now:
Proxy Error
The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /downloads/pd-extended/0.43.4.
Reason: Error reading from remote server
Apache/2.2.9 (Debian) DAV/2 SVN/1.5.1 PHP/4.4.4-8+etch6 mod_ssl/2.2.9 OpenSSL/0.9.8o mod_perl/2.0.4 Perl/v5.10.0 Server at puredata.info Port 80
.hc
On 01/31/2013 10:00 PM, Hans-Christoph Steiner wrote:
It seems that there is some problematic proxy server involved in puredata.info and it pretty regularly freaks out, bringing puredata.info down with it for extended periods of time. Since I can now ssh to that server,I can see that its running fine when the proxy server freaks out. I was wondering:
there is no "problematic proxy" involved iirc. the setup is: client -> [ apache2(http/https) -> plone ] with the services in brackets being run on pd.i. indeed apache2 is a proxy for plone (which runs an http service), in order to be able to support virtual hosts, https and proper rooting of the virtual filesystem.
restarting the plone instance usually helps.
fgmasdr IOhannes
On 02/01/2013 03:58 AM, IOhannes zmölnig wrote:
On 01/31/2013 10:00 PM, Hans-Christoph Steiner wrote:
It seems that there is some problematic proxy server involved in puredata.info and it pretty regularly freaks out, bringing puredata.info down with it for extended periods of time. Since I can now ssh to that server,I can see that its running fine when the proxy server freaks out. I was wondering:
there is no "problematic proxy" involved iirc. the setup is: client -> [ apache2(http/https) -> plone ] with the services in brackets being run on pd.i. indeed apache2 is a proxy for plone (which runs an http service), in order to be able to support virtual hosts, https and proper rooting of the virtual filesystem.
restarting the plone instance usually helps.
Ah, ok, so that error means plone crashed? Sounds like we should poke whoever said they'd try a trial upgrade offline. Who was that again?
.hc
-
Hans-Christoph Steiner -
IOhannes zmölnig