<div>Hi,</div><div><br></div>What is the behaviour of rgmanager supposed to be in case one adds a new LVM and FS resources to an already running service?<div><br></div><div>Let's say I have a running database service on one node, and I need to add some storage to this service.</div> <div><br></div><div>After creating all the LVM things, the filesystems,, mount them on the right node etc...</div><div>I edit the cluster.conf, setup the lines concerning what I've added, and upgrade file version.</div> <div><br></div><div>Running then ccs_tool update /etc/cluster/cluster.conf will it restart my modified service ? </div><div>Brem</div><div> <br><br><div class="gmail_quote">2009/8/19 brem belguebli <span dir="ltr"><<a href="mailto:brem.belguebli@gmail.com">brem.belguebli@gmail.com</a>></span><br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>Hi,</div> <div> </div> <div>Changing the cluster version reloads the rgmanager configuration, but it restarts my custom resources despite the fact that they were "started" (in clustat).</div> <div> </div> <div>Just changing the cluster.conf version, not doing anything to my custom resource makes this happen. </div> <div> </div> <div>In the log I get the message :</div> <div><info> Stopping changed resources</div> <div><info> Restarting changed resources</div> <div><info> Starting changed resources</div> <div> </div> <div>which may be generic messages and then I see my resources being stopped and restarted.</div> <div> </div> <div>Sometimes, I also can notice that my service after being stopped, I have a monitor action that is triggered that fails (normal service is stopped) and that disables (status failed) completely the service.</div> <div> </div> <div>I'm running Rhel 5.3 (I saw the post about VM's on RHel 5.2 which seems to be similar).</div> <div> </div> <div>I've tried to run rgmanager in debug (clurgmgrd -d) mode but it seems to get stuck </div> <div> </div> <div>Any idea on what I may be missing ?</div> <div> </div> <div> </div> <div><span class="gmail_quote">2009/8/19, brem belguebli <<a href="mailto:brem.belguebli@gmail.com" target="_blank">brem.belguebli@gmail.com</a>>:</span><div><div></div><div class="h5"> <blockquote class="gmail_quote" style="padding-left:1ex;margin:0px 0px 0px 0.8ex;border-left:#ccc 1px solid">thx Lon<br><br> <div class="gmail_quote">2009/8/18 Lon Hohberger <span dir="ltr"><<a href="mailto:lhh@redhat.com" target="_blank">lhh@redhat.com</a>></span> <div><span><br> <blockquote class="gmail_quote" style="padding-left:1ex;margin:0px 0px 0px 0.8ex;border-left:#ccc 1px solid"> <div>On Tue, 2009-08-18 at 11:01 +0200, brem belguebli wrote:<br>> Hello,<br>><br>> I have a few questions about rgmanager:<br>><br>> 1) How to make it take into account resource metadata changes without<br> > restarting it. service rgmanager reload (or kill -HUP) doesn't.<br>> In case one needs to change some timers in a resource metadata,<br>> the only way to make it is to stop and start rgmanager which brings<br> > down the resources.<br><br> </div>Need to change the configuration version in cluster.conf; rgmanager<br>doesn't record for example file mtimes and run stat() to see if metadata<br>changed. Doing this wouldn't work anyway, as some resources have<br> external metadata.<br> <div><br>> 2) Is there a way to log what "rules" rgmanager succeded to load at<br>> start time (or the ones it failed to), as having a "24 rules loaded"<br>> message isn't very explicit.<br> <br> </div>You can run:<br><br> rg_test rules | grep ^Agent<br><br>There's no way currently to have rgmanager log specifically which agent<br>it loaded at run-time.<br> <div><br>> The last point concerns the potential replacement of rgmanager with<br>> pacemaker (as stated at<br>> <a href="http://sources.redhat.com/cluster/wiki/RGManager" target="_blank">http://sources.redhat.com/cluster/wiki/RGManager</a>). Will this happen in<br> > a near future ?<br><br> </div>Not immediately; we still have a bit to go:<br><br>* need configuration file format conversion utility<br>* need basic "work-alike" tools. Ex: clustat.<br>* need to do a bit of work on rgmanager agents so they work<br> on pacemaker - the standard by which rgmanager+pacemaker<br> operate was inadequate and the two programs have diverged<br> in slightly incompatible ways<br><br>-- Lon<br><font color="#888888"><br>--<br>Linux-cluster mailing list<br> <a href="mailto:Linux-cluster@redhat.com" target="_blank">Linux-cluster@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/linux-cluster" target="_blank">https://www.redhat.com/mailman/listinfo/linux-cluster</a><br> </font></blockquote></span></div></div><br></blockquote></div></div></div><br> </blockquote></div><br></div>