pcp
[Top] [All Lists]

Re: [pcp] pmchart crash on OSX with certain archive (#35)

To: performancecopilot/pcp <pcp@xxxxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pmchart crash on OSX with certain archive (#35)
From: Ken McDonell <notifications@xxxxxxxxxx>
Date: Mon, 10 Aug 2015 14:27:51 -0700
Delivered-to: pcp@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=github.com; h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=N643tP2XR30Tkv6x24ACDrSQk9w=; b=IKT4mrPHvvmZ+1ly Yo+m6sz5DmFpBiVz6JtmYKWKbLAtsEnHgHYMzVnK3nFi9Im5TYGP9qTgxOLmjAID y2ezL3uf6ElmlPd8IGzo11Lg3NELv2Or9NOOxbjSp9Lg5WBe8GWTUTdK6J5lljIF dKMaqh++zRJESs29QkgTm//rB04=
In-reply-to: <performancecopilot/pcp/issues/35@xxxxxxxxxx>
List-archive: https://github.com/performancecopilot/pcp
List-id: performancecopilot/pcp <pcp.performancecopilot.github.com>
List-post: <mailto:reply+00bd08b660998f6f28b374d41014c57c13d0bb1f31607cba92cf0000000111e0d95792a169ce05f5b0f7@reply.github.com>
List-unsubscribe: <mailto:unsub+00bd08b660998f6f28b374d41014c57c13d0bb1f31607cba92cf0000000111e0d95792a169ce05f5b0f7@reply.github.com>, <https://github.com/notifications/unsubscribe/AL0ItmkKDah7ucGUzi4JVQXUEcc6tl0zks5omQ7XgaJpZM4Foc6e>
References: <performancecopilot/pcp/issues/35@xxxxxxxxxx>
Reply-to: performancecopilot/pcp <reply+00bd08b660998f6f28b374d41014c57c13d0bb1f31607cba92cf0000000111e0d95792a169ce05f5b0f7@xxxxxxxxxxxxxxxx>

Thanks for that Paul ... especially as it lands in my lap via the much maligned interp.c.

I would expect this to have nothing to do with pmchart, other than guilt by association.

But I will need some additional information to prosecute this:
1. the archive (maybe under NDA if the information is sensitive)
2. the metrics you were monitoring ... if these came from a pmchart config, then that file would help and it would help to know if you added or deleted metrics and/or charts between the start of pmchart and the failure
3. update interval (default, or -t from command line, or changed via time control widget)
4. travelling forwards or backwards in the archive
5. position in the archive ... just playing forwards from the start, or just playing backwards from the end, or -S, -O, -A or -T command line options, or drag-n-drop the time line via the time control widget)

Unfortunately there are many levers that influence the interpolation code, and it helps to have the fullest possible picture of all of them leading up to the kaboom.


Reply to this email directly or view it on GitHub.

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