-
Notifications
You must be signed in to change notification settings - Fork 704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update to nc-aio 10 from nc-aio 8.x failed (nextcloud-aio-nextcloud won't start) #5683
Comments
I Think I updated from a 8.x version But I have the same Issue. This is after I restored from backup and once stopped and started the containers. 2024-12-03T18:54:46.285726335Z Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded! |
Having the same issue here
|
This seems to be the problem |
Hi, thanks for the report! A fix is in #5718 |
This is now fixed with v10.1.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel |
I use docker-installed nextcloud-aio and follow standard upgrade path to 10.0 via https://myhost:11080/api ....token=5ad2e0f...
mastercontainer was upgraded successfully
containers start to upgrade, redis & db upgraded successfully and started
others are depend on nextcloud-aio-nextcloud, but it was not started (waiting to start in loop, but cannot start because " update.failed file in the datadir " was created
I was wait for half of hour, bit see in log only "failed message" loop. Then I delete "update.failed" file and restart container nextcloud-aio-nextcloud, and it continue to update (and finish it successfully). Logs below
Steps to reproduce
Expected behavior
Smooth upgrade as earlier versions
Actual behavior
Upgrade hangs and containers was not start
Other information
Host OS Synology ds220+
Output of
sudo docker info
Server Version: 20.10.23
OSType: linux
Architecture: x86_64
CPUs: 2
Security Options:
apparmor
Kernel Version: 4.4.302+
Operating System: Synology NAS
Storage Driver: btrfs
Build Version: Btrfs v4.0
Library Version: 101
Logging Driver: db
Cgroup Driver: cgroupfs
Cgroup Version: 1
Other valuable info
upgrade failed log (see "Parse error: syntax error, unexpected token "/"" )
2024-11-30T10:06:49.430492541Z Connection to nextcloud-aio-database (172.18.0.3) 5432 port [tcp/postgresql] succeeded!
2024-11-30T10:06:52.240996762Z now
2024-11-30T10:06:52.241438900Z -------------------------------
2024-11-30T10:06:52.241479283Z 2024-11-30 14:06:52.225645+04
2024-11-30T10:06:52.241518704Z (1 row)
2024-11-30T10:06:52.241551684Z
2024-11-30T10:06:52.339465137Z + '[' -f /dev-dri-group-was-added ']'
2024-11-30T10:06:52.339759934Z ++ find /dev -maxdepth 1 -mindepth 1 -name dri
2024-11-30T10:06:52.350560599Z + '[' -n '' ']'
2024-11-30T10:06:52.350628848Z + set +x
2024-11-30T10:06:52.404613611Z Enabling Imagick...
2024-11-30T10:07:00.501831372Z WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.20/main: No such file or directory
2024-11-30T10:07:00.502241053Z WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.20/community: No such file or directory
2024-11-30T10:07:00.628945907Z Connection to nextcloud-aio-redis (172.18.0.4) 6379 port [tcp/redis] succeeded!
2024-11-30T10:07:02.064018222Z + NEXT_MAJOR=29
2024-11-30T10:07:02.064309781Z + curl -fsSL -o nextcloud.tar.bz2 https://download.nextcloud.com/server/releases/latest-29.tar.bz2
2024-11-30T10:07:58.840349394Z + curl -fsSL -o nextcloud.tar.bz2.asc https://download.nextcloud.com/server/releases/latest-29.tar.bz2.asc
2024-11-30T10:07:59.804160355Z ++ mktemp -d
2024-11-30T10:08:00.203165398Z + GNUPGHOME=/tmp/tmp.c6uEYhj0E0
2024-11-30T10:08:00.203289590Z + export GNUPGHOME
2024-11-30T10:08:00.203320684Z + gpg --batch --keyserver keyserver.ubuntu.com --recv-keys 28806A878AE423A28372792ED75899B9A724937A
2024-11-30T10:08:00.960621648Z gpg: keybox '/tmp/tmp.c6uEYhj0E0/pubring.kbx' created
2024-11-30T10:08:02.270380410Z gpg: /tmp/tmp.c6uEYhj0E0/trustdb.gpg: trustdb created
2024-11-30T10:08:02.270854691Z gpg: key D75899B9A724937A: public key "Nextcloud Security [email protected]" imported
2024-11-30T10:08:02.693998851Z gpg: Total number processed: 1
2024-11-30T10:08:02.694156097Z gpg: imported: 1
2024-11-30T10:08:02.694322899Z + gpg --batch --verify nextcloud.tar.bz2.asc nextcloud.tar.bz2
2024-11-30T10:08:04.524019459Z gpg: Signature made Thu Oct 10 13:18:34 2024 +04
2024-11-30T10:08:04.524453015Z gpg: using RSA key 28806A878AE423A28372792ED75899B9A724937A
2024-11-30T10:08:04.525354312Z gpg: Good signature from "Nextcloud Security [email protected]" [unknown]
2024-11-30T10:08:04.525407498Z gpg: WARNING: This key is not certified with a trusted signature!
2024-11-30T10:08:04.525445235Z gpg: There is no indication that the signature belongs to the owner.
2024-11-30T10:08:04.525479528Z Primary key fingerprint: 2880 6A87 8AE4 23A2 8372 792E D758 99B9 A724 937A
2024-11-30T10:08:04.526097753Z + mkdir -p /usr/src/tmp
2024-11-30T10:08:04.527736638Z + tar -xjf nextcloud.tar.bz2 -C /usr/src/tmp/
2024-11-30T10:08:59.851799949Z + gpgconf --kill all
2024-11-30T10:09:00.116868044Z + rm nextcloud.tar.bz2.asc nextcloud.tar.bz2
2024-11-30T10:09:00.226535149Z + mkdir -p /usr/src/tmp/nextcloud/data
2024-11-30T10:09:00.226686197Z + mkdir -p /usr/src/tmp/nextcloud/custom_apps
2024-11-30T10:09:00.231298919Z + chmod +x /usr/src/tmp/nextcloud/occ
2024-11-30T10:09:00.241266171Z + cp -r /usr/src/nextcloud/config/CAN_INSTALL /usr/src/nextcloud/config/aio.config.php /usr/src/nextcloud/config/apcu.config.php /usr/src/nextcloud/config/apps.config.php /usr/src/nextcloud/config/config.sample.php /usr/src/nextcloud/config/proxy.config.php /usr/src/nextcloud/config/redis.config.php /usr/src/nextcloud/config/reverse-proxy.config.php /usr/src/nextcloud/config/s3.config.php /usr/src/nextcloud/config/smtp.config.php /usr/src/nextcloud/config/swift.config.php /usr/src/tmp/nextcloud/config/
2024-11-30T10:09:00.276738922Z + mkdir -p /usr/src/tmp/nextcloud/apps/nextcloud-aio
2024-11-30T10:09:00.276819155Z + cp -r /usr/src/nextcloud/apps/nextcloud-aio/appinfo /usr/src/nextcloud/apps/nextcloud-aio/composer /usr/src/nextcloud/apps/nextcloud-aio/lib /usr/src/nextcloud/apps/nextcloud-aio/readme.md /usr/src/nextcloud/apps/nextcloud-aio/templates /usr/src/tmp/nextcloud/apps/nextcloud-aio/
2024-11-30T10:09:00.276865560Z + mv /usr/src/nextcloud /usr/src/temp-nextcloud
2024-11-30T10:09:00.446109534Z + mv /usr/src/tmp/nextcloud /usr/src/nextcloud
2024-11-30T10:09:00.460686966Z + rm -r /usr/src/tmp
2024-11-30T10:09:00.462260119Z + rm -r /usr/src/temp-nextcloud
2024-11-30T10:09:05.952406959Z ++ php -r 'require /usr/src/nextcloud/version.php; echo implode('''.''', $OC_Version);'
2024-11-30T10:09:07.422229099Z + image_version='
2024-11-30T10:09:07.422583593Z Parse error: syntax error, unexpected token "/" in Command line code on line 1'
2024-11-30T10:09:20.691762396Z Connection to nextcloud-aio-database (172.18.0.3) 5432 port [tcp/postgresql] succeeded!
2024-11-30T10:09:23.057917491Z now
2024-11-30T10:09:23.058334138Z ------------------------------
2024-11-30T10:09:23.058369182Z 2024-11-30 14:09:23.05725+04
2024-11-30T10:09:23.058402232Z (1 row)
2024-11-30T10:09:23.058428370Z
2024-11-30T10:09:23.121637853Z + '[' -f /dev-dri-group-was-added ']'
2024-11-30T10:09:23.121965369Z ++ find /dev -maxdepth 1 -mindepth 1 -name dri
2024-11-30T10:09:23.163495958Z + '[' -n '' ']'
2024-11-30T10:09:23.163621223Z + set +x
2024-11-30T10:09:23.260387193Z Connection to nextcloud-aio-redis (172.18.0.4) 6379 port [tcp/redis] succeeded!
2024-11-30T10:09:23.630625718Z The last Nextcloud update failed.
2024-11-30T10:09:23.630775680Z Please restore from backup and try again!
2024-11-30T10:09:23.630875184Z 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.
And when upgrade continues after restart, notification was failed also
2024-11-30T11:16:10.992375753Z Posting notifications to users that are admins...
2024-11-30T11:16:15.906754771Z Posting 'Nextcloud update to 29.0.8.1 successful!' to: ncp
2024-11-30T11:16:16.385444856Z
2024-11-30T11:16:16.389520917Z
2024-11-30T11:16:16.389744086Z The "--object-type" option does not exist.
2024-11-30T11:16:16.389900480Z
2024-11-30T11:16:16.389948526Z
2024-11-30T11:16:16.389973560Z notification:generate [-l|--long-message LONG-MESSAGE] [-d|--dummy] [--]
2024-11-30T11:16:16.390015312Z
2024-11-30T11:16:16.404878023Z Done!
The text was updated successfully, but these errors were encountered: