>>> Dominik Klein <[email protected]> schrieb am 16.12.2011 um 12:34 >>> in Nachricht <[email protected]>:
> > On 12/15/2011 11:19 AM, Ulrich Windl wrote: > > Hi! > > > > I have a problem with some client-server software (I don't want to > > name it here) where client and server both need an etry for inetd > > (xinetd). It's also possible that client and server are running on > > one machine. > > > > For a cluster solution I set up the server to run on one node only > > (using -INFINITY location restrictions for the other nodes). I've > > added a RA that diesables the indetd service when the server is to be > > down, and enabled it when the server is to be up. > > > > Summary of a longer story: Even when the resource is never intended > > to run anywhere else, the cluster checks the indetd service through > > the RA on every node, and then complains: > > > > Dec 15 09:10:55 h03 pengine: [15876]: WARN: See > > http://clusterlabs.org/wiki/FAQ#Resource_is_Too_Active for more > > information. > > Then your RA is wrong. It should not say that things are running when > they are not. Hi! Please read again: The RA is right; the software just uses some strange concepts. I need to start some thing when it's down on the local node, whatever happened on the other nodes. Maybe I should just use a clone to start it everywhere, but I'm not sure I fully understood clones and their constraints thoroughly. Regards, Ulrich > > Regards > Dominik > > > I'm afraid this might cause unintended fencing at some time. > > > > Are there any rather clean solutions for this problem? > > > > I was thinking to send the node's name to the RA that check's the > > inetd service, and to make him lie about the state on the other > > nodes, but I think that is terrible solution. > > > > Cool ideas? > > > > Regards, Ulrich > > > > > > _______________________________________________ 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 > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
