>>> Ken Gaillot schrieb am 11.01.2021 um 21:16 in
Nachricht
:
> Pacemaker doesn't currently support it, sorry. It should be pretty easy
> to add though (when built with libqb 2), so hopefully we can get it in
> 2.1.0.
Some time ago I wrote my own set of logging routines, and actually I uses
>>> Ken Gaillot schrieb am 11.01.2021 um 16:45 in
>>> Nachricht
<3e78312a1c92cde0a1cdd82c2fed33a679f63770.ca...@redhat.com>:
...
>> > from growing indefinitely). (Plus some timing issues to consider.)
>>
>> Wouldn't a temporary local status variable do also?
>
Hi Ken,
I appreciate your
On 1/11/21 11:17 PM, Ulrich Windl wrote:
Hi!
I'm fixing my configuration after each unexpected fencing. Probably I missed
some dependency, but these messages seem somewhat unexpected to me:
Jan 11 15:54:32 h18 Raid1(prm_lockspace_raid_md10)[30630]: INFO: running lsof
to list /dev/md10
Hi Steffen,
I've been experimenting with it since last weekend, but I haven't been able to
reproduce the same situation.
It seems that the cause is that the reproduction method cannot be limited.
Can I attach a problem log?
Best Regards,
Hideo Yamauchi.
- Original Message -
> From:
Hey Reid, Ken,Thank you for your quick replies. I figured this was the case. As Ken suggested I will likely work around this by configuring high resolution timestamps in the system log, and I think I can use some journalctl options on systems that don't have rsyslog by default.I assume that the
On Mon, Jan 11, 2021 at 12:17 PM Ken Gaillot wrote:
> Pacemaker doesn't currently support it, sorry. It should be pretty easy
> to add though (when built with libqb 2), so hopefully we can get it in
> 2.1.0.
>
> Of course Pacemaker has always supported logging via syslog, and syslog
> can be
Pacemaker doesn't currently support it, sorry. It should be pretty easy
to add though (when built with libqb 2), so hopefully we can get it in
2.1.0.
Of course Pacemaker has always supported logging via syslog, and syslog
can be configured to use high-res timestamps, so that's a workaround.
Does
It doesn't look like it to me, but that would be a cool feature. Corosync
now implements the %T (milliseconds) time spec from libqb if it's available
in the provided libqb version. Pacemaker uses %t (seconds).
-
https://github.com/ClusterLabs/libqb/blob/v2.0.2/lib/log_format.c#L396-L417
-
Hello,I am wondering if it is possible to configure high resolution timestamps (including milliseconds) in the pacemaker.log? I was able to get hi-res timestamps in the corosync.log by adding 'timestamp: hires' under the logging directive in corosync.conf. I was hoping Pacemaker has something
Hi all,
The Pacemaker 2.1.0 release, expected toward the middle of this year,
will be fully backward compatible in both the CIB and the C API. The
middle version number is being bumped to draw attention to more
significant changes than usual, including changes that may affect
custom scripts or
On Mon, 2021-01-11 at 16:31 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 11.01.2021 um
> > > > 15:46 in
>
> Nachricht
> <3df79a20eb4440357759cca4fe5b0e0729e47085.ca...@redhat.com>:
> > On Mon, 2021-01-11 at 08:25 +0100, Ulrich Windl wrote:
> > > > > > Ken Gaillot schrieb am
>>> Ken Gaillot schrieb am 11.01.2021 um 15:46 in
Nachricht
<3df79a20eb4440357759cca4fe5b0e0729e47085.ca...@redhat.com>:
> On Mon, 2021-01-11 at 08:25 +0100, Ulrich Windl wrote:
>> > > > Ken Gaillot schrieb am 08.01.2021 um
>> > > > 17:38 in
>>
>> Nachricht
>>
Hi!
I'm fixing my configuration after each unexpected fencing. Probably I missed
some dependency, but these messages seem somewhat unexpected to me:
Jan 11 15:54:32 h18 Raid1(prm_lockspace_raid_md10)[30630]: INFO: running lsof
to list /dev/md10 users...
Jan 11 15:54:32 h18 systemd[1]: Stopping
On Mon, 2021-01-11 at 08:25 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 08.01.2021 um
> > > > 17:38 in
>
> Nachricht
> <662b69bff331fae41771cf8833e819c2d5b18044.ca...@redhat.com>:
> > On Fri, 2021‑01‑08 at 11:46 +0100, Ulrich Windl wrote:
> > > Hi!
> > >
> > > Trying to reproduce
14 matches
Mail list logo
