> 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
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.
Since last pacemaker update the events notification to the external script
worked perfectly.
After pacemaker update to version 1.1.11, the ClusterMon resource conti
On 18 Oct 2013, at 7:49 am, Denise Cosso wrote:
> Hello,
>
>
>I configured in Pacemaker ClusterMon but not receive email. Already tested
> the email from the command line and working.
>
>I think it's the version of crm_mon
>
>Could anyone help
Hello,
I configured in Pacemaker ClusterMon but not receive email. Already tested
the email from the command line and working.
I think it's the version of crm_mon
Could anyone help me??
Thank you,
Denise
crm configure
primitive resMON ocf:pacemaker:ClusterMon \
op mo
Hi,
On Tue, Jul 30, 2013 at 12:56:00PM +0200, D.Gossrau wrote:
> Hi,
>
> I'm trying to get the failcount of a resource (crm resource
> failcount show ) in a script which is used in ClusterMon
> as external agent. The configuration is as follows:
>
> # resource Cluster Monitor
> primitive resClu
Hi,
I'm trying to get the failcount of a resource (crm resource failcount
show ) in a script which is used in ClusterMon as external
agent. The configuration is as follows:
# resource Cluster Monitor
primitive resClusterMon ocf:pacemaker:ClusterMon \
params user="root" \
extra_option
Le 09/05/2013 16:40, Steven Bambling a écrit :
I'm having some issues with getting some cluster monitoring setup and
configured on a 3 node multi-state cluster. I'm using Florian's blog
as an example
http://floriancrouzat.net/2013/01/monitor-a-pacemaker-cluster-with-ocfpacemakerclustermon-ando
On 10/05/2013, at 7:35 PM, Steven Bambling wrote:
>>> If this is correct what is the best practice for monitoring additional
>>> resource states?
>>
>> Define "additional"?
>> If the resource fails we'll normally recover it automatically.
> An example of an additional resource would be a vip u
On 10/05/2013, at 8:08 PM, Steven Bambling wrote:
>
> On May 10, 2013, at 5:35 AM, Steven Bambling wrote:
>
>>
>> On May 9, 2013, at 8:05 PM, Andrew Beekhof wrote:
>>
>>>
>>> On 10/05/2013, at 12:40 AM, Steven Bambling wrote:
>>>
I'm having some issues with getting some cluster mo
On May 10, 2013, at 5:35 AM, Steven Bambling wrote:
>
> On May 9, 2013, at 8:05 PM, Andrew Beekhof wrote:
>
>>
>> On 10/05/2013, at 12:40 AM, Steven Bambling wrote:
>>
>>> I'm having some issues with getting some cluster monitoring setup and
>>> configured on a 3 node multi-state cluster
On May 9, 2013, at 8:05 PM, Andrew Beekhof wrote:
>
> On 10/05/2013, at 12:40 AM, Steven Bambling wrote:
>
>> I'm having some issues with getting some cluster monitoring setup and
>> configured on a 3 node multi-state cluster. I'm using Florian's blog as an
>> example
>> http://florianc
On 10/05/2013, at 12:40 AM, Steven Bambling wrote:
> I'm having some issues with getting some cluster monitoring setup and
> configured on a 3 node multi-state cluster. I'm using Florian's blog as an
> example
> http://floriancrouzat.net/2013/01/monitor-a-pacemaker-cluster-with-ocfpacemake
I'm having some issues with getting some cluster monitoring setup and
configured on a 3 node multi-state cluster. I'm using Florian's blog as an
example
http://floriancrouzat.net/2013/01/monitor-a-pacemaker-cluster-with-ocfpacemakerclustermon-andor-external-agent/.
When I create the primitiv
On Mon, Dec 6, 2010 at 5:18 PM, Ryan Steele wrote:
> I think I've found the problem - comments below.
>
> On 12/05/2010 08:26 PM, Ryan Steele wrote:
>>
>> Hi folks,
>>
>
> <...snip...>
>
>> crm(live)configure# primitive ResourceMonitor ocf:pacemaker:ClusterMon
>> params pidfile="/var/run/crm_mon.p
I think I've found the problem - comments below.
On 12/05/2010 08:26 PM, Ryan Steele wrote:
Hi folks,
<...snip...>
crm(live)configure# primitive ResourceMonitor ocf:pacemaker:ClusterMon
params pidfile="/var/run/crm_mon.pid" htmlfile="/var/tmp/crm_mon.html"
extra_options="-T o...@example.co
Hi folks,
I'd like to use crm_mon for monitoring & email notifications, but I've
hit a snag when it comes to incorporating it into the crm
configuration. When I run crm_mon manually from the command line (with
no cluster crm configurations), it all works great, but obviously
running crm_mon
-Ursprüngliche Nachricht-
Von: Dejan Muhamedagic [mailto:deja...@fastmail.fm]
Gesendet: Donnerstag, 24. Juni 2010 15:33
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] ClusterMon failing: call=220, rc=1, status=complete):
unknown error
On Thu, Jun 24, 2010 at 02:14:51PM +0200
On Thu, Jun 24, 2010 at 02:14:51PM +0200, Koch, Sebastian wrote:
> Hi,
>
> i got a small issue with the CLusterMon agent. The monitor
> actions for this agent seem to fail (if i look into syslog,
> you'll find it below) and i am not able to troubleshoot it. I
> tried to start the agent on the fail
Hi,
i got a small issue with the CLusterMon agent. The monitor actions for this
agent seem to fail (if i look into syslog, you'll find it below) and i am not
able to troubleshoot it. I tried to start the agent on the failed node by hand
but it don't see startup / status errors. The ClusterMon s
31 matches
Mail list logo
