book
Article ID: KB0093261
calendar_today
Updated On:
Description
Resolution:
Note: The format of the dateTime is MM/dd/yy HH:mm:ss.S, and the format of the levelLog is Finest, Finer, Fine, Config, Info, Warning, Severe.
Useful Events mapped from Logs entry for Tivoli or HP OpenView.
Events Name Log Event Log Location Explanation
Driver Added <dateTime_ levelLog>: Driver:<HostName/UserNameClient>:Added Broker
Driver Removed <dateTime_ levelLog>: Driver:<USERNAME>:Removed Broker
Engine Added <dateTime_ levelLog>: EngineDaemon:<hostName>-<IP>:Added Broker
Engine Removed <dateTime_ levelLog>: EngineDaemon:<hostName>-<IP>:Removed:Code:<value> Broker
Engine Died <dateTime_ levelLog>: Engine Daemon:<hostName>-<IP>:Died Broker
Job Cancelled <dateTime_ levelLog>: JobId:<SERVICEID>-<SERVICEID>:CancelledJob Broker
Job Finished <dateTime_ levelLog>: Driver:<SERVICENAME>:CompletedService:<SERVICENAME>-<SERVICEID> Broker
Server Started <dateTime_ levelLog>: Message Server has started. Broker
Task Error (autopack off)
<dateTime_ levelLog>: Engine:<hostName>-<instanceNbr>:TaskCompleted:<serviceName>-<serviceID>-<tasksID>
<dateTime_ levelLog>: <serviceName>-<serviceID>-<taskID>, Task failed due to : <Exception>: Throw Exception to fail task. on Engine: <hostName>
( autopack on )
<dateTime_ levelLog>: Engine:<hostName>-<instanceNbr>:TaskCompleted:<serviceName>-<serviceID>-<tasksID>
<dateTime_ levelLog>: <serviceName>-<serviceID>-<taskID>, <Exception>: Throw Exception to fail task., subtask number <nbr> Broker Two Entries are needed to determine which Engine is associated to which failed task. The Error Message is slightly different when using the Autopack option.
Broker Added <dateTime_ levelLog>: Broker:http://<hostName>:<port>/livecluster-<brokerName>:Added
Director
Broker Removed <dateTime_ levelLog>: Broker:http://<hostName>:<port>/livecluster-<brokerName>:Removed
Director
Broker Died <dateTime_ levelLog>: Broker:http://<hostName>:<port>/livecluster-<brokerName>:Died
Director
EngineDaemon Added <dateTime_ levelLog>: EngineDaemon:<hostName>-<IPAddress>:Added Director
EngineDaemon Removed <dateTime_ levelLog>: EngineDaemon:<hostName>-<ip>:Removed:Code:<value> Director
EngineDaemon Died <dateTime_ levelLog>: Engine Daemon:<hostName>-<ip>:Died Director
Remote Database Backup Failure <dateTime_ levelLog>: problem backing up db to <Base Dir>/webapps/livecluster/WEB-INF/db/internal/backup <Exception>
<dateTime_ levelLog>: Scheduling network backup (0) at location http://<hostName>:<port>/livecluster/director/DatabaseNetworkBackupPlugin?internal=<ID>
Director Failure to backup the secondary internal DB
Local Database Backup Failure Event <dateTime_ levelLog>: problem backing up db to <ErrorMessage>
<dateTime_ levelLog>: Failed to backup database <Exception> Director Failure to backup the primary internal DB
Server Started <dateTime_ levelLog>: Message Server has started Director
Driver Initial Task Submitted <dateTime_ levelLog>: Driver:<HostName/UsernameClient>:SubmittedTasks:<ServiceName>-<ServiceID>:Amount:0 Broker First Task of the Service
Driver Subsequent Task Submitted <dateTime_ levelLog>: Driver:<HostName/UsernameClient>:SubmittedTasks:<ServiceName>-<ServiceID>:Amount:1 Broker other Tasks
Driver Task Collected <dateTime_ levelLog>: Driver:<hostName/UserNameClient>:CollectedTasks:<serviceName>-<serviceID>:Amount:1 Broker Task Collected by the Driver for a specific Service
Driver State Update <dateTime_ levelLog>: Driver:<hostName/UserNameClient>:UpdateState:<serviceID> Broker Update to the State for the Service
Engine LogOff <dateTime_ levelLog>: Engine:<hostName>-<instanceNbr>:Logoff:<ReasonForLogOff> Broker An engine can LogOff for multiple reasons: 1. Native daemon shut down the Engine 1. Restarting to load librar 1. Rerouted by the Engine Balancer 1. etc...
BlackListing Engine <dateTime_levelLog>: blacklisting engine <HOSTNAME>-<INSTANCE> for Service <SERVICEID>-<SERVICEID> Broker
Primary Down <dateTime_levelLog>: Broker:http://<hostname>:<port>/livecluster-<brokerName>:LoggedOff:<IPPrimary>:<port>
<dateTime_levelLog>: Will try to relogin to <IPPrimary>:<port>
<dateTime_levelLog>: Sending login message on <IPPrimary>:<port> {x Times}
<dateTime_levelLog>: Logged in to <IPPrimary>:<port>
<dateTime_levelLog>: Broker:http://<hostname>:<port>/livecluster-<BrokerName>:LoggedIn:<IPPrimary>:<port>
Broker The message {<dateTime_levelLog>: Sending login message on <IPPrimary>:<port>} repeated Multiples times over the period of time Primary Down
Primary Down <dateTime_levelLog>: Will try to relogin to <IPPrimary>:<port>
<dateTime_levelLog>: Sending login message on <IPPrimary>:<port>
<dateTime_levelLog>: Logged in to <IPPrimary>:<port>
<dateTime_levelLog>: Secondary logged into the Primary, so logging off Deamons Secondary The message {<dateTime_levelLog>: Sending login message on <IPPrimary>:<port>} repeated Multiples times over the period of time Primary Down.
Secondary Down <dateTime_levelLog>: Broker:http://<hostname>:<port>/livecluster-<BrokerName>:LoggedOff:<IPSecondary>:<port>
<dateTime_levelLog>: Will try to relogin to <IPSecondary>:<port>
<dateTime_levelLog>: Sending login message on <IPSecondary>:<port>
<dateTime_levelLog>: Logged in to <IPSeconday>:<port>
<dateTime_levelLog>: Broker:http://<hostName>:<port>/livecluster-<BrokerName>:LoggedIn:<IPSecondary>:<port>
Broker The message {<dateTime_levelLog>: Sending login message on <IPSecondary>:<port>} repeated Multiples times over the period of time Primary Down.
Server Shutdown <dateTime_levelLog>: Shutting down Message Server.
<dateTime_levelLog>: Shutdown reason: <Reason> Director These Message will be logged only if the manager is shutdown correctly.
If the Manager's JVM dies for any reasons you will not see these messages.
Server Shutdown <dateTime_levelLog>: Shutting down Message Server.
<dateTime_levelLog>: Shutdown reason: <Reason> Broker These Message will be logged only if the manager is shutdown correctly.
If the Manager's JVM dies for any reasons you will not see these messages.
Note: The format of the dateTime is MM/dd/yy HH:mm:ss.S, and the format of the levelLog is Finest, Finer, Fine, Config, Info, Warning, Severe.
Issue/Introduction
Useful Events Mapping to Logs entry and SNMP