Update failure from 23.0.6.1 to 24.0.5.1

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
,
1

I went to update 23.0.6.1 to 24.0.5.1 through the AIO interface and it did not complete.

Both Nextcloud and Apache containers are stuck on starting.

It seems like the issue is with the Nextcloud container and possibly one of the addons and/or getaddrinfo function…I’m stuck at this point and moving slow to understand it from here. I would greatly appreciation some thoughts or hints.

This was installed and is running from the marketplace package from Linode.

Here are the logs from the NC container…

Waiting for database to start…
nc: getaddrinfo: Name does not resolve
now

2022-09-16 10:19:47.519069-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
Checking connection to appstore
Appstore is reachable
Maintenance mode already disabled
Getting and backing up the status of apps for later, this might take a while…
System config value app_install_overwrite deleted
analytics new version available: 4.4.0
analytics updated
timemanager new version available: 0.3.3
timemanager updated
Initializing nextcloud 24.0.5.1 …
Initializing finished
Upgrading nextcloud from 23.0.6.1 to 24.0.5.1…
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: breezedark
Disabled incompatible app: deck
Disabled incompatible app: epubreader
Disabled incompatible app: external
Disabled incompatible app: fulltextsearch
Disabled incompatible app: groupfolders
Disabled incompatible app: occweb
Disabled incompatible app: quicknotes
Disabled incompatible app: richdocuments
Disabled incompatible app: shifts
Disabled incompatible app: spreed
Updating …
Updated to 1.14.0
Updating <lookup_server_connector> …
Updated <lookup_server_connector> to 1.12.0
Updating …
Updated to 1.12.0
Updating <password_policy> …
Updated <password_policy> to 1.14.0
Updating …
Updated to 1.19.0
Updating …
Updated to 2.16.0
Updating …
Updated to 24.0.1
Updating <cloud_federation_api> …
Updated <cloud_federation_api> to 1.7.0
Updating …
Fix broken values of calendar objects

Starting …

Clean up old calendar subscriptions from deleted users that were not cleaned-up

0/0 [>---------------------------]   0% Starting ...

Updated to 1.22.0
Updating <files_external> …
Updated <files_external> to 1.16.1
Updating <files_sharing> …
Updated <files_sharing> to 1.16.2
Updating <files_trashbin> …
Updated <files_trashbin> to 1.14.0
Updating <files_versions> …
Updated <files_versions> to 1.17.0
Updating …
Updated to 1.14.0
Updating …
Updated to 2.6.0
Updating <admin_audit> …
Updated <admin_audit> to 1.14.0
Updating …
Updated to 1.14.0
Updating …
Updated to 2.13.0
Updating <nextcloud_announcements> …
Updated <nextcloud_announcements> to 1.13.0
Updating …
Updated to 2.12.1
Updating …
Updated to 1.14.0
Updating …
Updated to 1.15.0
Updating …
Updated to 1.5.0
Updating …
Updated to 7.4.0
Updating …
Updated to 1.14.0
Updating <files_pdfviewer> …
Updated <files_pdfviewer> to 2.5.0
Updating <files_rightclick> …
Updated <files_rightclick> to 1.3.0
Updating <files_videoplayer> …
Updated <files_videoplayer> to 1.13.0
Updating …
Updated to 2.9.0
Updating …
Updated to 0.2.0
Updating …
Updated to 1.6.0
Updating …
Updated to 1.8.0
Updating <provisioning_api> …
Updated <provisioning_api> to 1.14.0
Updating …
Updated to 1.3.0
Updating …
Updated to 1.14.0
Updating …
Updated to 1.6.0
Updating …
Updated to 1.7.0
Updating …
Updated to 3.5.1
Updating <twofactor_backupcodes> …
Updated <twofactor_backupcodes> to 1.13.0
Updating <user_status> …
Updated <user_status> to 1.4.0
Updating …
Updated to 1.8.0
Update app breezedark from App Store
Update app deck from App Store
Update app external from App Store
Update app fulltextsearch from App Store
An unhandled exception has been thrown:
Error: Undefined constant OCA\FullTextSearch\Service\ConfigService::MIGRATION_24 in /var/www/html/custom_apps/fulltextsearch/lib/Migration/Version2400Date202201301329.php:159

ace:
#0 /var/www/html/lib/private/DB/MigrationService.php(547): OCA\FullTextSearch\Migration\Version2400Date202201301329->postSchemaChange(Object(OC\Migration\SimpleOutput), Object(Closure), Array)
#1 /var/www/html/lib/private/DB/MigrationService.php(425): OC\DB\MigrationService->executeStep(‘2400Date2022013…’, false)
#2 /var/www/html/lib/private/legacy/OC_App.php(1022): OC\DB\MigrationService->migrate()
#3 /var/www/html/lib/private/Installer.php(201): OC_App::updateApp(‘fulltextsearch’)
#4 /var/www/html/lib/private/Updater.php(415): OC\Installer->updateAppstoreApp(‘fulltextsearch’)
#5 /var/www/html/lib/private/Updater.php(277): OC\Updater->upgradeAppStoreApps(Array, Array)
#6 /var/www/html/lib/private/Updater.php(133): OC\Updater->doUpgrade(‘24.0.5.1’, ‘23.0.6.1’)
#7 /var/www/html/core/Command/Upgrade.php(235): OC\Updater->upgrade()
#8 /var/www/html/custom_apps/collectives/vendor/symfony/console/Command/Command.php(298): OC\Core\Command\Upgrade->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#9 /var/www/html/custom_apps/collectives/vendor/symfony/console/Application.php(1024): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#10 /var/www/html/custom_apps/collectives/vendor/symfony/console/Application.php(299): Symfony\Component\Console\Application->doRunCommand(Object(OC\Core\Command\Upgrade), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#11 /var/www/html/custom_apps/collectives/vendor/symfony/console/Application.php(171): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#12 /var/www/html/lib/private/Console/Application.php(211): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#13 /var/www/html/console.php(100): OC\Console\Application->run()
#14 /var/www/html/occ(11): require_once(‘/var/www/html/c…’)
#15 {main}Upgrade failed. Please restore from backup.
0/0 [->--------------------------] 0%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
Posting notifications to users that are admins…
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
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
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
Posting ‘Nextcloud update to 24.0.5.1 failed!’ to: fong_user
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

There are no commands defined in the “notification” namespace.

Done!
now

2022-09-16 10:21:06.104778-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:21:08.935068-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:21:11.941973-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:21:15.387242-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:21:19.681474-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:21:25.491566-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:21:34.683207-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:21:50.234187-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:22:18.590255-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:23:12.592013-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:24:15.313767-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:25:18.106931-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:26:20.929658-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:27:23.63177-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:28:26.356789-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:29:29.212181-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:30:32.030515-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:31:34.732257-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:32:37.457978-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:33:40.245529-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:34:42.930523-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:35:45.779862-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
now

2022-09-16 10:36:48.516978-05
(1 row)

Configuring Redis as session handler…
Setting php max children…
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.

2

This is the solution.

After restoring from backup you can disable the fulltextsearch app and restart the containers twice which should trigger the update again and suceed this time.

3

I do have a backup of the server from the snapshot backup function Linode provides. However, when I restore that, the Nextcloud instance is not reachable even though the containers are running. I will do the restore again and provide any logs that indicate a problem. Beyond that, do you have any suggestions of what to look for?

4

Getting this in the nextcloud container logs…

cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to operatingintelligence.com:443
5

Looks unrelated to me…

6

I googled a bit and found this for you: Upgrade of fulltextsearch to NC 24 fails · Issue #713 · nextcloud/fulltextsearch · GitHub

7

Thank you, that is helpful. I’m not at that point yet as I need to get the backup instance accessible again.

This seems to indicate a problem. Have not been able to get enough permission to see or do anything in the container’s file system. Is this a trail worthy of digging?

(…from apache logs)
apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites-enabled/000-default.conf: Permission denied

8

Yes, that looks like it could be worth digging.

1 Like
9

Well, I abandoned this in the interest of getting going again. Thank you szaimen for the fast help. Below is what Linode support provided for anyone that comes across this…

Based on that message, it seems like something in your website/docker configs got messed up when you restored from the backup. Apache is attempting to enable the 000-default.conf website file when it should be enabling the nextcloud.conf file.

I suggest attempting to get the Nextcloud site to start using the following command:

docker exec -u 0 -it nextcloud-aio-apache a2ensite nextcloud && service apache2 reload

This will connect to the Apache Docker container as root, enable the Nextcloud site, and reload the Apache service on the container.

During this process, your Nextcloud instance may tell you to stop the container with the following command:

sudo docker start nextcloud-aio-apache

In which case you may need your original password to log back into the application - the one that is several different words.

P.S. -for anyone struggling with Nextcloud, I would say this. This is an amazing project that allows separating from the big guys’ sticky interest in our data, with at times, more impressive performance. However, learn how to maintain and support it first. It’s easy to setup but hard to get running again when things go bad. I suggest testing your steps (especially upgrades) in another, disposable instance to see what happens.