On Thu, 2018-09-27 at 18:00 +0200, Ferenc Wágner wrote:
> Ken Gaillot writes:
>
> > On Thu, 2018-09-27 at 09:36 +0200, Ulrich Windl wrote:
> >
> > > Obviously you violated the most important cluster rule that is
> > > "be
> > > patient". Maybe the next important is "Don't change the
> > >
Christine Caulfield writes:
> I'm also looking into high-res timestamps for logfiles too.
Wouldn't that be a useful option for the syslog output as well? I'm
sometimes concerned by the batching effect added by the transport
between the application and the (local) log server (rsyslog or
Ken Gaillot writes:
> libqb would simply provide the API for reopening the log, and clients
> such as pacemaker would intercept the signal and call the API.
Just for posterity: you needn't restrict yourself to signals. Logrotate
has nothing to do with signals. Signals are a rather limited
On 2018-09-27 03:13 AM, Kristoffer Grönlund wrote:
> On Thu, 2018-09-27 at 02:49 -0400, Digimer wrote:
>> On 2018-09-27 01:54 AM, Ulrich Windl wrote:
>> Digimer schrieb am 26.09.2018 um 18:29 in
>> Nachricht
>>>
>>> <1c70b5e2-ea8e-8cbe-3d83-e207ca47b...@alteeve.ca>:
On 2018-09-26
Hi Ken - Thanks for the response. Pacemaker is still not running on that
node. So I am still wondering what could be the issue ? Any other
configurations or logs should I be sharing to understand this more ?
Thanks!
On Thu, Sep 27, 2018 at 8:08 PM Ken Gaillot wrote:
> On Thu, 2018-09-27 at
Ken Gaillot writes:
> On Thu, 2018-09-27 at 09:36 +0200, Ulrich Windl wrote:
>
>> Obviously you violated the most important cluster rule that is "be
>> patient". Maybe the next important is "Don't change the
>> configuration while the cluster is not in IDLE state" ;-)
>
> Agreed -- although
On Thu, 2018-09-27 at 14:57 +, cfpubl...@verimatrix.com wrote:
> > On Thu, 2018-09-27 at 10:23 +, cfpubl...@verimatrix.com wrote:
> > > > > With pacemaker 1.1.17, we observe the following messages
> > > > > during
> > > > > startup of
> > > > > pacemaker:
> > > > >
On Thu, 2018-09-27 at 16:09 +0100, Christine Caulfield wrote:
> On 27/09/18 16:01, Ken Gaillot wrote:
> > On Thu, 2018-09-27 at 09:58 -0500, Ken Gaillot wrote:
> > > On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
> > > > Christine Caulfield writes:
> > > >
> > > > > TBH I would be quite
> On Thu, 2018-09-27 at 10:23 +, cfpubl...@verimatrix.com wrote:
> > > > With pacemaker 1.1.17, we observe the following messages during
> > > > startup of
> > > > pacemaker:
> > > > 2018-09-18T11:58:18.452951+03:00 p12-0001-bcsm03
> > > > crmd[2871]: warning:
> > > > Cannot execute
On 27/09/18 16:01, Ken Gaillot wrote:
> On Thu, 2018-09-27 at 09:58 -0500, Ken Gaillot wrote:
>> On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
>>> Christine Caulfield writes:
>>>
TBH I would be quite happy to leave this to logrotate but the
message I
was getting here is
On Thu, 2018-09-27 at 09:58 -0500, Ken Gaillot wrote:
> On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
> > Christine Caulfield writes:
> >
> > > TBH I would be quite happy to leave this to logrotate but the
> > > message I
> > > was getting here is that we need additional help from
On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
> Christine Caulfield writes:
>
> > TBH I would be quite happy to leave this to logrotate but the
> > message I
> > was getting here is that we need additional help from libqb. I'm
> > willing
> > to go with a consensus on this though
>
>
On Thu, 2018-09-27 at 10:23 +, cfpubl...@verimatrix.com wrote:
> > > With pacemaker 1.1.17, we observe the following messages during
> > > startup of
> > > pacemaker:
> > > 2018-09-18T11:58:18.452951+03:00 p12-0001-bcsm03
> > > crmd[2871]: warning:
> > > Cannot execute
On Thu, 2018-09-27 at 13:45 +0530, Prasad Nagaraj wrote:
> Hello - I was trying to understand the behavior or cluster when
> pacemaker crashes on one of the nodes. So I hard killed pacemakerd
> and its related processes.
>
> ---
>
On Thu, 2018-09-27 at 09:36 +0200, Ulrich Windl wrote:
> Hi!
>
> Obviously you violated the most important cluster rule that is "be
> patient".
> Maybe the next important is "Don't change the configuration while the
> cluster
> is not in IDLE state" ;-)
Agreed -- although even idle, removing a
Christine Caulfield writes:
> TBH I would be quite happy to leave this to logrotate but the message I
> was getting here is that we need additional help from libqb. I'm willing
> to go with a consensus on this though
Yes, to do a proper job logrotate has to have a way to get the log files
On 27/09/18 12:52, Ferenc Wágner wrote:
> Christine Caulfield writes:
>
>> I'm looking into new features for libqb and the option in
>> https://github.com/ClusterLabs/libqb/issues/142#issuecomment-76206425
>> looks like a good option to me.
>
> It feels backwards to me: traditionally,
Christine Caulfield writes:
> I'm looking into new features for libqb and the option in
> https://github.com/ClusterLabs/libqb/issues/142#issuecomment-76206425
> looks like a good option to me.
It feels backwards to me: traditionally, increasing numbers signify
older rotated logs, while this
>> With pacemaker 1.1.17, we observe the following messages during
>> startup of
>> pacemaker:
>> 2018-09-18T11:58:18.452951+03:00 p12-0001-bcsm03 crmd[2871]: warning:
>> Cannot execute '/usr/lib/ocf/resource.d/verimatrix/anything4':
>> Permission denied (13)
>>
>>> "cfpubl...@verimatrix.com" schrieb am 27.09.2018
um
11:19 in Nachricht
> Hi all,
>
> we have been using pacemaker 1.1.7 for many years on RedHat 6. Recently, we
> moved to RedHat 7.3 and pacemaker 1.1.17.
> Note that we build pacemaker from source RPMs and don’t use the packages
>
Hi all,
we have been using pacemaker 1.1.7 for many years on RedHat 6. Recently, we
moved to RedHat 7.3 and pacemaker 1.1.17.
Note that we build pacemaker from source RPMs and don’t use the packages
supplied by RedHat.
With pacemaker 1.1.17, we observe the following messages during startup of
Hello - I was trying to understand the behavior or cluster when pacemaker
crashes on one of the nodes. So I hard killed pacemakerd and its related
processes.
[root@SG-mysqlold-907 azureuser]#
Hi!
Obviously you violated the most important cluster rule that is "be patient".
Maybe the next important is "Don't change the configuration while the cluster
is not in IDLE state" ;-)
I feel these are issues that should be fixed, but the above rules make your
life easier while these issues
On 26/09/18 09:21, Ferenc Wágner wrote:
> Jan Friesse writes:
>
>> wagner.fer...@kifu.gov.hu writes:
>>
>>> triggered by your favourite IPC mechanism (SIGHUP and SIGUSRx are common
>>> choices, but logging.* cmap keys probably fit Corosync better). That
>>> would enable proper log rotation.
>>
On Thu, 2018-09-27 at 02:49 -0400, Digimer wrote:
> On 2018-09-27 01:54 AM, Ulrich Windl wrote:
> > > > > Digimer schrieb am 26.09.2018 um 18:29 in
> > > > > Nachricht
> >
> > <1c70b5e2-ea8e-8cbe-3d83-e207ca47b...@alteeve.ca>:
> > > On 2018-09-26 11:11 AM, Patrick Whitney wrote:
> > > > Hey
On 2018-09-27 01:54 AM, Ulrich Windl wrote:
Digimer schrieb am 26.09.2018 um 18:29 in Nachricht
> <1c70b5e2-ea8e-8cbe-3d83-e207ca47b...@alteeve.ca>:
>> On 2018-09-26 11:11 AM, Patrick Whitney wrote:
>>> Hey everyone,
>>>
>>> I'm doing some pacemaker/corosync/dlm/clvm testing. I'm without a
Hi,
The current behavior of cancelled migration with Pacemaker 1.1.16 with a
resource implementing push migration:
# /usr/sbin/crm_resource --ban -r vm-conv-4
vhbl03 crmd[10017]: notice: State transition S_IDLE -> S_POLICY_ENGINE
vhbl03 pengine[10016]: notice: Migrate vm-conv-4#011(Started
27 matches
Mail list logo
