On Sat, Feb 11 2017, Michael Biebl wrote:
> While I can reproduce the error messages on shutdown, it does *not*
> cause a dirty file system (in particular /var) here.
> I do have persistent journal enabled on the test VM, but the filing
> killing/unmount spree in systemd-shutdown properly unmounts
Am 11.02.2017 um 14:38 schrieb Yuri D'Elia:
> reached? If I cannot get a clean journal out, there's nothing much I can
> debug.
You could try to attach a serial device to your VM and log the output to
that device [1]. This will get us a more complete log.
Attach the complete file.
[1] https://fr
On Sat, Feb 11 2017, Michael Biebl wrote:
>> reached? If I cannot get a clean journal out, there's nothing much I can
>> debug.
>
> You could try to attach a serial device to your VM and log the output to
> that device [1]. This will get us a more complete log.
> Attach the complete file.
But for
Am 11.02.2017 um 16:21 schrieb Yuri D'Elia:
> On Sat, Feb 11 2017, Michael Biebl wrote:
>>> reached? If I cannot get a clean journal out, there's nothing much I can
>>> debug.
>>
>> You could try to attach a serial device to your VM and log the output to
>> that device [1]. This will get us a more
Processing control commands:
> tag -1 pending
Bug #854814 [systemd] Fails to start systemd-resolved
Added tag(s) pending.
--
854814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Control: tag -1 pending
Michael Biebl [2017-02-10 19:20 +0100]:
> Am 10.02.2017 um 17:49 schrieb Yuri D'Elia:
> >
> > With the update to 232-17, systemd-resolved fails to start with the
> > following error:
> >
>
> > -- The error number returned by this process is 2.
> > Feb 10 17:46:31 test sy
On Fri, 10 Feb 2017 18:29:05 +0100 Goran LAZAREVIC
wrote:
> Same bug here, temporary workaroud is to edit :
> /usr/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
> and quote as following :
>
> [Service]
> ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] ||
> echo "
Am 11.02.2017 um 17:17 schrieb Martin Pitt:
> Michael Biebl [2017-02-10 19:20 +0100]:
>> I guess this should only be used in addition with ProtectSystem=, which
>> is a recent upstream change but the Debian version does not use that yet.
>
> No, I did test it with our current systemd package and i
On Sat, 11 Feb 2017 at 21:38:42 +0100, Alexander Kurtz wrote:
> I have marked this as serious since I experienced other packages (i.e.
> avahi-daemon) failing to install because of this. However, please feel
> free to downgrade the severity if you think it's appropriate!
I'm not sure whether this
Control: severity -1 normal
Hi!
Thanks for your quick reply! I tried to make this bug reproducible and
eventually succeeded: The crucial point was, that the package
installation must happen *before* systemd considers the system fully
booted, i.e. by installing the package inside "/etc/rc.local".
Am 12.02.2017 um 00:39 schrieb Alexander Kurtz:
> Control: severity -1 normal
>
> Hi!
>
> Thanks for your quick reply! I tried to make this bug reproducible and
> eventually succeeded: The crucial point was, that the package
> installation must happen *before* systemd considers the system fully
>
On Sat, 11 Feb 2017 17:17:20 +0100 Martin Pitt wrote:
No, I did test it with our current systemd package and it worked. However, I
apparently only tested it with resolvconf installed, but not without
resolvconf. Trivial fix, pushed:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/comm
12 matches
Mail list logo
