On Fri, 2017-07-28 at 09:04 +0200, Jan Pokorný wrote:
> On 27/07/17 17:40 -0500, Ken Gaillot wrote:
> > On Thu, 2017-07-27 at 23:26 +0200, Jan Pokorný wrote:
> >> On 24/07/17 17:59 +0200, Valentin Vidic wrote:
> >>> On Mon, Jul 24, 2017 at 09:57:01AM -0500, Ken Gaillot wrote:
> Are you sure
On 27/07/17 17:40 -0500, Ken Gaillot wrote:
> On Thu, 2017-07-27 at 23:26 +0200, Jan Pokorný wrote:
>> On 24/07/17 17:59 +0200, Valentin Vidic wrote:
>>> On Mon, Jul 24, 2017 at 09:57:01AM -0500, Ken Gaillot wrote:
Are you sure you have pacemaker 1.1.17 inside the container as well? The
On Thu, 2017-07-27 at 23:26 +0200, Jan Pokorný wrote:
> On 24/07/17 17:59 +0200, Valentin Vidic wrote:
> > On Mon, Jul 24, 2017 at 09:57:01AM -0500, Ken Gaillot wrote:
> >> Are you sure you have pacemaker 1.1.17 inside the container as well? The
> >> pid-1 reaping stuff was added then.
> >
> >
On 24/07/17 17:59 +0200, Valentin Vidic wrote:
> On Mon, Jul 24, 2017 at 09:57:01AM -0500, Ken Gaillot wrote:
>> Are you sure you have pacemaker 1.1.17 inside the container as well? The
>> pid-1 reaping stuff was added then.
>
> Yep, the docker container from the bundle example got an older
>
On Mon, Jul 24, 2017 at 09:57:01AM -0500, Ken Gaillot wrote:
> Are you sure you have pacemaker 1.1.17 inside the container as well? The
> pid-1 reaping stuff was added then.
Yep, the docker container from the bundle example got an older
version installed, so mystery solved :)
On Mon, 2017-07-24 at 13:34 +0200, Valentin Vidic wrote:
> On Mon, Jul 24, 2017 at 01:04:06PM +0200, Klaus Wenninger wrote:
> > Interesting... Looking at the code I would expect 2 processes. Some
> > 'pcmk-init' with pidone and
> > 'pacemaker_remoted' that is spawned out as child.
> > So looks as
On Mon, Jul 24, 2017 at 01:04:06PM +0200, Klaus Wenninger wrote:
> Interesting... Looking at the code I would expect 2 processes. Some
> 'pcmk-init' with pidone and
> 'pacemaker_remoted' that is spawned out as child.
> So looks as if the spawning thing isn't working. Strange thing is that
> the
On 07/24/2017 12:37 PM, Valentin Vidic wrote:
> On Mon, Jul 24, 2017 at 12:19:20PM +0200, Klaus Wenninger wrote:
>> Wasn't aware of the different behavior of pacemaker_remoted as pidone.
>> If it is really spawned as pidone - which might be worth verifying -
>> it should indeed create a zombie
On Mon, Jul 24, 2017 at 12:19:20PM +0200, Klaus Wenninger wrote:
> Wasn't aware of the different behavior of pacemaker_remoted as pidone.
> If it is really spawned as pidone - which might be worth verifying -
> it should indeed create a zombie catcher pid1.
You are right about PID 1, it looks
On 07/23/2017 10:19 AM, Valentin Vidic wrote:
> I'm seeing this state when trying to stop the docker bundle
> with pacemaker 1.1.17:
>
> 15738 ?Ssl7:23 /usr/sbin/dockerd -H fd://
> 15742 ?Ssl5:31 \_ containerd -l
> unix:///var/run/docker/libcontainerd/containerd.sock
I'm seeing this state when trying to stop the docker bundle
with pacemaker 1.1.17:
15738 ?Ssl7:23 /usr/sbin/dockerd -H fd://
15742 ?Ssl5:31 \_ containerd -l
unix:///var/run/docker/libcontainerd/containerd.sock --metrics-interval=0
--start-timeout 2m --state-dir
11 matches
Mail list logo
