[OpenSIPS-Users] Opensips just stops responding

Bogdan-Andrei Iancu bogdan at voice-system.ro
Thu Dec 23 15:34:08 CET 2010


Cool...I also had a lot of issues in the past with Selinux :(

Regards,
Bogdan

Maciej Bylica wrote:
> Hi Bogdan,
>
> Thanks for prompt answer.
>
> Port 5060 is open, but thanks to your advice i tried to originate the
> INVITE directly from the server and the result was that Opensips
> responded properly.
> Then i found out that centos has Selinux enabled :)
>
> Problem is solved,
> Once again many  thanks,
> Maciej.
>
> 2010/12/22 Bogdan-Andrei Iancu <bogdan at voice-system.ro>:
>   
>> Hi Maciej,
>>
>> What opensips version are you using ? 4448 is quite old rev number...Current
>> 1.6.4 has 7611 rev number...
>>
>> Anyhow, are you sure you are sending the traffic on a port  which is used by
>> opensips ?  try with "netstat -ulnp" to see where opensips is listening and
>> if there is any pending data to be read.
>>
>> Regards,
>> Bogdan
>>
>> Maciej Bylica wrote:
>>     
>>> Hello,
>>>
>>> It is quite old post, but i have just encoutered quite similiar problem.
>>> I have the latest revision installed $Revision: 4448 in my server.
>>> Opensips is starting itself properly:
>>>
>>> # ps -ef | grep opensips
>>> root     20982  6115  0 02:01 pts/1    00:00:00 gdb
>>> /usr/local/sbin/opensips
>>> root     21326     1  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21328 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21329 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21330 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21331 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21332 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21333 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21334 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21335 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21336 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21337 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21338 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21339 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21340 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21341 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21342 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21343 21326  0 02:14 ?        00:00:00
>>> /usr/local/sbin/opensips -P /var/run/opensips/opensips.pid
>>> root     21392  6258  0 02:18 pts/2    00:00:00 grep opensips
>>>
>>> and there is a opensips.pid file generated.
>>> The problem is that opensips is not responding to any request, there
>>> are no debug information at all (default opensips.conf file)
>>> I even created simple script ---- route { log... } and the effect is the
>>> same.
>>>
>>> Here is how opensips is starting (debug 5):
>>> Dec 22 02:25:50 mac opensips: WARNING:core:fix_socket_list: could not
>>> rev. resolve 62.29.162.76
>>> Dec 22 02:25:50 mac opensips: WARNING:core:fix_socket_list: could not
>>> rev. resolve 62.29.162.76
>>> Dec 22 02:25:50 mac opensips: INFO:core:init_tcp: using epoll_lt as
>>> the TCP io watch method (auto detected)
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]: NOTICE:core:main:
>>> version: opensips 1.6.4-notls (i386/linux)
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]: INFO:core:main:
>>> using 32 Mb shared memory
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]: INFO:core:main:
>>> using 1 Mb private memory per process
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]:
>>> NOTICE:signaling:mod_init: initializing module ...
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]: INFO:sl:mod_init:
>>> Initializing StateLess engine
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]: INFO:tm:mod_init:
>>> TM - initializing...
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]: INFO:rr:mod_init:
>>> rr - initializing
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]:
>>> INFO:maxfwd:mod_init: initializing...
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]:
>>> INFO:usrloc:ul_init_locks: locks array size 512
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]:
>>> INFO:registrar:mod_init: initializing...
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]:
>>> INFO:textops:mod_init: initializing...
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]:
>>> INFO:acc:mod_init: initializing...
>>> Dec 22 02:25:50 mac /usr/local/sbin/opensips[21463]:
>>> INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255
>>> kb
>>>
>>>
>>> more info from gdb /usr/local/sbin/opensips
>>> (gdb)
>>> No stack.
>>>
>>> and the output from  opensipsctl fifo ps
>>> Process::  ID=0 PID=21326 Type=attendant
>>> Process::  ID=1 PID=21328 Type=MI FIFO
>>> Process::  ID=2 PID=21329 Type=SIP receiver udp:127.0.0.1:5060
>>> Process::  ID=3 PID=21330 Type=SIP receiver udp:127.0.0.1:5060
>>> Process::  ID=4 PID=21331 Type=SIP receiver udp:127.0.0.1:5060
>>> Process::  ID=5 PID=21332 Type=SIP receiver udp:127.0.0.1:5060
>>> Process::  ID=6 PID=21333 Type=SIP receiver udp:62.29.162.76:5060
>>> Process::  ID=7 PID=21334 Type=SIP receiver udp:62.29.162.76:5060
>>> Process::  ID=8 PID=21335 Type=SIP receiver udp:62.29.162.76:5060
>>> Process::  ID=9 PID=21336 Type=SIP receiver udp:62.29.162.76:5060
>>> Process::  ID=10 PID=21337 Type=time_keeper
>>> Process::  ID=11 PID=21338 Type=timer
>>> Process::  ID=12 PID=21339 Type=TCP receiver
>>> Process::  ID=13 PID=21340 Type=TCP receiver
>>> Process::  ID=14 PID=21341 Type=TCP receiver
>>> Process::  ID=15 PID=21342 Type=TCP receiver
>>> Process::  ID=16 PID=21343 Type=TCP main
>>>
>>> I have no idea where the problem is located, despite of the fact that
>>> it is not my first instalation.
>>>
>>> Any ideas?
>>> Thanks in advance,
>>> Maciej.
>>>
>>>
>>> 2010/4/2 Bogdan-Andrei Iancu <bogdan at voice-system.ro>:
>>>
>>>       
>>>> I see, let me know if without the Localcache module works ok or not.
>>>>
>>>> Regards,
>>>> Bogdan
>>>>
>>>> Jayesh Nambiar wrote:
>>>>
>>>>         
>>>>> Hi Bogdan,
>>>>> Thanks for your reply. I will try this the next time my config behaves
>>>>> like this.
>>>>> By the way the only change that I did in this lastly was, I removed
>>>>> the "LocalCache  module" support and have had the opensips to query
>>>>> the DB for Authentication. It's been 18 hours and till now the server
>>>>> is up and running fine.
>>>>> I'll keep a watch and follow the steps mentioned by you !!
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --- Jayesh
>>>>>
>>>>>
>>>>>    Message: 2
>>>>>    Date: Fri, 02 Apr 2010 11:40:32 +0300
>>>>>    From: Bogdan-Andrei Iancu <bogdan at voice-system.ro
>>>>>    <mailto:bogdan at voice-system.ro>>
>>>>>    Subject: Re: [OpenSIPS-Users] Opensips just stops responding
>>>>>    To: OpenSIPS users mailling list <users at lists.opensips.org
>>>>>    <mailto:users at lists.opensips.org>>
>>>>>    Message-ID: <4BB5AD80.80204 at voice-system.ro
>>>>>    <mailto:4BB5AD80.80204 at voice-system.ro>>
>>>>>    Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>>>
>>>>>    Hi Jayesh,
>>>>>
>>>>>    Could you try to use gdb to attached to the unresponsive processes
>>>>> and
>>>>>    to see where they are stuck ? Use "gdb /path/opensips PID" and do
>>>>> "bt"
>>>>>    to get backtrace. Check for processes responsible for the network
>>>>> read
>>>>>    (do an "opensipsctl fifo ps" to see which are the UDP listener
>>>>>    processes)
>>>>>
>>>>>    Regards,
>>>>>    Bogdan
>>>>>
>>>>>    Jayesh Nambiar wrote:
>>>>>    > Hi all,
>>>>>    > I am running Opensips 1.6.2 and am running a strange problem of
>>>>>    > Opensips not responding to any SIP messages after a day or two. It
>>>>>    > needs to be restarted for it to get working again.
>>>>>    > The overview of my setup is as follows:
>>>>>    > 1) I am using Localcache module to authorize REGISTER and INVITE
>>>>>    > requests from cache.
>>>>>    > 2) Using Mediaproxy for Nated clients with Media-Relay on a
>>>>>    different
>>>>>    > server
>>>>>    > 3) Running basic queries based on INVITE before placing the call.
>>>>>    >
>>>>>    > After running for a day or two, Opensips just stops responding
>>>>>    to any
>>>>>    > SIP message. I check moni, it shows me the server is alive and
>>>>>    in_use
>>>>>    > transactions keep on increasing since Opensips is not processing
>>>>>    > anyone. I checked get_statistics shmem: even that is perfectly ok.
>>>>>    > I have assigned 1GB to shmem and hardly 30 MB is used. I dont
>>>>>    even see
>>>>>    > any error logs etc. The top command shows no over utilization of
>>>>> CPU
>>>>>    > and memory.
>>>>>    >
>>>>>    > Can someone point me on where and how to check for this problem.
>>>>> Has
>>>>>    > someone had a similar problem before. It looks similar to this
>>>>>    > post
>>>>>    http://www.mail-archive.com/users@lists.opensips.org/msg06098.html
>>>>> but
>>>>>    > I dont see a solution to this either.
>>>>>    >
>>>>>    > Thanks for any help.
>>>>>    >
>>>>>    > --- Jayesh
>>>>>    >
>>>>>    >
>>>>>
>>>>>  ------------------------------------------------------------------------
>>>>>    >
>>>>>    > _______________________________________________
>>>>>    > Users mailing list
>>>>>    > Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>>>>    > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>>
>>>>>           
>> --
>> Bogdan-Andrei Iancu
>> OpenSIPS Event - expo, conf, social, bootcamp
>> 2 - 4 February 2011, ITExpo, Miami,  USA
>> www.voice-system.ro
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>     
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>   


-- 
Bogdan-Andrei Iancu
OpenSIPS Event - expo, conf, social, bootcamp
2 - 4 February 2011, ITExpo, Miami,  USA
www.voice-system.ro




More information about the Users mailing list