[INUG-Users] nco_p_mttrapd not running

Mario Behring mariobehring at yahoo.com
Tue Aug 6 10:11:20 EDT 2013


The props file seems ok, pointing to the right places. I have this error on the mttrapd.log:

2013-08-06T10:48:12: Information: I-UNK-000-000: Connecting ...
2013-08-06T10:48:12: Debug: D-UNK-000-000: Shutting down Probewatch heartbeat thread.
2013-08-06T10:48:12: Debug: D-UNK-000-000: Probewatch heartbeat thread is already shutdown.
2013-08-06T10:48:12: Debug: D-UNK-000-000: Stopping separate communications threads if they are running.
2013-08-06T10:48:12: Debug: D-UNK-000-000: Running with single threaded communications.
2013-08-06T10:48:12: Debug: D-UNK-000-000: Reading /opt/IBM/tivoli/netcool/omnibus/etc/rules/snmptrap.rules
2013-08-06T10:48:12: Debug: D-UNK-000-000: Plain text rules file detected.
2013-08-06T10:48:12: Error: E-UNK-000-000: Rules file '/opt/IBM/tivoli/netcool/omnibus/etc/rules/snmptrap.rules' line 119: Failed to read lookup table file '$NC_RULES_HOME/include-snmptrap/CorrScore.snmptrap.lookup'
2013-08-06T10:48:12: Information: I-UNK-000-000: Falling back to previous rules file.
2013-08-06T10:48:12: Error: E-UNK-000-000: Failed to read rules: error in rules file
2013-08-06T10:48:12: Error: E-P_M-102-000: Failed to initialise session: Opl library error (see previous messages)

...and here is line 119 from the snmtrap.rules file:

table snmptrapCorrScore = "$NC_RULES_HOME/include-snmptrap/CorrScore.snmptrap.lookup"

I´ve checked and this file exists and is in this exact path....so, what could be wrong?


 From: William Cain <aloha at bill-lani.com>
To: users at netcoolusers.org 
Sent: Saturday, August 3, 2013 12:31 PM
Subject: Re: [INUG-Users] nco_p_mttrapd not running

Your probe props file are by default in
    Example:  $OMNIHOME/probes/linux2x86/mttrapd.props   for linux
          %OMNIHOME%\probes\win32\ping.props         for windows

To see what is uncommented and the probe will try to use perform
    --> grep -v ^#  $OMNIHOME/probes/linux2x86/mttrapd.props

To start a probe they reference a file analogous to a /etc/hosts file
This file is created via two command line steps:
    1. Edit $NCHOME/etc/omni.dat
    2. Run $NCHOME/bin/nco_igen   <---This builds file

To see what properties your probe will try to run with when it starts
    -->  $OMNIHOME/probes/nco_p_mttrapd -dumpprops

Notice there is also a help with the probes which shows the command line
options allowing you to over ride the probe props file
    ---> $OMNIHOME/probes/nco_p_mttrapd -help

If you still have issues you might consider
    $OMNIHOME/bin/nco_ping NCOMS

Notice there are two environmental variables listed, you must set NCHOME
and as someone else mentioned its very good to set OMNIHOME also

On 7/31/13 3:34 PM, "Mario Behring" <mariobehring at yahoo.com> wrote:

>About that....I have changed the mttrapd.props file at
>$NCHOME/omnibus/probes/linux2x86 and
>$NCHOME/omnibus/probes/linux2x86/default....just in case...to point to
>the correct ObjServer (OMNIBUS). I did the same for the tivoli_eif.props
>Still, I am getting the errors below on their respective log files (even
>when starting the probe at the command line):
>Error: E-UNK-000-000: ct_connect(): directory service layer: internal
>directory control layer error: Requested server name not found.
>2013-07-31T15:52:06: Error: E-UNK-000-000: Failed to make a connection to
>server 'NCOMS'.
>2013-07-31T15:52:06: Error: E-UNK-000-000: Failed to connect to all
>required ObjectServers.
>2013-07-31T15:52:06: Error: E-UNK-000-000: Failed to read rules: general
>it is
>still searching for an ObjServer named NCOMS....but the
>tivoli_eif.props ($NCHOME/omnibus/probes/linux2x86) file points to the
>'OMNIBUS' ObjServer...

Sent by the netcoolusers.org "users" mailing list
Post: users at netcoolusers.org
Unsubscribe: users-unsubscribe at netcoolusers.org
Search: http://netcoolusers.org/Search

More information about the Users mailing list