[Home]

Summary:ASTERISK-11585: WARNING Messege
Reporter:Thiago Garcia (thiagarcia)Labels:
Date Opened:2008-03-05 19:21:31.000-0600Date Closed:2008-03-07 11:14:43.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_iax2
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) debug.log
Description:After upgraded the asterisk to SVN-branch-1.4-r106237 because the bug ASTERISK-1207145, in console appeared this warning, and sometimes the channel remains open.

WARNING[7508]: chan_iax2.c:2570 schedule_delivery: Unable to cancel schedule ID 16809.  This is probably a bug (chan_iax2.c: schedule_delivery, line 2570).
WARNING[7509]: chan_iax2.c:2570 schedule_delivery: Unable to cancel schedule ID 13540.  This is probably a bug (chan_iax2.c: schedule_delivery, line 2570).
WARNING[7507]: chan_iax2.c:2570 schedule_delivery: Unable to cancel schedule ID 13573.  This is probably a bug (chan_iax2.c: schedule_delivery, line 2570).


****** ADDITIONAL INFORMATION ******

    -------------
Our scenario:
-------------
extensions prococol: IAX2
softphone: IDEFISK
softphone codec: ALAW/GSM/ULAW
* Server are compiled with DONT_OPTIMIZE, DEBUG_THREADS and MALLOC_DEBUG options.
-------------

---------------------
Hardware Description:
---------------------

Server :
-Intel(R) Core(TM)2 Duo CPU
-Digium TE110P card
-Digium TDM2400 (with 6 FXS modules)
-Digium TDM400P (with 4 FXO modules)

---------------------
Software Description:
---------------------

Slackware 12 kernel 2.6.23.17

Asterisk SVN-branch-1.4-r106237
Zaptel SVN-branch-1.4-r3939
Libpri SVN-branch-1.4-r528
Comments:By: Thiago Garcia (thiagarcia) 2008-03-05 19:26:05.000-0600

That occurs when a call is blind transfered.
By: Badalian Vyacheslav (slavon) 2008-03-06 00:21:51.000-0600

Great... after patch (http://bugs.digium.com/view.php?id=12140) you may look where delete not exists sch =)

look also there (in 1.4 SVN):
[Mar  6 09:22:30] WARNING[24091]: rtp.c:2047 ast_rtp_stop: Unable to cancel schedule ID 0.  This is probably a bug (rtp.c: ast_rtp_stop, line 2047).
and there:
[Mar  6 09:22:36] WARNING[23887]: rtp.c:2151 ast_rtp_destroy: Unable to cancel schedule ID 0.  This is probably a bug (rtp.c: ast_rtp_destroy, line 2151).

1.6 svn last have only this warnings:
[Mar  6 09:21:12] WARNING[22226]: rtp.c:2381 ast_rtp_stop: Unable to cancel schedule ID 0.  This is probably a bug (rtp.c: ast_rtp_stop, line 2381).

many messages...
i think need to rename bugreport and catch all wrong deleted schedule =)
By: Mike Anikienko (mike anikienko) 2008-03-07 06:48:37.000-0600

I see same messages in SIP.
before incoming call and after blind transer:
[Mar  7 15:44:13] WARNING[5789]: rtp.c:2511 ast_rtp_destroy: Unable to cancel schedule ID 0.  This is probably a bug (rtp.c: ast_rtp_destroy, line 2511)
and after hangup:
[Mar  7 15:42:41] WARNING[5789]: rtp.c:2381 ast_rtp_stop: Unable to cancel schedule ID 0.  This is probably a bug (rtp.c: ast_rtp_stop, line 2381).

SVN-trunk-r106553M
By: Digium Subversion (svnbot) 2008-03-07 09:17:01.000-0600

Repository: asterisk
Revision: 106606

U   branches/1.4/main/rtp.c

------------------------------------------------------------------------
r106606 | tilghman | 2008-03-07 09:16:59 -0600 (Fri, 07 Mar 2008) | 3 lines

Properly initialize rtp->schedid
(Closes issue ASTERISK-11585)

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=106606
By: Digium Subversion (svnbot) 2008-03-07 09:18:44.000-0600

Repository: asterisk
Revision: 106607

_U  trunk/
U   trunk/main/rtp.c

------------------------------------------------------------------------
r106607 | tilghman | 2008-03-07 09:18:44 -0600 (Fri, 07 Mar 2008) | 11 lines

Merged revisions 106606 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r106606 | tilghman | 2008-03-07 09:20:52 -0600 (Fri, 07 Mar 2008) | 3 lines

Properly initialize rtp->schedid
(Closes issue ASTERISK-11585)

........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=106607
By: Digium Subversion (svnbot) 2008-03-07 09:20:12.000-0600

Repository: asterisk
Revision: 106608

_U  branches/1.6.0/
U   branches/1.6.0/main/rtp.c

------------------------------------------------------------------------
r106608 | tilghman | 2008-03-07 09:20:11 -0600 (Fri, 07 Mar 2008) | 19 lines

Merged revisions 106607 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk

................
r106607 | tilghman | 2008-03-07 09:22:34 -0600 (Fri, 07 Mar 2008) | 11 lines

Merged revisions 106606 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r106606 | tilghman | 2008-03-07 09:20:52 -0600 (Fri, 07 Mar 2008) | 3 lines

Properly initialize rtp->schedid
(Closes issue ASTERISK-11585)

........

................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=106608
By: Thiago Garcia (thiagarcia) 2008-03-07 10:41:36.000-0600

This issue also occurs with channels IAX.
After upgraded asterisk to SVN-branch-1.4-r106606.

[Mar  7 13:33:47] WARNING[9224]: chan_iax2.c:2411 update_jbsched: Unable to cancel schedule ID 51048.  This is probably a bug (chan_iax2.c: update_jbsched, line 2411).
[Mar  7 13:33:58] WARNING[9225]: chan_iax2.c:2411 update_jbsched: Unable to cancel schedule ID 52188.  This is probably a bug (chan_iax2.c: update_jbsched, line 2411).
[Mar  7 13:37:27] WARNING[9216]: chan_iax2.c:2411 update_jbsched: Unable to cancel schedule ID 65941.  This is probably a bug (chan_iax2.c: update_jbsched, line 2411).

Thanks.
By: Digium Subversion (svnbot) 2008-03-07 11:13:14.000-0600

Repository: asterisk
Revision: 106704

U   branches/1.4/include/asterisk/sched.h

------------------------------------------------------------------------
r106704 | russell | 2008-03-07 11:13:13 -0600 (Fri, 07 Mar 2008) | 8 lines

Change a warning message to a debug message.  This is happening quite frequently,
and it is not worth spamming users with these messages unless we are pretty confident
that it should never happen.  As it stands today, it _will_ and _does_ happen and
until that gets cleaned up a reasonable amount on the development side, let's not
spam the logs of everyone else.

(closes issue ASTERISK-11585)

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=106704
By: Digium Subversion (svnbot) 2008-03-07 11:13:39.000-0600

Repository: asterisk
Revision: 106707

_U  trunk/
U   trunk/include/asterisk/sched.h

------------------------------------------------------------------------
r106707 | russell | 2008-03-07 11:13:39 -0600 (Fri, 07 Mar 2008) | 16 lines

Merged revisions 106704 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r106704 | russell | 2008-03-07 11:16:58 -0600 (Fri, 07 Mar 2008) | 8 lines

Change a warning message to a debug message.  This is happening quite frequently,
and it is not worth spamming users with these messages unless we are pretty confident
that it should never happen.  As it stands today, it _will_ and _does_ happen and
until that gets cleaned up a reasonable amount on the development side, let's not
spam the logs of everyone else.

(closes issue ASTERISK-11585)

........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=106707
By: Digium Subversion (svnbot) 2008-03-07 11:14:43.000-0600

Repository: asterisk
Revision: 106713

_U  branches/1.6.0/
U   branches/1.6.0/include/asterisk/sched.h

------------------------------------------------------------------------
r106713 | russell | 2008-03-07 11:14:42 -0600 (Fri, 07 Mar 2008) | 24 lines

Merged revisions 106707 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk

................
r106707 | russell | 2008-03-07 11:17:30 -0600 (Fri, 07 Mar 2008) | 16 lines

Merged revisions 106704 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r106704 | russell | 2008-03-07 11:16:58 -0600 (Fri, 07 Mar 2008) | 8 lines

Change a warning message to a debug message.  This is happening quite frequently,
and it is not worth spamming users with these messages unless we are pretty confident
that it should never happen.  As it stands today, it _will_ and _does_ happen and
until that gets cleaned up a reasonable amount on the development side, let's not
spam the logs of everyone else.

(closes issue ASTERISK-11585)

........

................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=106713