On Thu, Sep 29, 2016, at 02:45 PM, Jan Pokorný wrote:
> Hello ,
>
> On 29/09/16 12:41 -0400, Christopher Harvey wrote:
> > I think something is failing at the execvp() level. I'm seeing
> > useful looking trace logs in the code, but can't enable them right
> > now. I have:
> > PCMK_debug=yes
> >
Hello ,
On 29/09/16 12:41 -0400, Christopher Harvey wrote:
> I think something is failing at the execvp() level. I'm seeing
> useful looking trace logs in the code, but can't enable them right
> now. I have:
> PCMK_debug=yes
> PCMK_logfile=/tmp/pacemaker.log
> PCMK_logpriority=debug
> PCMK_trace_
On Thu, Sep 29, 2016, at 12:20 PM, Jan Pokorný wrote:
> On 28/09/16 16:55 -0500, Ken Gaillot wrote:
> > On 09/28/2016 04:04 PM, Christopher Harvey wrote:
> >> My corosync/pacemaker logs are seeing a bunch of messages like the
> >> following:
> >>
> >> Sep 22 14:50:36 [1346] node-132-60 crmd:
On 28/09/16 16:55 -0500, Ken Gaillot wrote:
> On 09/28/2016 04:04 PM, Christopher Harvey wrote:
>> My corosync/pacemaker logs are seeing a bunch of messages like the
>> following:
>>
>> Sep 22 14:50:36 [1346] node-132-60 crmd: info:
>> action_synced_wait: Managed MsgBB-Active_meta-da
On 09/28/2016 04:04 PM, Christopher Harvey wrote:
> My corosync/pacemaker logs are seeing a bunch of messages like the
> following:
>
> Sep 22 14:50:36 [1346] node-132-60 crmd: info:
> action_synced_wait: Managed MsgBB-Active_meta-data_0 process 15613
> exited with rc=4
This is the
My corosync/pacemaker logs are seeing a bunch of messages like the
following:
Sep 22 14:50:36 [1346] node-132-60 crmd: info:
action_synced_wait: Managed MsgBB-Active_meta-data_0 process 15613
exited with rc=4
Sep 22 14:50:36 [1346] node-132-60 crmd:error:
generic_get_metada