could help, other than that everyone having had problems with “expected files” once, seems to suggest deleting those files (if possible) - or at least move them out of where they are to a different location for the upgrade and then move it back…
btw: did you download the recent zip-file before trying to install it via commandline?
The question is, why the updater is not able to delete the folder
/srv/www/htdocs/nextcloud/apps/dav
Due to missing permissions (should not be the case when you performed the commands I suggested above) or because this folder is not existing anymore.
If it is no longer existing you could try to create in manually for now (just empty folder) and retry the update.
This is strange. Don’t know what is causing that. Could please have a look at the updater.log and the nextcloud.log if there are more details why that folder can’t be removed or what exactly fails?
I just hope the logs tell us some more.
The folder does exist already. The “..” only means “parent-folder”. So nextcloud/updater/.. is nextcloud/ and therefor
/srv/www/htdocs/nextcloud/updater/../apps/dav
is actually
/srv/www/htdocs/nextcloud/apps/dav
I think it depends on the webserver you are using, but you need to reload the php settings. For nginx you usually use php-fpm as php handler and need to restart that systemctl restart php-fpm
I believe for apache you just need to restart apache, after making the changes to the php.ini.
If that doesn’t solve the problem, you might want to look if you edited the right php.ini file (in case you have different php versions running) or if there are other .ini files that contain any configurations, that might overwrite your changes to the php.ini. Let’s say an opcache.ini in the php/config directory.