[OpenSIPS-Users] FW: OpenSIPs 2.2.2 warnings during start service

Wed Jan 25 04:23:29 EST 2017

Hi Agalya,

That is really weird - I suppose you are using the latest 2.2, right ?

Are you using a VM or container to run OpenSIPS ?

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 01/24/2017 06:42 PM, Ramachandran, Agalya (Contractor) wrote:
>
> *From:*Ramachandran, Agalya (Contractor)
> *Sent:* Tuesday, January 24, 2017 11:42 AM
> *To:* 'Bogdan-Andrei Iancu' <bogdan at opensips.org>
> *Subject:* RE: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start 
> service
>
> Hi Bogdan,
>
> 1)do you get warning only for the tm-utimer job ? or do you see other 
> too ?
>
> I rarely see from blcore-expire job too.
>
>       2)    do you have some load on the server (in terms of traffic) 
> ? or is it idle/almost-idle ?
>
> Mostly its idle, May be it will process 5 to 10 calls in an hour. That 
> is the load it is been handling right now.
>
> Giving the Process id and its same logs.
>
> Process:: ID=0 PID=11744 Type=attendant
>
> Process:: ID=1 PID=11745 Type=MI FIFO
>
> Process:: ID=2 PID=11746 Type=time_keeper
>
> Process:: ID=3 PID=11747 Type=timer
>
> Process:: ID=4 PID=11748 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=5 PID=11749 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=6 PID=11750 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=7 PID=11751 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=8 PID=11752 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=9 PID=11753 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=10 PID=11754 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=11 PID=11755 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=12 PID=11756 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=13 PID=11757 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=14 PID=11758 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=15 PID=11759 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=16 PID=11760 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=17 PID=11761 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=18 PID=11762 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=19 PID=11763 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=20 PID=11764 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=21 PID=11765 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=22 PID=11766 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=23 PID=11767 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=24 PID=11768 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=25 PID=11769 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=26 PID=11770 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=27 PID=11771 Type=SIP receiver udp:10.0.0.1:5060
>
> Process:: ID=28 PID=11772 Type=Timer handler
>
> Jan 23 22:36:29 /usr/local/sbin/opensips[11771]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us 
> delay in execution
>
> Jan 23 22:49:42 /usr/local/sbin/opensips[11767]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us 
> delay in execution
>
> Jan 23 22:53:15 /usr/local/sbin/opensips[11771]: 
> WARNING:core:handle_timer_job: timer job <tm-timer> has a 80000 us 
> delay in execution
>
> Jan 23 22:53:15 /usr/local/sbin/opensips[11753]: 
> WARNING:core:handle_timer_job: timer job <blcore-expire> has a 80000 
> us delay in execution
>
> Jan 23 22:55:06 /usr/local/sbin/opensips[11771]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us 
> delay in execution
>
> Jan 23 22:59:37 /usr/local/sbin/opensips[11767]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us 
> delay in execution
>
> Jan 23 23:07:20 /usr/local/sbin/opensips[11771]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us 
> delay in execution
>
> Jan 23 23:29:51 /usr/local/sbin/opensips[11771]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us 
> delay in execution
>
> Jan 23 23:30:11 /usr/local/sbin/opensips[11771]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us 
> delay in execution
>
> Jan 23 23:30:26 /usr/local/sbin/opensips[11772]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us 
> delay in execution
>
> Jan 23 23:35:55 /usr/local/sbin/opensips[11758]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 30000 us 
> delay in execution
>
> Jan 23 23:35:55 /usr/local/sbin/opensips[11771]: 
> WARNING:core:handle_timer_job: utimer job <tm-utimer> has a 20000 us 
> delay in execution
>
> Regards,
> Agalya
>
> *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
> *Sent:* Tuesday, January 24, 2017 11:09 AM
> *To:* Ramachandran, Agalya (Contractor) 
> <Agalya_Ramachandran at comcast.com 
> <mailto:Agalya_Ramachandran at comcast.com>>; OpenSIPS users mailling 
> list <users at lists.opensips.org <mailto:users at lists.opensips.org>>
> *Subject:* Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start 
> service
>
> Hi Agalya,
>
> 1) do you get warning only for the tm-utimer job ? or do you see other 
> too ?
>
> 2) do you have some load on the server (in terms of traffic) ? or is 
> it idle/almost-idle ?
>
> 3) the "ps" and the logs are not from the same run (the pid's do not 
> match) - can you get the data from same run please ?
>
> Best regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170125/99593968/attachment-0001.html>