[prev in list] [next in list] [prev in thread] [next in thread]
List: lxc-users
Subject: [lxc-users] suddenly I cannot start lxcs due to cgroup error
From: John <da_audiophile () yahoo ! com>
Date: 2017-07-03 8:18:44
Message-ID: 1691886452.4016005.1499069924403 () mail ! yahoo ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I have been running lxcs for over a year without issues on an Odroid-C2 running \
Arch ARM (aarch64). Recently, I am unable to start any of the containers due to \
some errors around cgroups. This happened today after an update where 4 packages \
got updated but note that downgrading them back to the last-good versions and a \
reboot did not fix the problem. I am not finding anything contemporary when \
googling for causes. Advice is appreciated.
libsystemd (232-8 -> 233-6)
systemd (232-8 -> 233-6)
device-mapper (2.02.171-1 -> 2.02.172-1)
python2 (2.7.13-2 -> 2.7.13-3)
systemd-sysvcompat (232-8 -> 233-6)
Below is an example of the error when starting in foreground mode:
# lxc-start -n base-odroid64 -F
systemd 233 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK \
-SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID \
+ELFUTILS +KMOD +IDN default-hierarchy=hybrid) Detected virtualization lxc.
Detected architecture arm64.
Welcome to Arch Linux ARM!
Set hostname to <base-odroid64>.
Cannot determine cgroup we are running in: No medium found
Failed to allocate manager object: No medium found
[!!!!!!] Failed to allocate manager object, freezing.
Freezing execution.
[Attachment #5 (text/html)]
<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, \
sans-serif;font-size:medium;">I have been running lxcs for over a \
year without issues on an Odroid-C2 running Arch ARM (aarch64). Recently, \
I am unable to start any of the containers due to some errors around cgroups. \
This happened today after an update where 4 packages got updated but note that \
downgrading them back to the last-good versions and a reboot did not fix the problem. \
I am not finding anything contemporary when googling for causes. Advice \
is appreciated.<br><br><br>libsystemd (232-8 -> 233-6)<br>systemd (232-8 -> \
233-6)<br>device-mapper (2.02.171-1 -> 2.02.172-1) <br>python2 (2.7.13-2 \
-> 2.7.13-3)<br>systemd-sysvcompat (232-8 -> 233-6)<br><br><br>Below is an \
example of the error when starting in foreground mode:<br><br><br># lxc-start -n \
base-odroid64 -F<br>systemd 233 running in system mode. (+PAM -AUDIT -SELINUX -IMA \
-APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 \
+SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid)<br>Detected \
virtualization lxc.<br>Detected architecture arm64.<br><br>Welcome to Arch Linux \
ARM!<br><br>Set hostname to <base-odroid64>.<br>Cannot determine cgroup we are \
running in: No medium found<br>Failed to allocate manager object: No medium \
found<br>[!!!!!!] Failed to allocate manager object, freezing.<br>Freezing \
execution.<br></div></body></html>
[Attachment #6 (text/plain)]
_______________________________________________
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic