[OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed

Aqs Younas aqsyounas at gmail.com
Fri Jan 22 17:08:35 CET 2016


Hi, Bogdan


You mean children? First I thought it is due to children(10 default)
which I increased to 500 but no avail.

This I have in my configuration file.

debug=3
log_stderror=no
log_facility=LOG_LOCAL3

fork=yes
children=500
open_files_limit=99999

Thanks for replying.



On 22 January 2016 at 20:49, Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> How many workers have you configured into opensips ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 22.01.2016 17:43, Aqs Younas wrote:
>
> I see this warning when i am sending calls with more than 10 cps. On 5 to
> 10 cps everything seems ok.
>
> On 22 January 2016 at 19:38, Aqs Younas <aqsyounas at gmail.com> wrote:
>
>> Hi,
>>
>> I am using sipp to load test my opensips (version: opensips 2.1.2
>> (x86_64/linux)) after calls get terminated i see my opensips being flood
>> with below warnings.
>>
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1575170 ms (now 1575270 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1575270 ms (now 1575370 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1575370 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:timer_ticker: timer task <rl-timer> already schedualed for
>> 846540 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:timer_ticker: timer task <nt-pinger> already schedualed for
>> 867440 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:timer_ticker: timer task <nh-timer> already schedualed for
>> 867440 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:timer_ticker: timer task <lb-pinger> already schedualed for
>> 866440 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:timer_ticker: timer task <dlg-pinger> already schedualed for
>> 866440 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:timer_ticker: timer task <dlg-timer> already schedualed for
>> 867440 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:timer_ticker: timer task <ul-timer> already schedualed for
>> 896290 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:timer_ticker: timer task <tm-timer> already schedualed for
>> 836590 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:timer_ticker: timer task <blcore-expire> already schedualed
>> for 867440 ms (now 1575470 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1575470 ms (now 1575570 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1575570 ms (now 1575670 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1575670 ms (now 1575770 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1575770 ms (now 1575870 ms), it may overlap..
>> Jan 22 14:31:38 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1575870 ms (now 1575970 ms), it may overlap..
>> Jan 22 14:31:39 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1575970 ms (now 1576070 ms), it may overlap..
>> Jan 22 14:31:39 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1576070 ms (now 1576170 ms), it may overlap..
>> Jan 22 14:31:39 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1576170 ms (now 1576270 ms), it may overlap..
>> Jan 22 14:31:39 66-226-76-150
>> /usr/local/origination/opensips/sbin/opensips[22844]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already schedualed for
>> 1576270 ms (now 1576360 ms), it may overlap..
>>
>> Below command never gets executed.
>>
>>  /usr/local/origination/opensips/sbin/opensipsctl trap
>> INFO: Trap file: /tmp/gdb_opensips_20160122_143249
>> ^C/usr/local/origination/opensips//lib64/opensips/opensipsctl/opensipsctl.fifo:
>> line 109: /tmp/opensips_fifo: Interrupted system call
>> Terminated
>>
>> This files is empty
>> cat /tmp/gdb_opensips_20160122_143249
>>
>> ps -el | grep opensips
>>
>>
>> 1 S     0 22782 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22783 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22785 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22789 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22792 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22796 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22798 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22800 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22804 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22807 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22811 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22814 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22817 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22819 22762  0  80   0 - 39789 -      ?        00:00:00 opensips
>> 1 S     0 22821 22762  0  80   0 - 39789 -      ?        00:00:01 opensips
>> 5 S     0 22830     1  0  80   0 - 36876 -      ?        00:00:00 opensips
>> 1 S     0 22833 22830  0  80   0 - 36876 -      ?        00:00:00 opensips
>> 1 S     0 22834 22830  0  80   0 - 36876 -      ?        00:00:00 opensips
>> 1 S     0 22835 22830  0  80   0 - 36876 -      ?        00:00:00 opensips
>> 1 S     0 22838 22830  0  80   0 - 36878 -      ?        00:00:00 opensips
>> 1 S     0 22840 22830  0  80   0 - 36876 -      ?        00:00:01 opensips
>> 1 S     0 22844 22830  0  80   0 - 36876 -      ?        00:00:01 opensips
>> 1 R     0 22846 22830  6  80   0 - 36876 -      ?        00:01:56 opensips
>> 1 S     0 22847 22830  8  80   0 - 36876 -      ?        00:02:28 opensips
>> 1 R     0 22849 22830  6  80   0 - 36876 -      ?        00:01:58 opensips
>> 1 S     0 22852 22830  8  80   0 - 36876 -      ?        00:02:30 opensips
>> 1 R     0 22855 22830  6  80   0 - 36876 -      ?        00:01:57 opensips
>> 1 R     0 22858 22830  8  80   0 - 36876 -      ?        00:02:27 opensips
>> 1 S     0 22862 22830  8  80   0 - 36876 -      ?        00:02:27 opensips
>> 1 R     0 22864 22830  6  80   0 - 36909 -      ?        00:01:56 opensips
>> 1 S     0 22869 22830  8  80   0 - 36876 -      ?        00:02:27 opensips
>> 1 S     0 22872 22830  6  80   0 - 36876 -      ?        00:01:58 opensips
>> 1 S     0 22875 22830  6  80   0 - 36876 -      ?        00:01:57 opensips
>> 1 S     0 22878 22830  6  80   0 - 36876 -      ?        00:01:58 opensips
>> 1 S     0 22879 22830  6  80   0 - 36876 -      ?        00:01:57 opensips
>> 1 S     0 22884 22830  6  80   0 - 36876 -      ?        00:01:58 opensips
>> 1 S     0 22887 22830  3  80   0 - 36876 -      ?        00:01:05 opensips
>> 1 S     0 22889 22830  6  80   0 - 36876 -      ?        00:01:57 opensips
>> 1 S     0 22892 22830  6  80   0 - 36876 -      ?        00:01:57 opensips
>> 1 S     0 22895 22830  3  80   0 - 36876 -      ?        00:00:53 opensips
>> 1 S     0 22899 22830  6  80   0 - 36876 -      ?        00:01:57 opensips
>> 1 S     0 22902 22830  6  80   0 - 36876 -      ?        00:01:57 opensips
>>
>> CTRL+C does not seem to stop the warnings.
>> I had to kill the opensips to restart it.
>>
>> Any help in this regard.
>>
>> Best Regards.
>>
>>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160122/af694528/attachment-0001.htm>


More information about the Users mailing list