Hi,
On 2016-04-15 01:37, Nathan Scott wrote:
> ----- Original Message -----
>> On 2016-04-13 07:52, Nathan Scott wrote:
>>> ----- Original Message -----
>>>> [...]
>>>> connect.pl says "OK", after PMDA installation there are no oracle
>>>> metrics available and the Oracle PMDA log is silent.
>>>
>>> Hmm, I've not seen anything like that. Usually theres a big warning
>>> in the pmcd/oracle.log file ... and usually its that initial connect
>>> that fails.
>>>
>>>> Are there any recommended sanity checks that could be done in this case?
>>>
>>> I'd verify the connection with sqlplus, issuing queries like those
>>> listed in the pmdaoracle.pl code (near the start - bunch of 'em you
>>> could try there). Those should all show columns/values returned by
>>> sqlplus.
>>
>> Here are some additional details and perhaps a clue:
>>
>
> Ah - does this patch help?
>
> # $ENV{PCP_PERL_DEBUG} = 'LIBPMDA';
> $pmda = PCP::PMDA->new('oracle', 32);
> +$pmda->connect_pmcd;
> $pmda->set_user($os_user);
Unfortunately not, the error remains the same. But enabling the above
debug I see the following (with the patch):
Lots of these:
[Fri Apr 15 09:08:31] pmdaoracle(125624) Debug: pmdaInit: PMDA
pmdaoracle: Metric 32.9.3(265) matched to indom 32.6(6)
Once this:
[Fri Apr 15 09:08:31] pmdaoracle(125624) Debug: pmdaInit: PMDA
pmdaoracle: No help text path specified
[Fri Apr 15 09:08:31] pmdaoracle(125624) Warning: pmdaDirect: PMDA
pmdaoracle: Direct mapping for metrics disabled @ metrics[191] 32.1.0
[Fri Apr 15 09:08:31] pmdaoracle(125624) Info: name = pmdaoracle
[Fri Apr 15 09:08:31] pmdaoracle(125624) Info: domain = 32
[Fri Apr 15 09:08:31] pmdaoracle(125624) Info: ext flags = c
[Fri Apr 15 09:08:31] pmdaoracle(125624) Info: num metrics = 266
[Fri Apr 15 09:08:31] pmdaoracle(125624) Info: num indom = 18
[Fri Apr 15 09:08:31] pmdaoracle(125624) Info: metric map = linear
[Fri Apr 15 09:08:32] pmdaoracle(125624) Debug: Received PDU_PMNS_TRAVERSE
And finally this:
[Fri Apr 15 09:08:32] pmdaoracle(125624) Debug: Received PDU_PMNS_NAMES
[Fri Apr 15 09:08:32] pmdaoracle(125624) Debug: Received PDU_PMNS_NAMES
[Fri Apr 15 09:08:32] pmdaoracle(125624) Debug: Received PDU_PMNS_NAMES
[Fri Apr 15 09:08:32] pmdaoracle(125624) Debug: Received PDU_PMNS_NAMES
[Fri Apr 15 09:08:32] pmdaoracle(125624) Debug: Received PDU_DESC_REQ
[Fri Apr 15 09:08:32] pmdaoracle(125624) Debug: Received PDU_PROFILE
[Fri Apr 15 09:08:32] pmdaoracle(125624) Debug: Received PDU_FETCH
[Fri Apr 15 09:08:48] pmdaoracle(125624) Error: pmdaFetch: Unavailable
metric PMID 32.12.4[1]
[Fri Apr 15 09:08:48] pmdaoracle(125624) Error: pmdaFetch: Unavailable
metric PMID 32.12.4[3]
[Fri Apr 15 09:08:48] pmdaoracle(125624) Error: pmdaFetch: Unavailable
metric PMID 32.12.4[7]
[Fri Apr 15 09:08:48] pmdaoracle(125624) Error: pmdaFetch: Unavailable
metric PMID 32.0.73[0]
[Fri Apr 15 09:08:48] pmdaoracle(125624) Error: pmdaFetch: Unavailable
metric PMID 32.0.79[0]
Log finished Fri Apr 15 09:08:48 2016
Thanks,
--
Marko Myllynen
|