Error message in fs_cli permission denied

[Andrew Byrd]

I see this message about every 3 or 4 lines in the cli. Can anyone shed some light on this and what it means?


2019-07-10 20:04:33.786263 [ERR] switch_cpp.cpp:1365 [cache] can not write file `/var/cache/fusionpbx/directory.1001@fpbx1.npusa.us.ef871fb0-a34d-11e9-b3c3-2bcb8950d720.tmp`: /var/cache/fusionpbx/directory.1001@fpbx1.npusa.us.ef871fb0-a34d-11e9-b3c3-2bcb8950d720.tmp: Permission denied

 

[smn]

mkdir -p /var/cache/fusionpbx
chown -R www-data. /var/cache/fusionpbx

 

[TimGuyUK]

I have had this issue on Centos, for me the user was freeswitch.

mkdir -p /var/cache/fusionpbx
chown -R freeswitch /var/cache/fusionpbx

 

[JamesBorne]

for me the user was freeswitch

The Systemd entry for FusionPBX starts Freeswitch as user www-data to be consistent with accessing web resources.

Not sure how it would be that for yourself.

 

[TimGuyUK]

No idea. Default centos 7 basic install, www-data comes back with invalid user. I listed the users, saw freeswitch, tried it, it worked, log error went away.

Tim

 

[TimGuyUK]

Would you believe while trying to get the letsencrypt script working to install a wildcart I got www-data user errors. Apparently 'apache' is the preferred replacement to www-data for Centos, www-data not being there. Modifying the script got me further but I think the Centos folder layout still stops the script running as Ive got losts of missing folders and files. shame

Tim

 

[smn]

No idea. Default centos 7 basic install, www-data comes back with invalid user. I listed the users, saw freeswitch, tried it, it worked, log error went away.

Tim

The "www-data" user is the default used in Debian/Ubuntu, not CentOS. I think the fusion script makes the user "freeswitch" for CentOS.

 

[TimGuyUK]

The "www-data" user is the default used in Debian/Ubuntu, not CentOS. I think the fusion script makes the user "freeswitch" for CentOS.

Yes its freeswitch, in trying to get letsencrypt working with the script I came across it.

 

[simoNZ]

I have this on a Debian install also (Stretch). Notably this Fusion install has been continuously updated starting on 4.2.2, now running on master.
Although no call issues were noted, the adding of the directory and owner/permissions has stopped error logs from appearing.