Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specified directory "..." exists, but is not writable See Note 2. #620

Open
curtishall opened this issue Nov 15, 2023 · 0 comments
Open
Assignees

Comments

@curtishall
Copy link
Member

When adding any storage, even the default /var/lib/bluecherry/recordings this error is shown:

Specified directory "/var/lib/bluecherry/recordings" exists, but is not writable See Note 2.

The output of the check_dir_permission.sh shows -wrx, so it should be writeable...however the PHP code indicates it is not.

Output of check_dir_permissions.sh:

www-data@2639774e211f:~$ /usr/share/bluecherry/scripts/check_dir_permission.sh /media/test
-wrx

Function:

https://github.com/bluecherrydvr/bluecherry-apps/blob/592e8757efe484722f5ed5c948e8c8d1d17c61ce/www/ajax/storagecheck.php#L38C7-L40C10

andrey-utkin added a commit to andrey-utkin/bluecherry-docker that referenced this issue Nov 24, 2023
Issue bluecherrydvr/bluecherry-apps#620
arises because the dir exists, is owned by bluecherry:bluecherry, but is
by default writable only by owning user, but not the owning group.

Fix this here in docker setup code.
bluecherry-apps code will be amended to handle this, too.
andrey-utkin added a commit to andrey-utkin/bluecherry-docker that referenced this issue Nov 24, 2023
Issue bluecherrydvr/bluecherry-apps#620
arises because the dir exists, is owned by bluecherry:bluecherry, but is
by default writable only by owning user, but not the owning group.

Fix this here in docker setup code.
bluecherry-apps code will be amended to handle this, too.

root@df79d5606903:~# sudo -u www-data php -r "echo is_writable('/var/lib/bluecherry/recordings') ? 'writable' : 'not writable';"; echo
not writable
root@df79d5606903:~# sudo -u www-data touch /var/lib/bluecherry/recordings/www-data.was.here
touch: cannot touch '/var/lib/bluecherry/recordings/www-data.was.here': Permission denied
root@df79d5606903:~# id
uid=0(root) gid=0(root) groups=0(root)
root@df79d5606903:~# id www-data
uid=33(www-data) gid=33(www-data) groups=33(www-data),4(adm),20(dialout),29(audio),44(video),999(bluecherry)
root@df79d5606903:~# ls -l /var/lib/bluecherry/recordings -d
drwxr-xr-x 2 bluecherry bluecherry 4096 Nov 24 00:36 /var/lib/bluecherry/recordings
root@df79d5606903:~# chmod g+w /var/lib/bluecherry/recordings
root@df79d5606903:~# ls -l /var/lib/bluecherry/recordings -d
drwxrwxr-x 2 bluecherry bluecherry 4096 Nov 24 00:36 /var/lib/bluecherry/recordings
root@df79d5606903:~# sudo -u www-data touch /var/lib/bluecherry/recordings/www-data.was.here
root@df79d5606903:~# sudo -u www-data php -r "echo is_writable('/var/lib/bluecherry/recordings') ? 'writable' : 'not writable';"; echo
writable
andrey-utkin added a commit to andrey-utkin/bluecherry-docker that referenced this issue Nov 24, 2023
Issue bluecherrydvr/bluecherry-apps#620
arises because the dir exists, is owned by bluecherry:bluecherry, but is
by default writable only by owning user, but not the owning group.

Fix this here in docker setup code.
bluecherry-apps code will be amended to handle this, too.

root@df79d5606903:~# sudo -u www-data php -r "echo is_writable('/var/lib/bluecherry/recordings') ? 'writable' : 'not writable';"; echo
not writable
root@df79d5606903:~# sudo -u www-data touch /var/lib/bluecherry/recordings/www-data.was.here
touch: cannot touch '/var/lib/bluecherry/recordings/www-data.was.here': Permission denied
root@df79d5606903:~# id
uid=0(root) gid=0(root) groups=0(root)
root@df79d5606903:~# id www-data
uid=33(www-data) gid=33(www-data) groups=33(www-data),4(adm),20(dialout),29(audio),44(video),999(bluecherry)
root@df79d5606903:~# ls -l /var/lib/bluecherry/recordings -d
drwxr-xr-x 2 bluecherry bluecherry 4096 Nov 24 00:36 /var/lib/bluecherry/recordings
root@df79d5606903:~# chmod g+w /var/lib/bluecherry/recordings
root@df79d5606903:~# ls -l /var/lib/bluecherry/recordings -d
drwxrwxr-x 2 bluecherry bluecherry 4096 Nov 24 00:36 /var/lib/bluecherry/recordings
root@df79d5606903:~# sudo -u www-data touch /var/lib/bluecherry/recordings/www-data.was.here
root@df79d5606903:~# sudo -u www-data php -r "echo is_writable('/var/lib/bluecherry/recordings') ? 'writable' : 'not writable';"; echo
writable
andrey-utkin added a commit to andrey-utkin/bluecherry-apps that referenced this issue Nov 24, 2023
Issue bluecherrydvr#620
arises because the dir exists, is owned by bluecherry:bluecherry, but is
by default writable only by owning user, but not the owning group.

Fix this here in docker image building code.

root@df79d5606903:~# sudo -u www-data php -r "echo is_writable('/var/lib/bluecherry/recordings') ? 'writable' : 'not writable';"; echo
not writable
root@df79d5606903:~# sudo -u www-data touch /var/lib/bluecherry/recordings/www-data.was.here
touch: cannot touch '/var/lib/bluecherry/recordings/www-data.was.here': Permission denied
root@df79d5606903:~# id
uid=0(root) gid=0(root) groups=0(root)
root@df79d5606903:~# id www-data
uid=33(www-data) gid=33(www-data) groups=33(www-data),4(adm),20(dialout),29(audio),44(video),999(bluecherry)
root@df79d5606903:~# ls -l /var/lib/bluecherry/recordings -d
drwxr-xr-x 2 bluecherry bluecherry 4096 Nov 24 00:36 /var/lib/bluecherry/recordings
root@df79d5606903:~# chmod g+w /var/lib/bluecherry/recordings
root@df79d5606903:~# ls -l /var/lib/bluecherry/recordings -d
drwxrwxr-x 2 bluecherry bluecherry 4096 Nov 24 00:36 /var/lib/bluecherry/recordings
root@df79d5606903:~# sudo -u www-data touch /var/lib/bluecherry/recordings/www-data.was.here
root@df79d5606903:~# sudo -u www-data php -r "echo is_writable('/var/lib/bluecherry/recordings') ? 'writable' : 'not writable';"; echo
writable
curtishall added a commit that referenced this issue Dec 11, 2023
Fix recordings dir reported not writable (#620)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants