Have you tried crm_resource -C yet? That will clear away any errors and tell the cluster its ok to try again.
On Wed, May 6, 2009 at 5:46 PM, Imran Chaudhry <[email protected]> wrote: > Hi Guys, > > I need some advice regarding my cluster config. It's in production so > I'm treating it as fragile. > > In summary it is a 2-node cluster with a virtual IP mapped to one node > as a shared resource. It was working nicely under Debian Etch, then once > of the nodes was upgraded to Debian Lenny which caused several warnings > and error messages to be produced but the heartbeat continued. Now the > remaining node has been upgraded to Debian Lenny. The virtual IP has > been manually assigned to the interface of the master node, node4. > > I'm looking for some advice to clean it up and start the virtual IP > which is named "ip_resource" in the CIB: > > # crm_resource -L > ip_resource (heartbeat::ocf:IPaddr) > alert_mail (heartbeat::ocf:MailTo) > > # crm_resource -W -r ip_resource > resource ip_resource is NOT running > > # crm_resource -W -r alert_mail > resource alert_mail is running on: node5.foo-company.net > > I have attached the ouput of "cibadmin --cib_query" as an XML file. > > A desirable outcome would be to alter the config to makes things sane or > to "reset" the config somehow. > > I've tried a few things myself but they have caused problems: > > a) I used ifconfig to assign the VIP manually to eth0:0. The CIB refers > to eth0:4 though. > Running "crm_resource -V -P" caused this assignment to be removed. I > manually re-assigned it using ifconfig. > > b) reading man crm_resource, I tried this in the hope of started the > resource: > crm_resource -r ip_resource -p target_role -v started > > It did not start it, instead there was some dense log output that was > more or less similar to the crm_verify output below. > > node4.foo-company.net is the DC > > # crm_verify -LV > crm_verify[7883]: 2009/05/06_16:31:10 WARN: cluster_option: Using > deprecated name 'no_quorum_policy' for cluster option 'no-quorum-policy' > crm_verify[7883]: 2009/05/06_16:31:10 WARN: cluster_option: Using > deprecated name 'symmetric_cluster' for cluster option > 'symmetric-cluster' > crm_verify[7883]: 2009/05/06_16:31:10 ERROR: unpack_rsc_op: Remapping > ip_resource_start_0 (rc=1) on node4.foo-company.net to an ERROR > crm_verify[7883]: 2009/05/06_16:31:10 WARN: unpack_rsc_op: Processing > failed op ip_resource_start_0 on node4.foo-company.net: Error > crm_verify[7883]: 2009/05/06_16:31:10 WARN: unpack_rsc_op: Compatability > handling for failed op ip_resource_start_0 on node4.foo-company.net > crm_verify[7883]: 2009/05/06_16:31:10 ERROR: unpack_rsc_op: Remapping > ip_resource_start_0 (rc=1) on node5.foo-company.net to an ERROR > crm_verify[7883]: 2009/05/06_16:31:10 WARN: unpack_rsc_op: Processing > failed op ip_resource_start_0 on node5.foo-company.net: Error > crm_verify[7883]: 2009/05/06_16:31:10 WARN: unpack_rsc_op: Compatability > handling for failed op ip_resource_start_0 on node5.foo-company.net > crm_verify[7883]: 2009/05/06_16:31:10 WARN: native_color: Resource > ip_resource cannot run anywhere > Warnings found during check: config may not be valid > > > My fall back is to try and replicate this config on a couple of virtual > machines and then try and recover myself. > > I work am in the UK BST timezone and am happy to chat on #linux-ha @ > freenode > > Many thanks. > > Regards > > Imran Chaudhry > Software Engineer > > SmoothWall Ltd > 1 John Charles Way > Leeds > LS12 6QA > > Tel: +44 (0)870 1 999 500 > Fax: +44 (0)870 1 991 399 > > SmoothWall Ltd. - http://www.smoothwall.net/ > > This email and any attachments transmitted with it are confidential to > the > intended recipient(s) and may not be communicated to any other person or > published by any means without the express permission of SmoothWall > Limited. > > Any views expressed in this message are solely those of the author. > > See: http://www.smoothwall.net/emailnotice.html for the full text of > this notice. > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
