[Spacewalk-list] Spacewalk 1.5 Monitoring issue

[David Nutter]

On Tue, Jul 26, 2011 at 11:27:19AM +0530, trm asn wrote:

*snip*
 
> 'ProbeRecord', 'get_hostAddress') ; that error I have resolved by editing
> "NPRecords.pm" & changed the parameter "hostAddress" to "HOSTADDRESS" .
> 
> now my "scout config push" are getting success, but unfortunately still the
> monitoring status is "PENDING, Awaiting Update" .
> 
> 
> -bash-3.2$ rhn-runprobe --probe=261 --log=all=4
> Can't locate object method "hostname" via package
> "NOCpulse::Probe::Config::ProbeRecord" at
> blib/lib/Class/MethodMaker/Engine.pm (autosplit into
> blib/lib/auto/Class/MethodMaker/Engine/new.al) line 941.
> 
> Any idea...

Hi, 

I've worked around/fixed the above error, and the error where
rhn-catalog output is missing probe details by changing NOCPulse::Probe::Config::ProbeRecord
and /var/lib/nocpulse/libexec/ProbeCatalog.pm as per the patches
below. For information only, I don't recommend that anyone apply these
to a production install!

--- ProbeRecord.pm.orig 2011-08-02 19:27:20.000000000 +0100
+++ ProbeRecord.pm      2011-08-02 19:26:57.000000000 +0100
@@ -54,6 +54,8 @@
    contactGroupCustomers => 'contact_group_customers',
    contactGroupNames     => 'contact_group_names',
    hostAddress           => 'host_ip',
+   HOSTADDRESS           => 'host_ip',
+   HOSTNAME              => 'host_name',
    hostName              => 'host_name',
    hostRecid             => 'host_id',
    parsedCommandLine     => 'parameters',

--- ProbeCatalog.pm.orig        2011-08-02 19:27:41.000000000 +0100
+++ ProbeCatalog.pm     2011-08-02 19:25:58.000000000 +0100
@@ -35,10 +35,10 @@
     my $result;
     if ($probe_id) {
        $result = $probeHashRef->{RECID}.' '.$probeHashRef->{PROBE_TYPE};;
-       if ($probeHashRef->{hostName}) {
-           $result .= ' on '.$probeHashRef->{hostName}.' ('.$probeHashRef->{hostAddress}.')';
+       if ($probeHashRef->{HOSTNAME}) {
+           $result .= ' on '.$probeHashRef->{HOSTNAME}.' ('.$probeHashRef->{HOSTADDRESS}.')';
        } else {
-           $result .= ' on '.$probeHashRef->{hostAddress};
+           $result .= ' on '.$probeHashRef->{HOSTADDRESS};
        }
        $result .= ': '.$probeHashRef->{DESCRIPTION};



So, now I can run a probe from the commandline and get correct results
but my probes still won't update as far as the UI is concerned.

I can even see the correct probe output is being placed in files like

/var/log/nocpulse/TSDBLocalQueue/queue/1312307617.13995

containing 

1-33-latency,1312307616,0.367097
1-102-latency,1312307654,1.467809
1-40-load5,1312308198,2.02
1-40-load15,1312308198,2.00
1-40-load1,1312308198,2.00
1-39-nusers,1312308227,3
1-40-load5,1312308227,2.02
1-40-load15,1312308227,2.00
1-40-load1,1312308227,2.00
1-29-latency,1312308229,1.233025
1-39-nusers,1312308242,3
1-102-latency,1312308240,0.120207
1-31-latency,1312308242,0.940315
1-29-latency,1312308448,0.0258
1-40-load5,1312309441,2.02
1-40-load15,1312309441,2.00
1-40-load1,1312309441,2.00
1-32-pingtime,1312309441,0.2177
1-32-pctlost,1312309441,0
1-32-pingtime,1312309868,0.2177
1-32-pctlost,1312309868,0

so it's mostly working. 

Any ideas where to go next? It seems that the probe outputs are not
being properly loaded into the DB after execution completes. 

Regards,

-- 
David Nutter  				Tel: +44 (0)131 650 4888
BioSS, JCMB, King's Buildings, Mayfield Rd, EH9 3JZ. Scotland, UK 

Biomathematics and Statistics Scotland (BioSS) is formally part of The
James Hutton Institute (JHI), a registered Scottish charity No. SC041796
and a company limited by guarantee No. SC374831