[SR-Users] Kamailio 4.0.0 not listening on TCP

David Wilson dw at zaq.com.au
Fri Apr 12 11:03:02 CEST 2013


Jeremy,

"Is it running?" was a very sensible question, especially since I said I was running from the command line.  I'm actually using a second terminal to monitor the host while the first one is running kamailio in the foreground.

I like to work from the command line until the config is right, then I'll run the service.

Thanks for the tip on ss, but it also reports nothing listening on 55060 (or 5060).

Without the grep, netstat shows me other processes listening for TCP (on different ports).  Other evidence is that a connection attempt fails.

'disable_tcp=yes' is NOT active.  When it is (I checked) Kamailio doesn't report that it's listening on TCP.

Dave.

On 12/04/2013, at 3:11 PM, Jeremy Ardley <jeremy.ardley at gmail.com> wrote:

> netstat is a bit tricky. Luckily it's now obsoleted by ss
> 
> Try
> 
> netstat -a -n | grep 5060
> 
> Also check if your kamialio.cfg file has "disable_tcp=yes" Comment it
> out if it does.
> 
> P.S. I only asked about whether it was still running because it can
> easily die on startup if the scripts detect some error like the control
> files still exists. I just checked now on my system which I installed
> using 'official' RPMs for Centos 6. The 'service kamailio restart'
> command appears to work but fails quietly for the following reason
> 
> Apr 12 14:55:40 sentinel /usr/sbin/kamailio[7501]: ERROR: ctl [ctl.c:379]: ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1)
> 
> 
> On 12/04/13 14:37, David Wilson wrote:
>> Hi Jeremy,
>> 
>> Thanks for the suggestion, I'm hoping I haven't overlooked something quite that obvious!
>> 
>> The last debug output I see on startup is:
>> 
>>> Listening on 
>>>             udp: 192.168.44.66:55060
>>>             tcp: 192.168.44.66:55060
>>> Aliases:
>>> 	<snip>
>>> 
>>> WARNING: no fork mode 
>>> 0(20372) INFO: <core> [tcp_main.c:4833]: init_tcp: using epoll_lt as the io watch method (auto detected)
>>> 0(20372) INFO: usrloc [hslot.c:53]: locks array size 512
>>> 0(20372) INFO: <core> [udp_server.c:179]: INFO: udp_init: SO_RCVBUF is initially 229376
>>> 0(20372) INFO: <core> [udp_server.c:230]: INFO: udp_init: SO_RCVBUF is finally 262142
>> netstat shows listening for UDP on 55060, but nothing on TCP:
>> 
>> $ netstat -l | grep 5060
>> udp        0      0 192.168.44.66:55060 *:*  
>> 
>> ps shows four kamailio processes running, all of which end when I Ctrl-C.
>> 
>> Cheers,
>> Dave.
>> 
>>> Date: Fri, 12 Apr 2013 14:22:45 +0800
>>> From: Jeremy Ardley <jeremy.ardley at gmail.com>
>>> Subject: Re: [SR-Users] Kamailio 4.0.0 not listening on TCP
>>> 
>>> 
>>> Have you checked to make sure it's still running?
>>> 
>>> 
>>> On 12/04/13 14:19, David Wilson wrote:
>>>> Hello All,
>>>> 
>>>> New to Kamailio, I'm running 4.0 on Ubuntu 12.04 (precise).
>>>> 
>>>> Running from the command line with a minimal config, it tells me that it is listening on port 5060 for both TCP and UDP.  I see the same behaviour with the default cfg.
>>>> 
>>>> However, netstat does not list anything listening on TCP port 5060 and an attempted connection is rejected consistent with there being no open socket.
>>>> 
>>>> Any suggestions on where I need to be looking to fix this?
>>>> 
>>> 
>>> 




More information about the sr-users mailing list