[Moabusers] moab not clearing old triggers
Lloyd Brown
somewhere_or_other at byu.edu
Wed Sep 27 13:28:31 MDT 2006
So, I'm using Moab to do triggers to notify when a node goes down. The
specification looks something like this in the moab.cfg:
> NODECFG[DEFAULT] TRIGGER=AType=exec,Action="/opt/moab/node_down_notification.pl $OID",EType=fail,MultiFire=TRUE,RearmTime=5:00
Somehow, though, whenever moab restarts, I get a bunch of the nodes with
a duplicate trigger. I mean that when I start with a clean slate,
having deleted all the triggers by hand (mschedctl -d
trigger:trigger_id), and I re-cycle moab (mschedctl -R), I get a
"default" trigger, as well as a copy for each node, in this case, mdiag
-T | wc -l shows 624 total lines. If I then immediately re-cycle again,
I get 1029 lines. Not all the nodes seem to have duplicates, but it
looks like there's some arbitrary limit on triggers that limits you to
1024 (plus 5 lines of header/footer to the mdiag -T command). I don't
have any problem staying under that limit for now, but I wanted to
understand why the old copy of the triggers isn't getting deleted. Is
there some variable I can set so we don't get these duplicates any time
moab re-starts?
Thanks,
Lloyd Brown
More information about the moabusers
mailing list