Ken Gaillot napsal(a):
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.
ht
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.
> >
> >
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/fe44f400a3116a158ab33
On 08/07/2017 07:02 PM, Ken Gaillot wrote:
> On Mon, 2017-08-07 at 17:48 +0100, lejeczek wrote:
>> hi everyone
>>
>> I wonder, is it possible to dry-run an alert agent? Test it
>> somehow without the actual event taking place?
>>
>>
>> many thanks.
>> L.
> There's no special tool to do so, but it
On 08/14/2017 03:12 PM, Edwin Török wrote:
> On 14/08/17 13:46, Klaus Wenninger wrote:
> > How does your /etc/sysconfig/sbd look like?
> > With just that pcs-command you get some default-config with
> > watchdog-only-support.
>
> It currently looks like this:
>
> SBD_DELAY_START=no
> SBD_OPTS="-n c
On 08/14/2017 03:19 PM, Sriram wrote:
> Yes, I had precreated the script file with the required permission.
>
> [root@*node1* alerts]# ls -l /usr/share/pacemaker/alert_file.sh
> -rwxr-xr-x. 1 root root 4140 Aug 14 01:51
> /usr/share/pacemaker/alert_file.sh
> [root@*node2* alerts]# ls -l /usr/shar
Yes, I had precreated the script file with the required permission.
[root@*node1* alerts]# ls -l /usr/share/pacemaker/alert_file.sh
-rwxr-xr-x. 1 root root 4140 Aug 14 01:51 /usr/share/pacemaker/alert_file.sh
[root@*node2* alerts]# ls -l /usr/share/pacemaker/alert_file.sh
-rwxr-xr-x. 1 root root
On 14/08/17 13:46, Klaus Wenninger wrote:
> How does your /etc/sysconfig/sbd look like?
> With just that pcs-command you get some default-config with
> watchdog-only-support.
It currently looks like this:
SBD_DELAY_START=no
SBD_OPTS="-n cluster1"
SBD_PACEMAKER=yes
SBD_STARTMODE=always
SBD_WATCHD
On 08/14/2017 12:20 PM, Ulrich Windl wrote:
> Hi!
>
> Have you tried studying the logs? Usually you get useful information from
> there (to share!).
>
> Regards,
> Ulrich
>
Edwin Török schrieb am 14.08.2017 um 11:51 in
> Nachricht <3d1653ad-50b5-07e3-9392-92d7d6513...@citrix.com>:
>> Hi,
>>
>
On 08/14/2017 12:32 PM, Sriram wrote:
> Hi Ken,
>
> I used the alerts as well, seems to be not working.
>
> Please check the below configuration
> [root@node1 alerts]# pcs config show
> Cluster Name:
> Corosync Nodes:
> Pacemaker Nodes:
> node1 node2 node3
>
> Resources:
> Resource: TRR (class=oc
Hi Ken,
I used the alerts as well, seems to be not working.
Please check the below configuration
[root@node1 alerts]# pcs config show
Cluster Name:
Corosync Nodes:
Pacemaker Nodes:
node1 node2 node3
Resources:
Resource: TRR (class=ocf provider=heartbeat type=TimingRedundancyRA)
Operations: s
Hi!
Have you tried studying the logs? Usually you get useful information from
there (to share!).
Regards,
Ulrich
>>> Edwin Török schrieb am 14.08.2017 um 11:51 in
Nachricht <3d1653ad-50b5-07e3-9392-92d7d6513...@citrix.com>:
> Hi,
>
>
> When setting up a cluster with just 1 node with auto-tie-
Hi,
When setting up a cluster with just 1 node with auto-tie-breaker and
DLM, and incrementally adding more I got some unexpected fencing if the
2nd node doesn't join the cluster soon enough.
What I also found surprising is that if the cluster has ever seen 2
nodes, then turning off the 2nd
13 matches
Mail list logo