Sponsored Content
Operating Systems Linux Red Hat Clustering Red Hat Enterprise linux Advanced Platform 5.2 (x86-64 bit) Post 302308832 by sixstrings on Monday 20th of April 2009 11:30:02 AM
Old 04-20-2009
Can you post your cluster.conf file?

Also, for fencing use ipmi... that should just allow for the fencing of nodes via the ilo without needed the advanced pack.
 

5 More Discussions You Might Find Interesting

1. Linux

Red Hat Enterprise Linux Version 3

Hello there guys, i'm new in this linux world and i'm having problems with telnet session. I enabled telnet login but it wont let me login as root. is there a file that i need to take a look to make sure that root could telnet to the system. Thanks a lot guys for your help. (2 Replies)
Discussion started by: josramon
2 Replies

2. News, Links, Events and Announcements

Red Hat Enterprise Linux - For Free!

CentOS 2 and 3 are a 100% compatible rebuild of the RHEL 2 and 3 versions, in full compliance with RedHat's redistribution requirements. It is for people who need an enterprise class OS without the cost of certification and support. Read more here. I've just installed it on a spare box and it... (0 Replies)
Discussion started by: zazzybob
0 Replies

3. Red Hat

Enterprise RED HAT Linux

The Adobe Flash Player does not work in my Enterprise Red Hat Linux. It instructs me to download the Flash Player which I have done. However, it does not install. Do I have a GUI in Red Hat that I can use or do I have to do it via command line. Would appreciate any help. Thanks, Anil (3 Replies)
Discussion started by: AnilAnand
3 Replies

4. Red Hat

Help with Linux Red Hat Enterprise 5.4

I installed Red Hat Enterprise Linux version 5.4 on a desktop in work. I am stuck on the following 1. I have to ensure that Syslogd options in the /etc/sysconfig/syslog file read SYSLOGD_OPTIONS="-r -m 0". After making this execute service syslog restart the syslog and make this change... (0 Replies)
Discussion started by: thomas.colgan
0 Replies

5. Fedora

Which is the better platform to learn UNIX/Linux (Kali Linux Vs. Red Hat or other)?

I just started a new semester and I started my UNIX class yesterday. I've already decided to use python along with my learning process but what I really want to use with it is Kali as my UNIX/Linux platform to learn off of since I already wanted to learn Cyber Sec. anyways. I just wanted to know if... (12 Replies)
Discussion started by: ApacheOmega
12 Replies
POLICY 
ENGINE(8) Pacemaker Configuration POLICY ENGINE(8) NAME
pengine - Policy Engine Options SYNOPSIS
[no-quorum-policy=enum] [symmetric-cluster=boolean] [default-resource-stickiness=integer] [is-managed-default=boolean] [maintenance-mode=boolean] [start-failure-is-fatal=boolean] [enable-startup-probes=boolean] [stonith-enabled=boolean] [stonith-action=enum] [stonith-timeout=time] [startup-fencing=boolean] [cluster-delay=time] [batch-limit=integer] [default-action-timeout=time] [stop-all-resources=boolean] [stop-orphan-resources=boolean] [stop-orphan-actions=boolean] [remove-after-stop=boolean] [pe-error-series-max=integer] [pe-warn-series-max=integer] [pe-input-series-max=integer] [node-health-strategy=enum] [node-health-green=integer] [node-health-yellow=integer] [node-health-red=integer] [placement-strategy=enum] DESCRIPTION
This is a fake resource that details the options that can be configured for the Policy Engine. SUPPORTED PARAMETERS
no-quorum-policy = enum [stop] What to do when the cluster does not have quorum What to do when the cluster does not have quorum Allowed values: stop, freeze, ignore, suicide symmetric-cluster = boolean [true] All resources can run anywhere by default default-resource-stickiness = integer [0] is-managed-default = boolean [true] Should the cluster start/stop resources as required maintenance-mode = boolean [false] Should the cluster monitor resources and start/stop them as required start-failure-is-fatal = boolean [true] Always treat start failures as fatal This was the old default. However when set to FALSE, the cluster will instead use the resource's failcount and value for resource-failure-stickiness enable-startup-probes = boolean [true] Should the cluster check for active resources during startup stonith-enabled = boolean [true] Failed nodes are STONITH'd stonith-action = enum [reboot] Action to send to STONITH device Action to send to STONITH device Allowed values: reboot, poweroff stonith-timeout = time [60s] How long to wait for the STONITH action to complete startup-fencing = boolean [true] STONITH unseen nodes Advanced Use Only! Not using the default is very unsafe! cluster-delay = time [60s] Round trip delay over the network (excluding action execution) The "correct" value will depend on the speed and load of your network and cluster nodes. batch-limit = integer [30] The number of jobs that the TE is allowed to execute in parallel The "correct" value will depend on the speed and load of your network and cluster nodes. default-action-timeout = time [20s] How long to wait for actions to complete stop-all-resources = boolean [false] Should the cluster stop all active resources (except those needed for fencing) stop-orphan-resources = boolean [true] Should deleted resources be stopped stop-orphan-actions = boolean [true] Should deleted actions be cancelled remove-after-stop = boolean [false] Remove resources from the LRM after they are stopped Always set this to false. Other values are, at best, poorly tested and potentially dangerous. pe-error-series-max = integer [-1] The number of PE inputs resulting in ERRORs to save Zero to disable, -1 to store unlimited. pe-warn-series-max = integer [-1] The number of PE inputs resulting in WARNINGs to save Zero to disable, -1 to store unlimited. pe-input-series-max = integer [-1] The number of other PE inputs to save Zero to disable, -1 to store unlimited. node-health-strategy = enum [none] The strategy combining node attributes to determine overall node health. Requires external entities to create node attributes (named with the prefix '#health') with values: 'red', 'yellow' or 'green'. Allowed values: none, migrate-on-red, only-green, progressive, custom node-health-green = integer [0] The score 'green' translates to in rsc_location constraints Only used when node-health-strategy is set to custom or progressive. node-health-yellow = integer [0] The score 'yellow' translates to in rsc_location constraints Only used when node-health-strategy is set to custom or progressive. node-health-red = integer [-INFINITY] The score 'red' translates to in rsc_location constraints Only used when node-health-strategy is set to custom or progressive. placement-strategy = enum [default] The strategy to determine resource placement The strategy to determine resource placement Allowed values: default, utilization, minimal, balanced AUTHOR
Andrew Beekhof <andrew@beekhof.net> Author. Pacemaker Configuration 07/05/2010 POLICY ENGINE(8)
All times are GMT -4. The time now is 02:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy