pcp
[Top] [All Lists]

Re: [performancecopilot/pcp] pmcd causes complete system lockup on CentO

To: performancecopilot/pcp <pcp@xxxxxxxxxxxxxxxxxx>
Subject: Re: [performancecopilot/pcp] pmcd causes complete system lockup on CentOS 7 on VMware (#107)
From: Jeff White <notifications@xxxxxxxxxx>
Date: Tue, 16 Aug 2016 15:15:47 -0700
Cc: pcpemail <pcp@xxxxxxxxxxx>, Comment <comment@xxxxxxxxxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=U0mJ31wl95IkInP1Knkx4TguFrw=; b=MsXU9SEKUW69O77U S6Dc+6HLTBFwydgLQIHXdOPPne4kNEJ/kHT6AEL9IZlrPS0jgizlPqEdteUwG5SM 2NKddkwFcLmaDf13+KfGsuxbWHmb6HwIr+y07mSWZHzaw4no1EXiob1BGGK6EGwT 0MiLxCe//RFA3dS4FAF30GEQVCk=
In-reply-to: <performancecopilot/pcp/issues/107@xxxxxxxxxx>
List-archive: https://github.com/performancecopilot/pcp
List-id: performancecopilot/pcp <pcp.performancecopilot.github.com>
List-post: <mailto:reply+00bd08b6db838d657ec5422053a95ec20b99a63611d9dc0a92cf0000000113cb529392a169ce0a350886@reply.github.com>
List-unsubscribe: <mailto:unsub+00bd08b6db838d657ec5422053a95ec20b99a63611d9dc0a92cf0000000113cb529392a169ce0a350886@reply.github.com>, <https://github.com/notifications/unsubscribe/AL0Itpi9AWHdVdJz2ZwCvjHr232p_z3wks5qgjaTgaJpZM4JktgK>
References: <performancecopilot/pcp/issues/107@xxxxxxxxxx>
Reply-to: performancecopilot/pcp <reply+00bd08b6db838d657ec5422053a95ec20b99a63611d9dc0a92cf0000000113cb529392a169ce0a350886@xxxxxxxxxxxxxxxx>

Thank you for looking into this. Here are some more vmcore dumps in case you are interested. The first one shows "swapper" as the process which triggered it so salt-minion isn't really at fault here, it could happen to anyone who does a call that triggers the bug.

https://drive.google.com/open?id=0B6emnuNXtougWXktR0l2VGRuYVk
https://drive.google.com/open?id=0B6emnuNXtougUEEwU183ZjFMNUU

I sure hope the calls which trigger the issue can only be ran by a privileged user, otherwise this is a security issue as well. Do you know if that is possible?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

<Prev in Thread] Current Thread [Next in Thread>