Hi,
Thanks for fixing. I checked this patch in pacemaker.
https://github.com/ClusterLabs/pacemaker/commit/dbfbc353aacd21faf59947f1e67d82ebe21608f8
Sincerely,
Yuichi
2013/6/14 Yuichi SEINO :
> Hi,
>
> 2013/6/14 David Vossel :
>>
>>
>>
>>
>> - Original Message -
>>> From: "Yuichi SEINO"
>
Anyway you can drop the firewall rejects and DROP rules all together
just for testing. At least the input ones since that is where the
problem is. Maybe turn your attention to the FW rules of the host
adapter as well as the bridge.
Just a guess however, the best way to get to the bottom of it is b
On 2013-06-16T13:30:03, Digimer wrote:
> All resource and fence agents are supposed to print out their usage details
> (in an XML validation format) when you pass ' meta-data' or
> ' -o metadata'.
>
> It's not ideal, but it is useful.
>
> Perhaps I should start documenting these...
https://www
Guest's firewall is off entirely, as is selinux.
On 06/16/2013 02:25 AM, Vladislav Bogdanov wrote:
16.06.2013 06:19, Digimer wrote:
Tried allowing everything into the host from the bridge. No luck...
I meant guest's firewall.
Tried with;
iptables -I INPUT -i virbr0 -j ACCEPT
new rules;
=
All resource and fence agents are supposed to print out their usage
details (in an XML validation format) when you pass '
meta-data' or ' -o metadata'.
It's not ideal, but it is useful.
Perhaps I should start documenting these...
digimer
On 06/16/2013 12:42 PM, Michael Furman wrote:
Dear pa
Dear pacemaker gurus!
When I run command:
pcs resource agents
I see very long list:
AoEtarget
AudibleAlarm
CTDB
ClusterMon
…
fence_bladecenter
fence_apc_snmp
fence_apc
fence_ack_manual
Where can I find descriptions of all Pacemaker 1.1.8 resource
agents?
Trying to find in interne
