I have exactly the same problem on my host. Host OS: Debian 8.10.
Container OS: Debian 9.4
I started "/usr/sbin/sshd -d -p 8022", and when I connected to it from
another host, the process has hung with the latest log message:
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
Also strace s
looks like rsyslogd is the solution:
https://lists.linuxcontainers.org/pipermail/lxc-users/2015-March/008657.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572061
Title:
login sessions hangs in
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572061
Title
Hi,
There is no such file in any of my containers.
I had to take acton on this issue so I removed inetutils-syslogd in my affected
lxc:s.
Everything is now stable so I think it's clear that this i releated to behavior
of syslogd in 16.04 lxc:s .
I'm sorry to say but I have no cloud resources to
Hi - could you show the result of
ls -l /dev/kmsg
in the container?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572061
Title:
login sessions hangs in lxc
To manage notifications about this bug
I got an hanging session again in the container mentioned in last post.
strace -f syslogd
execve("/usr/sbin/syslogd", ["syslogd"], [/* 18 vars */]) = 0
brk(0) = 0xa67000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 819
Hi,
to go for the default rsylog for the ubuntu lxc seems stable, I had not run in
to any hanging sessions yet since replacing syslogd.
I still have an lxc with jessie and syslogd (the one from the mails above). I
can see if I can reproduce this error with a clone of the mentioned container
and
Hi,
thanks again for reporting this. I simply cannot reproduce this and haven't
found any likely cause. If you can reliably reproduce this in some sort
of cloud instance, i.e. so we could start a digitalocean or amazon instance
with a cloud-init script to set up a bad container, that would be
im
Latest observation from my side is that lxc-console hangs as well.
During login via lxc-console it hangs after motd
lxc-console -n kjell
Connected to tty 1
Type to exit the console, to enter Ctrl+a itself
Debian GNU/Linux 8 kjell tty1
kjell login:
Password:
Last login: Mon Apr 25 15:56:
Ok I tested as described.
127.0.0.1 localhost kjell
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
No it did not solv the issue :(
//Bjorn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Can you show the contents of the container's /etc/hosts? Does adding an
entry for
127.0.0.1 kjell
help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572061
Title:
login sessions hangs in lxc
T
check earlier post for un-cut strace
On Mon, Apr 25, 2016 at 8:59 PM, Bjorne wrote:
> Serge,
> Sorry for being unclear.
> This is not only related to ssh, as I mentioned earlier it happends to
> dovecot too.
>
> On Mon, Apr 25, 2016 at 8:34 PM, Serge Hallyn <1572...@bugs.launchpad.net>
> wrote:
Serge,
Sorry for being unclear.
This is not only related to ssh, as I mentioned earlier it happends to
dovecot too.
On Mon, Apr 25, 2016 at 8:34 PM, Serge Hallyn <1572...@bugs.launchpad.net>
wrote:
> Odd, I wonder why you are getting the re-exec requires full path error,
> as execve is clearly ge
Odd, I wonder why you are getting the re-exec requires full path error,
as execve is clearly getting a full path.
So it seems like an sshd bug, let's see when we get the un-cut strace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I lxc-attached the container and stopped sshd and started sshd .
Next step was to strace -p PID for sshd while opening a new ssh session from
outside.
As you can see no child processes started from sshd. se out put below from ps
aux, strace -p. I also attched output from netstan -an inside
strace -f sshd
execve("/usr/sbin/sshd", ["sshd"], [/* 18 vars */]) = 0
brk(0) = 0x559e98a77000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fe860909000
Sorry, my first strace was cut.
I will leave my lxc hanging with ssh problems for now, for be abler to answer
your questions quicker.
Thank you
//Bjorn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Just got an hanging lxc, this is the deb container mentioned above.
(127.0.0.1 localhost is defined in /etc/hosts
ps aux
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 28148 3176 ?Ss Apr23 0:00 /sbin/init
root38 0.0 0.0
It might help if you can show a ps -ef and screenshot of top while it is
hanging, or even better yet an strace -f of the sshd. One somewhat
common cause of such hangs is /etc/hosts in the container not having an
entry for the localhost.
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
Hi,
it's an intermittent error meaning it only occurs on rare occasions on the
containters.
I am rather sure it's pam or apparmor who is the issue here though. I received
the login prompt during the incident but it hangs after password. Valid for
both imaps and ssh protocols
ifconfig -a
eth0
Hi,
when I simply do
sudo lxc-create -t download -n kjell -B zfs -- -d debian -r jessie -a
amd64
the resulting container works for me. I can apt-get install openssh-
server and log in. However, your configuration file shows 'br0' is in
use. Please show how br0 is configured on the host. Plea
Debain container
lxc-create -t download( selected -> debian jessie amd64) -n kjell -B zfs
lxc-start -n kjell
function of container is remote access ssh.
Template used to create this container: /usr/share/lxc/templates/lxc-download
# Parameters passed to the template:
# For additional config
Please show us the exact commands you used to create, start, and log
into the container, as well as the container configuration file.
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
anyone please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572061
Title:
login sessions hangs in lxc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572061
Title:
login sessions hangs in lxc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
25 matches
Mail list logo
