Hi, On Mon, May 11, 2009 at 01:38:58PM -0400, Eliot Gable wrote: > I believe it is not expecting the resource to be running, but a > monitor action shows that it is running.
If that was the case, then CRM would do something about it (stop/migrate). > Thus, it is not > technically in the correct state, so a warning should be > issued. If the resource is managed, then Pacemaker will start > it by itself, but expects it to be not running to begin with. Basically, the CRM should be the only one to start/stop the resources it manages. Now, perhaps after the resource cleanup (i.e. status section removed for the resource on some node), it could still reduce the severity. This warning I normally encounter on cluster startup. No idea how complex would that be. Andrew? Thanks, Dejan > Eliot Gable > Senior Engineer > 1228 Euclid Ave, Suite 390 > Cleveland, OH 44115 > > Direct: 216-373-4808 > Fax: 216-373-4657 > ega...@broadvox.net<mailto:ega...@broadvox.net> > > [cid:image001.gif@01C9D23D.D6141C50] > CONFIDENTIAL COMMUNICATION. This e-mail and any files transmitted with it > are confidential and are intended solely for the use of the individual or > entity to whom it is addressed. If you are not the intended recipient, please > call me immediately. BROADVOX is a registered trademark of Broadvox, LLC. > > From: Karl Katzke [mailto:kkat...@tamu.edu] > Sent: Monday, May 11, 2009 1:01 PM > To: pacemaker@oss.clusterlabs.org > Subject: Re: [Pacemaker] crm_resource -C vs. crm/resource/cleanup > > > Ok, so that's not really an error, and can be ignored then? It's annoying to > see it show up in the crm_mon and warning logs if it's not an actual > problem... I would expect it to be an INFO message and not a WARN. > > > You can run crm resource cleanup only on one node (or I > > misunderstood). > > It seems that you can run it without specifying a node and it will run across > all nodes. I don't know why it works, although I see the command run in . > Sample, from my three node system, run from app-03: > > > crm(live)resource# cleanup fs-mount-xen-lock (running on app-03 as of this > moment) > > Error performing operation: The object/attribute does not exist > > Error performing operation: The object/attribute does not exist > > Error performing operation: The object/attribute does not exist > > > Log on app-04: > > May 11 10:19:52 app-04 lrmd: [4465]: WARN: Managed fs-mount-xen-lock:monitor > process 8906 exited with return code 7. > > May 11 10:19:52 app-04 crmd: [4468]: info: process_lrm_event: LRM operation > fs-mount-xen-lock_monitor_0 (call=23, rc=7, cib-update=55, confirmed=true) > complete not running > > > -K > > ________________________________ > CONFIDENTIAL. This e-mail and any attached files are confidential and should > be destroyed and/or returned if you are not the intended and proper recipient. > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
