> On 9 Jan 2015, at 6:23 pm, Marco Querci wrote:
>
> Sorry ... it was my error.
> My CentOS is 6.6:
same as I said last time, except s/6.6/6.7/
>
> [root@langate1 ~]# cat /etc/redhat-release
> CentOS release 6.6 (Final)
>
> full upgraded.
>
>
>
> Il 08/01/2015 23:00, Andrew Beekhof ha scr
I tried to insert some check code in my script:
#!/bin/bash
echo $(date) >> /tmp/check
monitorfile=/tmp/clustermonitor.html
hostname=$(hostname)
echo "Cluster state changes detected" | mail -r "$hostname@" -s "Cluster
Monitor" -a $monitorfile mquerc...@gmail.com
to check if the script is be
Sorry ... it was my error.
My CentOS is 6.6:
[root@langate1 ~]# cat /etc/redhat-release
CentOS release 6.6 (Final)
full upgraded.
Il 08/01/2015 23:00, Andrew Beekhof ha scritto:
On 8 Jan 2015, at 10:00 pm, Marco Querci wrote:
Thanks for your suggestion.
But my version is:
[root@langate1 ~
> On 8 Jan 2015, at 10:00 pm, Marco Querci wrote:
>
> Thanks for your suggestion.
> But my version is:
>
> [root@langate1 ~]# pacemakerd --version
> Pacemaker 1.1.11
>
> Why were you saying my version is 1.1.12-rc3?
Because that the tag that '97629de' in the following matches to:
> I ins
Thanks for your suggestion.
But my version is:
[root@langate1 ~]# pacemakerd --version
Pacemaker 1.1.11
Why were you saying my version is 1.1.12-rc3?
I installed pacemaker on CentOS 6.5 from repository. Why those
repository aren't updated with this patch?
Many Thanks.
Il 08/01/2015 03:39, A
> On 8 Jan 2015, at 1:31 pm, Andrew Beekhof wrote:
>
> And there is no indication this is being called?
Doh. I know this one... you're actually using 1.1.12-rc3.
You need this patch which landed after 1.1.12 shipped:
https://github.com/beekhof/pacemaker/commit/3df6aff
>
>> On 7 Jan 2015,
And there is no indication this is being called?
> On 7 Jan 2015, at 6:21 pm, Marco Querci wrote:
>
> #!/bin/bash
>
> monitorfile=/tmp/clustermonitor.html
> hostname=$(hostname)
>
> echo "Cluster state changes detected" | mail -r "$hostname@" -s
> "Cluster Monitor" -a $monitorfile mquerc...@g
#!/bin/bash
monitorfile=/tmp/clustermonitor.html
hostname=$(hostname)
echo "Cluster state changes detected" | mail -r "$hostname@" -s
"Cluster Monitor" -a $monitorfile mquerc...@gmail.com
Thanks.
Il 06/01/2015 01:21, Andrew Beekhof ha scritto:
On 6 Jan 2015, at 3:37 am, Marco Querci wrot
> On 6 Jan 2015, at 3:37 am, Marco Querci wrote:
>
> Hi All.
> Any news for my problem?
Maybe post your /home/administrator/clustermonitor_notification.sh script?
>
> Many thanks.
>
>
> Il 19/12/2014 12:13, Marco Querci ha scritto:
>> Many tahnk for your reply.
>> Here is my configuration:
Hi All.
Any news for my problem?
Many thanks.
Il 19/12/2014 12:13, Marco Querci ha scritto:
Many tahnk for your reply.
Here is my configuration:
validate-with="pacemaker-1.2" cib-last-written="Thu Dec 18 20:04:43
2014" update-origin="langate1" update-client="crmd"
crm_feature_set="3.0.9" ha
Many tahnk for your reply.
Here is my configuration:
validate-with="pacemaker-1.2" cib-last-written="Thu Dec 18 20:04:43
2014" update-origin="langate1" update-client="crmd"
crm_feature_set="3.0.9" have-quorum="1" dc-uuid="langate1">
value="1.1.11-97629de"/>
name=
Le 18/12/2014 16:21, Marco Querci a écrit :
Hi all,
I have a pacemaker + corosync cluster installed on a CentOS 6.5
I have a resource ClusterMon with external_agent param set up.
Before last pacemaker update the events notification to the external
script worked perfectly.
After pacemaker update t
Hi all,
I have a pacemaker + corosync cluster installed on a CentOS 6.5
I have a resource ClusterMon with external_agent param set up.
Before last pacemaker update the events notification to the external script
worked perfectly.
After pacemaker update to version 1.1.11, the ClusterMon resource cont
13 matches
Mail list logo
