Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#946179: [lxcfs] lxcfs tries to delete systemd cgroup folders, fails stopping lxc
41 views
Skip to first unread message
Synthea
Dec 4, 2019, 4:00:03 PM12/4/19
to
Package: lxcfs
Version: 2.0.7-1+deb9u1
Severity: grave
Here's lxc log:
lxc-start 20191204112931.787 INFO lxc_cgroup - cgroups/cgroup.c:cgroup_init:68 - cgroup driver cgroupfs initing for debian-test
lxc-start 20191204112931.790 ERROR lxc_cgfs - cgroups/cgfs.c:lxc_cgroupfs_create:901 - Could not find writable mount point for cgroup hierarchy 11 while trying to create cgroup.
lxc-start 20191204112931.802 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user/root/0
lxc-start 20191204112931.807 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user/root
lxc-start 20191204112931.808 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user
lxc-start 20191204112931.808 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-135.slice/session-1.scope
lxc-start 20191204112931.808 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-135.slice
lxc-start 20191204112931.808 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-0.slice/session-c1.scope
lxc-start 20191204112931.809 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-0.slice
lxc-start 20191204112931.817 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-1000.slice/session-2.scope
lxc-start 20191204112931.817 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-1000.slice
lxc-start 20191204112931.817 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice
lxc-start 20191204112931.817 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd/
lxc-start 20191204112931.817 ERROR lxc_start - start.c:lxc_spawn:1108 - Failed creating cgroups.
lxc-start 20191204112931.857 INFO lxc_conf - conf.c:lxc_delete_network:3015 - Removed interface "(null)" with index 18.
lxc-start 20191204112931.883 WARN lxc_conf - conf.c:lxc_delete_network:3038 - Failed to remove "vethXD8GPK" from host: Invalid argument.
lxc-start 20191204112931.883 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc-start 20191204112931.883 ERROR lxc_start - start.c:__lxc_start:1346 - Failed to spawn container "debian-test".
lxc-start 20191204112931.884 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc-start 20191204112931.884 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc-start 20191204112931.884 INFO lxc_conf - conf.c:run_script_argv:424 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "debian-test", config section "lxc".
lxc-start 20191204112932.401 ERROR lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
lxc-start 20191204112932.401 ERROR lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting
--- System information. ---
Architecture:
Kernel: Linux 4.9.0-5-amd64
Debian Release: 9.11
500 oldstable-updates deb.debian.org
500 oldstable security.debian.org
500 oldstable deb.debian.org
100 stretch-backports deb.debian.org
--- Package information. ---
Depends (Version) | Installed
==================================-+-===========
libc6 (>= 2.17) |
libfuse2 (>= 2.6) |
init-system-helpers (>= 1.18~) |
lsb-base (>= 3.0-6) |
Package's Recommends field is empty.
Package's Suggests field is empty.
Version: 2.0.7-1+deb9u1
Severity: grave
Here's lxc log:
lxc-start 20191204112931.787 INFO lxc_cgroup - cgroups/cgroup.c:cgroup_init:68 - cgroup driver cgroupfs initing for debian-test
lxc-start 20191204112931.790 ERROR lxc_cgfs - cgroups/cgfs.c:lxc_cgroupfs_create:901 - Could not find writable mount point for cgroup hierarchy 11 while trying to create cgroup.
lxc-start 20191204112931.802 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user/root/0
lxc-start 20191204112931.807 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user/root
lxc-start 20191204112931.808 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user
lxc-start 20191204112931.808 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-135.slice/session-1.scope
lxc-start 20191204112931.808 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-135.slice
lxc-start 20191204112931.808 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-0.slice/session-c1.scope
lxc-start 20191204112931.809 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-0.slice
lxc-start 20191204112931.817 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-1000.slice/session-2.scope
lxc-start 20191204112931.817 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-1000.slice
lxc-start 20191204112931.817 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice
lxc-start 20191204112931.817 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd/
lxc-start 20191204112931.817 ERROR lxc_start - start.c:lxc_spawn:1108 - Failed creating cgroups.
lxc-start 20191204112931.857 INFO lxc_conf - conf.c:lxc_delete_network:3015 - Removed interface "(null)" with index 18.
lxc-start 20191204112931.883 WARN lxc_conf - conf.c:lxc_delete_network:3038 - Failed to remove "vethXD8GPK" from host: Invalid argument.
lxc-start 20191204112931.883 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc-start 20191204112931.883 ERROR lxc_start - start.c:__lxc_start:1346 - Failed to spawn container "debian-test".
lxc-start 20191204112931.884 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc-start 20191204112931.884 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
lxc-start 20191204112931.884 INFO lxc_conf - conf.c:run_script_argv:424 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "debian-test", config section "lxc".
lxc-start 20191204112932.401 ERROR lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
lxc-start 20191204112932.401 ERROR lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting
--- System information. ---
Architecture:
Kernel: Linux 4.9.0-5-amd64
Debian Release: 9.11
500 oldstable-updates deb.debian.org
500 oldstable security.debian.org
500 oldstable deb.debian.org
100 stretch-backports deb.debian.org
--- Package information. ---
Depends (Version) | Installed
==================================-+-===========
libc6 (>= 2.17) |
libfuse2 (>= 2.6) |
init-system-helpers (>= 1.18~) |
lsb-base (>= 3.0-6) |
Package's Recommends field is empty.
Package's Suggests field is empty.
Pierre-Elliott Bécue
Dec 6, 2019, 6:20:03 AM12/6/19
to
Control: severity -1 normal
Hi,
Thanks for reporting this. The main issue with starting the container
does not seem to have anything to do with the failing cgroup_rmdir calls
even though I admit they shouldn't occur. The main issue lies in
the possibility to have this version released in stretch.
But, this bug is not as grave as you seem to think. I'm therefore
lowering the severity of the bug to the appropriate level.
With best regards,
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.
Hi,
Thanks for reporting this. The main issue with starting the container
does not seem to have anything to do with the failing cgroup_rmdir calls
even though I admit they shouldn't occur. The main issue lies in
"""lxc-start 20191204112931.790 ERROR lxc_cgfs - cgroups/cgfs.c:lxc_cgroupfs_create:901 - Could
not find writable mount point for cgroup hierarchy 11 while trying to create cgroup."""
A fix has been released in 2.0.8 by upstream, and I'll have a look at
not find writable mount point for cgroup hierarchy 11 while trying to create cgroup."""
the possibility to have this version released in stretch.
But, this bug is not as grave as you seem to think. I'm therefore
lowering the severity of the bug to the appropriate level.
With best regards,
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.
Pierre-Elliott Bécue
Dec 7, 2019, 9:30:03 AM12/7/19
to
Le vendredi 06 décembre 2019 à 23:25:42+0100, Synthea a écrit :
> Il giorno Fri, 6 Dec 2019 12:05:20 +0100
> Pierre-Elliott Bécue <p...@debian.org> ha scritto:
> By the way, are you sure it is solved in the version 2.0.8?
> I have tried to:
> -bump lxcfs and libpam-cgfs to backports (which are on version 2.0.8
> currently) and reboot
> -install lxcfs from the people repo here and reboot:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867619
> None solved my issue
>
> Best regards to you too :)
That's interesting. It supposed to be fixed in 2.0.8. :/
Do you have a full traceback with the bpo package?
Cheers!
> Il giorno Fri, 6 Dec 2019 12:05:20 +0100
> Pierre-Elliott Bécue <p...@debian.org> ha scritto:
>
> > Control: severity -1 normal
> >
> > Hi,
> >
> > Thanks for reporting this. The main issue with starting the container
> > does not seem to have anything to do with the failing cgroup_rmdir
> > calls even though I admit they shouldn't occur. The main issue lies in
> > Control: severity -1 normal
> >
> > Hi,
> >
> > Thanks for reporting this. The main issue with starting the container
> > does not seem to have anything to do with the failing cgroup_rmdir
> > calls even though I admit they shouldn't occur. The main issue lies in
> > """lxc-start 20191204112931.790 ERROR lxc_cgfs -
> > cgroups/cgfs.c:lxc_cgroupfs_create:901 - Could not find writable
> > mount point for cgroup hierarchy 11 while trying to create cgroup."""
> >
> > cgroups/cgfs.c:lxc_cgroupfs_create:901 - Could not find writable
> > mount point for cgroup hierarchy 11 while trying to create cgroup."""
> >
> > A fix has been released in 2.0.8 by upstream, and I'll have a look at
> > the possibility to have this version released in stretch.
> >
> > But, this bug is not as grave as you seem to think. I'm therefore
> > lowering the severity of the bug to the appropriate level.
> >
> > With best regards,
> >
>
> Fine, I thought it was a serious issue
> > the possibility to have this version released in stretch.
> >
> > But, this bug is not as grave as you seem to think. I'm therefore
> > lowering the severity of the bug to the appropriate level.
> >
> > With best regards,
> >
>
> By the way, are you sure it is solved in the version 2.0.8?
> I have tried to:
> -bump lxcfs and libpam-cgfs to backports (which are on version 2.0.8
> currently) and reboot
> -install lxcfs from the people repo here and reboot:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867619
> None solved my issue
>
> Best regards to you too :)
That's interesting. It supposed to be fixed in 2.0.8. :/
Do you have a full traceback with the bpo package?
Cheers!
Pierre-Elliott Bécue
Dec 8, 2019, 10:20:03 AM12/8/19
to
Le dimanche 08 décembre 2019 à 02:02:10+0100, Synthea a écrit :
> Sat, 7 Dec 2019 15:18:06 +0100 Pierre-Elliott Bécue <p...@debian.org>:
> include it in the original bugreport
> Sorry for not continuing the chat on the mailing list but it seems I've
> forgot to use the reply-to header
Start your container with lxc-start -n containername --logfile containername.log --logpriority TRACE
> Sat, 7 Dec 2019 15:18:06 +0100 Pierre-Elliott Bécue <p...@debian.org>:
> > Le vendredi 06 décembre 2019 à 23:25:42+0100, Synthea a écrit :
> > > Il giorno Fri, 6 Dec 2019 12:05:20 +0100
> > > Pierre-Elliott Bécue <p...@debian.org> ha scritto:
> > >
> > > > Control: severity -1 normal
> > > >
> > > > Hi,
> > > >
> > > > Thanks for reporting this. The main issue with starting the
> > > > container does not seem to have anything to do with the failing
> > > > cgroup_rmdir calls even though I admit they shouldn't occur. The
> > > > main issue lies in """lxc-start 20191204112931.790 ERROR lxc_cgfs
> > > Il giorno Fri, 6 Dec 2019 12:05:20 +0100
> > > Pierre-Elliott Bécue <p...@debian.org> ha scritto:
> > >
> > > > Control: severity -1 normal
> > > >
> > > > Hi,
> > > >
> > > > Thanks for reporting this. The main issue with starting the
> > > > container does not seem to have anything to do with the failing
> > > > cgroup_rmdir calls even though I admit they shouldn't occur. The
> > > > - cgroups/cgfs.c:lxc_cgroupfs_create:901 - Could not find writable
> > > > mount point for cgroup hierarchy 11 while trying to create
> > > > cgroup."""
> > > >
> > > > mount point for cgroup hierarchy 11 while trying to create
> > > > cgroup."""
> > > >
> > > > A fix has been released in 2.0.8 by upstream, and I'll have a
> > > > look at the possibility to have this version released in stretch.
> > > >
> > > > But, this bug is not as grave as you seem to think. I'm therefore
> > > > lowering the severity of the bug to the appropriate level.
> > > >
> > > > With best regards,
> > > >
> > >
> > > Fine, I thought it was a serious issue
> > > By the way, are you sure it is solved in the version 2.0.8?
> > > I have tried to:
> > > -bump lxcfs and libpam-cgfs to backports (which are on version 2.0.8
> > > currently) and reboot
> > > -install lxcfs from the people repo here and reboot:
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867619
> > > None solved my issue
> > >
> > > Best regards to you too :)
> >
> > That's interesting. It supposed to be fixed in 2.0.8. :/
> >
> > Do you have a full traceback with the bpo package?
> >
> > Cheers!
> >
>
> No, I don't have a full traceback, please tell me how to do one, I'll
> > > > look at the possibility to have this version released in stretch.
> > > >
> > > > But, this bug is not as grave as you seem to think. I'm therefore
> > > > lowering the severity of the bug to the appropriate level.
> > > >
> > > > With best regards,
> > > >
> > >
> > > Fine, I thought it was a serious issue
> > > By the way, are you sure it is solved in the version 2.0.8?
> > > I have tried to:
> > > -bump lxcfs and libpam-cgfs to backports (which are on version 2.0.8
> > > currently) and reboot
> > > -install lxcfs from the people repo here and reboot:
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867619
> > > None solved my issue
> > >
> > > Best regards to you too :)
> >
> > That's interesting. It supposed to be fixed in 2.0.8. :/
> >
> > Do you have a full traceback with the bpo package?
> >
> > Cheers!
> >
>
> include it in the original bugreport
> Sorry for not continuing the chat on the mailing list but it seems I've
> forgot to use the reply-to header
Start your container with lxc-start -n containername --logfile containername.log --logpriority TRACE
Synthea
Feb 1, 2020, 7:10:03 AM2/1/20
to
lxc-start 20191208225747.947 INFO lxc_start_ui - tools/lxc_start.c:main:275 - using rcfile [Containers folder (usually /var/lib/lxc)]/debian-test/config
lxc-start 20191208225748.571 WARN lxc_confile - confile.c:config_pivotdir:1910 - lxc.pivotdir is ignored. It will soon become an error.
lxc-start 20191208225748.864 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:309 - Going to wait for pid 5235.
lxc-start 20191208225748.872 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:328 - Trying to sync with child process.
lxc-start 20191208225748.877 INFO lxc_start - start.c:lxc_check_inherited:235 - Closed inherited fd: 4.
lxc-start 20191208225748.879 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:366 - Using pipe file descriptor 5 for monitord.
lxc-start 20191208225748.164 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:343 - Sucessfully synced with child process.
lxc-start 20191208225748.165 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:312 - Finished waiting on pid 5235.
lxc-start 20191208225748.166 INFO lxc_container - lxccontainer.c:do_lxcapi_start:804 - Attempting to set proc title to [lxc monitor] [Containers folder (usually /var/lib/lxc)] debian-test
lxc-start 20191208225748.169 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:309 - Going to wait for pid 5239.
lxc-start 20191208225748.170 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:328 - Trying to sync with child process.
lxc-start 20191208225748.171 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver nop
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .reject_force_umount # comment this to allow umount -f; not recommended.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for reject_force_umount action 0.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:251 - Setting Seccomp rule to reject force umounts.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for reject_force_umount action 0.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:251 - Setting Seccomp rule to reject force umounts.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .[all].
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .kexec_load errno 1.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for kexec_load action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for kexec_load action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .open_by_handle_at errno 1.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for open_by_handle_at action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for open_by_handle_at action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .init_module errno 1.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for init_module action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for init_module action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .finit_module errno 1.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for finit_module action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for finit_module action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:402 - processing: .delete_module errno 1.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:567 - Adding native rule for delete_module action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:570 - Adding compat rule for delete_module action 327681.
lxc-start 20191208225748.172 INFO lxc_seccomp - seccomp.c:parse_config_v2:580 - Merging in the compat Seccomp ctx into the main one.
lxc-start 20191208225748.173 DEBUG lxc_start - start.c:setup_signal_fd:273 - Set SIGCHLD handler with file descriptor: 5.
lxc-start 20191208225748.176 INFO lxc_start - start.c:lxc_check_inherited:235 - Closed inherited fd: 4.
lxc-start 20191208225748.177 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:366 - Using pipe file descriptor 5 for monitord.
lxc-start 20191208225748.179 DEBUG console - console.c:lxc_console_peer_default:468 - no console peer
lxc-start 20191208225748.179 INFO lxc_start - start.c:lxc_init:475 - Container "debian-test" is initialized.
lxc-start 20191208225748.181 DEBUG lxc_start - start.c:__lxc_start:1317 - Not dropping CAP_SYS_BOOT or watching utmp.
lxc-start 20191208225748.187 INFO lxc_conf - conf.c:instantiate_veth:2647 - Retrieved mtu 1500 from lxcbr0
lxc-start 20191208225748.189 INFO lxc_conf - conf.c:instantiate_veth:2672 - Attached 'veth91VC6G': to the bridge 'lxcbr0':
lxc-start 20191208225748.189 DEBUG lxc_conf - conf.c:instantiate_veth:2689 - instantiated veth 'veth91VC6G/veth3M6H5S', index is '17'
lxc-start 20191208225748.189 INFO lxc_cgroup - cgroups/cgroup.c:cgroup_init:68 - cgroup driver cgroupfs initing for debian-test
lxc-start 20191208225748.191 ERROR lxc_cgfs - cgroups/cgfs.c:lxc_cgroupfs_create:901 - Could not find writable mount point for cgroup hierarchy 11 while trying to create cgroup.
lxc-start 20191208225748.192 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user/root/0
lxc-start 20191208225748.192 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user/root
lxc-start 20191208225748.193 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user
lxc-start 20191208225748.194 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-135.slice/session-2.scope
lxc-start 20191208225748.194 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-135.slice
lxc-start 20191208225748.194 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-0.slice/session-c1.scope
lxc-start 20191208225748.195 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-0.slice
lxc-start 20191208225748.195 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-1000.slice/session-191.scope
lxc-start 20191208225748.195 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-1000.slice/session-3.scope
lxc-start 20191208225748.195 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice/user-1000.slice
lxc-start 20191208225748.195 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd//user.slice
lxc-start 20191208225748.196 ERROR lxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd/
lxc-start 20191208225748.196 ERROR lxc_start - start.c:lxc_spawn:1108 - Failed creating cgroups.
lxc-start 20191208225748.218 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:343 - Sucessfully synced with child process.
lxc-start 20191208225748.219 DEBUG lxc_monitor - monitor.c:lxc_monitord_spawn:312 - Finished waiting on pid 5239.
lxc-start 20191208225748.219 INFO lxc_monitor - monitor.c:lxc_monitor_sock_name:185 - Using monitor socket name "lxc/0c79b594b8cc6bb4/[Containers folder (usually /var/lib/lxc)]".
lxc-start 20191208225748.236 INFO lxc_conf - conf.c:lxc_delete_network:3015 - Removed interface "(null)" with index 17.
lxc-start 20191208225748.600 WARN lxc_conf - conf.c:lxc_delete_network:3038 - Failed to remove "veth91VC6G" from host: Invalid argument.
lxc-start 20191208225748.600 ERROR lxc_start - start.c:__lxc_start:1346 - Failed to spawn container "debian-test".
lxc-start 20191208225748.601 INFO lxc_conf - conf.c:run_script_argv:424 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "debian-test", config section "lxc".
lxc-start 20191208225749.208 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:172 - Command get_cgroup failed to receive response: Connection reset by peer.
lxc-start 20191208225754.214 ERROR lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
lxc-start 20191208225754.214 ERROR lxc_start_ui - tools/lxc_start.c:main:368 - To get more details, run the container in foreground mode.
lxc-start 20191208225754.214 ERROR lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options.
Mathias Gibbens
Dec 11, 2022, 9:20:03 PM12/11/22
to
Hi,
This bug was initially filed against a version from Debian stretch,
which is now oldoldstable. Is this problem still occurring for you, or
has it been resolved at some point over the past three years?
This evening I performed a minimal install of bullseye, and then
installed lxc and lxcfs. I was able to create both privileged and
unprivileged containers which appeared to operate correctly.
Mathias
This bug was initially filed against a version from Debian stretch,
which is now oldoldstable. Is this problem still occurring for you, or
has it been resolved at some point over the past three years?
This evening I performed a minimal install of bullseye, and then
installed lxc and lxcfs. I was able to create both privileged and
unprivileged containers which appeared to operate correctly.
Mathias
Mathias Gibbens
Aug 18, 2023, 4:40:05 PM8/18/23
to
Control: tags -1 + moreinfo
Tagging with moreinfo. This bug was opened against the version of
lxcfs in stretch, which is now oldoldoldstable. Since so much has
changed since then, without additional information or confirmation that
the problem still affects the version of lxcfs in bookworm, this bug
will be closed in a few months.
Mathias
Tagging with moreinfo. This bug was opened against the version of
lxcfs in stretch, which is now oldoldoldstable. Since so much has
changed since then, without additional information or confirmation that
the problem still affects the version of lxcfs in bookworm, this bug
will be closed in a few months.
Mathias
0 new messages