Hi,
I wanted to update to core 2.5.0-dev.5 but somehow the update progress ‘hangs’. I have this happing on 2 servers. The cluster admin GUI is not longer refreshing or accessable (refreshing horizontal bars keep refreshing).
A reboot only help to get back to the cluster admin Guide and the results is as per below screenshot.
I have no idea what to look for in the logs
i thought i was the only one getting this issue, tbh i was afraid to ask since av been doing alot on the server.
I saw something on the dev tracker regarding updates etc, maybe its in the pipline and should be resolved
Just to exclude it: Does it help to refresh the browser or clear the cache?
Are there errors or warnings in the cluster context logs after you started the update?
No, not at all. Tried everything with the browser at no luck. Resolution is at server level (in my simple reboot)
I’m not sure what to look for and audit or logs are not available through cluster admin, only after a reboot.
Adding info tat I can catch while the infinite spinner is showing:
Feb 13 03:22:50 srv1 podman[42801]: 6441aa302112e7d4f2127a496049d3f7ede4554ac158853491184c5b5ce11255
Feb 13 03:22:50 srv1 systemd[1394]: Started libcrun container.
Feb 13 03:22:50 srv1 podman[42812]: 6441aa302112e7d4f2127a496049d3f7ede4554ac158853491184c5b5ce11255
Feb 13 03:22:50 srv1 systemd[1394]: Started Podman mariadb.service.
Feb 13 03:22:50 srv1 systemd[1394]: Starting Podman phpmyadmin-app.service…
Feb 13 03:22:50 srv1 systemd[1394]: Started libcrun container.
Feb 13 03:22:50 srv1 podman[42849]: 1c4c91324c781a749fd29eee5fe0eefa00594277542834d01dc6cfa0811e4680
Feb 13 03:22:50 srv1 traefik[2930]: 192.145.39.170 - - [13/Feb/2024:02:22:50 +0000] “GET /cluster-admin/api/cluster/task/7daf81c8-0f13-496a-8118-8e3a3bcd7834/context HTTP/2.0” 200 280 “-” “-” 418 “ApiServer-https@file” “http://127.0.0.1:9311” 12ms
Feb 13 03:22:50 srv1 phpmyadmin-app[42861]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 10.0.2.100. Set the ‘ServerName’ directive globally to suppress this message
Feb 13 03:22:50 srv1 phpmyadmin-app[42861]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 10.0.2.100. Set the ‘ServerName’ directive globally to suppress this message
Feb 13 03:22:50 srv1 phpmyadmin-app[42861]: [Tue Feb 13 02:22:50.493997 2024] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.57 (Debian) PHP/8.2.8 configured – resuming normal operations
Feb 13 03:22:50 srv1 phpmyadmin-app[42861]: [Tue Feb 13 02:22:50.494418 2024] [core:notice] [pid 1] AH00094: Command line: ‘apache2 -D FOREGROUND’
Feb 13 03:22:50 srv1 podman[42870]: Enabling site phpmyadmin.
Feb 13 03:22:50 srv1 podman[42870]: To activate the new configuration, you need to run:
Feb 13 03:22:50 srv1 podman[42870]: service apache2 reload
Feb 13 03:22:50 srv1 phpmyadmin-app[42861]: [Tue Feb 13 02:22:50.749763 2024] [mpm_prefork:notice] [pid 1] AH00171: Graceful restart requested, doing restart
Feb 13 03:22:50 srv1 phpmyadmin-app[42861]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 10.0.2.100. Set the ‘ServerName’ directive globally to suppress this message
Feb 13 03:22:50 srv1 podman[42870]: Reloading Apache httpd web server: apache2.
Feb 13 03:22:50 srv1 phpmyadmin-app[42861]: [Tue Feb 13 02:22:50.802183 2024] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.57 (Debian) PHP/8.2.8 configured – resuming normal operations
Feb 13 03:22:50 srv1 phpmyadmin-app[42861]: [Tue Feb 13 02:22:50.802307 2024] [core:notice] [pid 1] AH00094: Command line: ‘apache2 -D FOREGROUND’
Feb 13 03:22:50 srv1 systemd[1394]: Started Podman phpmyadmin-app.service.
Feb 13 03:22:50 srv1 systemd[1394]: Starting Podman mariadb-app.service…
Feb 13 03:22:50 srv1 podman[42948]: time=“2024-02-13T03:22:50+01:00” level=warning msg=“Unmounting container "mariadb-app" while attempting to delete storage: unmounting "/home/mariadb1/.local/share/containers/storage/overlay/3dfbbc638ca42cb31732b4d4951d23f9199eafce1c536646d4d22cfca2b450b4/merged": invalid argument”
Feb 13 03:22:50 srv1 podman[42948]: Error: removing storage for container “mariadb-app”: unmounting “/home/mariadb1/.local/share/containers/storage/overlay/3dfbbc638ca42cb31732b4d4951d23f9199eafce1c536646d4d22cfca2b450b4/merged”: invalid argument
Feb 13 03:22:50 srv1 systemd[1394]: mariadb-app.service: Control process exited, code=exited, status=125/n/a
Feb 13 03:22:50 srv1 systemd[1394]: mariadb-app.service: Failed with result ‘exit-code’.
Feb 13 03:22:50 srv1 systemd[1394]: Failed to start Podman mariadb-app.service.
Feb 13 03:22:51 srv1 systemd[1394]: mariadb-app.service: Scheduled restart job, restart counter is at 119.
Feb 13 03:22:51 srv1 systemd[1394]: Stopped Podman mariadb-app.service.
Feb 13 03:22:51 srv1 systemd[1394]: Stopping Podman phpmyadmin-app.service…
Feb 13 03:22:51 srv1 phpmyadmin-app[42861]: [Tue Feb 13 02:22:51.400757 2024] [mpm_prefork:notice] [pid 1] AH00170: caught SIGWINCH, shutting down gracefully
Feb 13 03:22:52 srv1 podman[42967]: 1c4c91324c781a749fd29eee5fe0eefa00594277542834d01dc6cfa0811e4680
Feb 13 03:22:52 srv1 podman[42987]: 1c4c91324c781a749fd29eee5fe0eefa00594277542834d01dc6cfa0811e4680
Feb 13 03:22:52 srv1 systemd[1394]: Stopped Podman phpmyadmin-app.service.
Feb 13 03:22:52 srv1 systemd[1394]: Stopping Podman mariadb.service…
Feb 13 03:22:52 srv1 podman[42998]: 6441aa302112e7d4f2127a496049d3f7ede4554ac158853491184c5b5ce11255
Feb 13 03:22:52 srv1 systemd[1394]: Removed slice cgroup user-libpod_pod_6441aa302112e7d4f2127a496049d3f7ede4554ac158853491184c5b5ce11255.slice.
Feb 13 03:22:52 srv1 podman[43020]: 6441aa302112e7d4f2127a496049d3f7ede4554ac158853491184c5b5ce11255
Feb 13 03:22:52 srv1 systemd[1394]: Stopped Podman mariadb.service.
Feb 13 03:22:52 srv1 systemd[1394]: Starting Podman mariadb.service…
Feb 13 03:22:52 srv1 systemd[1394]: Created slice cgroup user-libpod_pod_4a85699298edb877976e959b22cab83e5a22ad623383c61167a2c5954cad2591.slice.
Feb 13 03:22:52 srv1 podman[43031]: 4a85699298edb877976e959b22cab83e5a22ad623383c61167a2c5954cad2591
Feb 13 03:22:53 srv1 systemd[1394]: Started libcrun container.
Feb 13 03:22:53 srv1 podman[43042]: 4a85699298edb877976e959b22cab83e5a22ad623383c61167a2c5954cad2591
Feb 13 03:22:53 srv1 systemd[1394]: Started Podman mariadb.service.
Feb 13 03:22:53 srv1 systemd[1394]: Starting Podman phpmyadmin-app.service…
I already hit a similar issue. Could you attach the output of
last reboot
reboot system boot 5.14.0-362.18.1. Tue Feb 13 03:30 still running
reboot system boot 5.14.0-362.18.1. Tue Feb 13 03:09 - 03:30 (00:20)
reboot system boot 5.14.0-362.18.1. Sun Feb 11 14:18 - 03:09 (1+12:50)
reboot system boot 5.14.0-362.18.1. Sun Feb 11 12:56 - 14:18 (01:21)
reboot system boot 5.14.0-362.18.1. Sun Feb 11 01:42 - 12:56 (11:13)
reboot system boot 5.14.0-362.18.1. Fri Feb 9 13:20 - 01:42 (1+12:21)
reboot system boot 5.14.0-362.18.1. Thu Feb 8 23:12 - 13:19 (14:07)
reboot system boot 5.14.0-362.18.1. Thu Feb 8 21:47 - 23:12 (01:25)
reboot system boot 5.14.0-362.8.1.e Thu Nov 23 01:57 - 21:46 (77+19:49)
reboot system boot 5.14.0-284.30.1. Sun Nov 19 18:56 - 01:56 (3+07:00)
reboot system boot 5.14.0-284.30.1. Sun Nov 19 05:39 - 18:56 (13:16)
reboot system boot 5.14.0-284.30.1. Wed Nov 15 22:08 - 18:56 (3+20:47)
reboot system boot 5.14.0-284.30.1. Sun Nov 12 05:55 - 22:08 (3+16:13)
reboot system boot 5.14.0-284.30.1. Mon Nov 6 18:30 - 05:54 (5+11:24)
reboot system boot 5.14.0-284.30.1. Sat Nov 4 19:56 - 17:36 (1+21:39)
reboot system boot 5.14.0-284.30.1. Sat Nov 4 10:08 - 19:56 (09:47)
reboot system boot 5.14.0-284.30.1. Fri Oct 20 02:27 - 09:07 (15+07:40)
reboot system boot 5.14.0-284.30.1. Sat Oct 7 00:00 - 02:26 (13+02:25)
reboot system boot 5.14.0-284.30.1. Wed Oct 4 14:03 - 02:26 (15+12:23)
reboot system boot 5.14.0-284.30.1. Mon Oct 2 20:45 - 14:02 (1+17:16)
wtmp begins Mon Oct 2 20:45:55 2023