New folders created in the /Data/Recordings have the wrong owner (Debian)

Status
Not open for further replies.

advantagevoice

Silver Partner
Basic Certified
Joined
Apr 19, 2021
Messages
11
Reaction score
2
One of my customers complained that many of their users are not able to download the call recordings. They get a 404 (resource not found) error. I looked at the media server log and found entries like this:
Recording cancelled. Failed to open file "/var/lib/3cxpbx/Instance1/Data/Recordings/531/[Inbound%3A19084741200]_19084741200-531_20210603134739(139150).wav" for writing

When I checked the Recordings folder, about half of the folders had root:root as the owner instead of phonesystem : phonesystem. I did a recursive chown on the Recordings folder to set it to phonesystem : phonesystem. However, when I created a new test user and made a call, the new folder for it came up as root:root.

Need help finding a fix to this.
Please let me know if you need more information.

Thanks!
 
Last edited by a moderator:
We are using a 3rd party tool by VOIP Tools in order to get custom white boards and a few other features. One of them includes a 3rd party call recording manager. However, all it does is copy the wav files to an off-site server. It isn't writing at all, and I confirmed with the developers that their app does not change permissions in any way. This makes sense as brand new folders in the /Recordings folder are created with the wrong ownership. (As opposed to being created with phonesystem:phonesystem as the owner and later changed to root:root.

I'll try changing the folder this weekend (have to wait until Sunday so they aren't live) and see what happens.
 
  • Like
Reactions: VasilisV_3CX
@advantagevoice,

No problem, let me know the outcome when you've finished and tested.
 
@advantagevoice,

No problem, let me know the outcome when you've finished and tested.
I didn't get a chance to yet. I'm going to try this Sunday.
In the meantime, I set up an hourly cron job to chown the Recordings directory as a workaround until it is fixed.
 
  • Like
Reactions: VasilisV_3CX
Status
Not open for further replies.