[Spce-user] mr5.5.6 lb process restart to work

[Daniel Grotti]

I wouldn't say so.
Looks like that TCP connection was lost.

-- 
Head of Customer Support                               Sipwise GmbH
e: dgrotti at sipwise.com                               Europaring F15
t: +43(0)130120332                          A-2345 Brunn Am Gebirge
w: www.sipwise.com          FN: 305595f      FG: LG Wiener Neustadt

On 11/28/18 2:10 AM, Abel Alejandro wrote:
> Actually just was able to find this error just before lb stopped working:
>
> Nov 27 12:09:44 sip lb[24610]: ERROR: <core> [tcp_main.c:4078]: handle_tcpconn_ev(): connect <client ip here>:49850 failed
>
> Would an error of this magnitude make lb stop processing new requests?
>
> -----Original Message-----
> From: Abel Alejandro
> Sent: Tuesday, November 27, 2018 1:15 PM
> To: 'Daniel Grotti' <dgrotti at sipwise.com>; spce-user at lists.sipwise.com
> Subject: RE: [Spce-user] mr5.5.6 lb process restart to work
>
> I will keep that command hand in case it happens again but if I do netstat -s, I see a have a non-zero receive buffer errors, could that be the cause?
>
> How do I increase this buffer?
>
> root at sip:/var/log/ngcp# netstat -s
> Ip:
>      Forwarding: 2
>      8713684523 total packets received
>      0 forwarded
>      3 with unknown protocol
>      0 incoming packets discarded
>      8713408544 incoming packets delivered
>      8861358901 requests sent out
>      175 fragments dropped after timeout
>      551437 reassemblies required
>      275461 packets reassembled ok
>      175 packet reassemblies failed
>      251606 fragments received ok
>      503488 fragments created
> Icmp:
>      8759015 ICMP messages received
>      11928 input ICMP message failed
>      InCsumErrors: 771
>      ICMP input histogram:
>          destination unreachable: 7908135
>          timeout in transit: 664457
>          redirects: 3
>          echo requests: 185537
>          echo replies: 47
>          timestamp request: 65
>      3915161 ICMP messages sent
>      0 ICMP messages failed
>      ICMP output histogram:
>          destination unreachable: 3729350
>          time exceeded: 173
>          echo requests: 36
>          echo replies: 185537
>          timestamp replies: 65
> IcmpMsg:
>          InType0: 47
>          InType3: 7908135
>          InType5: 3
>          InType8: 185537
>          InType11: 664457
>          InType13: 65
>          OutType0: 185537
>          OutType3: 3729350
>          OutType8: 36
>          OutType11: 173
>          OutType14: 65
> Tcp:
>      1708271 active connection openings
>      1629365 passive connection openings
>      219358 failed connection attempts
>      444798 connection resets received
>      43 connections established
>      620057081 segments received
>      1326342435 segments sent out
>      638923 segments retransmitted
>      205 bad segments received
>      608205 resets sent
>      InCsumErrors: 203
> Udp:
>      7952039041 packets received
>      143784012 packets to unknown port received
>      446607 packet receive errors
>      8638206706 packets sent
>      439491 receive buffer errors
>      0 send buffer errors
>      InCsumErrors: 7023
>      IgnoredMulti: 189631
>
>
>
> -----Original Message-----
> From: Spce-user <spce-user-bounces at lists.sipwise.com> On Behalf Of Daniel Grotti
> Sent: Tuesday, November 27, 2018 1:00 PM
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] mr5.5.6 lb process restart to work
>
> Hi,
> when this happens, try to run:
>
> netstat -anp | grep 5060
>
>
> do you see the UPD buffer full maybe?
>
> Cheers,
>
>