After updating from 10.1.0 to 10.1.1, Nextcloud container doesn’t boot (“It seems at least one container was not able to start correctly and is currently restarting”).
I did not make any changes to the setup, just ran “Update containers” from the AIO interface.
Logs:
2024-12-16T19:10:58.827211743Z Trying to fix docker.sock permissions internally...
2024-12-16T19:10:58.830506496Z Adding internal www-data to group ping
2024-12-16T19:10:59.497152646Z e[0;92mInitial startup of Nextcloud All-in-One complete!
2024-12-16T19:10:59.497221614Z You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
2024-12-16T19:10:59.497246913Z E.g. https://internal.ip.of.this.server:8080
2024-12-16T19:10:59.497267014Z ⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
2024-12-16T19:10:59.497288458Z
2024-12-16T19:10:59.497307007Z If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
2024-12-16T19:10:59.497327953Z https://your-domain-that-points-to-this-server.tld:8443e[0m
2024-12-16T19:11:00.918313229Z [Mon Dec 16 19:11:00.914287 2024] [mpm_event:notice] [pid 138:tid 138] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.2 configured -- resuming normal operations
2024-12-16T19:11:00.918344999Z [Mon Dec 16 19:11:00.914749 2024] [core:notice] [pid 138:tid 138] AH00094: Command line: 'httpd -D FOREGROUND'
2024-12-16T19:11:00.966258653Z [16-Dec-2024 19:11:00] NOTICE: fpm is running, pid 145
2024-12-16T19:11:00.966676110Z [16-Dec-2024 19:11:00] NOTICE: ready to handle connections
2024-12-16T19:11:00.968796929Z {"level":"info","ts":1734376260.9682603,"msg":"using config from file","file":"/Caddyfile"}
2024-12-16T19:11:00.970577107Z {"level":"info","ts":1734376260.97032,"msg":"adapted config to JSON","adapter":"caddyfile"}
2024-12-16T19:14:20.041453583Z e[0;92mInitial startup of Nextcloud All-in-One complete!
2024-12-16T19:14:20.041594419Z You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
2024-12-16T19:14:20.041602572Z E.g. https://internal.ip.of.this.server:8080
2024-12-16T19:14:20.041606069Z ⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
2024-12-16T19:14:20.041609986Z
2024-12-16T19:14:20.041613070Z If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
2024-12-16T19:14:20.041616388Z https://your-domain-that-points-to-this-server.tld:8443e[0m
2024-12-16T19:14:21.921621781Z {"level":"info","ts":1734376461.917305,"msg":"using config from file","file":"/Caddyfile"}
2024-12-16T19:14:21.934447991Z {"level":"info","ts":1734376461.9311073,"msg":"adapted config to JSON","adapter":"caddyfile"}
2024-12-16T19:14:21.956936014Z [Mon Dec 16 19:14:21.955806 2024] [mpm_event:notice] [pid 132:tid 132] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.2 configured -- resuming normal operations
2024-12-16T19:14:21.956966510Z [Mon Dec 16 19:14:21.955881 2024] [core:notice] [pid 132:tid 132] AH00094: Command line: 'httpd -D FOREGROUND'
2024-12-16T19:14:21.999616881Z [16-Dec-2024 19:14:21] NOTICE: fpm is running, pid 144
2024-12-16T19:14:21.999642947Z [16-Dec-2024 19:14:21] NOTICE: ready to handle connections
2024-12-16T19:20:58.462671368Z NOTICE: PHP message: 404 Not Found
2024-12-16T19:20:58.462698407Z Type: Slim\Exception\HttpNotFoundException
2024-12-16T19:20:58.462704142Z Code: 404
2024-12-16T19:20:58.462708381Z Message: Not found.
2024-12-16T19:20:58.462712615Z File: /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php
2024-12-16T19:20:58.462717168Z Line: 76
2024-12-16T19:20:58.462721370Z Trace: #0 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/RouteRunner.php(62): Slim\Middleware\RoutingMiddleware->performRouting(Object(GuzzleHttp\Psr7\ServerRequest))
2024-12-16T19:20:58.462726855Z #1 /var/www/docker-aio/php/vendor/slim/csrf/src/Guard.php(482): Slim\Routing\RouteRunner->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-12-16T19:20:58.462732059Z #2 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(177): Slim\Csrf\Guard->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Slim\Routing\RouteRunner))
2024-12-16T19:20:58.462737680Z #3 /var/www/docker-aio/php/vendor/slim/twig-view/src/TwigMiddleware.php(117): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-12-16T19:20:58.462743609Z #4 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Views\TwigMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
2024-12-16T19:20:58.462749272Z #5 /var/www/docker-aio/php/src/Middleware/AuthMiddleware.php(36): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-12-16T19:20:58.462754731Z #6 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(280): AIO\Middleware\AuthMiddleware->__invoke(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
2024-12-16T19:20:58.462761013Z #7 /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(77): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-12-16T19:20:58.462767059Z #8 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Middleware\ErrorMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
2024-12-16T19:20:58.462773005Z #9 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-12-16T19:20:58.462780112Z #10 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(209): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-12-16T19:20:58.462785754Z #11 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(193): Slim\App->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-12-16T19:20:58.462791383Z #12 /var/www/docker-aio/php/public/index.php(188): Slim\App->run()
2024-12-16T19:20:58.462796501Z #13 {main}
2024-12-16T19:20:58.462809023Z Tips: To display error details in HTTP response set "displayErrorDetails" to true in the ErrorHandler constructor.
Please help. Thanks.
Docker ps -a returns:
root@nc:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
81ad435e1684 nextcloud/aio-apache:beta "/start.sh /usr/bin/…" 11 minutes ago Up About a minute (healthy) 80/tcp, 0.0.0.0:11000->11000/tcp nextcloud-aio-apache
d5bf60a60b0d nextcloud/aio-whiteboard:beta "/start.sh" 11 minutes ago Up About a minute (healthy) 3002/tcp nextcloud-aio-whiteboard
9a5ed4305071 nextcloud/aio-notify-push:beta "/start.sh" 11 minutes ago Up About a minute (healthy) nextcloud-aio-notify-push
1d2d7f8caea9 nextcloud/aio-nextcloud:beta "/start.sh /usr/bin/…" 11 minutes ago Restarting (1) 27 seconds ago nextcloud-aio-nextcloud
e0a8f485d026 nextcloud/aio-imaginary:beta "/start.sh" 11 minutes ago Up About a minute (healthy) nextcloud-aio-imaginary
94c7412e1f21 nextcloud/aio-redis:beta "/start.sh" 11 minutes ago Up About a minute (healthy) 6379/tcp nextcloud-aio-redis
790f71993b73 nextcloud/aio-postgresql:beta "/start.sh" 11 minutes ago Up About a minute (healthy) 5432/tcp nextcloud-aio-database
b10aa97a5000 nextcloud/aio-talk:beta "/start.sh superviso…" 11 minutes ago Up About a minute (healthy) 0.0.0.0:3478->3478/tcp, 0.0.0.0:3478->3478/udp, :::3478->3478/tcp, :::3478->3478/udp nextcloud-aio-talk
6048c9acde0e nextcloud/aio-collabora:beta "/start-collabora-on…" 11 minutes ago Up About a minute (healthy) 9980/tcp nextcloud-aio-collabora
0dbddf5161e2 nextcloud/aio-watchtower:beta "/start.sh" 22 minutes ago Exited (0) 21 minutes ago nextcloud-aio-watchtower
c0b063e87bd4 nextcloud/aio-fulltextsearch:latest "/bin/tini -- /usr/l…" 7 months ago Exited (143) 7 months ago nextcloud-aio-fulltextsearch
905ba8d23dc5 nextcloud/aio-docker-socket-proxy:latest "/start.sh" 7 months ago Exited (138) 7 months ago nextcloud-aio-docker-socket-proxy
root@nc:~#
docker logs nextcloud-aio-nextcloud returns
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:21:29.003379+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Enabling Imagick...
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.20/main: No such file or directory
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.20/community: No such file or directory
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:21:32.937981+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:21:35.840266+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:21:39.066844+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:21:42.577744+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:21:46.947946+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:21:52.800591+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:22:01.808256+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
------------------------------
2024-12-16 20:22:17.26991+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:22:45.656724+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:23:39.537745+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:24:42.249711+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
------------------------------
2024-12-16 20:25:45.04675+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:26:47.799755+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:27:50.509783+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:28:53.353783+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:29:56.092535+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:30:16.815215+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:30:19.611265+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:30:22.460052+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:30:25.658456+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:30:29.137917+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:30:33.486882+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:30:39.362678+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.6) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.5) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:30:48.378718+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
nc: getaddrinfo for host "nextcloud-aio-redis" port 6379: Name does not resolve
Waiting for redis to start...
nc: getaddrinfo for host "nextcloud-aio-redis" port 6379: Name does not resolve
Waiting for redis to start...
Waiting for database to start...
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:31:14.067485+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:31:17.173555+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:31:20.495178+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:31:23.656661+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:31:27.204573+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:31:31.575992+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:31:37.448698+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:31:46.598558+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:32:02.005287+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:32:30.286336+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:33:24.190451+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-12-16 20:34:26.851696+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.8) 6379 port [tcp/redis] succeeded!
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.
Removing
/var/lib/docker/volumes/nextcloud_aio_nextcloud_data/_data/update.failed
and restarting the containers fixed the issue
1 Like