Hi Ellie, Here is the command we are trying to run:
sudo LD_LIBRARY_PATH=usr/lib:$LD_LIBRARY_PATH build/bin/rout -t -s 5054 -H 10.129.34.87:8888 -K 10.120.34.82:7253 -T 10.129.34.82 -c sip: 10.129.34.82:5054 -F /var/log/sprout -l 10.129.34.82 -D ims.hom Here is what we are trying to do. We are actually trying to benchmark our project Clearwater setup. We wrote a bunch of scripts for that. We used manual install method to install all the components. Now we want to change some part of sprouts code notably the algorithm which is managing the load. For this we installed the bleeding edge version of sprout in a VM and are trying to get it connected to our existing system. After adding the -D option we are able to perform tcp connection from bono to sprout. But there it is sending 408 later. Here is the relevant part from Sprouts log: Via: SIP/2.0/UDP 192.168.0.100:5060 ;rport=5060;received=10.3.160.21;branch=z9hG4bK1716268826^M From: <sip:[email protected]>;tag=340082174^M To: <sip:[email protected]>^M Call-ID: 790430480^M CSeq: 1 REGISTER^M Contact: <sip:[email protected]:5060 ;line=b38a6309da072ad>;+sip.instance="<urn:uuid:744a97e0-6c35-11e4-955c-6ddd4f8d4915>"^M Authorization: Digest username="[email protected]", realm="ims.hom", nonce=" ", uri="sip:ims.hom", response=" "^M Max-Forwards: 70^M User-Agent: eXosip/3.3.0^M Expires: 600000^M Supported: path, gruu^M Session-Expires: 600^M Route: <sip:sprout.ims.hom:5054;transport=TCP;lr;orig>^M Content-Length: 0^M ^M --end msg-- 14-11-2014 19:35:59.362 UTC Debug stack.cpp:463: Queuing cloned received message 0x7f540c061258 for worker threads 14-11-2014 19:35:59.362 UTC Debug stack.cpp:202: Worker thread dequeue message 0x7f540c061258 14-11-2014 19:35:59.362 UTC Debug statistic.cpp:103: Send new value for statistic incoming_requests, size 1 14-11-2014 19:35:59.362 UTC Debug zmq_lvc.cpp:167: Update to incoming_requests statistic 14-11-2014 19:35:59.362 UTC Debug zmq_lvc.cpp:250: Clearing message cache for 0x7f542802a060 14-11-2014 19:35:59.363 UTC Debug statistic.cpp:103: Send new value for statistic queue_size, size 5 14-11-2014 19:35:59.363 UTC Debug pjsip: sip_endpoint.c Distributing rdata to modules: Request msg REGISTER/cseq=1 (rdata0x7f540c061258) 14-11-2014 19:35:59.363 UTC Debug stack.cpp:204: Worker thread completed processing message 0x7f540c061258 14-11-2014 19:35:59.363 UTC Debug stack.cpp:210: Request latency = 1607us 14-11-2014 19:35:59.364 UTC Debug zmq_lvc.cpp:167: Update to queue_size statistic 14-11-2014 19:35:59.364 UTC Debug zmq_lvc.cpp:250: Clearing message cache for 0x7f54280333a0 14-11-2014 19:35:59.364 UTC Debug statistic.cpp:103: Send new value for statistic latency_us, size 5 14-11-2014 19:35:59.364 UTC Debug zmq_lvc.cpp:167: Update to latency_us statistic 14-11-2014 19:35:59.364 UTC Debug zmq_lvc.cpp:250: Clearing message cache for 0x7f5428012ff0 Here is the relevant part from bono: REGISTER sip:ims.hom SIP/2.0^M Via: SIP/2.0/TCP 10.129.34.51:38321 ;rport;branch=z9hG4bKPje6zRJ3HtS6-aUAABLjftiPxXRh.WX9fK^M Path: <sip:[email protected]:5058;transport=TCP;lr;ob>^M Via: SIP/2.0/UDP 192.168.0.100:5060 ;rport=5060;received=10.3.160.21;branch=z9hG4bK1806547393^M From: <sip:[email protected]>;tag=1937036704^M To: <sip:[email protected]>^M Call-ID: 761958977^M CSeq: 1 REGISTER^M Contact: <sip:[email protected]:5060 ;line=b38a6309da072ad>;+sip.instance="<urn:uuid:7d143ef4-6c34-11e4-955c-6ddd4f8d4915>"^M Authorization: Digest username="[email protected]", realm="ims.hom", nonce=" ", uri="sip:ims.hom", response=" "^M Max-Forwards: 70^M User-Agent: eXosip/3.3.0^M Expires: 600000^M Supported: path, gruu^M Session-Expires: 600^M Route: <sip:sprout.ims.hom:5054;transport=TCP;lr;orig>^M Content-Length: 0^M ^M --end msg-- 14-11-2014 19:24:31.710 UTC Debug pjsip: tsx0x11ecc78 State changed from Null to Calling, event=TX_MSG 14-11-2014 19:24:31.710 UTC Debug stateful_proxy.cpp:367: tsx0x11ecc78 - tu_on_tsx_state UAC, TSX_STATE TX_MSG state=Calling /user1 14-11-2014 19:24:34.134 UTC Debug pjsip: tsx0x11ecc78 State changed from Calling to Terminated, event=TRANSPORT_ERROR 14-11-2014 19:24:34.134 UTC Debug stateful_proxy.cpp:367: tsx0x11ecc78 - tu_on_tsx_state UAC, TSX_STATE TRANSPORT_ERROR state=Terminated 14-11-2014 19:24:34.134 UTC Debug stateful_proxy.cpp:4352: tsx0x11ecc78 - uac_data = 0x11ed3e0, uas_data = 0x11e9880 14-11-2014 19:24:34.134 UTC Debug stateful_proxy.cpp:4413: tsx0x11ecc78 - UAC tsx terminated while still connected to UAS tsx 14-11-2014 19:24:34.134 UTC Debug stateful_proxy.cpp:4416: Timeout or transport error 14-11-2014 19:24:34.134 UTC Debug stateful_proxy.cpp:3392: tsx0x11ecc78 - Not forked request 14-11-2014 19:24:34.134 UTC Debug pjsip: tsx0x11e8f08 Sending Response msg 408/REGISTER/cseq=1 (tdta0x11e9a10) in state Trying 14-11-2014 19:24:34.134 UTC Verbose stack.cpp:249: TX 272 bytes Response msg 408/REGISTER/cseq=1 (tdta0x11e9a10) to UDP 10.3.160.21:5060: --start msg-- SIP/2.0 408 Request Timeout^M Via: SIP/2.0/UDP 192.168.0.100:5060 ;rport=5060;received=10.3.160.21;branch=z9hG4bK1806547393^M Call-ID: 761958977^M From: <sip:[email protected]>;tag=1937036704^M To: <sip:[email protected]>;tag=z9hG4bK1806547393^M CSeq: 1 REGISTER^M Content-Length: 0^M ^M and we do not get any relevant trace on homestead. There seems to be a minor thing which we are missing here. Regards, Sushant Sushant Hiray, Senior Undergrad CSE, IIT Bombay On Sat, Nov 15, 2014 at 12:42 AM, Eleanor Merry < [email protected]> wrote: > Hi, > > > > Sprout is listening on the loopback address – it needs to listen on its > private address instead (10.120.34.82). > > > > What command are you using to start Sprout? Do you have the ‘–c’ option > specified for the scscf_uri? You don’t need to have the ‘–l ’ option > specified, as this defaults to the private address already. > > > > It’s important to note that these are the minimum parameters needed to > successfully start Sprout. Depending on what functionality you want the > Sprout to have, and whether it’s running on an all-in-one node, then there > are different values you’ll want to pass in as well (e.g. if your Sprout is > not on an all-in-one node then you will also have to pass in the > home_domain parameter to allow calls to be routed correctly). > > > > Ellie > > > > > > *From:* Sushant Hiray [mailto:[email protected]] > *Sent:* 12 November 2014 12:35 > *To:* Eleanor Merry > *Cc:* Sanchit Garg; [email protected] > > *Subject:* Re: [Clearwater] SegFault while running sprout from source code > > > > Hi Ellie, > > We tried the updated command and it starts perfectly fine. > > However while sending request from Bono, we are still getting errors: > > 12-11-2014 12:04:45.916 UTC Debug connection_pool.cpp:181: Successfully > resolved sprout.ims.hom to IPv4 address > 12-11-2014 12:04:45.916 UTC Verbose pjsip: tcpc0x7fbfcc15 TCP client > transport created > 12-11-2014 12:04:45.917 UTC Verbose pjsip: tcpc0x7fbfcc15 TCP transport > 10.129.34.51:45528 is connecting to 10.129.34.82:5054... > 12-11-2014 12:04:45.917 UTC Debug connection_pool.cpp:251: Created > transport tcpc0x7fbfcc15a578 in slot 46 (10.129.34.51:45528 to > 10.129.34.82:5054) > 12-11-2014 12:04:45.937 UTC Error pjsip: tcpc0x7fbfcc14 TCP connect() > error: Connection refused [code=120111] > 12-11-2014 12:04:45.937 UTC Debug connection_pool.cpp:363: Transport > tcpc0x7fbfcc1450a8 in slot 0 has failed > 12-11-2014 12:04:45.937 UTC Debug baseresolver.cpp:471: Add > 10.129.34.82:5054 transport 6 to blacklist for 30 seconds > 12-11-2014 12:04:45.937 UTC Error pjsip: tcpc0x7fbfcc14 TCP connect() > error: Connection refused [code=120111] > 12-11-2014 12:04:45.937 UTC Debug connection_pool.cpp:363: Transport > tcpc0x7fbfcc14f8a8 in slot 1 has failed > 12-11-2014 12:04:45.937 UTC Debug baseresolver.cpp:471: Add > 10.129.34.82:5054 transport 6 to blacklist for 30 seconds > 12-11-2014 12:04:45.937 UTC Error pjsip: tcpc0x7fbfcc13 TCP connect() > error: Connection refused [code=120111] > 12-11-2014 12:04:45.937 UTC Debug connection_pool.cpp:363: Transport > tcpc0x7fbfcc1358b8 in slot 2 has failed > > So essentially Bono is not able to connect to Sprout via TCP. > > We did not receive any updates in log of Sprout. However sprout does seem > to listen on 5054. > > Here is the output of netstat: > synerg@ubuntu-precise:~$ sudo netstat -anp | grep 5054 > tcp 0 0 127.0.1.1:5054 0.0.0.0:* > LISTEN 2034/sprout > udp 0 0 127.0.1.1:5054 0.0.0.0:* > 2034/sprout > > > Can you suggest what could be the plausible issue? > > Regards, > > Sushant > > > Sushant Hiray, > > Senior Undergrad CSE, > > IIT Bombay > > > > On Wed, Nov 12, 2014 at 1:07 AM, Eleanor Merry < > [email protected]> wrote: > > Hi Sanchit, > > Sorry, I told you the wrong thing before. The HTTP bind address should be > the IP address of the Sprout, not the Homestead. Can you change this and > retry? > You will also need to add the scscf_uri option – you can do this by adding > ‘–c sip:<sprout<sip:%3csprout> domain>:5054’ > > Ellie > > From: Sanchit Garg [mailto:[email protected]] > Sent: 10 November 2014 09:23 > To: Eleanor Merry > Cc: [email protected] > Subject: Re: [Clearwater] SegFault while running sprout from source code > > Hi Ellie > Thank you for the reply. I tried what you suggested. It doesn't give > SIGSEV signal. But a new problem arose. It now catches HttpStack::Exception > . Following is the log output: > 10-11-2014 09:02:18.378 UTC Error httpstack.cpp:197: evhtp_bind_socket > failed with address 10.129.34.87 and port 9888 > 10-11-2014 09:02:18.378 UTC Error main.cpp:1523: Caught > HttpStack::Exception - evhtp_bind_socket - -1 > We ran the following command: > sudo LD_LIBRARY_PATH=usr/lib:$LD_LIBRARY_PATH build/bin/sprout -t -s 5054 > -l localhost -H 10.129.34.87:8888<http://10.129.34.87:8888> -K > 10.120.34.82:7253<http://10.120.34.82:7253> -T 10.129.34.87 -F > /var/log/sprout > Where: 10.129.34.87 is the IP of Homestead and 10.129.34.82 is of sprout. > > HttpStack::start(®_httpthread_with_pjsip) called in main.cpp calls > evhtp_bind_socket which returns -1 and then it throws HttpStack::Exception. > Also we checked the output of netstat -a |egrep '9888' command in > Homestead which outputs: unix 3 [ ] STREAM CONNECTED > 9888 > We think that homestead is listening on port 9888 but sprout is unable to > bind http socket to homestead. > Can you please suggest how to fix this issue > Thank You > Sanchit Garg > > > On Thu, Nov 6, 2014 at 11:35 PM, Eleanor Merry < > [email protected]<mailto:[email protected]>> wrote: > Hi Sanchit, > > Thanks for raising this. > > Sprout is hitting a segfault as the scscf_uri parameter hasn't been > defined. This defaults to > sip:<localhost>:<scscf<sip:%3clocalhost%3e:%3cscscf> port>;transport=TCP > if you run Sprout as a daemon, but it isn't currently defaulted when > running Sprout interactively. > > I've raised an issue to fix the documentation and defaults (please see > https://github.com/Metaswitch/sprout/issues/851) - in the meantime can > you please add these extra parameters? You will also need to pass in the > HTTP bind address (e.g. -T 10.129.34.87). > > You can see what other parameters are available by running with -h > > Ellie > > -----Original Message----- > From: [email protected]<mailto: > [email protected]> [mailto: > [email protected]<mailto: > [email protected]>] On Behalf Of Sanchit Garg > Sent: 06 November 2014 08:57 > To: [email protected]<mailto: > [email protected]> > Subject: [Clearwater] SegFault while running sprout from source code > > Hi All, > > We are trying to install Sprout from source code on a server Ubuntu 12.04. > We have successfully built the source code. While running the command > <sudo LD_LIBRARY_PATH=usr/lib:$LD_LIBRARY_PATH build/bin/sprout -t -s 5054 > -H 10.129.34.87:8888<http://10.129.34.87:8888> -K 10.120.34.82:7253< > http://10.120.34.82:7253> -F /var/log/sprout> a SIGSEGV signal is raised. > We have figured out that 'init_registrar(...)' in the main.cpp and in > particular 'pjsip_parse_uri(...)' in 'init_registrar(...)' has raised the > signal. The function 'pjsip_parse_uri(...)' is returning NULL to be > specific. > > Please suggest how to resolve the issue. > > Thank You > Sanchit Garg > Senior Undergrad CSE IIT Bombay > _______________________________________________ > Clearwater mailing list > [email protected]<mailto: > [email protected]> > > http://lists.projectclearwater.org/listinfo/clearwater > > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/listinfo/clearwater > > > _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
