Post a Reply
1390 views

unable to lock path

  1. 7 years ago

    AlexRS

    28 Dec 2016
    Edited 7 years ago by AlexRS

    When I try to remove voicemail message, I receive
    Cannot move/delete messages: Unable to lock path.

    How can I remove it without locking?

    Answered by admin

    See post in context

    If your voicemail path is not standard, you will find to set it correctly in /usr/local/fop2/fop2.cfg. If that is already done, then you might have issues with file creation on your CIF share, in order to manipulate voicemails a lock file is created on the same voicemail directory, that is unavoidable, and it is safe.. If your system gives you that error, it means it is not allowed to write the lock file (lack of write permissions on file or execute permission on path).

    Best regards,

  2. admin

    28 Dec 2016 Administrator

    seems you have write permissions problems on the spool voicemail directory. Perhaps your voicemail directory is not the default or correctly defined?

  3. AlexRS

    28 Dec 2016

    The directory is default, but I have separetely installed Fop2 and the directory is mounted by cifs. In my case nfs is no option for us. But its no problem to remove files from it by console.

  4. admin

    29 Dec 2016 Administrator Answer
    Edited 7 years ago by admin

    If your voicemail path is not standard, you will find to set it correctly in /usr/local/fop2/fop2.cfg. If that is already done, then you might have issues with file creation on your CIF share, in order to manipulate voicemails a lock file is created on the same voicemail directory, that is unavoidable, and it is safe.. If your system gives you that error, it means it is not allowed to write the lock file (lack of write permissions on file or execute permission on path).

    Best regards,

  5. AlexRS

    29 Dec 2016
    Edited 7 years ago by AlexRS

    Its strange. I thinked you use something like flock().. Yes, I already did this. I see voicemail, can play it and download. But cannot move or remove.
    I set all (777) permissions on the directory and files in this directory. If my file is

    /var/spool/asterisk/voicemail/sip_viocemail/100/INBOX/msg0000.wav

    Where and what lock file will be created? From /var/spool/asterisk/voicemail/sip_viocemail/100 und up all 777 permissions, as I sad before.

  6. AlexRS

    29 Dec 2016
    Edited 7 years ago by AlexRS

    My problem was in permission to create link from .lock-xxxx to .lock

    Now after deleting voice messages the lock files is not removed and used by fop2 (I cant remove them manually by rm unless restart fop2). What fop2 waiting for?

    As I see in log, it was twice opened and ones closed. I cant remove .lock-xxxx bacause its opened for 'write only' by fop2.

    This was solved by remove 'cache=no' from fstab.
    Now all works fine.

or Sign Up to reply!