You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by "Client Services of New York, LLC" <cl...@gmail.com> on 2006/02/15 14:38:22 UTC

2.06 -> 2.07 Fedora Core 4 Yum upgrade broke something?

Throws an Internal Server now.

And returns

"[Tue Feb 14 21:43:44 2006] [error] [client 24.195.xx.xxx] Conflicting
information"

Any gotchas I'm not seeing in the docs that could be responsible?

Mike



--
Mike Lieman
Client Services of New York, L.L.C.
client.services.ny@gmail.com
518-496-8431

Re: 2.06 -> 2.07 Fedora Core 4 Yum upgrade broke something?

Posted by "Client Services of New York, LLC" <cl...@gmail.com>.
On 2/15/06, Joe Schaefer <jo...@sunstarsys.com> wrote:
>
> Joe Schaefer <jo...@sunstarsys.com> writes:


Thanks, Joe.  I'll take a look at those, and follow up later.

>
>


--
Mike Lieman
Client Services of New York, L.L.C.
client.services.ny@gmail.com

Re: 2.06 -> 2.07 Fedora Core 4 Yum upgrade broke something?

Posted by "Client Services of New York, LLC" <cl...@gmail.com>.
On 2/15/06, Joe Schaefer <jo...@sunstarsys.com> wrote:
>
> Joe Schaefer <jo...@sunstarsys.com> writes:
>
>
> In particular, your POST_MAX argument.  You'll get this error
> if that's larger than 64M.


The web app in question uses:

$session{req} = Apache2::Request->new($r, POST_MAX => 1024 *
$session{setting}{maxAttachmentSize});

With a max AttachmentSize of a meg, that gives me a gig.  And when I do the
math, I get:

POST_MAX =  1024 * 1000000

so that when I add:

APREQ2_ReadLimit 1024M

to the apache config, everything picks up fine.

Is this a "Crazy" number to have there?


--
Mike Lieman
Client Services of New York, L.L.C.
client.services.ny@gmail.com

Re: 2.06 -> 2.07 Fedora Core 4 Yum upgrade broke something?

Posted by Joe Schaefer <jo...@sunstarsys.com>.
Joe Schaefer <jo...@sunstarsys.com> writes:

> "Client Services of New York, LLC" <cl...@gmail.com> writes:
>
>> Throws an Internal Server now.
>>
>> And returns
>>
>> "[Tue Feb 14 21:43:44 2006] [error] [client 24.195.xx.xxx] Conflicting
>> information"
>>
>> Any gotchas I'm not seeing in the docs that could be responsible?
>
> Hm, how are you calling new() (what are the arguments)?

In particular, your POST_MAX argument.  You'll get this error
if that's larger than 64M.

If you need more space than that, use 

   APREQ2_ReadLimit 100M

or somesuch in your server config.

-- 
Joe Schaefer

Re: 2.06 -> 2.07 Fedora Core 4 Yum upgrade broke something?

Posted by Joe Schaefer <jo...@sunstarsys.com>.
"Client Services of New York, LLC" <cl...@gmail.com> writes:

> Throws an Internal Server now.
>
> And returns
>
> "[Tue Feb 14 21:43:44 2006] [error] [client 24.195.xx.xxx] Conflicting
> information"
>
> Any gotchas I'm not seeing in the docs that could be responsible?

Hm, how are you calling new() (what are the arguments)?

-- 
Joe Schaefer