On Friday, June 17, 2011 06:49:11 Dejan Muhamedagic wrote: > On Thu, Jun 16, 2011 at 10:31:44AM -0400, imnotpc wrote: > > On Thursday, June 16, 2011 09:28:20 Dejan Muhamedagic wrote: > > > On Thu, Jun 16, 2011 at 07:32:30AM -0400, imnotpc wrote: > > > > On Thursday, June 16, 2011 02:38:51 Florian Haas wrote: > > > > > On 06/16/2011 12:50 AM, imnotpc wrote: > > > > > >> Funny but it looks fairly unequivocal to me. > > > > > > > > > > > > Yes and no. The message is clear but unless you have someone > > > > > > sitting at a console 24/7 running tail on the log file, it has > > > > > > little value. According to the ClusterLabs stonith docs (which I > > > > > > just realized you > > > > > > > > > > > wrote, haha): > > > > > Meatware requires operator intervention, that much is a given. > > > > > _Notifying_ an operator that intervention is necessary, beyond > > > > > logging to the console or a log file, is beyond meatware's domain. > > > > > > > > > > However, it's extremely easy to combine meatware with automated > > > > > monitoring: any time a node is meatware-fencing another, it creates > > > > > a socket file named /var/run/meatware.<hostname>, where hostname > > > > > is the name of the node being fenced. Configure your automated > > > > > monitoring to page an operator any time this file is present, and > > > > > you've solved the notification problem. > > > > > > > > > > Hope this is useful. > > > > > > > > It was. I had seen mention of that file when I'd run meatclient on a > > > > node that wasn't DC. That's actually the best idea so far as long as > > > > you only want notification of fencing since it only exists on the DC > > > > node. Well, in theory. It turns out I had a few stale files that > > > > hadn't been deleted and it seems that was the cause of those > > > > warnings and errors in my log. I still don't get a console message > > > > but that is of limited value anyway. > > > > > > Perhaps somebody may want to add a send sms or mail feature to > > > meatware. > > > > Can you tell me where the current dev source code for meatware and MailTo > > is located? I'd be willing to take a look and see if this is something I > > could do. > > The repository (mercurial) is at hg.linux-ha.org/glue. meatware > is in lib/plugins/stonith. > > The resource agents repository (git) is at > https://github.com/ClusterLabs/resource-agents > MailTo is in the heartbeat directory.
MailTo is pretty straightforward but I've got a lot to learn about how the cluster works and a whole lot of included functions to understand before messing with a plugin like meatware. I'll keep this on my ToDo list while I learn and get experience. Jeff _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
