Siproxyd on 2.3 just exits randomly without reason



  • Im using exact same config as I used on a working 2.2.6 box.

    Here is the log. I don't know what signal 11 is. Censored out phone numbers.

    
    Apr 18 16:14:40  siproxd  6052  siproxd.c:233 INFO:siproxd-0.8.1-53 amd64-portbld-freebsd10.3 starting up  
    Apr 18 16:14:40  siproxd  6303  siproxd.c:290 INFO:daemonized, pid=6303  
    Apr 18 16:14:40  siproxd  6303  plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40  
    Apr 18 16:14:40  siproxd  6303  plugins.c:112 INFO:Plugin 'plugin_defaulttarget' [Forwards all unknown calls to a default internal location] loaded with success, exemask=0x20  
    Apr 18 16:14:40  siproxd  6303  rtpproxy_relay.c:121 INFO:Current thread stacksize is 2048 kB  
    Apr 18 16:14:40  siproxd  6303  sock.c:131 INFO:bound to port 5060  
    Apr 18 16:14:40  siproxd  6303  siproxd.c:344 INFO:siproxd-0.8.1-53 amd64-portbld-freebsd10.3 started  
    Apr 18 16:14:43  siproxd  6737  siproxd.c:233 INFO:siproxd-0.8.1-53 amd64-portbld-freebsd10.3 starting up  
    Apr 18 16:14:43  siproxd  7254  siproxd.c:290 INFO:daemonized, pid=7254  
    Apr 18 16:14:43  siproxd  7254  plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40  
    Apr 18 16:14:43  siproxd  7254  plugins.c:112 INFO:Plugin 'plugin_defaulttarget' [Forwards all unknown calls to a default internal location] loaded with success, exemask=0x20  
    Apr 18 16:14:43  siproxd  7254  rtpproxy_relay.c:121 INFO:Current thread stacksize is 2048 kB  
    Apr 18 16:14:43  siproxd  7254  sock.c:543 ERROR:bind failed: Address already in use  
    Apr 18 16:14:43  siproxd  7254  siproxd.c:332 ERROR:unable to bind to SIP listening socket - aborting  
    Apr 18 20:26:17  siproxd  6303  sock.c:310 WARNING:recv() returned error [Connection reset by peer], disconnecting TCP [46.101.51.89] fd=6  
    Apr 18 20:26:29  siproxd  6303  sock.c:672 WARNING:sip_tcp_cache[0].rx_buffer was not freed! Potential memleak.  
    Apr 18 20:28:17  siproxd  6303  sock.c:310 WARNING:recv() returned error [Connection reset by peer], disconnecting TCP [46.101.51.89] fd=6  
    Apr 18 20:28:38  siproxd  6303  sock.c:672 WARNING:sip_tcp_cache[0].rx_buffer was not freed! Potential memleak.  
    Apr 19 02:49:18  siproxd  6303  sip_utils.c:627 ERROR:I'm trying to delete a VIA but it's not mine! host=127.0.0.1  
    Apr 19 10:50:58  siproxd  6303  plugin_logcall.c:126 INFO:Incoming Call: *@80.232.37.178 -> *@80.232.37.178 [Req: *@185.86.107.140]  
    Apr 19 10:50:58  siproxd  6303  plugin_logcall.c:126 INFO:ACK Call: *@80.232.37.178 -> *@80.232.37.178 [Req: *@185.86.107.140]  
    Apr 19 10:51:24  siproxd  6303  plugin_logcall.c:126 INFO:Ending Call: *@80.232.37.178 -> *@80.232.37.178 [Req: *NULL*@80.232.37.178]  
    Apr 19 10:51:32  siproxd  6303  plugin_logcall.c:126 INFO:Outgoing Call: *@sip.phonzo.com -> *@sip.phonzo.com [Req: *@sip.phonzo.com]  
    Apr 19 10:51:32  siproxd  6303  plugin_logcall.c:126 INFO:ACK Call: *@sip.phonzo.com -> *@sip.phonzo.com [Req: *@sip.phonzo.com]  
    Apr 19 10:51:32  siproxd  6303  plugin_logcall.c:126 INFO:Outgoing Call: *@sip.phonzo.com -> *@sip.phonzo.com [Req: *@sip.phonzo.com]  
    Apr 19 10:51:34  siproxd  6303  plugin_logcall.c:126 INFO:ACK Call: *@sip.phonzo.com -> *@sip.phonzo.com [Req: *@sip.phonzo.com]  
    Apr 19 10:51:55  siproxd  6303  plugin_logcall.c:126 INFO:Incoming Call: *@80.232.37.178 -> *@80.232.37.178 [Req: *@185.86.107.140]  
    Apr 19 10:51:55  siproxd  6303  plugin_logcall.c:126 INFO:ACK Call: *@80.232.37.178 -> *@80.232.37.178 [Req: *@185.86.107.140]  
    Apr 19 10:51:59  kernel   pid 6303 (siproxd), uid 65534: exited on signal 11  
    
    

  • Rebel Alliance Developer Netgate

    Signal 11 is a segmentation violation. Usually random signal 11 crashes are a sign of a hardware issue, though it is possible for it to happen from a software bug on occasion. Are you certain it's only siproxd that crashes?



  • yes. Did never crash in 2.2.6, crash randomly in 2.3.
    Same hardware, and only siproxyd that crash.


  • Rebel Alliance Developer Netgate

    It may be something about the request, then. I have heard recently from the siproxd author that he is working on a new version, it's possible it's a bug that has been corrected there.


Log in to reply