Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

2015-12-17 Thread Matthias Urlichs
Package: systemd-container
Version: 227-2
Severity: important
File: /usr/bin/systemd-nspawn

systemd-nspawn --link-journal=host should accept an existing directory.

root@iron:~# systemctl start systemd-nspawn@foo
[ everything works ]
root@iron:~# systemctl stop systemd-nspawn@foo
root@iron:~# systemctl status -l systemd-nspawn@foo
● systemd-nspawn@foo.service - Container foo
   Loaded: loaded (/lib/systemd/system/systemd-nspawn@.service; enabled; vendor 
preset: enabled)
  Drop-In: /etc/systemd/system/systemd-nspawn@.service.d
   └─smurf.conf
   Active: failed (Result: exit-code) since Do 2015-12-17 13:00:33 CET; 7s ago
 Docs: man:systemd-nspawn(1)
  Process: 12750 ExecStart=/usr/bin/systemd-nspawn --quiet --network-bridge=br0 
--network-veth-extra=vb-%i:host443 --keep-unit --boot --link-journal=host 
--directory=/d/vm/%i --bind=/var/cache (code=exited, status=1/FAILURE)
 Main PID: 12750 (code=exited, status=1/FAILURE)
   Status: "Terminating..."

Dez 17 13:00:33 iron systemd[1]: Starting Container foo...
Dez 17 13:00:33 iron systemd-nspawn[12750]: mount(/d/vm/foo/sys/fs/selinux) 
failed, ignoring: No such file or directory
Dez 17 13:00:33 iron systemd-nspawn[12750]: mount(/d/vm/foo/sys/fs/selinux) 
failed, ignoring: Invalid argument
Dez 17 13:00:33 iron systemd-nspawn[12750]: /etc/localtime is not a symlink, 
not updating container timezone.
Dez 17 13:00:33 iron systemd-nspawn[12750]: Failed to create 
/var/log/journal/15bfd317d6044649beb2e509acfd0cac: File exists
Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Main process 
exited, code=exited, status=1/FAILURE
Dez 17 13:00:33 iron systemd[1]: Failed to start Container foo.
Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Unit entered 
failed state.
Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Failed with result 
'exit-code'.
root@iron:~# ls -l /var/log/journal/15bfd317d6044649beb2e509acfd0cac
total 8192
-rw-r-+ 1 root netdev 8388608 Jan 18  2015 system.journal
root@iron:~# rm -r /var/log/journal/15bfd317d6044649beb2e509acfd0cac
root@iron:~# systemctl start systemd-nspawn@foo
[ everything works ]
root@iron:~# 

-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-container depends on:
ii  libblkid12.25.2-6
ii  libbz2-1.0   1.0.6-7+b3
ii  libc62.19-18+deb8u1
ii  libcap2  1:2.24-8
ii  libcurl3-gnutls  7.45.0-1+b1
ii  libgcrypt20  1.6.3-2
ii  liblzma5 5.1.1alpha+20120614-2+b3
ii  libseccomp2  2.1.1-1
ii  libselinux1  2.3-2
ii  systemd  227-2
ii  zlib1g   1:1.2.8.dfsg-2+b1

systemd-container recommends no packages.

systemd-container suggests no packages.

-- no debconf information

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

2015-12-17 Thread Michael Biebl
Control: severity -1 normal
Control: tags -1 upstream

Hi

Am 17.12.2015 um 13:06 schrieb Matthias Urlichs:
> Package: systemd-container
> Version: 227-2
> Severity: important
> File: /usr/bin/systemd-nspawn
> 
> systemd-nspawn --link-journal=host should accept an existing directory.
> 

Please test with the latest version 228-2 and if the problem still
persists, file the bug upstream at
https://github.com/systemd/systemd/issues


-- 
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
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

2015-12-17 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #808222 [systemd-container] /usr/bin/systemd-nspawn: systemd-nspawn 
--link-journal=host fails when the directoy exists
Severity set to 'normal' from 'important'
> tags -1 upstream
Bug #808222 [systemd-container] /usr/bin/systemd-nspawn: systemd-nspawn 
--link-journal=host fails when the directoy exists
Added tag(s) upstream.

-- 
808222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

2015-12-17 Thread Matthias Urlichs
On 17.12.2015 14:59, Michael Biebl wrote:
> Control: severity -1 normal
> Control: tags -1 upstream
>
> Hi
>
> Am 17.12.2015 um 13:06 schrieb Matthias Urlichs:
>> Package: systemd-container
>> Version: 227-2
>> Severity: important
>> File: /usr/bin/systemd-nspawn
>>
>> systemd-nspawn --link-journal=host should accept an existing directory.
>>
> Please test with the latest version 228-2
Actually this is from 228-2, I simply forgot to update the header.
>  and if the problem still
> persists, file the bug upstream at
> https://github.com/systemd/systemd/issues
>
>
OK, will do.

-- 
-- Matthias Urlichs

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers