Am Mittwoch, 7. Oktober 2009 17:23:18 schrieb Yves Schumann: > Hi > > I'm trying to bring up a two node cluster with a company internal system > with the same settings as with an two node cluster running on openSUSE11.1. > But I got a problem with the resource IPaddr2. On my openSUSE-cluster > everything works nice but on the other system I got the following error: > > ============ > Last updated: Wed Oct 7 19:20:58 2009 > Stack: Heartbeat > Current DC: oan-master (392d5983-173c-41f9-9746-16c9000e7e3e) - partition > with quorum > Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7 > 2 Nodes configured, unknown expected votes > 1 Resources configured. > ============ > > Online: [ oan-master oan-redundanz ] > > Full list of resources: > > Resource Group: oanRscGroup > rscIpaddr2 (ocf::heartbeat:IPaddr2): Stopped > > Migration summary: > * Node oan-master: > * Node oan-redundanz: > > Failed actions: > rscIpaddr2_monitor_0 (node=(null), call=3, rc=2, status=complete): > invalid parameter > rscIpaddr2_monitor_0 (node=(null), call=2, rc=2, status=complete): > invalid parameter > > > > Crm_verify tells me this: > > r...@oan-master[172.17.206.167]:~ # crm_verify -LVV > crm_verify[10603]: 2009/10/07_19:21:59 ERROR: unpack_rsc_op: Hard error - > rscIpaddr2_monitor_0 failed with rc=2: Preventing rscIpaddr2 from > re-starting on oan-master > crm_verify[10603]: 2009/10/07_19:21:59 ERROR: unpack_rsc_op: Hard error - > rscIpaddr2_monitor_0 failed with rc=2: Preventing rscIpaddr2 from > re-starting on oan-redundanz > crm_verify[10603]: 2009/10/07_19:21:59 notice: group_print: Resource Group: > oanRscGroup > crm_verify[10603]: 2009/10/07_19:21:59 notice: native_print: rscIpaddr2 > (ocf::heartbeat:IPaddr2): Stopped > crm_verify[10603]: 2009/10/07_19:21:59 WARN: native_color: Resource > rscIpaddr2 cannot run anywhere > crm_verify[10603]: 2009/10/07_19:21:59 notice: LogActions: Leave resource > rscIpaddr2 (Stopped) > Warnings found during check: config may not be valid > r...@oan-master[172.17.206.167]:~ # > > > > Here's the configuration part for this: > > <resources> > <group id="oanRscGroup"> > <meta_attributes id="oanRscGroupMetaAttrs"> > <nvpair id="oanRscGroupMetaattrIsManaged" name="is-managed" > value="true"/> > </meta_attributes> > <primitive class="ocf" id="rscIpaddr2" provider="heartbeat" > type="IPaddr2"> > <operations id="rscIpaddr2Operations"> > <op id="rscIpaddr2OpMonitor10s" interval="10s" name="monitor" > start-delay="0" timeout="20s"/> > </operations> > <instance_attributes id="rscIpaddr2InstanceAttributes"> > <nvpair id="rscIpaddr2InstanceAttributesIp" name="ip" > value="172.17.206.169"/> > </instance_attributes> > <meta_attributes id="rscIpaddr2MetaAttributes"> > <nvpair id="rscIpaddr2MetaAttributesTargetRole" > name="target-role" value="Started"/> > </meta_attributes> > </primitive> > </group> > </resources> > <constraints> > <rsc_location id="cliPreferOanRscGroup" rsc="oanRscGroup"> > <rule id="cliPreferRuleOanRscGroup" score="INFINITY" > boolean-op="and"> > <expression id="cliPreferExprOanRscGroup" attribute="#uname" > operation="eq" value="oan-master" type="string"/> > </rule> > </rsc_location> > </constraints> > > > I've compared the configuration with the one from the openSUSE system for > hours now but cannot find the difference which leads to this error!? Any > suggestion would be welcome! > > Regards, > > Yves Schumann
Hi, does the cluster know on what interface the IP should be added? Perhaps you add a "nic" and a "cidr_netmask" attribute. -- Dr. Michael Schwartzkopff MultiNET Services GmbH Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany Tel: +49 - 89 - 45 69 11 0 Fax: +49 - 89 - 45 69 11 21 mob: +49 - 174 - 343 28 75 mail: [email protected] web: www.multinet.de Sitz der Gesellschaft: 85630 Grasbrunn Registergericht: Amtsgericht München HRB 114375 Geschäftsführer: Günter Jurgeneit, Hubert Martens --- PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B Skype: misch42 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
