Support intro
Sorry to hear you’re facing problems
help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.
In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:
example
Or for longer, use three backticks above and below the code snippet:
longer
example
here
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can
Nextcloud version (eg, 20.0.5): 20.0.8
Operating system and version (eg, Ubuntu 20.04): OpenBSD
Apache or nginx version (eg, Apache 2.4.25): OpenBSD httpd
PHP version (eg, 7.4): 7.4
The issue you are facing:
Every update, but also after “some” unindentified circumstance nextloud “corrects” my datadirectory setting, so it is no longer accessible. I have to manually correct that to bring my instance back to life. Case is that I run it over OpenBSD httpd, chrooted by default. To properly run cron tasks I cannot simply ste path to data directory it has to be in format:
‘datadirectory’ => ((php_sapi_name() == ‘cli’) ? ‘/var/www’ : ‘’) . ‘/my/data/directory’,
The ‘/var/www’ is default openbsd chroot, “/my/data/directory” is path within chrooted environment.
There is no other way to run for instance OCC commands without setting data directory that way. Earlier versions of nextcloud stripped /var/www/ part in string while “correcting” my config. That caused errors “no readable data directory” but instance itself worked. Present version simplifies setting to “/var/www/my/data/directory” and collapses whole nextcloud forcing me to manually reset things. Of course I can workaround that with cron job validating settings in config.php and resetting it in case of changes, but I find it odd and dirty trick.
I suppose it is a sort of code integrity validation e.g. during cron.php execution or other automatic task, but form my point of view it is annoying bug.
Thanks in advance for any help/ideas
Is this the first time you’ve seen this error? (Y/N):
no
Steps to replicate it:
- For instance upgrade some app
- Probably after some coron.php execution
- After each upgrade of whole instance
The output of your Nextcloud log in Admin > Logging:
no logs involved
The output of your config.php file in /path/to/nextcloud
(make sure you remove any identifiable information!):
no need to paste whole config - case is simple
The output of your Apache/nginx/system log in /var/log/____
:
no signs of activity in logs