Hi, pacemaker list.
I try set IBM HTTPServer work with pacemaker/heartbeat.
In apache resource agent config I see:
# The config-file-pathname is the pathname to the configuration
# file for this web server. Various appropriate defaults are
# assumed if no config file is specif
Hello pacemaker users,
I noticed that neither "-p" nor "-f" option does not make any sense for
pacemakerd -
pid_file is never used, and "f" option marked as "Legacy".
Is the ability to run as a daemon disappeared completely?
Also I'd like to know if there are any reasons to worry about the foll
Hello,
I updated last night from RHEL 6.3 to 6.4 (eg. from Pacemaker
1.1.7 to 1.1.8). A few hours later I got into a bit trouble
when the cib process ran out of file handles.
After restarting stuff, I noticed that /proc/cib-pid/fd/ list
was steadily growing by a few UNIX socket handles every
few
On 04/08/2013 07:24 PM, Andrew Beekhof wrote:
> On 09/04/2013, at 3:47 AM, Matthew O'Connor wrote:
>
>> On version 1.1.5... I happened to (accidentally) start a second
>> instance of pacemakerd while fumbling about to get its feature list.
>> After killing the second instance, crm wouldn't conn
On 09/04/2013, at 1:29 PM, Daniel Black wrote:
>>> /usr/sbin/corosync -v
>>> Corosync Cluster Engine, version '1.4.2'
>>>
>>> So 1.4.2 from Debian backports.
>>
>> I think there have been some important bug fix releases since then.
>> I'd suggest trying to get a more recent version, somehow.
>
> > /usr/sbin/corosync -v
> > Corosync Cluster Engine, version '1.4.2'
> >
> > So 1.4.2 from Debian backports.
>
> I think there have been some important bug fix releases since then.
> I'd suggest trying to get a more recent version, somehow.
Thanks Andrew.
It wasn't as bad as I thought.
For th
On 09/04/2013, at 12:25 PM, Andrew Beekhof wrote:
>
> On 08/04/2013, at 5:20 PM, Junko IKEDA wrote:
>
>> Strangely, crm_resource --refresh also doesn't work.
>> It seemed that it worked well just one month before...
>>
>> [root@GUEST03 ~]# crm_mon -1
>> Last updated: Mon Apr 8 16:17:30 2013
On 08/04/2013, at 5:20 PM, Junko IKEDA wrote:
> Strangely, crm_resource --refresh also doesn't work.
> It seemed that it worked well just one month before...
>
> [root@GUEST03 ~]# crm_mon -1
> Last updated: Mon Apr 8 16:17:30 2013
> Last change: Mon Apr 8 16:16:53 2013 via cibadmin on GUEST03
On 08/04/2013, at 7:09 PM, Andreas Mock wrote:
> Hi all,
>
> I'm wondering whether someone built a pacemaker rpm for
> version 1.1.9 fitting in RHEL 6.x and clones?
64-bit is up at http://clusterlabs.org/rpm-next now.
32-bit will follow later today.
be warned however, there are some memory le
On 08/04/2013, at 5:14 PM, Junko IKEDA wrote:
> Hi,
>
> Yes, Corosync version is v2.3.1, so I thought that this should work well.
> Heartbeat is needed to modified to handle this.
It doesn't make sense to me how adding heartbeat specific code helps when
running corosync.
Can you create a bug
On 08/04/2013, at 5:20 PM, Junko IKEDA wrote:
> Strangely, crm_resource --refresh also doesn't work.
> It seemed that it worked well just one month before...
Hmmm, this is not good at all.
Can you file bugs for these please?
>
> [root@GUEST03 ~]# crm_mon -1
> Last updated: Mon Apr 8 16:17:3
All the other replies will work, however the original intention was that people
would use
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/_using_rules_to_control_resource_options.html
In practice it may be more or less usable than the alternatives.
On 08/04/20
On 09/04/2013, at 3:47 AM, Matthew O'Connor wrote:
> On version 1.1.5... I happened to (accidentally) start a second
> instance of pacemakerd while fumbling about to get its feature list.
> After killing the second instance, crm wouldn't connect to the original
> instance. Is this something t
On 08/04/2013, at 7:24 PM, Andreas wrote:
> Just tried this to isolate the problem.
>
> Trying this there was definitely no other cluster component running!
You mean no other copies in the "ps" output?
___
Pacemaker mailing list: Pacemaker@oss.clust
Hi Felix,
basically you have three option to provide information to the resource agent.
- Resource parameters
- Resource meta attributes
- Node attributes
Let me assume some information for an example.
Your nodes are named nodeA and nodeB.
The hardware address for nodeA shall be 0x30
On version 1.1.5... I happened to (accidentally) start a second
instance of pacemakerd while fumbling about to get its feature list.
After killing the second instance, crm wouldn't connect to the original
instance. Is this something that should clear itself up given enough
time, or did I just ho
- Original Message -
> From: "Felix Zachlod"
> To: Pacemaker@oss.clusterlabs.org
> Sent: Monday, April 8, 2013 2:34:07 AM
> Subject: [Pacemaker] Clone Resources Individual Configuration per Node
>
> Hello List,
>
> I am up to writing a resource agent for Pacemaker which shall be used
Thanks! just what i needed. i wasn't looking at cman at all, as "service
pacemaker start" started all including cman...
Yuriy Demchenko
On 04/08/2013 02:52 PM, David Coulson wrote:
On 4/8/13 6:42 AM, Yuriy Demchenko wrote:
The purpose of my cluster is to provide HA VM and routing/gateway
(
On 4/8/13 7:37 AM, Vadym Chepkov wrote:
What if a clustered volume group appears only when pacemaker establishes iSCSI
connection?
just make sure you activate the VG before trying to mount anything.
___
Pacemaker mailing list: Pacemaker@oss.cluste
On Apr 8, 2013, at 6:52 AM, David Coulson wrote:
>
> On 4/8/13 6:42 AM, Yuriy Demchenko wrote:
>>
>> The purpose of my cluster is to provide HA VM and routing/gateway (thus RHCS
>> isn't an option for me - no IPaddr2 and Route resources).
>> But I cannot find any documentation how to use cLVM
On 4/8/13 6:42 AM, Yuriy Demchenko wrote:
The purpose of my cluster is to provide HA VM and routing/gateway
(thus RHCS isn't an option for me - no IPaddr2 and Route resources).
But I cannot find any documentation how to use cLVM in cman+pacemaker
cluster, everything I found requires use of "o
Hi
I've set up 3-node cluster with cman+pacemaker as instructed in this
doc:
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Clusters_from_Scratch/index.html
The purpose of my cluster is to provide HA VM and routing/gateway (thus
RHCS isn't an option for me - no IPaddr2 and
Am 08.04.2013 03:54, schrieb Andrew Beekhof:
Looks like pacemaker is already running. How are you try to start
pacemaker?
Started as usual with the init script:
service heartbeat start
This produces the following error messages:
Apr 5 13:35:11 lb1 pengine[29465]: error: main: Failed to cre
Hi all,
I'm wondering whether someone built a pacemaker rpm for
version 1.1.9 fitting in RHEL 6.x and clones?
Hints are welcome.
Best regards
Andreas
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listin
Hello List,
I am up to writing a resource agent for Pacemaker which shall be used in a
Master/Slave manner. So the cluster shall always run two instances and one
of them shall be Master. My clone instances need a different configuration
depending on the node that they are running on. I know I coul
Strangely, crm_resource --refresh also doesn't work.
It seemed that it worked well just one month before...
[root@GUEST03 ~]# crm_mon -1
Last updated: Mon Apr 8 16:17:30 2013
Last change: Mon Apr 8 16:16:53 2013 via cibadmin on GUEST03
Stack: corosync
Current DC: GUEST03 (3232242816) - partition
Hi,
Yes, Corosync version is v2.3.1, so I thought that this should work well.
Heartbeat is needed to modified to handle this.
Thanks,
Junko
2013/4/8 Andrew Beekhof
> This is using corosync 2.0?
>
> On 04/04/2013, at 9:55 PM, Junko IKEDA wrote:
>
> > Hi,
> >
> > I run the latest pacemaker + c
Hi,
crm_resource -P showed the same.
[root@GUEST03 ~]# crm_resource -P -H 'GUEST03'
Waiting for 1 replies from the CRMdNo messages received in 60 seconds..
aborting
[root@GUEST03 ~]# crm_resource -P -H 'GUEST04'
Waiting for 1 replies from the CRMdNo messages received in 60 seconds..
aborting
[r
28 matches
Mail list logo
