On 24 September 2010 18:12, Dejan Muhamedagic deja...@fastmail.fm wrote:
[...snip...]
Default timeout is coded into the resource agent. You safely can ignore
the
WARNINGs. These are also removed from more recent versions of pacemaker.
These warnings shouldn't be ignored. The defaults
Hi,
On Mon, Sep 27, 2010 at 12:00:19PM +0200, Pavlos Parissis wrote:
On 24 September 2010 18:12, Dejan Muhamedagic deja...@fastmail.fm wrote:
[...snip...]
Default timeout is coded into the resource agent. You safely can ignore
the
WARNINGs. These are also removed from more recent
On 27 September 2010 12:17, Dejan Muhamedagic deja...@fastmail.fm wrote:
Hi,
On Mon, Sep 27, 2010 at 12:00:19PM +0200, Pavlos Parissis wrote:
On 24 September 2010 18:12, Dejan Muhamedagic deja...@fastmail.fm
wrote:
[...snip...]
Default timeout is coded into the resource agent.
Hi,
I'm just getting started using pacemaker and the crm shell but ran into
a problem using crm via sudo. Ignore the complaints about no stonith
resources, like I said, i'm just getting started :)
`-- sudo crm configure
crm(live)configure# property stonith-enabled=true
crm(live)configure#
I'm running pacemaker-1.1.2-0.6.1 on sles11sp1. I was only able to
successfully login to the crm_gui from one of my nodes in spite of the
fact that the login parameters appeared to be identical. I traced the
problem to a zero length /etc/pam.d/hbmgmt file on the node that
exhibited the login
Hi,
On Mon, Sep 27, 2010 at 08:50:21AM -0800, Justin Burket wrote:
Hi,
I'm just getting started using pacemaker and the crm shell but ran into
a problem using crm via sudo. Ignore the complaints about no stonith
resources, like I said, i'm just getting started :)
`-- sudo crm
Hello,
I was wondering what side effects occur if you don't add all the
cluster nodes to the /etc/hosts file on each node?
I'd also be interested in hearing how others keep the hosts file in
sync. For example, lets say you have 3 nodes, and 1 node is currently
down. Then you add a 4th node, but
