Well, actually, no but it's your ass so.....

I mean, will you be able to make sure that each node on its own will be able to recognize when to take over the IP and not make the mistake of either leaving the IP unattended or both nodes taking over it? pacemaker provides the infrastructure so that those cases don't happen (unless there's a catastrophe involved).

Hi,

would you please provide me any example of an lsb script that monitors tomcat application if it is running or maybe another service, not only tomcat?

thank you a lot!

Well, you have plenty of examples in /etc/init.d, for sure.

The problem is creating your script so that it is "lsb" compliant because, from what I read on pacemaker's documentation, some of those scripts do not interface correctly making pacemaker misbehave.

Here's all the magic explained:
http://clusterlabs.org/doc/en-US/Pac...ed/ap-lsb.html
http://refspecs.linuxbase.org/LSB_3....iscrptact.html

The trick for my suggestion to create an lsb script is that you really don't have to start/stop tomcat. It will be running all the time. You just tell pacemaker that you started/stopped it (without really starting/stopping it) and it will do. What you have to do is perform a _test_ of the tomcat service in status and tell pacemaker about it (is it running? Is it not?). That's it.

Hi, i was reading this post http://foaa.de/old-blog/2010/10/intr...s-all-the-same . Its something about clones and scores...
It seems like this could do for my need..
would you please help me a little bit?

aaaahhhhh, well, pacemaker does it for me and I already gave you an idea what you could to use pacemaker. Want to go another route? That's fine but I don't have the time (nor the will) to sit down to learn how to do it some other way at this point. So have fun with what you found.

no,it is actually about pacemaker.Clones and preference location scores are part of pacemaker configuration. I thought you could help me with these conf options.

Oh.... no experience with that either so won't be of much help.