Hallo Maxim,

raising up the timeout value to 180 seems to fix the problem, no more
strange error messages :)

thanks for your help

Juergen



Maxim Dounin wrote:
> Hello!
>
> On Mon, Aug 17, 2009 at 12:58:03PM +0200, Juergen Gotteswinter wrote:
>
>> Hello,
>>
>> someone could give me a hint what this error messages should mean? e.g.
>> if its something nginx related, client related or backend...
>>
>>
>> 2009/08/17 12:22:48 [error] 22557#0: *1683003 upstream timed out (110:
>> Connection timed out) while reading upstream, client: 82.207.xxxxxx,
>> server: xxx.de, request: "POST /index.php?content= HTTP/1.1", upstream:
>> http://192.168.xxxxx:80/index.php?content=", host: "www.xxxx", referrer:
>> https://www.xxxxde/index.php?content="
>
> It means that nginx wasn't able to read response in time from the
> upstream server in question. Usually it means that backend isn't
> fast enough or overloaded, but depending on usage pattern this may
> also mean that specified timeout values are too low.
>
> For more information see:
>
> http://wiki.nginx.org/NginxHttpProxyModule#proxy_read_timeout
>
> Maxim Dounin
>
>


--
InterNetX GmbH
Maximilianstrasse 6
D-93047 Regensburg

Tel. +49 941 59559-480
Fax +49 941 59559-245

Gesch