Thank you very much Ken!! You nailed it, now it's working :-)
On Tue, Dec 5, 2017 at 5:29 AM, Ken Gaillot wrote:
> On Mon, 2017-12-04 at 23:15 +0800, Hui Xiang wrote:
> > Thanks Ken very much for the helpful information. It indeed help a
> > lot for debbuging.
> >
> > "
On Mon, 2017-12-04 at 23:15 +0800, Hui Xiang wrote:
> Thanks Ken very much for the helpful information. It indeed help a
> lot for debbuging.
>
> " Each time the DC decides what to do, there will be a line like
> "...
> saving inputs in ..." with a file name. The log messages just before
> that
Thanks Ken very much for the helpful information. It indeed help a lot for
debbuging.
" Each time the DC decides what to do, there will be a line like "...
saving inputs in ..." with a file name. The log messages just before
that may give some useful information."
- I am unable to find such
On Fri, 2017-12-01 at 09:36 +0800, Hui Xiang wrote:
> Hi all,
>
> I am using the ovndb-servers ocf agent[1] which is a kind of multi-
> state resource,when I am creating it(please see my previous email),
> the monitor is called only once, and the start operation is never
> called, according to
Hi all,
I am using the ovndb-servers ocf agent[1] which is a kind of multi-state
resource,when I am creating it(please see my previous email), the monitor
is called only once, and the start operation is never called, according to
below description, the once called monitor operation returned
The really weired thing is that the monitor is only called once other than
expected repeatedly, where should I check for it?
On Thu, Nov 30, 2017 at 4:14 PM, Hui Xiang wrote:
> Thanks Ken very much for your helpful infomation.
>
> I am now blocking on I can't see the
Thanks Ken very much for your helpful infomation.
I am now blocking on I can't see the pacemaker DC do any further
start/promote etc action on my resource agents, no helpful logs founded.
So my first question is that in what kind of situation DC will decide do
call start action? does the