Hi,
Since O_DIRECT is not specified in open() [1], it reads the buffer cache and
may result in a false negative. I fear that this possibility increases
in environments with large buffer cache and running disk-reading applications
such as database.
So, I think it's better to specify O_RDONLY|O_DIR
On Thu, Mar 18, 2021 at 6:31 PM Jehan-Guillaume de Rorthais
wrote:
>
> On Thu, 18 Mar 2021 17:29:59 +0900
> 井上和徳 wrote:
>
> > On Tue, Mar 16, 2021 at 10:23 PM Jehan-Guillaume de Rorthais
> > wrote:
> > >
> > > > On Tue, 16 Mar 2
cent83 snmptrapd[33312]: (snip) rhel83-3 (snip) STRING: "joined"
Mar 18 16:24:11 cent83 snmptrapd[33312]: (snip) rhel83-3 (snip)
STRING: "quorate"
Mar 18 16:24:11 cent83 snmptrapd[33312]: (snip) rhel83-3 (snip) STRING: "joined"
Mar 18 16:24:11 cent83 snmptrapd[
On Tue, Mar 16, 2021 at 10:23 PM Jehan-Guillaume de Rorthais
wrote:
>
> > On Tue, 16 Mar 2021, 09:58 井上和徳, wrote:
> >
> > > Hi!
> > >
> > > Cluster (corosync and pacemaker) can be started with pcs,
> > > but corosync-notifyd needs to be started
Hi!
Cluster (corosync and pacemaker) can be started with pcs,
but corosync-notifyd needs to be started separately with systemctl,
which is not easy to use.
# pcs cluster start --all
rhel83-1: Starting Cluster...
rhel83-2: Starting Cluster...
rhel83-3: Starting Cluster...
# ssh rhel83-1 systemctl
ilable upstream in
> commit ddb0d3fed3273181356cd638d724b891ecd78263.
>
>
> Regards,
> Tomas
>
>
> Dne 23. 12. 20 v 5:25 井上和徳 napsal(a):
> > Hi!
> >
> > Is it a specification that pcsd (pcs-0.10.6-4.el8) outputs logs to syslog?
> > If it is a specification, which
Hi!
Is it a specification that pcsd (pcs-0.10.6-4.el8) outputs logs to syslog?
If it is a specification, which change/commit is it due to?
# rpm -q pcs
pcs-0.10.6-4.el8.x86_64
#
# cat /var/log/pcsd/pcsd.log
I, [2020-12-23T13:17:36.748 #00010] INFO -- : Starting Daemons
I, [2020-12-23T13:17:36
Thanks for the comments, everyone.
I'll go over the details and create an improved PullRequest with
proposal (2).
Best Regards,
Kazunori INOUE
On Fri, Jul 3, 2020 at 12:09 AM Ken Gaillot wrote:
>
> On Thu, 2020-07-02 at 18:12 +0900, 井上和徳 wrote:
> > Hi all,
> >
> >
Hi all,
We think it is desirable to output the log indicating the start and
finish of RA execution to syslog on the same node. (End users
monitoring the syslog are requesting that the output be on the same
node.)
Currently, the start[1] and finish[2] logs may be output by different
nodes.
Cluste
2019年7月18日(木) 22:42 Jan Pokorný :
> On 18/07/19 18:08 +0900, 井上和徳 wrote:
> > 'pcs config export' fails in RHEL 8.0 environment because clufter
> > does not support Corosync 3 (Camelback).
> > How is the state of progress? https://pagure.io/clufter/issue/4
>
>
Hi,
'pcs config export' fails in RHEL 8.0 environment because clufter does not
support Corosync 3 (Camelback).
How is the state of progress? https://pagure.io/clufter/issue/4
[root@r80-1 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.0 (Ootpa)
[root@r80-1 ~]# dnf list | grep -E "
> -Original Message-
> From: Klaus Wenninger [mailto:kwenn...@redhat.com]
> Sent: Wednesday, June 13, 2018 6:40 PM
> To: Cluster Labs - All topics related to open-source clustering welcomed; 井上 和
> 徳
> Subject: Re: [ClusterLabs] Questions about SBD behavior
>
> On
lf Of Klaus
> Wenninger
> Sent: Friday, May 25, 2018 4:08 PM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Questions about SBD behavior
>
> On 05/25/2018 07:31 AM, 井上 和徳 wrote:
> > Hi,
> >
> > I am checking the watchdog function of SBD (without shared b
Hi,
I am checking the watchdog function of SBD (without shared block-device).
In a two-node cluster, if one cluster is stopped, watchdog is triggered on the
remaining node.
Is this the designed behavior?
[vmrh75b]# cat /etc/corosync/corosync.conf
(snip)
quorum {
provider: corosync_votequoru
02 AM
> To: Cluster Labs - All topics related to open-source clustering welcomed
> Subject: Re: [ClusterLabs] PCMK_node_start_state=standby sometimes does not
> work
>
> On Tue, 2017-11-28 at 09:36 +, 井上 和徳 wrote:
> > Hi,
> >
> > Sometimes a node with
Hi,
Sometimes a node with 'PCMK_node_start_state=standby' will start up Online.
[ reproduction scenario ]
* Set 'PCMK_node_start_state=standby' to /etc/sysconfig/pacemaker.
* Delete cib (/var/lib/pacemaker/cib/*).
* Start pacemaker at the same time on 2 nodes.
# for i in rhel74-1 rhel74-3 ;
t; starts, rather than when the crmd completes its first join. This
> eliminates the window where attributes can be set before the CIB is
> cleared.
>
> On Tue, 2017-08-15 at 08:42 +, 井上 和徳 wrote:
> > Hi Ken,
> >
> > Thanks for the explanation.
> >
42 AM
> To: Cluster Labs - All topics related to open-source clustering welcomed
> Subject: Re: [ClusterLabs] Updated attribute is not displayed in crm_mon
>
> On Mon, 2017-08-14 at 12:33 -0500, Ken Gaillot wrote:
> > On Wed, 2017-08-02 at 09:59 +, 井上 和徳 wrote:
> >
Hi,
In Pacemaker-1.1.17, the attribute updated while starting pacemaker is not
displayed in crm_mon.
In Pacemaker-1.1.16, it is displayed and results are different.
https://github.com/ClusterLabs/pacemaker/commit/fe44f400a3116a158ab331a92a49a4ad8937170d
This commit is the cause, but the followin
the issue to the crm shell developers. It should
> probably at least warn if the node isn't known.
>
>
> On 05/31/2017 09:35 PM, 井上 和徳 wrote:
> > Hi Ken,
> >
> > I'm sorry. Attachment size was too large.
> > I attached it to GitHub, so look at it.
>
7 8:43 AM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Node attribute disappears when pacemaker is started
>
> On 05/26/2017 03:21 AM, 井上 和徳 wrote:
> > Hi Ken,
> >
> > I got crm_report.
> >
> > Regards,
> > Kazunori INOUE
>
ednesday, May 17, 2017 11:09 PM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Pacemaker's "stonith too many failures" log is not
> accurate
>
> On 05/17/2017 04:56 AM, Klaus Wenninger wrote:
> > On 05/17/2017 11:28 AM, 井上 和徳 wrote:
> >> Hi,
> >&
> On 05/24/2017 05:13 AM, 井上 和徳 wrote:
> > Hi,
> >
> > After loading the node attribute, when I start pacemaker of that node, the
> > attribute disappears.
> >
> > 1. Start pacemaker on node1.
> > 2. Load configure containing node attribute of node2
Hi,
After loading the node attribute, when I start pacemaker of that node, the
attribute disappears.
1. Start pacemaker on node1.
2. Load configure containing node attribute of node2.
(I use multicast addresses in corosync, so did not set "nodelist {nodeid: }"
in corosync.conf.)
3. Start pac
too many failures" log is not
> accurate
>
> On 05/17/2017 04:56 AM, Klaus Wenninger wrote:
> > On 05/17/2017 11:28 AM, 井上 和徳 wrote:
> >> Hi,
> >> I'm testing Pacemaker-1.1.17-rc1.
> >> The number of failures in "Too many failures (10) to fence&q
Hi,
I'm testing Pacemaker-1.1.17-rc1.
The number of failures in "Too many failures (10) to fence" log does not match
the number of actual failures.
After the 11th time fence failure, "Too many failures (10) to fence" is output.
Incidentally, stonith-max-attempts has not been set, so it is 10 by d
26 matches
Mail list logo
