Failed to open Rules File The problem could be one of the following issues: Failed to read rules: v The rules file does not could not open rules file exist. V The probe does not have permissions to read the rules file. V An incorrect file path was specified. 14 IBM Tivoli Netcool/OMNIbus Probe Extension Package: Reference Guide Ensure the rules file is readable and verify that the path is correctly defined in the rules file or in the environment variable. The ObjectServer records the amount of time that each trigger uses during each granularity period and saves the details in the $NCHOME/omnibus/log/servername_trigger_stats.logn file. You can use this file to identify which triggers are using the most time, to prioritize which triggers to review, and to monitor the system to ensure that it is running as expected.

1. What Is A Log File
2. Generic Log Of When Bills Are Due

When configuring the mttrapd probe for failover the PeerHost should be different to increase the resilience of the system. Example configuration: MASTER HOST Properties file: PeerHost: 'slavehost' PeerPort: 6789 Mode: 'master' MessageLevel: 'debug' MessageLog: '/opt/Omnibus/log/mttrapdmaster.log' Port: 162 SLAVE HOST Properties file: PeerHost: 'masterhost' PeerPort: 6789 Mode: 'slave' MessageLevel: 'debug' MessageLog: '/opt/Omnibus/log/mttrapdslave.log' Port: 162 It is possible to run two mttrapd probes on the same host in failover mode. Tp link drivers wireless card. In order to do this use unique mttrapd probe ports and define these within the master and slave mttrapd probes property files e.g.

MASTER HOST Properties file: Name: 'mttrapdmaster' PeerHost: 'myhost' PeerPort: 6789 Mode: 'master' MessageLevel: 'debug' MessageLog: '/opt/Omnibus/log/mttrapdmaster.log' Port: 162 SLAVE HOST Properties file: Name: 'mttrapdslave' PeerHost: 'myhost' PeerPort: 6789 Mode: 'slave' MessageLevel: 'debug' MessageLog: '/opt/Omnibus/log/mttrapdslave.log' Port: 1620.

What Is A Log File

Generic Log Of When Bills Are Due

. USERS AFFECTED: All Users. PROBLEM DESCRIPTION: Probe does not read log file. RECOMMENDATION:. This was not a problem with the probe but with the libCore libraries and the call to OmniSleep within the probe. Problem conclusion Temporary fix Comments.