>> > The monitor op shouldn't make any changes. If the rule has gone >> > away, the monitor op should return failure to indicate the resource >> > is broken, which will result in Pacemaker telling the the failed >> > resource to stop, and start again. Actually, from the logs it looks >> > like a restart was attempted, and the stop op reported success, but >> > the subsequent start failed for some reason. >> > >> > Regards, >> > >> > Tim >> >> Exactly. So the RA seems to have a problem handeling this error >> scenario correctly. > > OK. Anybody knows how should it work and where's the problem. It seems > like it can't find some proc file.
I will have a go at fixing the RA today to do the following: 1. Detect the error in monitor and return the correct value 2. Stop the resource cleanly 3. Start it up again. Will let you know how it goes. Chris _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
