pcp
[Top] [All Lists]

Re: [pcp] json pmda qa/1052 failing on Centos6.6

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] json pmda qa/1052 failing on Centos6.6
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 05 Aug 2015 10:55:46 +1000
Cc: David Smith <dsmith@xxxxxxxxxx>, PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <934995702.4411085.1438732642013.JavaMail.zimbra@xxxxxxxxxx>
References: <017301d0cc28$d7c78640$875692c0$@internode.on.net> <440072288.2807362.1438581950952.JavaMail.zimbra@xxxxxxxxxx> <55BFC26D.8040503@xxxxxxxxxx> <1889100767.3736026.1438652097204.JavaMail.zimbra@xxxxxxxxxx> <55C14FAF.9010100@xxxxxxxxxxxxxxxx> <934995702.4411085.1438732642013.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
On 05/08/15 09:57, Nathan Scott wrote:
Hi Ken,

----- Original Message -----
Does this help any?

Yep - that looks like the known-rhel6-pmdajson-issue, see start of this thread:
http://www.pcp.io/pipermail/pcp/2015-July/007758.html


OK ... but if pmdajson is not built for RHEL6, shouldn't this be reflected in the open source PCP configurery for both RHEL6 and CentOS6.6? If this was the case, then I would not have the failure, I would not spend time trying to debug it and we'd have less email volume?

Traceback (most recent call last):
...
   File "/usr/lib64/python2.6/json/__init__.py", line 318, in loads
     return cls(encoding=encoding, **kw).decode(s)
TypeError: __init__() got an unexpected keyword argument 'object_pairs_hook'


Did you have to make any code changes to get that stack trace into the logfile?

No code changes, just ran dbpma interactively ... maybe there is one more pmcd restart in the qa test and the real json.log is no longer in json.log.prev?

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