Hello ive just notice that Collabora Online Development Edition version 24.04.8.2 do not start anymore
Im running UCS version 5.0-9 errata1166
Here is some debug ive take
root@cloud:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
24e33ba4a995 docker.software-univention.de/collabora:24.04.8.2 “/bin/sh -c 'bash st…” 3 weeks ago Created objective_bhabha
d55564f33fcb docker.software-univention.de/collabora:24.04.8.2 “/bin/sh -c 'bash st…” 3 weeks ago Up 24 hours 0.0.0.0:9980->9980/tcp trusting_davinci
b4aa8dc29c61 docker.software-univention.de/nextcloud:28.0.7-0 “/bin/sh -c /usr/sbi…” 4 months ago Up 24 hours 0.0.0.0:40000->80/tcp dazzling_robinson
Is it normal that we see 2 collabora docker here ?
root@cloud:~# systemctl start docker-app-collabora.service
Job for docker-app-collabora.service failed because the control process exited with error code.
See “systemctl status docker-app-collabora.service” and “journalctl -xe” for details.
root@cloud:~# systemctl status docker-app-collabora.service
● docker-app-collabora.service - LSB: Start the Container for collabora
Loaded: loaded (/etc/init.d/docker-app-collabora; generated)
Active: failed (Result: exit-code) since Thu 2024-11-21 10:08:09 EST; 14s ago
Docs: man:systemd-sysv-generator(8)
Process: 15891 ExecStart=/etc/init.d/docker-app-collabora start (code=exited, status=1/FAILURE)
Nov 21 10:08:08 cloud systemd[1]: Starting LSB: Start the Container for collabora…
Nov 21 10:08:09 cloud docker-app-collabora[15891]: Starting collabora Container 24e33ba4a995dce6611e482227e68a1fcf4f809dc2fe4c10f7d770c9819650e7 …Error response from daemon
Nov 21 10:08:09 cloud systemd[1]: docker-app-collabora.service: Control process exited, code=exited, status=1/FAILURE
Nov 21 10:08:09 cloud systemd[1]: docker-app-collabora.service: Failed with result ‘exit-code’.
Nov 21 10:08:09 cloud systemd[1]: Failed to start LSB: Start the Container for collabora.
root@cloud:~# journalctl -xe
– The job identifier is 5026.
Nov 21 10:08:09 cloud kernel: docker0: port 3(vethee15b02) entered blocking state
Nov 21 10:08:09 cloud kernel: docker0: port 3(vethee15b02) entered disabled state
Nov 21 10:08:09 cloud kernel: device vethee15b02 entered promiscuous mode
Nov 21 10:08:09 cloud systemd-udevd[15936]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 21 10:08:09 cloud systemd-udevd[15936]: Using default interface naming scheme ‘v240’.
Nov 21 10:08:09 cloud systemd-udevd[15936]: Could not generate persistent MAC address for vethbdc2c7d: No such file or directory
Nov 21 10:08:09 cloud systemd-udevd[15937]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 21 10:08:09 cloud systemd-udevd[15937]: Using default interface naming scheme ‘v240’.
Nov 21 10:08:09 cloud systemd-udevd[15937]: Could not generate persistent MAC address for vethee15b02: No such file or directory
Nov 21 10:08:09 cloud dockerd[818]: time=“2024-11-21T10:08:09.132229986-05:00” level=warning msg="Failed to allocate and map port 9980-9980: Bind for 0.0.0.0:9980 failed: por
Nov 21 10:08:09 cloud kernel: docker0: port 3(vethee15b02) entered disabled state
Nov 21 10:08:09 cloud kernel: device vethee15b02 left promiscuous mode
Nov 21 10:08:09 cloud kernel: docker0: port 3(vethee15b02) entered disabled state
Nov 21 10:08:09 cloud dockerd[818]: time=“2024-11-21T10:08:09.193930524-05:00” level=error msg="24e33ba4a995dce6611e482227e68a1fcf4f809dc2fe4c10f7d770c9819650e7 cleanup: fail
Nov 21 10:08:09 cloud systemd[1]: var-lib-docker-overlay-7d7a9064f9d16335f992fb2c3cc6d2223adb4e47eabee2c4d95534d65bb11e1c-merged.mount: Succeeded.
– Subject: Unit succeeded
– Defined-By: systemd
– Support: Debian -- User Support
– The unit var-lib-docker-overlay-7d7a9064f9d16335f992fb2c3cc6d2223adb4e47eabee2c4d95534d65bb11e1c-merged.mount has successfully entered the ‘dead’ state.
Nov 21 10:08:09 cloud dockerd[818]: time=“2024-11-21T10:08:09.207578437-05:00” level=error msg="Handler for POST /v1.41/containers/24e33ba4a995dce6611e482227e68a1fcf4f809dc2f
Nov 21 10:08:09 cloud docker-app-collabora[15891]: Starting collabora Container 24e33ba4a995dce6611e482227e68a1fcf4f809dc2fe4c10f7d770c9819650e7 …Error response from daemon
Nov 21 10:08:09 cloud systemd[1]: docker-app-collabora.service: Control process exited, code=exited, status=1/FAILURE
– Subject: Unit process exited
– Defined-By: systemd
– Support: Debian -- User Support
– An ExecStart= process belonging to unit docker-app-collabora.service has exited.
– The process’ exit code is ‘exited’ and its exit status is 1.
Nov 21 10:08:09 cloud systemd[1]: docker-app-collabora.service: Failed with result ‘exit-code’.
– Subject: Unit failed
– Defined-By: systemd
– Support: Debian -- User Support
– The unit docker-app-collabora.service has entered the ‘failed’ state with result ‘exit-code’.
Nov 21 10:08:09 cloud systemd[1]: Failed to start LSB: Start the Container for collabora.
– Subject: A start job for unit docker-app-collabora.service has failed
– Defined-By: systemd
– Support: Debian -- User Support
– A start job for unit docker-app-collabora.service has finished with a failure.
– The job identifier is 5026 and the job result is failed.
Nov 21 10:08:46 cloud CRON[15665]: pam_unix(cron:session): session closed for user root
lines 1144-1189/1189 (END)
Can someone help me with that please
Thanks !