Bug#771675: systemd: machinectl: Failed to get container bus: Input/output error

2014-12-13 Thread Michael Biebl
Am 01.12.2014 um 15:24 schrieb Mario Lang:
 Package: systemd
 Version: 215-7
 Severity: minor
 
 Trying to access a container with machinectl login fails.
 But booting the container manually gives a login prompt.
 
 root@host:/# mkdir /var/lib/container
 root@host:/# debootstrap jessie /var/lib/container/debian-jessie
 I: Retrieving Release I: Retrieving Release.gpg
 I: Checking Release signature
 ...
 I: Base system installed successfully.
 root@host:/# systemd-nspawn -D /var/lib/container/debian-jessie
 Spawning container debian-jessie on /var/lib/container/debian-jessie.
 Press ^] three times within 1s to kill container.
 /etc/localtime is not a symlink, not updating container timezone.
 root@debian-jessie:~# exit
 root@fzidpc73:/# systemd-nspawn -bD /var/lib/container/debian-jessie
 ...
 Debian GNU/Linux jessie/sid fzidpc73 console
 
 fzidpc73 login:
 
 OK, so the container boots with systemd-nspawn, but:
 
 root@fzidpc73:/# systemctl start systemd-nspawn@debian-jessie.service
 root@fzidpc73:/# machinectl list
 MACHINE  CONTAINER SERVICE
 debian-jessiecontainer nspawn
 
 1 machines listed.
 root@fzidpc73:~# machinectl login debian-jessie
 Failed to get container bus: Input/output error
 
 
 I am confused, possibly because I don't fully get all the technology
 involed yet.  machinectl *sees* the running machine, but it fails to
 connect to it, with a rather generic error message.

Actually, the message is not that generic. It fails to connect to the
container bus. After installing the dbus package inside the container
(and rebooting it), you should be able to use machinectl login


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#771675: systemd: machinectl: Failed to get container bus: Input/output error

2014-12-13 Thread Michael Biebl
Am 14.12.2014 um 00:59 schrieb Michael Biebl:
 Actually, the message is not that generic. It fails to connect to the
 container bus. After installing the dbus package inside the container
 (and rebooting it), you should be able to use machinectl login

I just tried with an minimal jessie chroot created via debootstrap and
installing dbus.
While machinectl login successfully connects to the container, I'm
unable to login via machinectl:

Dec 13 23:59:47 pluto login[68]: FAILED LOGIN (2) on '/dev/pts/0' FOR
'root', Authentication failure
Dec 13 23:59:49 pluto login[68]: pam_securetty(login:auth): access
denied: tty '/dev/pts/0' is not secure !


Looks like this needs further tweaks.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#771675: systemd: machinectl: Failed to get container bus: Input/output error

2014-12-13 Thread Michael Biebl
Am 14.12.2014 um 01:02 schrieb Michael Biebl:
 Am 14.12.2014 um 00:59 schrieb Michael Biebl:
 Actually, the message is not that generic. It fails to connect to the
 container bus. After installing the dbus package inside the container
 (and rebooting it), you should be able to use machinectl login
 
 I just tried with an minimal jessie chroot created via debootstrap and
 installing dbus.
 While machinectl login successfully connects to the container, I'm
 unable to login via machinectl:
 
 Dec 13 23:59:47 pluto login[68]: FAILED LOGIN (2) on '/dev/pts/0' FOR
 'root', Authentication failure
 Dec 13 23:59:49 pluto login[68]: pam_securetty(login:auth): access
 denied: tty '/dev/pts/0' is not secure !
 
 
 Looks like this needs further tweaks.


Adding pts/0 to /etc/securetty inside the container made it possible
to login via machinectl login.

I don't know the security implications of that change, so I've CCed the
login maintainers. Maybe the can chime in here if this is something we
could ship in the default login /etc/securetty configuration.


Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#771675: [Pkg-shadow-devel] Bug#771675: systemd: machinectl: Failed to get container bus: Input/output error

2014-12-13 Thread Christian PERRIER
Quoting Michael Biebl (bi...@debian.org):

 Adding pts/0 to /etc/securetty inside the container made it possible
 to login via machinectl login.
 
 I don't know the security implications of that change, so I've CCed the
 login maintainers. Maybe the can chime in here if this is something we
 could ship in the default login /etc/securetty configuration.

Hello Michael and Mario (and others, eventually),

Well, the login maintainers are actually meand I wouldn't even
call myself a real maintainer for this key package I'm just one of
the last people who still barely look at theh package's bug and check
if there are RC bugs.

So, well, don't hope too much from me, here, I'm really lacking the
proper skills to have a good advice.

Still I would happily apply any patch in case more skilled people (who
I trust) provide it.





signature.asc
Description: Digital signature


Bug#771675: systemd: machinectl: Failed to get container bus: Input/output error

2014-12-01 Thread Mario Lang
Package: systemd
Version: 215-7
Severity: minor

Trying to access a container with machinectl login fails.
But booting the container manually gives a login prompt.

root@host:/# mkdir /var/lib/container
root@host:/# debootstrap jessie /var/lib/container/debian-jessie
I: Retrieving Release I: Retrieving Release.gpg
I: Checking Release signature
...
I: Base system installed successfully.
root@host:/# systemd-nspawn -D /var/lib/container/debian-jessie
Spawning container debian-jessie on /var/lib/container/debian-jessie.
Press ^] three times within 1s to kill container.
/etc/localtime is not a symlink, not updating container timezone.
root@debian-jessie:~# exit
root@fzidpc73:/# systemd-nspawn -bD /var/lib/container/debian-jessie
...
Debian GNU/Linux jessie/sid fzidpc73 console

fzidpc73 login:

OK, so the container boots with systemd-nspawn, but:

root@fzidpc73:/# systemctl start systemd-nspawn@debian-jessie.service
root@fzidpc73:/# machinectl list
MACHINE  CONTAINER SERVICE
debian-jessiecontainer nspawn

1 machines listed.
root@fzidpc73:~# machinectl login debian-jessie
Failed to get container bus: Input/output error


I am confused, possibly because I don't fully get all the technology
involed yet.  machinectl *sees* the running machine, but it fails to
connect to it, with a rather generic error message.

-- Package-specific info:
-- BEGIN ATTACHMENTS --
/tmp/tmp.5ER6WRp9wF/systemd-delta.txt
/tmp/tmp.5ER6WRp9wF/systemd-analyze-dump.txt
/tmp/tmp.5ER6WRp9wF/dsh-enabled.txt
/etc/fstab
-- END ATTACHMENTS --

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-58
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1
ii  libblkid1   2.25.2-3
ii  libc6   2.19-13
ii  libcap2 1:2.24-6
ii  libcap2-bin 1:2.24-6
ii  libcryptsetup4  2:1.6.6-3
ii  libgcrypt20 1.6.2-4
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b2
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-7
ii  mount   2.25.2-3
ii  sysv-rc 2.88dsf-58
ii  udev215-7
ii  util-linux  2.25.2-3

Versions of packages systemd recommends:
ii  dbus1.8.12-1
ii  libpam-systemd  215-7

Versions of packages systemd suggests:
pn  systemd-ui  none

-- no debconf information

-- 
Regards,
  Mario Lang

Graz University of Technologymailto:ml...@tugraz.at
Department Computing   http://www.ZID.TUGraz.at/lang/
Phone: +43 (0) 316 / 873 - 6897
//
  /_Apparently a teacher has been arrested in the UK in possession_/
 /of a compass, protractor, and straight edge. It is claimed he is a/
/member of the Al Gebra movement, bearing weapons of math instruction/