I've not seen this issue in quite a long time at least on bionic/focal,
so will tentatively mark it as fix released. If someone still hits this,
please tell us on what release and we'll add some SRU tasks.
** Changed in: binfmt-support (Ubuntu)
Status: Confirmed => Fix Released
** Changed
This worked on my xenial host to unwedge the trusty containers:
sudo service binfmt-support restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555760
Title:
Too many levels of symbolic lin
Forcing a reload of the LPAR brings the system back online with juju,
lxd, and df happy again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555760
Title:
Too many levels of symbolic links /proc/s
2c - just hit this myself on xenail s390x with a soaking openstack-on-
lxd installation.
masking proc-sys-fs-binfmt_misc.automount seemed to be a bad idea...
systemd is in a bad state..
ubuntu@zs93kvi:~$ systemctl -a | grep binfmt
proc-sys-fs-binfmt_misc.automount
For any poor soul who wanders here, here is the best known workaround
for this issue I've seen to date:
22-09-2016 15:23:18 < stgraber!~stgraber@ubuntu/member/stgraber: cmars:
if you mask (systemctl mask) the systemd units related to binfmt
(systemctl -a | grep binfmt) and reboot, then the problem
I apt purge'ed binfmt-support from my system and I'm still able to
comment here :) We'll see if this fixes the issue.
If it does, why was it even installed on my system by default to begin
with?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still seeing this on xenial enough that I've written a script to perform
the umounting when LXD gets stuck. Do I even need binfmt_misc on my
system? Can I just remove it or would that break something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
To continue my previous comment...
It is reproducible with :
binfmt-support (2.1.6-1)
systemd(229-4ubuntu6)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555760
Title:
Too many levels of
I don't have the error "Too many levels of symbolic links" when doing an
"ls" command but I do have a problem using "df" on Xenial after
installing Openstack with lxd using "conjure-up"
"df" works fine, but after a reboot, it hangs.
A "strace df" shows that it hangs at doing :
..
stat("/sys/fs/cg
We'd have to find a way to reproduce it and find what's actually causing
it before we have any chance of fixing it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555760
Title:
Too many levels of s
When is this going to be fixed upstream? I'm having to remount on the
host and restart containers quite often. I can't imagine this will be a
good user experience for new LXD users on xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
That redhat bug shows a similar end result though I doubt the cause is
the same in Ubuntu's case. We wouldn't see such random occurrences of
the bug if it was something as simple as a package shipping a completely
broken binfmt snippet.
--
You received this bug notification because you are a memb
Just found this report too
https://bugzilla.redhat.com/show_bug.cgi?id=986339
** Bug watch added: Red Hat Bugzilla #986339
https://bugzilla.redhat.com/show_bug.cgi?id=986339
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I'm also affected by this bug.
Host: Ubuntu Xenial amd64 (all updates installed)
Containers: Multiple xenial containers, one privileged Trusty container.
Affected container: Unprivileged Trusty container (privileged works fine).
--
You received this bug notification because you are a member of U
@cmars
Note that the too many levels of symlink is on the host, not in the container
and is the reason why you needed to do the umount and remount.
In fact, your log file says you did get that error:
lxc 20160331183429.245 ERRORlxc_utils - utils.c:safe_mount:1692
- Too many level
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: binfmt-support (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555760
Titl
I'm not seeing the symbolic links error, but I am seeing this when
trying to start a trusty container on xenial:
https://github.com/lxc/lxd/issues/1836
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/155
I tried starting stopping trusty, wily and xenial containers, none of
that triggers it.
What's odd though is that every report I've seen so far, show no binfmt
mounted, just the autofs. But LXC itself accesses the path so should
have triggered autofs for the previous container startups.
So either
Not having much success reproducing this on a clean machine. In the mean
time, I figured I'd fix my laptop and try to see what changes after a
restart:
root@castiana:~# ls -lh /proc/sys/fs/binfmt_misc/
ls: cannot access '/proc/sys/fs/binfmt_misc/': Too many levels of symbolic links
root@castiana:
Just tested a dozen Xenial systems I have around and only found the
issue on one, my laptop today:
root@castiana:~# ls -lh /proc/sys/fs/binfmt_misc
ls: cannot open directory '/proc/sys/fs/binfmt_misc': Too many levels of
symbolic links
root@castiana:~#
--
You received this bug notification beca
The issue isn't inside a container, for that matter lxd is completely
irrelevant here.
We're seeing that weird symlink loop happen randomly on xenial machines.
Normal users likely won't notice it though as they don't use that mountpoint,
LXC users do though as LXC bind-mounts it into the containe
root@castiana:~# systemctl status proc-sys-fs-binfmt_misc.mount
● proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System
Loaded: loaded (/lib/systemd/system/proc-sys-fs-binfmt_misc.mount; static;
vendor preset: enabled)
Active: inactive (dead) since Sat 2016-03-12 13:2
stgraber@dakara:~$ rssh castiana.lan.mtl
root@castiana:~# ls -lh /proc/sys/fs/binfmt_misc
ls: cannot open directory '/proc/sys/fs/binfmt_misc': Too many levels of
symbolic links
root@castiana:~# cat /proc/mounts | grep binfmt
systemd-1 /proc/sys/fs/binfmt_misc autofs
rw,relatime,fd=29,pgrp=1,time
I'm trying to get a system that doesn't even have lxc installed to get
into the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555760
Title:
Too many levels of symbolic links /proc/sys/fs/bi
I tried to reproduce this with the standard images.linuxcontainers.org
trusty container image, on both a wily and a xenial host, but this
doesn't happen with obvious steps (otherwise we would have noticed this
much earlier already).
>From the github issue I take it you are using Ubuntu wily -- whi
25 matches
Mail list logo
