Am 12.02.2015 um 08:31 schrieb Michael Biebl:
> Am 12.02.2015 um 07:34 schrieb Michael Biebl:
>> Am 12.02.2015 um 07:29 schrieb Peter Colberg:
>>> On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
>>
>>> It is curious that the bug only manifests itself with the qemu watchdog.
>>> Two p
Am 12.02.2015 um 07:34 schrieb Michael Biebl:
> Am 12.02.2015 um 07:29 schrieb Peter Colberg:
>> On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
>
>> It is curious that the bug only manifests itself with the qemu watchdog.
>> Two physical machines using the hardware iTCO_wdt watchdo
Am 12.02.2015 um 07:34 schrieb Michael Biebl:
> Am 12.02.2015 um 07:29 schrieb Peter Colberg:
>> On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
>
>> It is curious that the bug only manifests itself with the qemu watchdog.
>> Two physical machines using the hardware iTCO_wdt watchdo
Am 12.02.2015 um 07:29 schrieb Peter Colberg:
> On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
> It is curious that the bug only manifests itself with the qemu watchdog.
> Two physical machines using the hardware iTCO_wdt watchdog reboot fine.
In my tests, I did indeed have an unc
On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
> Thanks, I was able to reproduce the issue this way (marking the bug
> accordingly).
> It's likely that the watchog is resetting systemd/rsyslog before it has
> a chance to stop properly.
>
> Let's see, where we can go from here.
In
control: tags -1 = confirmed
control: retitle -1 data corruption on reboot when using watchdog/qemu
Am 12.02.2015 um 06:57 schrieb Peter Colberg:
> On Thu, Feb 12, 2015 at 05:44:59AM +0100, Michael Biebl wrote:
>> Fwiw, I pulled the debian_wheezy_amd64_desktop.qcow2 qemu-kvm image from
>> [1], sta
Processing control commands:
> tags -1 = confirmed
Bug #35 [systemd] systemd: Disk corruption on reboot initiated through
systemd
Added tag(s) confirmed; removed tag(s) unreproducible and moreinfo.
> retitle -1 data corruption on reboot when using watchdog/qemu
Bug #35 [systemd] systemd:
On Thu, Feb 12, 2015 at 05:44:59AM +0100, Michael Biebl wrote:
> Fwiw, I pulled the debian_wheezy_amd64_desktop.qcow2 qemu-kvm image from
> [1], started it with "qemu-system-x86_64 -enable-kvm -hda
> debian_wheezy_amd64_standard.qcow2".
> Then did a dist-upgrade to jessie, which replaced sysvinit w
On Thu, Feb 12, 2015 at 04:28:38AM +0100, Michael Biebl wrote:
> Just to be clear here: Is this only happening once after the
> dist-upgrade from wheezy (sysvinit) to jessie (systemd-sysv) on reboot
> or everytime you reboot your jessie system?
It happens everytime I reboot from within the VM.
>
Processing control commands:
> severity -1 important
Bug #35 [systemd] systemd: Disk corruption on reboot initiated through
systemd
Severity set to 'important' from 'grave'
--
35: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=35
Debian Bug Tracking System
Contact ow...@bugs.debia
control: severity -1 important
Am 12.02.2015 um 04:28 schrieb Michael Biebl:
>> I could reproduce this issue with three machines that are virtualized
>> > with qemu-kvm. On the other hand, I did not see this issue with two
>> > physical machines. All of these are running the above version of
>> >
Processing control commands:
> tags -1 moreinfo unreproducible
Bug #35 [systemd] systemd: Disk corruption on reboot initiated through
systemd
Added tag(s) unreproducible and moreinfo.
--
35: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=35
Debian Bug Tracking System
Contact ow...
control: tags -1 moreinfo unreproducible
Am 12.02.2015 um 03:19 schrieb Peter Colberg:
> Package: systemd
> Version: 215-11
> Severity: grave
> Justification: causes non-serious data loss
>
> Dear Maintainer,
>
> After upgrading to jessie from wheezy, I noticed that some of the
> system logs exp
Package: systemd
Version: 215-11
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
After upgrading to jessie from wheezy, I noticed that some of the
system logs experience corruption when rebooting the system.
After rebooting the system using the command ‘reboot’ or ‘s
FYI: The status of the systemd source package
in Debian's testing distribution has changed.
Previous version: 215-10
Current version: 215-11
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
l
On Wed, Feb 11, 2015 at 11:24:02AM +0100, Michael Biebl wrote:
...
> > Feb 11 09:06:10 cob systemd[1]: Looping too fast. Throttling execution a
> > little.
>
> Can you provide the journalctl -alb output somewhere?
No, sorry, I've since rebooted, it seems to work now.
I had completed the broken u
Control: forcemerge -1 694332
Control: tag -1 upstream confirmed fixed-upstream
Felipe Sateler [2014-12-04 0:38 -0300]:
> The tmpfiles snippets set the /run/log/journal directory owned to
> root:systemd-journal, but it does not add a read acl for the adm group
> as README.Debian suggests. I'm not
Processing control commands:
> forcemerge -1 694332
Bug #771980 [systemd] systemd: /run/log/journal is not readable by the adm group
Bug #694332 [systemd] systemctl man page deficiency re user needing to be in
adm group
Marked as found in versions systemd/215-7.
Bug #771980 [systemd] systemd: /ru
Am 11.02.2015 um 09:10 schrieb Ralf Schlatterbeck:
> On Wed, Feb 11, 2015 at 08:55:37AM +0100, Ralf Schlatterbeck wrote:
>> Hmm, looking closer: Is there a process "systemd" supposed to run?
>
> OK, looks like it is running as init with pid 1.
> But it seems that it isn't really working. From sysl
Processing commands for cont...@bugs.debian.org:
> tags 777613 + pending
Bug #777613 [systemd] systemctl enable/disable does not handle alias symlinks
if there is a corresponding sysv script
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
77
Processing control commands:
> reassign -1 ifupdown 0.7.52
Bug #777003 {Done: Michal Suchanek } [systemd] systemd:
Network is not configured
Bug reassigned from package 'systemd' to 'ifupdown'.
No longer marked as found in versions systemd/215-11.
Ignoring request to alter fixed versions of bug #
Control: reassign -1 ifupdown 0.7.52
Control: retitle -1 warn on syntax errors
Hello Michal,
Michael Biebl [2015-02-04 1:25 +0100]:
> Well, this should be dealt with by ifupdown then, though. E.g it could
> log a warning message.
>
> >
> > The interesting thing is that until now I did have wor
On Wed, Feb 11, 2015 at 08:55:37AM +0100, Ralf Schlatterbeck wrote:
> Hmm, looking closer: Is there a process "systemd" supposed to run?
OK, looks like it is running as init with pid 1.
But it seems that it isn't really working. From syslog I get:
Feb 11 09:05:54 cob systemd[1]: Looping too fast.
Processing commands for cont...@bugs.debian.org:
> retitle 777613 systemctl enable/disable does not handle alias symlinks if
> there is a corresponding sysv script
Bug #777613 [systemd] systemctl enable/disable does not handle .service symlinks
Changed Bug title to 'systemctl enable/disable does
24 matches
Mail list logo
