2010/2/13 renayama19661...@ybb.ne.jp:
Hi Andrew,
I confirmed it in the next environment.
* CentOS 5.4 (on ESXi)
* Pacemaker-1-0-0bf7d14dd554
* Cluster-Resource-Agents-a3db4fe39301
* Reusable-Cluster-Components-f547243d9245
* corosync-1.2.0
I attach a result of hb_report as a
Hi Andrew,
Thank you for a reply.
I test your patch.
Best Regards,
Hideo Yamauchi.
--- Andrew Beekhof and...@beekhof.net wrote:
2010/2/13 renayama19661...@ybb.ne.jp:
Hi Andrew,
I confirmed it in the next environment.
\xA0* CentOS 5.4 (on ESXi)
\xA0* Pacemaker-1-0-0bf7d14dd554
Hi Andrew,
About the cause of this problem, did you understand what it was?
Please contact me if there is the information that is necessary for
investigation else.
Best Regards,
Hideo Yamauchi.
--- renayama19661...@ybb.ne.jp wrote:
Hi Andrew,
I confirmed it in the next environment.
Odd, I don't see any pacemaker messages in the log files...
Anyway, I'll look at the PE files.
2010/2/8 renayama19661...@ybb.ne.jp:
Hi,
I set slightly complicated colocation.
* corosync 1.2.0
* Pacemaker 1.0.7(Pacemaker-1-0-d3fa20fc76c7)
On Wed, Feb 10, 2010 at 1:42 PM, Andrew Beekhof and...@beekhof.net wrote:
Odd, I don't see any pacemaker messages in the log files...
Anyway, I'll look at the PE files.
Actually, none of the included pe files seem to match the failure
case... can you supply the cib from that condition?
Hi Andrew,
Thank you for comment.
Actually, none of the included pe files seem to match the failure
case... can you supply the cib from that condition?
I report the result that carried out cibadmin -Q at the stage of each problem.
Is this information(cibadmin -Q) enough?
Best Regards,
Hideo