Your message dated Mon, 15 Jul 2019 11:23:55 +0200
with message-id <[email protected]>
and subject line Re: Bug#932078: Starting systemd-docker directly
has caused the Debian Bug report #932078,
regarding systemd: errors out starting docker: Failed to trim compat systemd
cgroup [...]: Device or resource busy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
932078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932078
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 241-5
Severity: normal
Dear Maintainer,
after an upgrade from stretch to buster, starting a systemd service
fails. It tries to start a docker container, and fails with
> > Failed to trim compat systemd cgroup
/system.slice/tau-alert.service: Device or resource busy
More information:
root@tina:~# systemctl cat tau-alert.service
# /etc/systemd/system/tau-alert.service
[Unit]
Description=tau-alert
After=docker.service
Requires=docker.service
[Service]
ExecStart=/usr/bin/systemd-docker run -p 127.0.0.1:10000:10000 --rm
--name %n moritzlenz/tau-alert
Restart=always
RestartSec=10s
Type=notify
NotifyAccess=all
TimeoutStartSec=120
TimeoutStopSec=15
[Install]
WantedBy=multi-user.target
root@tina:~# systemctl status tau-alert.service
● tau-alert.service - tau-alert
Loaded: loaded (/etc/systemd/system/tau-alert.service; enabled;
vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun
2019-07-14 21:35:13 CEST; 3s ago
Process: 22243 ExecStart=/usr/bin/systemd-docker run -p
127.0.0.1:10000:10000 --rm --name tau-alert.service moritzlenz/tau-alert
(code=exited,
Main PID: 22243 (code=exited, status=1/FAILURE)
Jul 14 21:35:13 tina systemd[1]: tau-alert.service: Main process exited,
code=exited, status=1/FAILURE
Jul 14 21:35:13 tina systemd[1]: tau-alert.service: Failed with result
'exit-code'.
Jul 14 21:35:13 tina systemd[1]: Failed to start tau-alert.
root@tina:~# journalctl -xe|tail
-- The unit tau-alert.service has entered the 'failed' state with result
'exit-code'.
Jul 14 21:35:54 tina systemd[1]: Failed to trim compat systemd cgroup
/system.slice/tau-alert.service: Device or resource busy
Jul 14 21:35:54 tina systemd[1]: Failed to start tau-alert.
-- Subject: A start job for unit tau-alert.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit tau-alert.service has finished with a failure.
--
-- The job identifier is 14130 and the job result is failed.
I have no idea how to debug this.
-- Package-specific info:
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-4
ii libapparmor1 2.13.2-10
ii libaudit1 1:2.8.4-3
ii libblkid1 2.33.1-0.1
ii libc6 2.28-10
ii libcap2 1:2.25-2
ii libcryptsetup12 2:2.1.0-5
ii libgcrypt20 1.8.4-5
ii libgnutls30 3.6.7-4
ii libgpg-error0 1.35-1
ii libidn11 1.33-2.2
ii libip4tc0 1.8.2-4
ii libkmod2 26-1
ii liblz4-1 1.8.3-1
ii liblzma5 5.2.4-1
ii libmount1 2.33.1-0.1
ii libpam0g 1.3.1-5
ii libseccomp2 2.3.3-4
ii libselinux1 2.8-1+b1
ii libsystemd0 241-5
ii mount 2.33.1-0.1
ii util-linux 2.33.1-0.1
Versions of packages systemd recommends:
ii dbus 1.12.16-1
ii libpam-systemd 241-5
Versions of packages systemd suggests:
pn policykit-1 <none>
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.133
ii udev 241-5
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 15.07.19 um 07:45 schrieb Moritz Lenz:
> When I start systemd-docker directly, I get this error:
>
> root@tina:~# /usr/bin/systemd-docker run -p 127.0.0.1:10000:10000 --rm
> --name tau-alert moritzlenz/tau-alert
> docker: Error response from daemon: driver failed programming external
> connectivity on endpoint tau-alert
> (e06175d196da0a900cb6cfa34c3e083fbf34c8773b0ce9b065b6cf1b6a4ad8cc): Bind
> for 127.0.0.1:10000 failed: port is already allocated.
>
> I don't know what "allocated" means in this context, it's not in use at
> least:
>
> root@tina:~# netstat -tlpen|grep 10000|wc -l
> 0
>
>
>
I guess it makes sense to treat this as a docker problem then.
As I didn't find a package for /usr/bin/systemd-docker, I'm unable to
reassign the bug report (is this binary from a non-Debian provided
package?), so closing the bug report at this point.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
