This problem has been discussed, but not answered some years ago. Today i ran the update on the ocsreport server and it's now reporting back that /var/lib/ocsinventory-reports/logs is not writable. SElinux is off, and the route to the directory is all either 777 permissions or owned by www-data:www-data so there's no reason at all for it to not be writable. Also, to compound the issue, it doesn't seem to matter if I change the log directory to be /var/ocsreports/logs, it still reports back that /var/lib/ocsinventory-reports/logs is not writable.
SELinux is permissive, so warning only, effectively off.
The 777 to the directory was simply a sledgehammer to ensure it was writeable, and yet OCSinventory still thinks it is not writable.
OCSinventory was installed using the setup.sh, and it was not complaining about the un-writable directory until I ran the update from the OCSinventory website.
It's running on Ubuntu 20.04LTS
The User is an interesting idea, the software installed under /opt/OCSREPORT is a mess, I'll need to sort that out, it is part owned by my own username, part by root, which does not look good. What do you mean the "user and group from Debian?"
thanks for your help