Open nemihome opened 1 year ago
Is your datadirectory on a separate drive?
Data: /var/nextcloud/data and Web: /var/www/html/URL/nextcloud
did you make sure that the drive is still corrreclty mounted?
Yes, before update I can access everything but I think it's also strange that web updater is not running through. I think this error message is maybe only the last in the row.
Well I think I found something. The datadir was not the problem. Nextcloud did overwrite user.ini on that server in the nextcloud folder (but this did not happen with this update it happened already at the last update). Not sure why 24.0.6 did work that way and update to 24.0.9 did not (maybe I have tried to get rid of the modified user.ini error). Therefore php basedir settings were overwritten before this update. On a higher folder level there were still basedir restrictions in place. Due to the fact that /tmp was not available because of the restictions on upper folder level the abovementioned effects occur. I removed the restrictions completely. The error messages from Nextcloud are not helful to identify such root causes. Basically the message should not point to data directory or in case of web installer to nowhere. If data directory would be the problem 24.0.6 would also not work but it did with exactly the same user.ini file. Problem can only be related to requirements within update process or changed requirements.
Hi @nemihome
Therefore php basedir settings were overwritten before this update. On a higher folder level there were still basedir restrictions in place. Due to the fact that /tmp was not available because of the restictions on upper folder level the abovementioned effects occur. I removed the restrictions completely. The error messages from Nextcloud are not helful to identify such root causes. Basically the message should not point to data directory or in case of web installer to nowhere. If data directory would be the problem 24.0.6 would also not work but it did with exactly the same user.ini file. Problem can only be related to requirements within update process or changed requirements.
I'm not really following this. It sounds like you made local changes to your Nextcloud .user.ini
because you have open_basedir restrictions in place. Is that correct? And since the one in the Nextcloud installation folder is managed by Nextcloud it was overwritten during the Updater run. This then led to later problems when the db/app upgrades ran as well as when you tried to access Nextcloud after the update (e.g. the .ocdata
error)?
The .ocdata
one makes sense: the open_basedir restrictions were in place. We just do a simple file_exists()
check and with the restriction in place PHP tells us "doesn't exist" if it's not permitting us to access it.
I can't say what other specific error messages you might trigger in either the Updater or the upgrader because it'll depend on the specific restrictions you have in place I guess.
There may be some hints in your data/updater.log
.
⚠️ This issue respects the following points: ⚠️
Bug description
Update from Nextcloud 24.0.6 to 24.0.9 not working
Steps to reproduce
Expected behavior
Update running through or descriptive error message
Installation method
None
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
After that Nextcloud is in maintenance mode. I can switch that off and run exactly into the same result. There is no log file from the update byself.
With manual upgrade via /occ upgrade the messages are:
This is wrong. The .ocdata is working the authorizations are exactly the same than before upgrade. I can also copy the backup before installation of the update and no errors are shown. The path in the config.php file is correct.
Additional info
No response