| To: | Nathan Scott <nathans@xxxxxxxxxx>, Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] json pmda qa/1052 failing on Centos6.6 |
| From: | David Smith <dsmith@xxxxxxxxxx> |
| Date: | Mon, 3 Aug 2015 14:35:09 -0500 |
| Cc: | PCP <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <440072288.2807362.1438581950952.JavaMail.zimbra@xxxxxxxxxx> |
| References: | <017301d0cc28$d7c78640$875692c0$@internode.on.net> <440072288.2807362.1438581950952.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 |
On 08/03/2015 01:05 AM, Nathan Scott wrote: > Hi Ken, > > David looked into a problem with the python JSON APIs on RHEL6 > not supporting all the features needed by pmdajson (IIRC) - it > may be this is the same issue. The lack of diagnostics is not > helping though, so I can't really tell. The lack of diagnostics when developing a python PMDA is a real pain-in-you-know-where. One of the reasons why there are so many try/except statements in the JSON PMDA is that that's the only way I could see python exceptions. As far as the failure itself goes, without more information about the system itself I couldn't even guess. -- David Smith dsmith@xxxxxxxxxx Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax) |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 1249572] pcp-iostat exception at the end of an archive, bugzilla |
|---|---|
| Next by Date: | Re: [pcp] json pmda qa/1052 failing on Centos6.6, Nathan Scott |
| Previous by Thread: | Re: [pcp] json pmda qa/1052 failing on Centos6.6, Nathan Scott |
| Next by Thread: | Re: [pcp] json pmda qa/1052 failing on Centos6.6, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |