re: mod perl + proxy returns Document has no data
Ok it's definitely a problem with the proxy... Set the backend running on its own with httpd -X, run a large (3MB) upload and everything is fine - so no mod_perl/embperl problem... (Thanks Gerald!) Set both the backend and frontend running, both with httpd -X, run the same upload: Frontend appears to accept the upload, but returns a document with no data. Backend bombs out with: [error] CGI.pm: Server closed socket during multipart read (client aborted?) After this, any access to the back-end (directly) returns no data at all and is logged as '200 - ' in the log. This can be repeated consistently, so I guess this is a mod_proxy problem... I have worked around by getting the front-end to run embpcgi.pl as a CGI script for uploads which (so far as I have tested) works fine...
Re: mod perl + proxy returns Document has no data
While I have no specific insight to your problem, you might want to do the following. Grab the latest version of Apache, and use the mod_proxy in that. You also might want to take a look at the patches that are lying around for mod_proxy, theres been a lot of work on it of late, but most of it's waiting around and being implemented in the 2.0 version. Also you may want to put this on the new-httpd list..., that's more so where it should be, and that's where all the other modproxy hackers hang out. In particular Chris Sail, and Graham are two folks that might be able to help you out. Chris is the old mod_proxy maintainer, and Graham has done EXTENSIVE work on mod_proxy. There is also Sam, but he's more involved with the port to 2.0. It sounds like a bug to me with the caching or something like that. (Well, not directly involved with the caching, but auxiliarly involved with the caching) Thanks, Shane. On Fri, May 05, 2000 at 03:24:40PM +0100, lists wrote: I am having a tricky problem with a mod_perl backend and a vanilla proxying front end I have set up: Apache 1.3.9 + Mod_perl 1.23 + Embperl 1.2.1 as a back-end server Apache 1.3.9 + mod_proxy as a front-end server. Occasionally the back-end server gets into a state where it returns empty documents to the front-end, and the front-end then returns a "502 Proxy Error - document has no data" error to the client. The only thing logged by the backend is a 200 result code with "-" for the amount of data transferred. I am at a complete loss as to what is happening - server load is not excessive, and there are plenty of spare servers. The only thing I have noticed is this happens semi-consistently after a *large* file upload (from the client) through the proxy to the back-end server. The upload is handled by EmbPerl. Once the server is in this state, it will continue serving no-data pages at apparently random intervals until it is restarted. Any ideas/pointers would be much appreciated - I am stuck because the back-end is not giving any error messages - just a 200 code... Thanks, Chris Allen [EMAIL PROTECTED]
RE: mod perl + proxy returns Document has no data
Occasionally the back-end server gets into a state where it returns empty documents When this occurs, try to directly connect to the backend, and see if this shows the same behaviour, so we can see if it's a mod_perl/Embperl problem or a mod_proxy problem. Gerald - Gerald Richterecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice:+49 6133 925151 WWW:http://www.ecos.de Fax: +49 6133 925152 -
re: mod perl + proxy returns Document has no data
Ok it's definitely a problem with the proxy... Set the backend running on its own with httpd -X, run a large (3MB) upload and everything is fine - so no mod_perl/embperl problem... (Thanks Gerald!) Set both the backend and frontend running, both with httpd -X, run the same upload: Frontend appears to accept the upload, but returns a document with no data. Backend bombs out with: [error] CGI.pm: Server closed socket during multipart read (client aborted?) After this, any access to the back-end (directly) returns no data at all and is logged as '200 - ' in the log. This can be repeated consistently, so I guess this is a mod_proxy problem... I have worked around by getting the front-end to run embpcgi.pl as a CGI script for uploads which (so far as I have tested) works fine...
