Messages in the log file

To obtain the detailed log information, set the probe's MessageLevel property to debug. This enables the logging of the additional information that tracks the progress of a command's execution. For example, the following shows the progress of a resync command:

Information: I-UNK-000-000: Calling NSProbeBidirCB: 
Information: I-UNK-000-000: NSProbeBidirCNB: Thread id is 0x13e19a0 
{command:resync,params:[{"spectrumName":SpectroServer1"]}
Debug: D-JPR-000-000: com.ibm.tivoli.netcool.omnibus.probe.services.impl.
SimpleCommandService$BidiThread.parseRequest ENTERING
Debug: D-JPR-000-000: com.ibm.tivoli.netcool.omnibus.probe.bidi.CommandHandler.executeCommand ENTERING
Debug: D-JPR-000-000: com.ibm.tivoli.netcool.omnibus.probe.bidi.CommandHandler.executeCommand EXITING
Information: I-JPR-000-000: Command Port received Resync request for Spectrum Server : SpectroServer1
Information: I-JPR-000-000: Attempting to subscribe Resync 
request into queue for Spectrum Server : SpectroServer1
Information: I-JPR-000-000: Spectrum Server SpectroServer1 Successfully subscribed into Resync queue
Debug: D-NHT-105-008: [HTTP Listener]: Data available from 'localhost' (::1) on socket '16'.
Debug: D-NHT-105-028: [WorkPoolThread]: Successfully got a work item. Items left on work queue is '0'.
Debug: D-JPR-000-000: [ThreadMonitor] Thread added in  Monitor list.
Information: I-JPR-000-000: [ResyncWorker SpectroServer1] Thread started.
Information: I-UNK-000-000: Probewatch: Start resync for SpectroServer1
Information: I-JPR-000-000: [ResyncWorker SpectroServer1] Status: SUCCESS get active alarm list.
Debug: D-JPR-000-000: [ResyncWorker SpectroServer1] SQL command: UPDATE alerts.status 
SET Severity = 0 WHERE LastOccurrence <= 1447057398 AND Node = 'SpectroServer1' 
AND AlertKey NOT IN ('5620dec4-0029-1000-023b-008010b4d48f')
Debug: D-JPR-000-000: OmnibusDBManager executing sql command
Information: I-UNK-000-000: Probewatch: Complete resync for SpectroServer1

These messages can also help to isolate problems with a command. For example, the following shows the log messages for an unackAlarm command that contained an invalid alarm identifier.

Information: I-UNK-000-000: Calling NSProbeBidirCB
Information: I-UNK-000-000: NSProbeBidirCB: Thread id is 0xb84550
Information: I-JPR-000-000: [1 SpectroServer1] Successful poll of CORBA interface, primary SpectroServer
{"command":"unacknowledgeAlarm","params": 
[{"alarmID":"56079f60-0006-1000-0371-008010b4d48f","spectrumName":"SpectroServer1"}]}
Debug: D-JPR-000-000: com.ibm.tivoli.netcool.omnibus.probe.services.impl.
SimpleCommandService$BidiThread.parseRequest ENTERING
Debug: D-JPR-000-000: com.ibm.tivoli.netcool.omnibus.probe.bidi.CommandHandler.executeCommand ENTERING
Debug: D-JPR-000-000: com.ibm.tivoli.netcool.omnibus.probe.bidi.CommandHandler.executeCommand EXITING
Information: I-JPR-000-000: Command Port received unacknowledge alarm request for alarm : 
56079f60-0006-1000-0371-008010b4d48f
Information: I-JPR-000-000: Attempting to unacknowledge : 56079f60-0006-1000-0371-008010b4d48f
Error: E-JPR-000-000: [1 SpectroServer1] 
Error un-acknowledging alarmstruct com.aprisma.spectrum.core.idl.
CsCAlarmDomainPackage.CsCAttrErrorListOfAlarms {
com.aprisma.spectrum.core.idl.CsCAlarmDomainPackage.CsCAlarmAttrErrorList[] 
list={struct com.aprisma.spectrum.core.idl.CsCAlarmDomainPackage.CsCAlarmAttrErrorList {
byte[] alarmID={86,7,-97,96,0,6,16,0,3,113,0,-128,16,-76,-44,-113},
com.aprisma.spectrum.core.idl.CsCAttribute.CsCAttrErrorList 
attrErrorList=struct com.aprisma.spectrum.core.idl.CsCAttribute.CsCAttrErrorList {
com.aprisma.spectrum.core.idl.CsCAttribute.CsCAttrError[] 
list={struct com.aprisma.spectrum.core.idl.CsCAttribute.CsCAttrError {
int attributeID=73549,
com.aprisma.spectrum.core.idl.CsCError.CsCError_e error=DOES_NOT_EXIST
com.aprisma.spectrum.core.idl.CsCError.CsCError_e error=PARTIAL_FAILURE
com.aprisma.spectrum.core.idl.CsCError.CsCError_e error=PARTIAL_FAILURE
Error: E-JPR-000-000: Alarm 56079f60-0006-1000-0371-008010b4d48f Error in unacknowledge