I have found the updater to be flaky every time, requiring some work with occ in the background to complete the process. This time it left me with 257 files that it didn’t like, mostly mjs files, whatever those are.
I ended reinstalled from scratch and trying to restore the database/users and data. That seems to be unclean as well. The bad file list is shorter but why was it so large in the first place? find(1) couldn’t find the files in question so were they stored in some file cache? I stopped/started nginx/php_fpm a couple of times, thinking that was the case. No difference. So a full reinstall that can’t read a restored backup is where I am now.
I’m at the “do I even use nextcloud?” part of the process. It seemed interesting but the failed upgrades and now this are making me wonder about it.
Some of the reported errors are just wrong. memcache has been installed and running for years as is redis (works on wordpress but never has on Nextcloud).
opcache.interned_strings_buffer has been set to 32 for months. The error has been logged even longer.
“Last background job execution ran 11 months ago. Something seems wrong.” yeah, it is wrong. These were running two days ago.
-
Your remote address was identified as “192.168.0.1” and is brute-force throttled at the moment slowing down the performance of various requests. If the remote address is not your address this can be an indication that a proxy is not configured correctly. For more details see the documentation
. -
Last background job execution ran 11 months ago. Something seems wrong. Check the background job settings.
-
Some files have not passed the integrity check. List of invalid files… Rescan… For more details see the documentation
. -
Your web server is not properly set up to resolve “/ocm-provider/”. This is most likely related to a web server configuration that was not updated to deliver this folder directly. Please compare your configuration against the shipped rewrite rules in “.htaccess” for Apache or the provided one in the documentation for Nginx. On Nginx those are typically the lines starting with “location ~” that need an update. For more details see the documentation
. -
2 errors in the logs since February 22, 2025, 6:47:27 PM
-
Server has no maintenance window start time configured. This means resource intensive daily background jobs will also be executed during your main usage time. We recommend to set it to a time of low usage, so users are less impacted by the load caused from these heavy tasks. For more details see the documentation
. -
One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command
occ maintenance:repair --include-expensiveto perform the migrations. -
Detected some missing optional indices. Occasionally new indices are added (by Nextcloud or installed applications) to improve database performance. Adding indices can sometimes take awhile and temporarily hurt performance so this is not done automatically during upgrades. Once the indices are added, queries to those tables should be faster. Use the command
occ db:add-missing-indicesto add them. Missing indices: “dav_shares_resourceid_type” in table “dav_shares”, “dav_shares_resourceid_access” in table “dav_shares”, “mail_messages_strucanalyz_idx” in table “mail_messages”, “mail_acc_prov_idx” in table “mail_accounts”, “mail_alias_accid_idx” in table “mail_aliases”, “oc_npushhash_di” in table “notifications_pushhash”, “fs_name_hash” in table “filecache”, “schedulobj_lastmodified_idx” in table “schedulingobjects”, “systag_by_objectid” in table “systemtag_object_mapping”, “mail_messages_mb_id_uid_uidx” in table “mail_messages”, “mail_smime_certs_uid_email_idx” in table “mail_smime_certificates”, “mail_trusted_senders_idx” in table “mail_trusted_senders”, “mail_coll_idx” in table “mail_coll_addresses”. For more details see the documentation. -
SQLite is currently being used as the backend database. For larger installations we recommend that you switch to a different database backend. This is particularly recommended when using the desktop client for file synchronisation. To migrate to another database use the command line tool: “occ db:convert-type”. For more details see the documentation
. -
The PHP OPcache module is not properly configured. The OPcache interned strings buffer is nearly full. To assure that repeating strings can be effectively cached, it is recommended to apply “opcache.interned_strings_buffer” to your PHP configuration with a value higher than “16”… For more details see the documentation
. -
The database is used for transactional file locking. To enhance performance, please configure memcache, if available. For more details see the documentation
. -
No memory cache has been configured. To enhance performance, please configure a memcache, if available. For more details see the documentation
. -
Your installation has no default phone region set. This is required to validate phone numbers in the profile settings without a country code. To allow numbers without a country code, please add “default_phone_region” with the respective ISO 3166-1 code of the region to your config file. For more details see the documentation
.