[Home]

Summary:ASTERISK-15613: Failure of canary
Reporter:Scott Johnson (globalnetinc)Labels:
Date Opened:2010-02-11 13:20:37.000-0600Date Closed:2010-02-11 19:07:00.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) gdb.txt
Description:After upgrade to 1.6.2.3-rc2 from 1.6.2.1 most times on restart of the asterisk PBX we see this error:
asterisk.c: The canary is no more.  He has ceased to be!  He's expired and gone to meet his maker!  He's a stiff!  Bereft of life, he rests in peace.
Comments:By: Scott Johnson (globalnetinc) 2010-02-11 14:13:08.000-0600

This error appears almost every time a T.38 call is placed. That has no T.38 defined for that extension.  The lack of T.38 is by design.  These are extensions we do not want T.38 on.  The is all new behavior with this version.

[Feb 11 12:24:58] WARNING[3041]: asterisk.c:3050 canary_thread: The canary is no more.  He has ceased to be!  He's expired and gone to meet his maker!  He's a stiff!  Bereft of life, he rests in peace.  His metabo)
[Feb 11 12:27:01] WARNING[3070]: chan_sip.c:8291 process_sdp: Unsupported SDP media type in offer: image 16472 udptl t38
[Feb 11 12:27:01] NOTICE[3070]: chan_sip.c:8412 process_sdp: No compatible codecs, not accepting this offer!
[Feb 11 12:32:53] NOTICE[3070]: chan_sip.c:20357 handle_request_invite: Unable to create/find SIP channel for this INVITE
myphone*CLI>
Disconnected from Asterisk server
Asterisk ended with exit status 139
Asterisk exited on signal EXITSTATUS-128.

By: Leif Madsen (lmadsen) 2010-02-11 14:29:44.000-0600

Sounds like a crash. Someone else was reporting crashes with T.38 as well on the mailing list. Are you able to provide additional information such as a backtrace? (per doc/backtrace.txt in the Asterisk source).

By: Tilghman Lesher (tilghman) 2010-02-11 14:41:33.000-0600

Sounds like a crash that was fixed in revision 245732, issue ASTERISK-15251.

By: Scott Johnson (globalnetinc) 2010-02-11 15:40:59.000-0600

You have your backtrace

By: Scott Johnson (globalnetinc) 2010-02-11 17:22:32.000-0600

As I do not use app_fax I do not know how patching it would fix the issue.

By: Scott Johnson (globalnetinc) 2010-02-11 17:24:12.000-0600

Also that patch is already in 1.6.2.3-rc2