I FOUND IT!!

Like you said, it was in CGI.pm. It happens when doing a file upload

######
    while ($bytesread=read($image_filename_one,$buffer,1024)) {
    print OUTFILE $buffer;
  }
######

If during the upload the user stops, drops or dies then the errors come
through which makes me think now that its not as serious of a error as I
thought (meaning any ill effects I may have thought was a result of that
error message, really isn't).

At very least at least I know what causes it.

Thanks
-Chris



----- Original Message ----- 
From: "Stas Bekman" <[EMAIL PROTECTED]>


>
> You probably use CGI.pm or something else that calls $r->read(). This
happends
> in xs/Apache/RequestIO/Apache__RequestIO.h (hint grep the mod_perl source
code):
>
>                  /*
>                   * XXX: as stated in ap_get_client_block, the real
>                   * error gets lots, so we only know that there was one
>                   */
>                  ap_log_error(APLOG_MARK, APLOG_ERR, 0, r->server,
>                           "mod_perl: $r->read failed to read");
>                  break;
>
> As you can see from the comment due to a bad implementation of
> ap_get_client_block in Apache, the error is not available. I'm planning to
> rewrite all these functions to get rid of ap_get_client_block, and work
with
> bucket brigades instead.
>
> In any case that won't solve the problem that you are seeing, I'd dig in
> Apache. e.g. trying to use mod_cgi (which doesn't use ap_get_client_block)
to
> reproduce the problem and ask at the httpd list.
>
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com
>


> > We have been having some problems where all of a sudden apache will
> > start logging the error of:
> >
> > [error] mod_perl: $r->read failed to read
> >


Reply via email to