Hi, I suppose that these two posts are related.
On Mon, May 19, 2008 at 02:04:51PM +0100, lists wrote: > Question regarding heartbeat shutting down if one of the resources can't > map to a local network interface: > > > i.e. if haresources is: > > lbmaster 192.168.2.96 10.0.1.15 10.0.0.20 ldirectord haproxy pound > > > but ifconfig is: > eth0 Link encap:Ethernet HWaddr 00:1D:09:6A:CD:13 inet > addr:192.168.2.41 Bcast:192.168.2.255 Mask:255.255.255.0 > > Then the 10.0.1.15 and 10.0.0.20 can't be mapped so heartbeat shuts down: > > heartbeat[25542]: 2008/05/19_11:58:22 info: heartbeat: version 2.1.3 > > > IPaddr[27171]: 2008/05/19_13:55:31 INFO: ifconfig eth0:0 down > ResourceManager[26600]: 2008/05/19_13:55:31 info: Running > /etc/ha.d/resource.d/IPaddr 192.168.2.96 stop > IPaddr[27092]: 2008/05/19_13:55:31 INFO: Success > ResourceManager[26600]: 2008/05/19_13:55:31 info: Running > /etc/ha.d/resource.d/IPaddr 10.0.1.15 stop > IPaddr[27030]: 2008/05/19_13:55:31 INFO: Success > ResourceManager[26600]: 2008/05/19_13:55:31 info: Running > /etc/ha.d/resource.d/IPaddr 10.0.0.20 stop > ResourceManager[26600]: 2008/05/19_13:55:31 info: Running > /etc/ha.d/resource.d/ldirectord stop > ResourceManager[26600]: 2008/05/19_13:55:31 info: Running > /etc/init.d/haproxy stop > ResourceManager[26600]: 2008/05/19_13:55:31 info: Running > /etc/init.d/pound > stop > ResourceManager[26600]: 2008/05/19_13:55:30 info: Releasing resource > group: > lbmaster 192.168.2.96 10.0.1.15 10.0.0.20 ldirectord haproxy pound > ResourceManager[26600]: 2008/05/19_13:55:30 CRIT: Giving up resources > due > to failure of 10.0.1.15 > ResourceManager[26600]: 2008/05/19_13:55:30 ERROR: Return code 1 from > /etc/ha.d/resource.d/IPaddr > IPaddr[26873]: 2008/05/19_13:55:30 ERROR: Generic error > IPaddr[26890]: 2008/05/19_13:55:30 ERROR: /usr/lib64/heartbeat/findif > failed [rc=1]. > ResourceManager[26600]: 2008/05/19_13:55:30 info: Running > /etc/ha.d/resource.d/IPaddr 10.0.1.15 start > > Is their any way of changing this behaviour to ignore the error, as it > happens quite a lot with some of our users :-). > > Thanks. > > Regards, > Malcolm. On Tue, May 20, 2008 at 12:53:42PM +0100, lists wrote: > > Can you stop all resources shutting down if findif fails? Short answer is no, given your config. > i.e. if I put and IP in haresources that doesn't map to a physical > interface: > > ResourceManager[2937]: 2008/05/20_10:04:54 CRIT: Giving up resources > due to > failure of 10.0.0.20 > ResourceManager[2937]: 2008/05/20_10:04:54 ERROR: Return code 1 from > /etc/ha.d/resource.d/IPaddr > IPaddr[3418]: 2008/05/20_10:04:54 ERROR: Generic error > IPaddr[3435]: 2008/05/20_10:04:54 ERROR: /usr/lib64/heartbeat/findif failed > [rc=1]. > > heartbeat: version 2.1.3 If a resource fails then all resources depending on it will be stopped. You have to decide if this resource is really required for others. You can also try to put in another group if that makes sense, but in that case you can't make sure that it stays on the same node as another group. Unfortunately, v1/haresources style configuration doesn't allow this kind of setup. Thanks, Dejan > Thanks for any help. > Regards, > Malcolm. > > > > > > > _______________________________________________ > 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
