I spoke to Steve, and the only thing he could come up with was that
the group might not be correct.
When the cluster is in this state, please run:
ps x -o pid,euser,ruser,egroup,rgroup,command
And compare it to the normal output.
Also, confirm that there is only one group named haclient, and
2010/9/15 Michał Purzyński mic...@rsbac.org:
hey,
i'm in process of setting up a failover + load balancing cluster for
OpenLDAP (mirror mode).
i've got some strange log messages i don't really understand:
Sep 15 00:33:38 udalia3 crmd: [30332]: ERROR: crmd_ha_msg_filter:
Another DC
Hi,
On Thu, Sep 16, 2010 at 09:04:29AM -0400, liang...@asc-csa.gc.ca wrote:
Somehow this may not get through. Let me try it again.
Hi There,
I have setup a pair of primary/secondary servers for services
such as web, ftp, samba and nfs with pacemaker 1.1.1,
drdb-pacemaker 8.3.7, corosync
Hi,
On Fri, Sep 17, 2010 at 12:49:39AM +0800, Alister Wong wrote:
Hi, all,
I just setup a 2 node clusters in 2 RHEL server(5.5 x86_64).
After I setup and it looked fine. However, I found in
/var/log/messages I found some logs showed that it failed to append to
-Original Message-
From: Dejan Muhamedagic [mailto:deja...@fastmail.fm]
Sent: Friday, September 17, 2010 6:01 PM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] cannot append to /var/log/cluster/corosync.log
permission denied
Hi,
On Fri, Sep 17, 2010 at 12:49:39AM
Change log owner and group to:
-rw-rw 1 hacluster haclient 111231 17 set 13:01
/var/log/corosync/corosync.log
and check logrotate config (if you use it).
Even if in corosync.conf you have specified user: root the crmd daemon
is executed as hacluster and not as root. I think this change has
Hello guys,
I'm a newbie with Linux-ha and as all newbies I have a problem that I'm
trying to sort out.
I have a shared storage (iSCSI) and 2 nodes connected to it.
I wanted to have stonith active.
I configured a separate partition on the shared storage, initialized it,
configured it in
Andrew Beekhof wrote:
I spoke to Steve, and the only thing he could come up with was that
the group might not be correct.
When the cluster is in this state, please run:
ps x -o pid,euser,ruser,egroup,rgroup,command
And compare it to the normal output.
Also, confirm that there is only one
Thanks Dejan.
I will try to look for answers from other components.
Liang Ma
Contractuel | Consultant | SED Systems Inc.
Ground Systems Analyst
Agence spatiale canadienne | Canadian Space Agency
6767, Route de l'Aéroport, Longueuil (St-Hubert), QC, Canada, J3Y 8Y9
Tél/Tel : (450) 926-5099 |