|Summary:||ASTERISK-14137: crash in voicemail when more than maxmsg already stored in folder|
|Reporter:||Stéphane Berthelot (sberthelot)||Labels:|
|Date Opened:||2009-05-15 05:31:59||Date Closed:||2009-11-19 11:15:55.000-0600|
|Description:||I've looked into the voicemail bug reports and did not find this one, so I hope it's not duplicate (since it's very trivial)|
I have installed asterisk 18.104.22.168-beta2
It was an upgrade from a 1.4.x system but I don't think it's relevant here.
There were some voicemail boxes with a lot of messages (around 60-80) and I wanted to use the upgrade to also set a maxmsg count in voicemail.conf (I've put maxmsg=20 in voicemail.conf, previously it was commented)
I have asked my users to purge their boxes and when they go to the maxmsg+1 th message asterisk crashes !
Nothing specific in debug or full log more than :
[May 15 12:09:42] WARNING app_voicemail.c: No message attribute file?!! (/var/spool/asterisk/voicemail/default/212/Old/msg0019.txt)
It's always reproducible until I empty their voicemail boxes by hand on the filesystem.
I know that setting the value lower than the count of messages in a box could make some messages unreadable but certainly not to a complete asterisk crash!
I suspect that on a running system (without upgrading asterisk) lowering maxmsg with voicemail boxes having more than the new value may lead to an unwanted crash. I know it's a corner case but it should get treated correctly in app_voicemail according to me ...
|Comments:||By: Leif Madsen (lmadsen) 2009-05-19 13:29:27|
Please reproduce the issue with DONT_OPTIMIZE enabled in menuselect, reinstall Asterisk, reproduce the issue, then provide a backtrace by following the documentation in doc/backtrace.txt of your Asterisk source. Thanks!
By: Leif Madsen (lmadsen) 2009-06-16 14:08:34
Assigned to dbrooks.
Think you could try reproducing this, and if so, see if you can determine a fix? Thanks!
By: David Brooks (dbrooks) 2009-06-25 13:42:00
I have attempted to reproduce this issue with 1.4SVN, but am unable to. I've tried with maxmsg -1, maxmsg, and maxmsg +1 in both INBOX and Old, but no crash has occurred.
By: Leif Madsen (lmadsen) 2009-06-29 11:26:28
dbrooks: this issue is reported against Asterisk-22.214.171.124-beta2. Could you try reproducing with that issue? If you can reproduce it, can you update to 1.6.2 branch (latest) and try again. If it does not crash in the same test, close this issue. If you can reproduce it, then mark this as Acknowledged.
By: David Brooks (dbrooks) 2009-06-29 15:19:51
lmadsen: sorry, I don't know what I was thinking, testing with 1.4. Anyway, I just tried to recreate with 126.96.36.199-beta2, but was still unable to reproduce the issue.
By: Leif Madsen (lmadsen) 2009-07-01 07:53:05
Sorry, it seems we are unable to reproduce the issue. If you are able to provide more information about this issue that can lead to successfully reproducing the problem (or a patch to fix it!) then please reopen the issue. Thanks!