On 2017-01-11 19:37:37 +0100, Michael Biebl wrote:
> [moving this over to #850959]
> Am 11.01.2017 um 19:13 schrieb Michael Biebl:
> > Am 11.01.2017 um 19:12 schrieb Michael Biebl:
> >> Am 11.01.2017 um 18:55 schrieb Vincent Lefevre:
> >>> What info do you need?
> >>
> >> A verbose debug log from
Control: severity -1 normal
Control: tags -1 moreinfo unreproducible
[moving this over to #850959]
Am 11.01.2017 um 19:13 schrieb Michael Biebl:
> Am 11.01.2017 um 19:12 schrieb Michael Biebl:
>> Am 11.01.2017 um 18:55 schrieb Vincent Lefevre:
>>> What info do you need?
>>
>> A verbose debug log
Am 11.01.2017 um 19:12 schrieb Michael Biebl:
> Am 11.01.2017 um 18:55 schrieb Vincent Lefevre:
>> On 2017-01-11 18:36:30 +0100, Michael Biebl wrote:
>>> Am 11.01.2017 um 18:28 schrieb Michael Biebl:
Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
> On 2017-01-11 18:09:51 +0100, Michael
Am 11.01.2017 um 18:55 schrieb Vincent Lefevre:
> On 2017-01-11 18:36:30 +0100, Michael Biebl wrote:
>> Am 11.01.2017 um 18:28 schrieb Michael Biebl:
>>> Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
> Am 11.01.2017 um 18:05 schrieb
On 2017-01-11 17:40:09 +, Ben Hutchings wrote:
> On Wed, 2017-01-11 at 16:20 +0100, Vincent Lefevre wrote:
> > On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> > > Unless you can show that some data had been written *and flushed* to
> > > disk by the application, but was not readable
On 2017-01-11 18:36:30 +0100, Michael Biebl wrote:
> Am 11.01.2017 um 18:28 schrieb Michael Biebl:
> > Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
> >> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
> >>> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
> Why is this no normal shutdown?
On Wed, 2017-01-11 at 16:20 +0100, Vincent Lefevre wrote:
> On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> > Unless you can show that some data had been written *and flushed* to
> > disk by the application, but was not readable afterward - this does not
> > count. Writes are buffered, and
Am 11.01.2017 um 18:28 schrieb Michael Biebl:
> Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
>> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
>>> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
Why is this no normal shutdown?
>>
>> Services are not stopped as usual.
>
> How do you
Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
>> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
>>> Why is this no normal shutdown?
>
> Services are not stopped as usual.
How do you conclude that?
--
Why is it that all of the instruments
On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
> > Why is this no normal shutdown?
Services are not stopped as usual.
> > Did you actually have a file corruption?
Yes, /var/log/monit.log, which got null bytes in it, and some
other file created
Am 11.01.2017 um 18:05 schrieb Michael Biebl:
> Am 11.01.2017 um 17:05 schrieb Vincent Lefevre:
>> Control: clone -1 -2
>> Control: reassign -2 systemd 232-8
>> Control: retitle -2 systemd: power off without always a normal shutdown when
>> resuming after suspend with the power button
>> Control:
Am 11.01.2017 um 17:05 schrieb Vincent Lefevre:
> Control: clone -1 -2
> Control: reassign -2 systemd 232-8
> Control: retitle -2 systemd: power off without always a normal shutdown when
> resuming after suspend with the power button
> Control: severity -2 grave
>
> as the lack of shutdown
Control: clone -1 -2
Control: reassign -2 systemd 232-8
Control: retitle -2 systemd: power off without always a normal shutdown when
resuming after suspend with the power button
Control: severity -2 grave
as the lack of shutdown yields visible file corruption and potentially
data loss.
On
On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> Unless you can show that some data had been written *and flushed* to
> disk by the application, but was not readable afterward - this does not
> count. Writes are buffered, and user space has to deal with that.
If I understand the journalctl
Control: severity -1 important
On Wed, 2017-01-11 at 15:52 +0100, Vincent Lefevre wrote:
> Control: severity -1 grave
>
> because it can corrupt files.
>
> When this occurred on December 23, the log file of monit got
> corrupted:
>
> [CET Dec 22 07:35:07] info : 'zira' Monit reloaded
> [CET
Control: severity -1 grave
because it can corrupt files.
When this occurred on December 23, the log file of monit got
corrupted:
[CET Dec 22 07:35:07] info : 'zira' Monit reloaded
[CET Dec 22 07:35:07] error: Queued event file: unable to read event size
-- end of file
[CET Dec 23
Package: src:linux
Version: 4.8.11-1
Severity: important
After suspending my laptop (13:54:33 below), when I pressed the power
button to resume (19:35:53 below), the laptop was automatically
powered off. This is a regression (tried twice, occurred twice,
but there was no such problem in the past,
17 matches
Mail list logo
