[Serdev] TCP Blocking Connect issue - further analysis

[Andrew Mee]

When the client crashes with an connected TCP connection, it closes the 
UA, SER displays the following in debug mode

19(15002) tcp_main_loop: reader response= 402e1ba0, 0 from 0
19(15002) tcp_main_loop: CONN_RELEASE  0x402e1ba0 refcnt= 0
19(15002) tcp_main_loop: data available on 0x402e1ba0 [h:7] 33
19(15002) send2child: to tcp child 0 11(14986), 0x402e1ba0
11(14986) received n=4 con=0x402e1ba0, fd=20
11(14986) ERROR: tcp_read: error reading: Connection reset by peer
11(14986) ERROR: tcp_read_req: error reading
11(14986) releasing con 0x402e1ba0, state -2, fd=20, id=35
11(14986)  extra_data (nil)
19(15002) tcp_main_loop: reader response= 402e1ba0, -2 from 0
19(15002) tcp_main_loop: destroying connection

Could it be that the tcp_main_loop is not releasing these connections 
properly??? I also find this stops all UA's connected to SER from 
passing on the ACK of an INVITE.... (and possibly other commands)

Perhaps state should be 0 not -2 ???

Andrew Mee

Andrew Mee wrote:

> To fix this problem I have to restart SER.... Which is not what I want
> to have to do obviously :)
> I am using 0.8.14 on Gentoo.... any chance of fixing it?
>
> Andrew
>
> Jiri Kuthan wrote:
>
>> It appears to be an unresponsive TCP server downstream of SER.
>>
>> -jiri
>>
>> At 06:24 AM 8/18/2004, Andrew Mee wrote:
>>  
>>
>>> I get this in SER after the UA (yes the client :) crashes and I 
>>> restart the client (and reboot the machine), then make a new invite...
>>>
>>> 11(3048) check_via_address(192.168.2.11, 192.168.2.11, 0)
>>> 11(3048) Sending:
>>> ACK sip:192.168.2.28:8727;transport=tcp SIP/2.0
>>> Record-Route: 
>>> <sip:test2 at 192.168.2.253;transport=tcp;ftag=d55c81a6d09346408fd6620a72401024;lr=on> 
>>>
>>> Via: SIP/2.0/TCP 192.168.2.253;branch=0;i=76
>>> Via: SIP/2.0/TCP 192.168.2.11:9493
>>> Max-Forwards: 69
>>> From: "James West" 
>>> <sip:support at 192.168.2.253>;tag=d55c81a6d09346408fd6620a72401024;epid=c001967d41 
>>>
>>> To: <sip:test2 at 192.168.2.253>;tag=01587e6c3efb47878b015161a575864b
>>> Call-ID: 9c7f7f9b1b084b0bbf793be7fee2225d at 192.168.2.11
>>> CSeq: 1 ACK
>>> User-Agent: RTC/1.2
>>> Content-Length: 0
>>> .
>>> 11(3048) orig. len=501, new_len=528, proto=2
>>> 11(3048) tcp_send: no open tcp connection found, opening new one
>>> 11(3048) ERROR: tcp_blocking_connect: SO_ERROR (111) Connection refused
>>> 11(3048) ERROR: tcpconn_connect: tcp_blocking_connect failed
>>> 11(3048) ERROR: tcp_send: connect failed
>>> 11(3048) msg_send: ERROR: tcp_send failed
>>> 11(3048) Warning: sl_send_reply: I won't send a reply for ACK!!
>>> 11(3048) ERROR: sl_reply_error used: Unfortunately error on sending 
>>> to next hop occured (477/SL)
>>> 11(3048) DEBUG:destroy_avp_list: destroing list (nil)
>>>
>>> I have yet to find out what is causing this in SER, but I thought 
>>> maybe someone might have some more info.
>>> I will in the meantime keep digging.
>>>
>>> -- 
>>> Andrew Mee
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Serdev mailing list
>>> serdev at lists.iptel.org
>>> http://lists.iptel.org/mailman/listinfo/serdev
>>>   
>>
>>
>> -- 
>> Jiri Kuthan            http://iptel.org/~jiri/
>>  
>>
>
>
>_______________________________________________
>Serdev mailing list
>serdev at lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serdev
>  
>


-- 
Andrew Mee


-------------- next part --------------
A non-text attachment was scrubbed...
Name: andrew.vcf
Type: text/x-vcard
Size: 889 bytes
Desc: not available
Url : http://lists.iptel.org/pipermail/serdev/attachments/20040819/50ce6e5d/andrew.vcf