https://bugs.koozali.org/show_bug.cgi?id=11343

John Crisp <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|10alpha                     |10.0

--- Comment #2 from John Crisp <[email protected]> ---
OK,

So I will add here how we upgrade to Nextcloud v22

Requires Maria v10.x - see 11856 for how to do this.

Other bugs

https://bugs.koozali.org/show_bug.cgi?id=11853
Nextcloud - open_basedir restriction in effect. File(/templates/) is not within
the allowed path
Fixed in v22 - depends on 11856

https://bugs.koozali.org/show_bug.cgi?id=11854
Database updates required after upgrade (Nextcloud 20.x)

https://bugs.koozali.org/show_bug.cgi?id=11855
Nextcloud gencache_init: Failed to create directory
You need to create this directory as per the bug

https://bugs.koozali.org/show_bug.cgi?id=11856
Upgrade MariaDB to 10.x
Upgrade to Maria 10 and make sure this is reliable and working

Make sure you update to the latest 20.x first.

Run these before upgrade. After an upgrade check Adminstration/Overview for
items to update

OCC db:add-missing-indices
OCC db:add-missing-primary-keys
OCC db:convert-filecache-bigint

Next upgrade to 21.x Check Admin/Overview. Logging may show a lot of
openbasedir errors.
These are fixed on upgrade 22.x

Then upgrade to 22.x

If you run add-missing-indices and get this issue:

An unhandled exception has been thrown:
OC\HintException: [0]: Memcache \OC\Memcache\APCu not available for local cache

Edit /usr/share/nextcloud/config/config.php

Comment this:
// 'memcache.local' => '\\OC\\Memcache\\APCu',
signal-event webapps-update;signal-event nextcloud-update

Run OCC db:add-missing-indices
Restore the previous line 
signal-event webapps-update;signal-event nextcloud-update

However, you still get errors with cron.

Test with:

sudo -u www php74 --define memory_limit=512M --define apc.enable_cli=1 -f
/usr/share/nextcloud/cron.php

Fix seems to be to modify /etc/e-smith/templates/etc/crontab/98nextcloud

Add --define apc.enable_cli=1 to both of the lines eg:

www scl enable php74 'php --define memory_limit=512M --define apc.enable_cli=1
-f /usr/share/nextcloud/cron.php > /dev/null 2>&1'

www cd /usr/share/nextcloud ; echo 'y' | scl enable php74 'php --define
memory_limit=512M --define apc.enable_cli=1 occ db:convert-filecache-bigint >
/dev/null 2>&1' 

signal-event webapps-update;signal-event nextcloud-update


Other things to fix

Duplicate log entry:

mcedit /usr/share/nextcloud/config/config.php

Once at v 22.x I noticed I had this in the config file

  'logfile' => '/var/log/nextcloud/nextcloud.log',
  'logfile:/var/log/nextcloud/nextcloud.log' => '',    <<< remove this

The second line should be removed.

Check Admin/Overview

Error:
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
https://docs.nextcloud.com/server/22/go.php?to=admin-mysql-utf8mb4

https://github.com/nextcloud/server/issues/25436
https://mariadb.com/docs/reference/mdb/cli/mariadbd/innodb-read-only-compressed/

This is ugly as settings changed with Maria 10.6 but both Nextcloud and us have
to make that work

sudo -u www php74 --define apc.enable_cli=1 occ maintenance:mode --on
sudo -u www php74 --define apc.enable_cli=1 occ config:system:set mysql.utf8mb4
--type boolean --value="true"
sudo -u www php74 --define apc.enable_cli=1 occ maintenance:repair
This error is ok
ERROR: An exception occurred while executing a query: SQLSTATE[HY000]: General
error: 4047 InnoDB refuses to write tables with ROW_FORMAT=COMPRESSED or
KEY_BLOCK_SIZE
Set the Rows correctly
mysql --batch --skip-column-names -e 'SELECT CONCAT("ALTER TABLE
",TABLE_SCHEMA,".",TABLE_NAME," ROW_FORMAT=DYNAMIC;") from
INFORMATION_SCHEMA.TABLES where CREATE_OPTIONS LIKE "row_format=compressed" AND
ENGINE="InnoDB"' | mysql
sudo -u www php74 --define apc.enable_cli=1 occ maintenance:mode --off

Note - for automysqlbackup:
Also make sure your backup strategy still work. If you use mysqldump make sure
to add the --default-character-set=utf8mb4 option. 
Otherwise your backups are broken and restoring them will result in ? instead
of the emojis, making files inaccessible.


Error:
Your web server is not properly set up to resolve "/.well-known/webfinger"
Your web server is not properly set up to resolve "/.well-known/nodeinfo". 

https://docs.nextcloud.com/server/22/go.php?to=admin-setup-well-known-URL

I think we need to edit
 /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/28nextcloud

Modify these in two places:

  #RewriteRule ^/\\.well-known/webfinger
/nextcloud/public.php?service=webfinger [QSA,L]
  RewriteRule ^/\\.well-known/webfinger
/nextcloud/index.php/.well-known/webfinger [R=301,L]
  RewriteRule ^/\\.well-known/nodeinfo
/nextcloud/index.php/.well-known/nodeinfo [R=301,L]


Error:

Your installation has no default phone region set

Add this to  /usr/share/nextcloud/config/config.php

'default_phone_region' => 'GB',


And with all that done we get a green button on the Admin/Overview !!!

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/

Reply via email to