[SR-Users] Address already in use error when starting Kamailio service

[Mahmoud Ramadan Ali]

Hiiii
Thanks for the reply...i really appreciate that....
The "netstat -altpn" command does not show any process or application
listing to 5060 other than kamailio !
Also after using the "ps -aux | grep kamailio" i see only kamailio is
running as single process and does not do process forking as below

[root at Kamailio kamailio]# ps -aux | grep kamailio
Warning: bad syntax, perhaps a bogus '-'? See
/usr/share/doc/procps-3.2.8/FAQ
root      4163  0.0  0.2 156916  2608 ?        S    09:00   0:00
/usr/local/sbin/kamailio -P /var/run/kamailio.pid -m 32 -M 4 -u root -g
kamailio
root      4245  0.0  0.0 103248   836 pts/1    S+   09:02   0:00 grep
kamailio

Also here is some logs tail  /var/log/messages | less

Nov  3 09:00:55 Kamailio /usr/local/sbin/kamailio[4162]: ERROR: <core>
[pt.c:479]: fork_tcp_process(): init_child failed for process 20, pid 4162,
"tcp receiver (generic) child=3"
Nov  3 09:00:55 Kamailio /usr/local/sbin/kamailio[4162]: ERROR: <core>
[tcp_main.c:4868]: tcp_init_children(): fork failed: Success
a
Aside Note:
I'm using Kamailio v4.2 on centos and this issue appears whenever i replace
the default config file with this config file from that link
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
i want to use this file in particular because it is easy to me as beginner
with Kamailo to configure it with Asterisk integration...thanks in advance
everyone


On Mon, Nov 3, 2014 at 2:34 PM, Rainer Piper <rainer.piper at soho-piper.de>
wrote:

>  Am 03.11.2014 um 11:50 schrieb Daniel-Constantin Mierla:
>
> Hello,
>
> On 02/11/14 21:47, Mahmoud Ramadan Ali wrote:
>
> Hiiiiii everyone,
> I'm receiving this error when starting Kamailio saying that it can not
> resolve my  ip addresses used by Kamailio and another "127.0.0.1:5060 :
> Address already in use " error message...so how can i fix this please ?
>
> Nov  2 15:39:26 Kamailio /usr/local/sbin/kamailio[7692]: CRITICAL: <core>
> [pass_fd.c:293]: receive_fd(): EOF on 35
> Nov  2 15:39:44 Kamailio kamailio: WARNING: <core> [socket_info.c:1392]:
> fix_hostname(): could not rev. resolve 192.168.100.1
> Nov  2 15:39:44 Kamailio kamailio: WARNING: <core> [socket_info.c:1392]:
> fix_hostname(): could not rev. resolve 192.168.50.1
> Nov  2 15:39:44 Kamailio kamailio: WARNING: <core> [socket_info.c:1392]:
> fix_hostname(): could not rev. resolve 192.168.100.1
> Nov  2 15:39:44 Kamailio kamailio: WARNING: <core> [socket_info.c:1392]:
> fix_hostname(): could not rev. resolve 192.168.50.1
>
> Nov  2 15:39:44 Kamailio /usr/local/sbin/kamailio[7726]: ERROR: <core>
> [tcp_main.c:2876]: tcp_init(): bind(b, 0x7faebd135ca4, 16) on
> 127.0.0.1:5060 : Address already in use
>
>
> the warning messages can be ignored -- perhaps we should make them notice
> or info, rather than warnings.
>
>  For address already in use, see if there is another application listening
> on that socket, can be a sip phone or even another kamailio running -- you
> can use netstat to check:
>
> netstat -altpn
>
> check UDP Listener parameter -u as well ... like:
>
> netstat -anupn
>
> Parameter:
> -t = TCP
> -u = UDP
>
> Regards
> Rainer
>
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
> Kamailio Advanced Training, Nov 24-27, Berlin - http://www.asipto.com
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users at lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> --
> *Rainer Piper*
> Integration engineer
> Koeslinstr. 56
> 53123 BONN
> GERMANY
> Phone: +49 228 97167161
> P2P: sip:rainer at sip.soho-piper.de:5072 (pjsip-test)
> XMPP: rainer at xmpp.soho-piper.de
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20141103/12798fe6/attachment.html>