Hello,
The core dump problem has been solved in the latest snapshot (2007-03-14).
There was an incorrect error handling of the pcap threads. The sendto problem
remains (by my side, I got Invalid argument errors),
and could be caused by a pcap play call rate limitation.
The discarded messages (Discarding message which can't be mapped to a known
SIPp call) are probably caused by retransmitted messages received after the
call was aborted and deleted on the client side because of a retransmission
timeout.
I also noticed that some retransmitted messages were not correctly handled
(treated as unexpected instead of just being ignored), but I did not
investigate it deeper.
Regards,
Olivier
________________________________
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoyé : lundi 5 mars 2007 15:34
À : Boulkroune, Olivier (Non-HP:Atos Origin); [email protected]
Objet : RE: [Sipp-users] Segmentation fault
Olivier,
Thanks for your reply.
Using SIPp v1.1-PCAP, version 20070228:
UAS: ./sipp -sn uas -rtp_echo -mi 10.0.0.1
UAC: ./sipp -trace_msg -trace_err -sn uac_pcap 10.0.0.1
after some time running on high speed (calls per second), uac crashed with:
--
2007-03-04 19:56:46: send_packets.c: sendto failed with error:
Resource temporarily unavailable.
sipp: There were more errors, see 'uac_pcap_4878_errors.log' file
--
# head uac_pcap_4878_errors.log
sipp: The following events occured:
2007-03-04 19:56:44: send_packets.c: sendto failed with error:
Resource temporarily unavailable.
2007-03-04 19:56:44: send_packets.c: sendto failed with error:
Resource temporarily unavailable.
2007-03-04 19:56:44: send_packets.c: sendto failed with error:
Resource temporarily unavailable.
2007-03-04 19:56:44: send_packets.c: sendto failed with error:
Resource temporarily unavailable.
2007-03-04 19:56:44: send_packets.c: sendto failed with error:
Resource temporarily unavailable.
(all messages are same, time from 19:56:44 to 19:56:47)
--
# wc -l uac_pcap_4878_errors.log
118 uac_pcap_4878_errors.log
--
last messages from uac_pcap_4878_messages.log:
----------------------------------------------- 2007-03-04 19:56:39 UDP message
sent:
BYE sip:[EMAIL PROTECTED]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.6:5060;branch=z9hG4bK-4878-129-9
From: sipp <sip:[EMAIL PROTECTED]:5060>;tag=4878SIPpTag09129
To: sut <sip:[EMAIL PROTECTED]:5060>;tag=5447SIPpTag013047
Call-ID: [EMAIL PROTECTED]
CSeq: 2 BYE
Contact: sip:[EMAIL PROTECTED]:5060
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2007-03-04 19:56:39 UDP message
sent:
BYE sip:[EMAIL PROTECTED]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.6:5060;branch=z9hG4bK-4878-130-9
From: sipp <sip:[EMAIL PROTECTED]:5060>;tag=4878SIPpTag09130
To: sut <sip:[EMAIL PROTECTED]:5060>;tag=5447SIPpTag013048
Call-ID: [EMAIL PROTECTED]
CSeq: 2 BYE
Contact: sip:[EMAIL PROTECTED]:5060
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2007-03-04 19:56:39 UDP message
sent:
BYE sip:[EMAIL PROTECTED]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.6:5060;branch=z9hG4bK-4878-131-9
From: sipp <sip:[EMAIL PROTECTED]:5060>;tag=4878SIPpTag09131
To: sut <sip:[EMAIL PROTECTED]:5060>;tag=5447SIPpTag013049
Call-ID: [EMAIL PROTECTED]
CSeq: 2 BYE
Contact: sip:[EMAIL PROTECTED]:5060
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2007-03-04 19:56:39 UDP message
sent:
BYE sip:[EMAIL PROTECTED]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.6:5060;branch=z9hG4bK-4878-132-9
From: sipp <sip:[EMAIL PROTECTED]:5060>;tag=4878SIPpTag09132
To: sut <sip:[EMAIL PROTECTED]:5060>;tag=5447SIPpTag013050
Call-ID: [EMAIL PROTECTED]
CSeq: 2 BYE
Contact: sip:[EMAIL PROTECTED]:5060
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
Let me know if you need any other info.
Regards,
Kevin
________________________________
From: Boulkroune, Olivier (Non-HP:Atos Origin) [mailto:[EMAIL
PROTECTED]
Sent: Friday, March 02, 2007 5:09 AM
To: [EMAIL PROTECTED]; [email protected]
Subject: [Bulk] RE: [Sipp-users] Segmentation fault
Hello Kevin,
May I ask you to retry with the latest sipp version on both sides, and
give us the -trace_msg and -trace_err logs ?
Regards,
Olivier
________________________________
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de [EMAIL
PROTECTED]
Envoyé : mercredi 14 février 2007 17:50
À : [email protected]
Objet : [Sipp-users] Segmentation fault
In the process of setting up SIPp we came across the following issues:
Setup:
./sipp -sn uac_pcap -i 10.0.0.6 -mp 6000 -trace_err 10.0.0.1
linux (uac) version 1.1rc6
Turion 2x, 512RAM, Debian Linux, 2.4.23 kernel. (runs as root user)
sipp -mi 10.0.0.1 -trace_err -rtp_echo -mp 6000 -sn uas
windows (uas) version 1.1rc8
Athlon, 512RAM, WindowsXP
Errors:
First:
UAS (Win) reports error: Error on RTP echo reception - stopping echo -
errno= 4" (sometimes errno=104 and doesn't echo RTP. but it works (accepts
calls, and uac is sending RTP)
However, after error uas continues to work.
Always shows 4 RTP packets received in all tests. (doesn't increase
after 4)
Then:
RTP rate reported on UAC is about 5MB per sec, but after some time
UAC crashes with error message: Aborting call on UDP retransmission
timeout for Call-ID '[EMAIL PROTECTED]'., then almost immediately UAS
reports "CPU CONGESTED". (Guess is that this can't be the result of
sipp crash on uac since sipp doesn't send anything after it crashes).
sipp: There were more errors, see scenarioname_pid_errors.log file
Segmentation fault (core dumped)
uac_pcap_22018_errors.log contains many records like:
2007-02-14 15:57:20: Discarding message which can't be mapped to a
known SIPp call:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.0.6:5060;branch=z9hG4bK-24545-9
From: sipp <sip:[EMAIL PROTECTED]:5060>;tag=24545
To: sut <sip:[EMAIL PROTECTED]:5060>;tag=4816SIPpTag0124468
Call-ID: [EMAIL PROTECTED]
CSeq: 2 BYE
Contact: <sip:10.101.23.102:5060;transport=UDP>
Content-Length: 0
and at the end of the file:
2007-02-14 15:57:25: send_packets.c: sendto failed with error: 11.
2007-02-14 15:57:25: send_packets.c: sendto failed with error: 11.
2007-02-14 15:57:25: send_packets.c: sendto failed with error: 11.
2007-02-14 15:57:25: send_packets.c: sendto failed with error: 11.
Note:
(Edited send_packets.c to report errno number, not text). This is
"Resource temporarily unavailable".
With sipp recompiled with -ggdb, in debugger see crash at
call.cpp:1184, function call::run, line - scenario[last_send_index] ->
nb_timeout ++; last_send_index = 9, scenario[last_send_index] = NULL.
Thank you for SIPp!
Kevin
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
