Summary:ASTERISK-28453: Voicemail: Failed to Lock Path: File Exists
Reporter:Luke Escude (lukeescude)Labels:
Date Opened:2019-06-18 09:29:49Date Closed:2019-06-18 09:34:52
Versions:16.3.0 Frequency of
is related toASTERISK-20207 Asterisk should clear out any .lock files in the voice mail directory on startup.
Environment:CentOS x64Attachments:
Description:Hello, we're having to occasionally restart (core restart now) a customer's PBX due to their lack of ability to access voicemail.

After entering voicemail, the CLI just shows the following error:

WARNING[24979][C-00000059]: app.c:2256 ast_lock_path_lockfile: Failed to lock path '/var/spool/asterisk/voicemail/voicemail/2299/INBOX': File exists

I don't see any .lock files in any of their voicemail directories, so maybe there's something else I need to look for?

Comments:By: Asterisk Team (asteriskteam) 2019-06-18 09:29:50.434-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

By: Luke Escude (lukeescude) 2019-06-18 09:33:05.979-0500

So it turns out I wasn't looking for hidden files properly - I found the .lock, removed it, and the issue is fixed.

We never had this issue with Asterisk 13 though, so maybe a bug still exists?

By: Joshua C. Colp (jcolp) 2019-06-18 09:34:52.413-0500

It was always possible for the problem to exist, and due to a change done in ASTERISK-20207 will now clean up the lock files on module load as of 16.4.0.