I still don't get the point about lsh - I mean what's the difference
with openssh? Are there some specific step by ssh server with regards to
user session setup necessary? Or some specific system-wide configuration
required somewhere?
--
You received this bug notification because you are a
cat /proc/self/cgroup
10:cpuset:/system.slice/lsh-server.service
9:memory:/system.slice/lsh-server.service
8:freezer:/system.slice/lsh-server.service
7:blkio:/system.slice/lsh-server.service
6:hugetlb:/system.slice/lsh-server.service
5:perf_event:/system.slice/lsh-server.service
I still don't get the point about lsh - I mean what's the difference
with openssh? Are there some specific step by ssh server with regards to
user session setup necessary? Or some specific system-wide configuration
required somewhere?
--
You received this bug notification because you are a
cat /proc/self/cgroup
10:cpuset:/system.slice/lsh-server.service
9:memory:/system.slice/lsh-server.service
8:freezer:/system.slice/lsh-server.service
7:blkio:/system.slice/lsh-server.service
6:hugetlb:/system.slice/lsh-server.service
5:perf_event:/system.slice/lsh-server.service
is lsh somehow not triggering pam_systemd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1467611
Title:
unprivileged lxc containers broken
To manage notifications about this bug go to:
is lsh somehow not triggering pam_systemd?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1467611
Title:
unprivileged lxc containers broken
To manage notifications about this bug go
How does this triggering happens normally? I mean should ssh server call
something specific explicitly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1467611
Title:
unprivileged lxc containers
How does this triggering happens normally? I mean should ssh server call
something specific explicitly?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1467611
Title:
unprivileged lxc
cat /proc/self/cgroups
cat: /proc/self/cgroups: No such file or directory
Hmm.. what ssh server have to do with this?
** Changed in: systemd (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
cat /proc/self/cgroups
cat: /proc/self/cgroups: No such file or directory
Hmm.. what ssh server have to do with this?
** Changed in: systemd (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So that seems to be an artifact of using lsh-server? After ssh'ing in,
please copypaste the output of cat /proc/self/cgroups
** Changed in: systemd (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
So that seems to be an artifact of using lsh-server? After ssh'ing in,
please copypaste the output of cat /proc/self/cgroups
** Changed in: systemd (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I meant /proc/self/cgroup, sorry.
what ssh server have to do with this?
Because your process is in /system.slice/lsh-server.service, which your
user cannot access.
** Changed in: systemd (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a
I meant /proc/self/cgroup, sorry.
what ssh server have to do with this?
Because your process is in /system.slice/lsh-server.service, which your
user cannot access.
** Changed in: systemd (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (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/1467611
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1467611
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (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/1467611
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
What is regular user session? Does ssh connection counts or it have to
be local console login?
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
** Changed in: systemd (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
What is regular user session? Does ssh connection counts or it have to
be local console login?
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
** Changed in: systemd (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
ssh connections should count for a regular user session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1467611
Title:
unprivileged lxc containers broken
To manage notifications about this bug go
ssh connections should count for a regular user session.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1467611
Title:
unprivileged lxc containers broken
To manage notifications about
The cgmanager log shows:
Invalid path /run/cgmanager/fs/none,name=systemd/system.slice/lsh-
server.service/lxc/asterisk
How are you logged in when you try to start the container?
To start an unprivileged container, you must be logged into a regular
user session, so /proc/self/cgroup should look
The cgmanager log shows:
Invalid path /run/cgmanager/fs/none,name=systemd/system.slice/lsh-
server.service/lxc/asterisk
How are you logged in when you try to start the container?
To start an unprivileged container, you must be logged into a regular
user session, so /proc/self/cgroup should look
That happens on x86_64 ubuntu 15.04 server btw. All the latest updates
installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1467611
Title:
unprivileged lxc containers broken
To manage
Btw, cgmanager is started and keep reporting junk which I fail to
interpret:
systemctl status cgmanager
● cgmanager.service - Cgroup management daemon
Loaded: loaded (/lib/systemd/system/cgmanager.service; enabled; vendor
preset: enabled)
Active: active (running) since Mon 2015-06-22
26 matches
Mail list logo
