asterisk users - Nov 2005 - Warning -- chan_iax2.c: ast_sched_runq tasks

I've started to see this lately on outgoing IAX calls using CVS Head:

    -- IAX2/voipjet-out-5 is making progress passing it to 
SIP/64.26.157.252-094e4058
    -- IAX2/voipjet-out-6 is making progress passing it to 
SIP/64.26.157.252-094e4058
Nov  2 16:56:15 WARNING[22566]: chan_iax2.c:7948 network_thread: 
chan_iax2: ast_sched_runq ran 2502 scheduled tasks all at once
Nov  2 16:56:15 WARNING[22566]: chan_iax2.c:7948 network_thread: 
chan_iax2: ast_sched_runq ran 3131 scheduled tasks all at once
Nov  2 16:56:15 WARNING[22566]: chan_iax2.c:7948 network_thread: 
chan_iax2: ast_sched_runq ran 3074 scheduled tasks all at once
    -- IAX2/voipjet-out-6 answered SIP/64.26.157.252-094e4058

Any interpretation?

MARK.

> I've started to see this lately on outgoing IAX calls using CVS Head:
> 
>     -- IAX2/voipjet-out-5 is making progress passing it to 
> SIP/64.26.157.252-094e4058
>     -- IAX2/voipjet-out-6 is making progress passing it to 
> SIP/64.26.157.252-094e4058
> Nov  2 16:56:15 WARNING[22566]: chan_iax2.c:7948 network_thread: 
> chan_iax2: ast_sched_runq ran 2502 scheduled tasks all at once
> Nov  2 16:56:15 WARNING[22566]: chan_iax2.c:7948 network_thread: 
> chan_iax2: ast_sched_runq ran 3131 scheduled tasks all at once
> Nov  2 16:56:15 WARNING[22566]: chan_iax2.c:7948 network_thread: 
> chan_iax2: ast_sched_runq ran 3074 scheduled tasks all at once
>     -- IAX2/voipjet-out-6 answered SIP/64.26.157.252-094e4058
> 
> Any interpretation?
The above would suggest a _very_ busy box. Any idea how many calls
were in progress during this?

Some of the folks on the -dev list might be interested in seeing
the above numbers, so I'll cross-post my response over there as
well.

Rich

Ok.  It seems my calls are completing ok.

MARK.

Rich Adamson wrote:
> Steve committed the source code changes to cvs-head to display these
> numbers, and I believe he was working on jitterbuffer or codec stuff.
> He has since posted an item that he wished he would not have done that
> as its generating lots of questions.
> 
> His thought process was something along the lines that if too many
> tasks are in the secheduler, then servicing the code he was playing
> with might not occur in the time frames that one might expect. So he
> dumped those lines of code in there to find out. Since there is no
> other data, no one knows what those other scheduled tasks might be,
> so there's no way to answer the question of 'what's going
on'.
> 
> Just ignore the item for now.
> 
> Rich
> 
> ------------------------
>   From: Mark Hulber <asterisk-admin@hulber.com>
>   Subject: Re: [Asterisk-Users] Warning -- chan_iax2.c: ast_sched_runq
tasks
>   Date: Wed, 02 Nov 2005 17:50:28 -0500 
>   To: Rich Adamson <radamson@routers.com>
> 
> 
>> Not busy at all.  Like these were the only calls in progress at the
time.
>>
>> MARK.
>>
>> Rich Adamson wrote:
>>>> I've started to see this lately on outgoing IAX calls using
CVS Head:
>>>>
>>>>     -- IAX2/voipjet-out-5 is making progress passing it to 
>>>> SIP/64.26.157.252-094e4058
>>>>     -- IAX2/voipjet-out-6 is making progress passing it to 
>>>> SIP/64.26.157.252-094e4058
>>>> Nov  2 16:56:15 WARNING[22566]: chan_iax2.c:7948
network_thread:
>>>> chan_iax2: ast_sched_runq ran 2502 scheduled tasks all at once
>>>> Nov  2 16:56:15 WARNING[22566]: chan_iax2.c:7948
network_thread:
>>>> chan_iax2: ast_sched_runq ran 3131 scheduled tasks all at once
>>>> Nov  2 16:56:15 WARNING[22566]: chan_iax2.c:7948
network_thread:
>>>> chan_iax2: ast_sched_runq ran 3074 scheduled tasks all at once
>>>>     -- IAX2/voipjet-out-6 answered SIP/64.26.157.252-094e4058
>>>>
>>>> Any interpretation?
>>> The above would suggest a _very_ busy box. Any idea how many calls
>>> were in progress during this?
>>>
>>> Some of the folks on the -dev list might be interested in seeing
>>> the above numbers, so I'll cross-post my response over there as
>>> well.
>>>
>>> Rich
>>>
>>>
> 
> ---------------End of Original Message-----------------
> 
>