[asterisk-bugs] [Asterisk 0016198]: WARNING channel.c __ast_channel_alloc_ap: Channel allocation failed: Can't create alert pipe!

[Asterisk Bug Tracker]

The following issue has been ASSIGNED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16198 
====================================================================== 
Reported By:                atis
Assigned To:                lmadsen
====================================================================== 
Project:                    Asterisk
Issue ID:                   16198
Category:                   Documentation
Reproducibility:            random
Severity:                   text
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-06 10:24 CST
Last Modified:              2009-11-09 09:36 CST
====================================================================== 
Summary:                    WARNING channel.c __ast_channel_alloc_ap: Channel
allocation failed: Can't create alert pipe!
Description: 
When spooling a lot of calls through pbx_spool, Asterisk sometimes starts
to fail:

    -- Attempting call on Local/8006772943 at did-dial for
8006772943 at did-out:1 (Retry 1)
[Nov  6 07:47:57] WARNING[14063]: channel.c:830 __ast_channel_alloc_ap:
Channel allocation failed: Can't create alert pipe!
[Nov  6 07:47:57] WARNING[14063]: chan_local.c:732 local_new: Unable to
allocate channel structure(s)                          
[Nov  6 07:47:57] NOTICE[14063]: channel.c:3785 __ast_request_and_dial:
Unable to request channel Local/8006772943 at did-dial                 
[Nov  6 07:47:57] NOTICE[14063]: pbx_spool.c:338 attempt_thread: Call
failed to go through, reason (0) Call Failure (not BUSY, and not NO_ANSWER,
maybe Circuit busy or down?)


====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-09 09:36 lmadsen        Status                   feedback => assigned
2009-11-09 09:36 lmadsen        Assigned To               => lmadsen         
======================================================================