Search squid archive

Re: Debuging ERR_CONNECT_FAIL with SYSERR=110

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Feb 12, 2014 at 12:40 PM, Pawel Mojski <pawcio@xxxxxxxxxx> wrote:
> Hi All;
>
> I have pretty loaded squid server working in interception mode.
> In about 0.5% of total http request I have an ERR_CONNECT_FAIL with
> additional error SYSERR=110.
> How can I debug a reason of those errors?
>
> The thing which consider me a lot is the URL and remote server of those
> requests.
> For example, I found three same requests for the same URL hosted on the
> same IP request.
> The first one finished with response 200, the second with 503 and
> ERR_CONNECT_FAIL(SYSERR=110) and the third with 200 again.
>
> Also, my customers complains that sometimes "they have problems surfing
> the web".
>
> What can I do to debug the problem?

Hi Pawel,
     SYSERR 110 on Linux is connection timeout (ETIMEOUT).
It would seem to indicate network issues somewhere, or a severely
overloaded server (which has used all its syn backlog)


-- 
  Kinkie




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux