Yes, something went wrong with my update that is for sure after your reply. I think I was to hasty when updating. I'll investigate a bit. Thanks.

You may also need to run:

/usr/clearos/apps/nextcloud_business/deploy/upgrade_20_0_11

as NC has already been upgraded so this script in the updated app-nextcloud(-business) will not be triggered.

Hi Marcel,
Have you upgraded NC without upgrading app-nextcloud or app-nectcloud-business? Some of those issues should go away. It

Some of the issues you will need to fix yourself as they are global PHP settings and we are nervous of changing the settings as it will affect the settings for all apps using that version of PHP.

File integrity will always be broken as we patch one of their files which blocks you from skipping a major version when updating. This means NC would normally block you from going from NC18 directly to NC20.

If you check the admin account and go to settings --> administration --> overview there are quite a couple of issues:

Security & setup warnings
It's important for the security and performance of your instance that everything is configured correctly. To help you with that we are doing some automatic checks. Please see the linked documentation for more information.

There are some errors regarding your setup.
Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the documentation. (List of invalid files… / Rescan…)
The PHP memory limit is below the recommended value of 512MB.
MySQL is used as database but does not support 4-byte characters. To be able to handle 4-byte characters (like emojis) without issues in filenames or comments for example it is recommended to enable the 4-byte support in MySQL. For further details read the documentation page about this.
Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation.
No memory cache has been configured. To enhance performance, please configure a memcache, if available. Further information can be found in the documentation.
You are currently running PHP 7.2.24. Upgrade your PHP version to take advantage of performance and security updates provided by the PHP Group as soon as your distribution supports it.
Nextcloud 20 is the last release supporting PHP 7.2. Nextcloud 21 requires at least PHP 7.3.
The PHP OPcache is not properly configured. For better performance it is recommended to use the following settings in the php.ini:
opcache.enable=1
opcache.interned_strings_buffer=8
opcache.max_accelerated_files=10000
opcache.memory_consumption=128
opcache.save_comments=1
opcache.revalidate_freq=1
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 "cards_abiduri" in table "oc_cards".
Missing index "calendarobject_calid_index" in table "oc_calendarobjects_props".
Missing index "schedulobj_principuri_index" in table "oc_schedulingobjects".
Missing index "properties_path_index" in table "oc_properties".
The database is missing some primary keys. Due to the fact that adding primary keys on big tables could take some time they were not added automatically. By running "occ db:add-missing-primary-keys" those missing primary keys could be added manually while the instance keeps running.
Missing primary key on table "oc_federated_reshares".
Missing primary key on table "oc_systemtag_object_mapping".
Missing primary key on table "oc_comments_read_markers".
Missing primary key on table "oc_collres_resources".
Missing primary key on table "oc_collres_accesscache".
Missing primary key on table "oc_filecache_extended".
The database is missing some optional columns. Due to the fact that adding columns on big tables could take some time they were not added automatically when they can be optional. By running "occ db:add-missing-columns" those missing columns could be added manually while the instance keeps running. Once the columns are added some features might improve responsiveness or usability.
Missing optional column "reference_id" in table "oc_comments".
This instance is missing some recommended PHP modules. For improved performance and better compatibility it is highly recommended to install them.
imagick
Some columns in the database are missing a conversion to big int. Due to the fact that changing column types on big tables could take some time they were not changed automatically. By running 'occ db:convert-filecache-bigint' those pending changes could be applied manually. This operation needs to be made while the instance is offline. For further details read the documentation page about this.
federated_reshares.share_id
mounts.storage_id
mounts.root_id
mounts.mount_id
share_external.id
share_external.parent
MariaDB version "5.5.68-MariaDB" is used. Nextcloud 21 will no longer support this version and requires MariaDB 10.2 or higher.
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 ↗.

Did you guys notice these errors? I'm not sure if it is a real problem... and is this on all systems? Maybe someone can check his server.

Forgive me I didn't want to start a rant but this is because of no information from ClearCenter what the plans are. You don't get a good feeling when devs are leaving ClearCenter and I'm still disappointed that the eGloo team left. A little bit of transparency to the community is the least they could do. In my opinion ClearOS is still a cool and good server OS and I hate it to see it dying. That is the impression I now have...

I have deep respect for you Nick how you keep the ship floating. Also you'r support is awesome.

Nick Howitt wrote:

Please don't think that ClearOS is not a priority. It is but currently it is focussing on 7.x and apps to support the decentralized infrastructure.

Nick,

I think the users like to see some information posted regarding COS way forward.
I know you are doing your utmost to help and inform us.

the iscussion is getting a bit off topic....

Please don't think that ClearOS is not a priority. It is but currently it is focussing on 7.x and apps to support the decentralized infrastructure.

Nick Howitt wrote:

Remember that, upstream, RedHat always try to avoid major updates to programs except when changing major versions like EL7 to EL8. Instead they have always tended to backport patches. Mariadb 5.5 > 10.x would be considered a major upgrade so can never be expected within a major version of EL.

Point taken about ClearOS 8 development. I can't find anything out either.

Yes, you'r right.

I contacted Peter some time ago after we had a chat. He said that ClearCenter did contact him about work on ClearOS 7.x but the eGloo team was busy with other development. You said something similar if I'm correct.I think a month ago I contacted him again and he said he didn't hear anything and his guess is ClearCenter has no hurry or ClearOS is not a priority...

Remember that, upstream, RedHat always try to avoid major updates to programs except when changing major versions like EL7 to EL8. Instead they have always tended to backport patches. Mariadb 5.5 > 10.x would be considered a major upgrade so can never be expected within a major version of EL.

Point taken about ClearOS 8 development. I can't find anything out either.

Nick Howitt wrote:

Unfortunately we are aware about v21 and it is a big problem. It requires MariaDB >= 10.2 which we don't have. There is an SCLO version for the main database but not for the system database.

We have some options:
1 - stop with v20 in the same way we have to stop when Kopano requires PHP 7.4
2 - Implement rh-mariadb102/3/5 and blow out the upstream version. This has the risk of knackering anyone using mariadb now and whose program is not compatible with 10.x. I don't think you can have both mariadb-5.x from upstream and rh-mariadb10x running at the same time as they both try to bind to port 3306. The upgrade would also need to dump the nextcloud database from the system-database and import it into the main database.
3 - roll our own version of 10.x like REMI, and this will have to replace 5.x with the same issues as in 2. I think 10.x will now co-exist with a system-database 5.x with a change I pushed earlier this year.
4 - roll out own version of system-database with MariaDB 10.x, but this will mean testing every app which uses the system-database and fix it if necessary.

None of these look pretty. If work ever starts on ClearOS8, I'd go for option 1, and, practically, it would probably have to be option 1 anyway. I think at some point mariadb ceased to be 100% compatible with MySQL so it could be dangerous to upgrade it in the user database. The system-database would be OK as that is under our control, but it may require program mods all over the place.

Thanks for testing. Were you coming from NC18 or NC19? NC19 was only ever in paid-testing and was never released.

I'm coming from NC18. So we can concluded that CentOS 7.x is getting old now that MariaDB not is supported anymore. I must agree with you that the start of development of ClearOS 8 takes a long time. ClearCenter shares nothing how they think about this matter. I often ask myself the question are we not on death track...

There is an update for app-nextcloud available:

yum update app-nextcloud --enablerepo=clearos*testing

All it does is fix the permissions of the htaccess script which should populate your /var/www/html/.htaccess file with some settings for various "wellknown" valuus. This will clear some of the warnings you see in the NC Admin console and also enable you to use NC for things like a Thunderbird shared address book.

@Patrick, for you this will be a very minor update for you as you've already the underlying NC.

So you have NC Home? I didn't get that but I have NC Business. I've looked at the sources and there seems to be a packaging error for that one file in Home.

I also don't remember getting all that output during the upgrade but mine is now upgraded so I can't roll back.

Nick Howitt wrote:

There is an update to take Nextcloud to v20.0.11 available for testing. If you would like to try it, please upgrade your installation with:

yum update *nextcloud* --enablerepo=clearos*testing

Note that when I installed the update, Nextcloud went into maintenance mode. To fix it I had to edit /etc/nextcloud/config.php, change the value of maintenance from true to false and then restart the webserver. We'd be interested to know if anyone else has the same problem as I have tinkered quite a lot with my system.

Please post any issues to this thread.

Great you have pushed the upgrade.

My upgrade from v18.04 went without the problem with maintenance mode.
I could login directly after upgrade with Admin or user.

This is my output of the upgrade.

Running transaction

  Installing : nextcloud-20.0.11-1.v7.noarch                                                                                        1/6

warning: /etc/httpd/conf.d/nextcloud.conf created as /etc/httpd/conf.d/nextcloud.conf.rpmnew

  Updating   : 1:app-nextcloud-core-3.1.5-3.v7.noarch                                                                               2/6

Updated trusted_domains in Nextcloud's config.php file.

/usr/clearos/apps/nextcloud/deploy/upgrade: line 20: /usr/clearos/apps/nextcloud/deploy/htaccess: Permission denied

  Updating   : 1:app-nextcloud-3.1.5-3.v7.noarch                                                                                    3/6

  Cleanup    : 1:app-nextcloud-3.1.2-2.v7.noarch                                                                                    4/6

  Cleanup    : 1:app-nextcloud-core-3.1.2-2.v7.noarch                                                                               5/6

  Cleanup    : nextcloud-18.0.4-1.v7.noarch                                                                                         6/6

Performing 19.0.0 to 20.0.11 upgrade script

Nextcloud or one of the apps require upgrade - only a limited number of commands are available

You may use your browser or the occ upgrade command to do the upgrade

user_ldap 1.10.2 disabled

Nextcloud or one of the apps require upgrade - only a limited number of commands are available

You may use your browser or the occ upgrade command to do the upgrade

Setting log level to debug

Turned on maintenance mode

Updating database schema

Updated database

Disabled incompatible app: bruteforcesettings

Updating <federation> ...

Updated <federation> to 1.10.1

Updating <lookup_server_connector> ...

Updated <lookup_server_connector> to 1.8.0

Updating <oauth2> ...

Updated <oauth2> to 1.8.0

Updating <files> ...

Updated <files> to 1.15.0

Updating <activity> ...

Updated <activity> to 2.13.4

Updating <cloud_federation_api> ...

Updated <cloud_federation_api> to 1.3.0

Updating <dav> ...

Fix broken values of calendar objects



 Starting ...

    0/0 [>---------------------------]   0%

Updated <dav> to 1.16.2

Updating <files_external> ...

Updated <files_external> to 1.11.1

Updating <files_sharing> ...

Updated <files_sharing> to 1.12.2

Updating <files_trashbin> ...

Updated <files_trashbin> to 1.10.1

Updating <files_versions> ...

Updated <files_versions> to 1.13.0

Updating <sharebymail> ...

Updated <sharebymail> to 1.10.0

Updating <workflowengine> ...

Updated <workflowengine> to 2.2.0

Updating <comments> ...

Updated <comments> to 1.10.0

Updating <firstrunwizard> ...

Updated <firstrunwizard> to 2.9.0

Updating <nextcloud_announcements> ...

Updated <nextcloud_announcements> to 1.9.0

Updating <notifications> ...

Updated <notifications> to 2.8.0

Updating <systemtags> ...

Updated <systemtags> to 1.10.0

Updating <theming> ...

Updated <theming> to 1.11.0

Updating <accessibility> ...

Migrate old user config



 Starting ...

    0/0 [->--------------------------]   0%

Updated <accessibility> to 1.6.0

Updating <federatedfilesharing> ...

Updated <federatedfilesharing> to 1.10.2

Updating <files_pdfviewer> ...

Updated <files_pdfviewer> to 2.0.1

Updating <files_rightclick> ...

Updated <files_rightclick> to 0.17.0

Updating <files_videoplayer> ...

Updated <files_videoplayer> to 1.9.0

Updating <logreader> ...

Updated <logreader> to 2.5.0

Updating <password_policy> ...

Updated <password_policy> to 1.10.1

Updating <photos> ...

Updated <photos> to 1.2.3

Updating <privacy> ...

Updated <privacy> to 1.4.0

Updating <provisioning_api> ...

Updated <provisioning_api> to 1.10.0

Updating <serverinfo> ...

Updated <serverinfo> to 1.10.0

Updating <settings> ...

Updated <settings> to 1.2.0

Updating <support> ...

Updated <support> to 1.3.0

Updating <survey_client> ...

Updated <survey_client> to 1.8.0

Updating <text> ...

Updated <text> to 3.1.0

Updating <twofactor_backupcodes> ...

Updated <twofactor_backupcodes> to 1.9.0

Updating <updatenotification> ...

Updated <updatenotification> to 1.10.0

Updating <viewer> ...

Updated <viewer> to 1.4.0

Checking for update of app accessibility in appstore

Checked for update of app "accessibility" in appstore

Checking for update of app activity in appstore

Checked for update of app "activity" in appstore

Checking for update of app cloud_federation_api in appstore

Checked for update of app "cloud_federation_api" in appstore

Checking for update of app comments in appstore

Checked for update of app "comments" in appstore

Checking for update of app dav in appstore

Checked for update of app "dav" in appstore

Checking for update of app federatedfilesharing in appstore

Checked for update of app "federatedfilesharing" in appstore

Checking for update of app federation in appstore

Checked for update of app "federation" in appstore

Checking for update of app files in appstore

Checked for update of app "files" in appstore

Checking for update of app files_external in appstore

Checked for update of app "files_external" in appstore

Checking for update of app files_pdfviewer in appstore

Checked for update of app "files_pdfviewer" in appstore

Checking for update of app files_rightclick in appstore

Checked for update of app "files_rightclick" in appstore

Checking for update of app files_sharing in appstore

Checked for update of app "files_sharing" in appstore

Checking for update of app files_trashbin in appstore

Checked for update of app "files_trashbin" in appstore

Checking for update of app files_versions in appstore

Checked for update of app "files_versions" in appstore

Checking for update of app files_videoplayer in appstore

Checked for update of app "files_videoplayer" in appstore

Checking for update of app firstrunwizard in appstore

Checked for update of app "firstrunwizard" in appstore

Checking for update of app logreader in appstore

Checked for update of app "logreader" in appstore

Checking for update of app lookup_server_connector in appstore

Checked for update of app "lookup_server_connector" in appstore

Checking for update of app nextcloud_announcements in appstore

Checked for update of app "nextcloud_announcements" in appstore

Checking for update of app notifications in appstore

Checked for update of app "notifications" in appstore

Checking for update of app oauth2 in appstore

Checked for update of app "oauth2" in appstore

Checking for update of app password_policy in appstore

Checked for update of app "password_policy" in appstore

Checking for update of app photos in appstore

Checked for update of app "photos" in appstore

Checking for update of app privacy in appstore

Checked for update of app "privacy" in appstore

Checking for update of app provisioning_api in appstore

Checked for update of app "provisioning_api" in appstore

Checking for update of app serverinfo in appstore

Checked for update of app "serverinfo" in appstore

Checking for update of app settings in appstore

Checked for update of app "settings" in appstore

Checking for update of app sharebymail in appstore

Checked for update of app "sharebymail" in appstore

Checking for update of app support in appstore

Checked for update of app "support" in appstore

Checking for update of app survey_client in appstore

Checked for update of app "survey_client" in appstore

Checking for update of app systemtags in appstore

Checked for update of app "systemtags" in appstore

Checking for update of app text in appstore

Checked for update of app "text" in appstore

Checking for update of app theming in appstore

Checked for update of app "theming" in appstore

Checking for update of app twofactor_backupcodes in appstore

Checked for update of app "twofactor_backupcodes" in appstore

Checking for update of app updatenotification in appstore

Checked for update of app "updatenotification" in appstore

Checking for update of app viewer in appstore

Checked for update of app "viewer" in appstore

Checking for update of app workflowengine in appstore

Checked for update of app "workflowengine" in appstore

Checking for update of app bruteforcesettings in appstore

Update app bruteforcesettings from appstore

Checked for update of app "bruteforcesettings" in appstore

Starting code integrity check...

Finished code integrity check

Update successful

Turned off maintenance mode

Resetting log level

user_ldap 1.10.2 enabled

Nextcloud is already latest version

Check indices of the share table.

Check indices of the filecache table.

Check indices of the twofactor_providers table.

Check indices of the login_flow_v2 table.

Check indices of the whats_new table.

Check indices of the cards table.

Adding cards_abiduri index to the cards table, this can take some time...

cards table updated successfully.

Check indices of the cards_properties table.

Check indices of the calendarobjects_props table.

Check indices of the schedulingobjects table.

Check indices of the oc_properties table.

Adding properties_path_index index to the oc_properties table, this can take some time...

oc_properties table updated successfully.

Check columns of the comments table.

Adding additional reference_id column to the comments table, this can take some time...

Comments table updated successfully.

Check primary keys.

Adding primary key to the federated_reshares table, this can take some time...

federated_reshares table updated successfully.

Adding primary key to the systemtag_object_mapping table, this can take some time...

systemtag_object_mapping table updated successfully.

Adding primary key to the comments_read_markers table, this can take some time...

comments_read_markers table updated successfully.

Adding primary key to the collres_resources table, this can take some time...

collres_resources table updated successfully.

Adding primary key to the collres_accesscache table, this can take some time...

collres_accesscache table updated successfully.

Adding primary key to the filecache_extended table, this can take some time...

filecache_extended table updated successfully.

Following columns will be updated:



* federated_reshares.share_id

* filecache_extended.fileid

* files_trash.auto_id

* share_external.id

* share_external.parent

Maybe this could be looked in, but doesn't look like a big issue

Updated trusted_domains in Nextcloud's config.php file.

/usr/clearos/apps/nextcloud/deploy/upgrade: line 20: /usr/clearos/apps/nextcloud/deploy/htaccess: Permission denied

Unfortunately we are aware about v21 and it is a big problem. It requires MariaDB >= 10.2 which we don't have. There is an SCLO version for the main database but not for the system database.

We have some options:
1 - stop with v20 in the same way we have to stop when Kopano requires PHP 7.4
2 - Implement rh-mariadb102/3/5 and blow out the upstream version. This has the risk of knackering anyone using mariadb now and whose program is not compatible with 10.x. I don't think you can have both mariadb-5.x from upstream and rh-mariadb10x running at the same time as they both try to bind to port 3306. The upgrade would also need to dump the nextcloud database from the system-database and import it into the main database.
3 - roll our own version of 10.x like REMI, and this will have to replace 5.x with the same issues as in 2. I think 10.x will now co-exist with a system-database 5.x with a change I pushed earlier this year.
4 - roll out own version of system-database with MariaDB 10.x, but this will mean testing every app which uses the system-database and fix it if necessary.

None of these look pretty. If work ever starts on ClearOS8, I'd go for option 1, and, practically, it would probably have to be option 1 anyway. I think at some point mariadb ceased to be 100% compatible with MySQL so it could be dangerous to upgrade it in the user database. The system-database would be OK as that is under our control, but it may require program mods all over the place.

Thanks for testing. Were you coming from NC18 or NC19? NC19 was only ever in paid-testing and was never released.

The only issue I had is mentioned above. I did what you suggested and it is was solved.

btw. Awesome that we received an update but are you guys aware that version 21 of Nexcloud is available?