Installed NC 27, getting the following security warnings (warnings were clean/non-existent before the update):
The database is used for transactional file locking. To enhance performance, please configure memcache, if available. See the documentation ? for more information.
The database is missing some indexes. Due to the fact that adding indexes on big tables could take some time they were not added automatically. By running "occ db:add-missing-indices" those missing indexes could be added manually while the instance keeps running. Once the indexes are added queries to those tables are usually much faster.
Missing index "mounts_user_root_path_index" in table "oc_mounts".
Please double check the installation guides ?, and check for any errors or warnings in the log.
Check the security of your Nextcloud over our security scan ?.
Running NC27 under OMV6 under docker on a Pi4.
Any comments appreciated.
R.
Because of this Warning I installed Redis but the warning won’t disappear. Checked if Redis is getting input, but redid-cli monitor is not showing anything when I surf on my nextcloud instance.
Tried both with Unix socket as well as over TCP.
I installed redis today and edited the config.php file accordingly with file locking enabled… everything works fine and Nextcloud 27 seems a little snappier. All warnings are now gone from my Nextcloud install. Happy days.
If you get a Cron error message
OCP\HintException: [0]: Memcache OC\Memcache\APCu not available for local cache (Is the matching PHP module installed and enabled?)
add apc.enable_cli=1 not to your php.ini file as this doesn’t seem to work but to your /etc/php/8.2/mods_available/apcu.ini file
Getting this after upgrading to 27.1.4. It seems redis, at least php-redis from debian repo updated lately with php8.3 required and Nextcloud isnt supporting php8.3.
When I run php occ files:scan --all
I get: “This version of Nextcloud is not compatible with PHP>=8.3”.
If I update webserver to use php8.3 instead of php8.2 it breaks the webui with the same error.
I used the memcache.locking to APCu workaround for now to suppress the warning even though redis was working before: