Hi Russell,<div><br></div><div>If you have the time to turn this into a tutorial, I think it would make a great entry for the wiki. I think a step-by-step guide with scripts for syncing (if you would like to share them) would be a great help for new users to get up and running with a distributed Merlin setup. I'd be happy to help out with proof-reading and suggesting corrections/improvements.</div>
<div><br></div><div>Cheers,</div><div>Martin<br><br><div class="gmail_quote">On Thu, Oct 29, 2009 at 9:22 PM, Russell Jennings <span dir="ltr"><<a href="mailto:russ@geekwhiz.com">russ@geekwhiz.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">So, I finally got all my merlin logisitics out.<br>
<br>
on the noc:<br>
each poller has it's own directory (though if i had multiple pollers<br>
per site, they would both share the same). this directory is where<br>
host/service definitions, templates and etc exist. It is setup in the<br>
following way:<br>
<br>
n.* files are sync'd over to the node<br>
.txt files are renamed on the node to become config files<br>
<br>
this allows me to have 1 file, like n.server1.cfg, which houses all<br>
relevant definitions for that server (granted, there are other ways to<br>
handle definitions, this is just how i do it to keep it modular) which<br>
can also get sync'd over to the node. so, both nagios instances can<br>
read this file and not hiccup.<br>
<br>
all other information is housed in a localdef.cfg file (which outlines<br>
templates and such) and also a n.nodenef.txt file, which has similar<br>
definitions so that i can use the same template in the server's file,<br>
and both local and remote have those definitions available. the local<br>
definitions are all defined as passive cehcks, and the remote ones are<br>
all defined as active.<br>
<br>
on the poller:<br>
a script runs every 5 minutes which rsync's the directory (only n.*<br>
files) and also, another rsync that does the commands.cfg file one<br>
level up the tree, since all nodes should have the same config.<br>
(though i just realized i should sync libexec too...)<br>
the script then renames all txt files to cfg, and then restarts nagios.<br>
Command exit codes are checked each step of the way, and a passive<br>
check is fired off if one fails in some way. otherwise it submits an<br>
OK passive check result at the end.<br>
<br>
it's not ideal, but it'll work.<br>
<br>
Cheers,<br>
Russell<br>
_______________________________________________<br>
op5-users mailing list<br>
<a href="mailto:op5-users@lists.op5.com">op5-users@lists.op5.com</a><br>
<a href="http://lists.op5.com/mailman/listinfo/op5-users" target="_blank">http://lists.op5.com/mailman/listinfo/op5-users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Martin Svangren<br>System Administrator<br><br>op5 AB<br>Första Långgatan 19<br>SE-413 27 Göteborg, SWEDEN<br><br>Direct: +46 (0)31-352 56 21<br>Mobile: +46 (0)733-70 90 21<br>
Switchboard: +46 (0)31-352 56 00<br><br>E-mail: <a href="mailto:martin.svangren@op5.com">martin.svangren@op5.com</a><br>Web: <a href="http://www.op5.com">http://www.op5.com</a><br>
</div>