[asterisk-bugs] [Asterisk 0016754]: Multiple segfaults in leave_voicemail at app_voicemail.c:4451 Asterisk 1.4.29

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16754 
====================================================================== 
Reported By:                aragon
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16754
Category:                   Applications/app_voicemail
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.29 
JIRA:                       SWP-844 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-02 13:08 CST
Last Modified:              2010-02-05 09:47 CST
====================================================================== 
Summary:                    Multiple segfaults in leave_voicemail at
app_voicemail.c:4451 Asterisk 1.4.29
Description: 
Asterisk 1.4.27 was locking at leave_voicemail and after upgrading to
1.4.29 in a desperate attempt to clear the locking Asterisk 1.4.29 started
segfaulting every 2 or 3 minutes.  I had to downgrade to 1.4.27 to prevent
the segfaults.
Here is the evidence of the lock in the ast CLI
app.c: Failed to lock path
'/var/spool/asterisk/voicemail/customer/3329/INBOX': File exists.
The permissions on this folder look normal.
Under 1.4.27 core show locks was useless, core show channels was useless.
When voicemail directories start locking htop showed CPU utilization at
300 where normal load is about 1 on 1.4.27

Attaching Asterisk CLI history.
Ran 1.4.29 under Valgrind for a few minutes until it crashed so I could
upload valgrind capture.
Uploading gdb file with bt, bt full, thread apply all bt full
I believe that while Asterisk was locked on mailbox leaving a message in
mailbox 3329 caused the segfault.  Other mailboxes display similar locking
symptoms in Asterisk CLI.


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

---------------------------------------------------------------------- 
 (0117789) aragon (reporter) - 2010-02-05 09:47
 https://issues.asterisk.org/view.php?id=16754#c117789 
---------------------------------------------------------------------- 
channel.c:946 __ast_queue_frame: Exceptionally long voice queue length
queuing to Local/6010 at default-local-voicemail-d3b2,2

These warnings are generated constantly while the caller is speaking into
the voicemail box to leave a message in a voicemail INBOX with a .lock file
in its directory.
For this reason I think this bug is a result of the fix for bug
https://issues.asterisk.org/view.php?id=15609 so
I think this is a regression.  Since this bug is also results in a segfault
every time Linux or Asterisk (I don't know which) writes a .lock file to a
mailbox INBOX folder and a caller tries to leave a message in that folder I
think this issue should also be a block.  I cannot put 1.4.29 into
production because of this issue.

I have no idea why the .lock is written in the first place but manually
creating the .lock file is enough to easily reproduce the segfault. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-05 09:47 aragon         Note Added: 0117789                          
======================================================================