[Chilli] CoovaChilli (Connection reset by peer) redir_read(0) failed!
David Bird
david at coova.com
Wed Apr 3 15:29:30 UTC 2013
I'd be interested to know more about your deployment (location, scale,
what solution you replaced, etc).
The errors could likely be processes (like Windows Update, etc) that are
getting caught up in the redirection. Unless you are getting user
experience issues, it may be something to ignore.
David
On Wed, 2013-04-03 at 10:33 +0000, Russell Mike wrote:
> Dear Mr. Steffen,
>
>
> Thanks for you help yesterday and today again, i understand it takes
> time. i will study about it and share the our come.
>
>
> More:
> It is actually brand new centralize implementation of CoovaChilli
> 1.3.0. CoovaChilli is running in ISP data center (Our) serving
> hotspots across the city running in multi-tenancy mode using VLANs to
> that we can serve different landing pages for each customers,
> anyways.
>
>
> We are in process of switching all hotspots to CoovaChilli from a
> existing commercial solution. i have few messages which i do not
> understand nor i am able to find a book of reference so that i can
> correct, only people those have already come across are helping. i
> am grateful for the assistance for community.
>
>
>
>
> i have three kinds of logs, any idea about other two ? i am not asking
> solution, if i can only figure out what coovachilli is trying to tell
> in enough for now.
>
>
>
>
> Apr 3 08:29:31 captive coova-chilli[3979]: redir.c: 2020: 104
> (Connection reset by peer) redir_read(0) failed!
>
> Apr 3 08:29:31 captive coova-chilli[3983]: redir.c: 2020: 104
> (Connection reset by peer) redir_read(0) failed!
>
> Apr 3 08:29:31 captive coova-chilli[4019]: redir.c: 2020: 104
> (Connection reset by peer) redir_read(0) failed!
>
>
> Apr 3 09:43:02 captive coova-chilli[9221]: redir.c: 54: Client
> process timed out: 1
>
> Apr 3 09:43:03 captive coova-chilli[9222]: redir.c: 54: Client
> process timed out: 1
>
> Apr 3 09:43:04 captive coova-chilli[9223]: redir.c: 54: Client
> process timed out:
>
>
> Apr 3 09:44:32 captive coova-chilli[9366]: redir.c: 1992: Too much
> data in http request! -30
>
> Apr 3 09:44:32 captive coova-chilli[9368]: redir.c: 1992: Too much
> data in http request! -111
>
> Apr 3 09:44:32 captive coova-chilli[9365]: redir.c: 1992: Too much
> data in http request! -97
>
>
> Thanks / Regards
> RM --
>
>
>
>
>
>
>
>
>
>
>
>
> On Wed, Apr 3, 2013 at 9:55 AM, Steffen Dettmer
> <steffen.dettmer at nomadrail.com> wrote:
> Hi,
>
> > Apr 3 08:29:31 captive coova-chilli[3979]: redir.c: 2020:
> 104 (Connection reset by peer) redir_read(0) failed!
>
>
> "Connection reset by peer" is often seen when a TCP
> communication partner ("peer") resets an initiated or
> established TCP connection, for example if a TCP packet was
> received, but the peer has no matching socket associated
> (could be caused by change of dynamic IP or closing a socket
> after an error). As a result, a locally invoked TCP receive
> (for example, by read(2), which could be "wrapped" by a
> higher-level reading function) will return -1 and set ERRNO to
> ECONNRESET, which on Linux might equal to 104.
>
> Sometimes it helps to see the RST packets, for example using:
>
> tcpdump -n -v 'tcp[tcpflags] & (tcp-rst) != 0'
>
> or for older versions:
>
> tcpdump -n -v 'tcp[13] & 4 != 0'
>
> (see also http://www.ihtb.org/security/tcpdump-explained.txt)
>
> Regards
> Steffen
>
>
>
> _______________________________________________
> Chilli mailing list
> Chilli at coova.org
> http://lists.coova.org/cgi-bin/mailman/listinfo/chilli
>
>
> _______________________________________________
> Chilli mailing list
> Chilli at coova.org
> http://lists.coova.org/cgi-bin/mailman/listinfo/chilli
--
--
David Bird
http://www.linkedin.com/in/dwbird
https://twitter.com/wlanmac
More information about the Chilli
mailing list