After Installing And Configuring A Monitoring Agent, It Fails To Start; Situation_Fullname Slot Missing For Delete Events; Logs Are Using The Situation Id String Instead Of The Display Name - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

3. Repeat step 2 for each agent or agent instance that you want to start as a
4. Save the file.
5. Run install_dir/bin/UpdateAutoRun.sh as root user.

After installing and configuring a monitoring agent, it fails to start

If the SecureMode file is in the registry directory, SecureMain was run in
environment. This does not allow the monitoring agent to start if you try to start it
without root privileges. See the IBM Tivoli Monitoring Installation and Setup
Guide for instructions on how to have monitoring agents work properly with
SecureMain in place.

situation_fullname slot missing for delete events

If you create a situation that has a long name (longer than 32 characters), distribute
the situation to an agent, and then delete it after the situation's associated event is
displayed in Tivoli Enterprise Console, the situation_fullname slot is missing.
The expected result would be that, for the deleted event, the situation status is set
to 'D".
Events do not reflect the long names if the definition is deleted, and the Tivoli
Enterprise Monitoring Server logs also do not reflect the long name.

Logs are using the situation ID string instead of the display name

Situations have both a display name (up to 256 bytes in length, UTF8 enabled) and
an ID string (up to 32 bytes in length ). For example, a situation display name can
be "don't let the pigeon drive the bus !" or 100 characters of Japanese text. The
associated ID string will be of the form 000000000000008D723DE7DFED450F. If the
186
IBM Tivoli Monitoring: Troubleshooting Guide
<productCode>ux</productCode>
<default>
<user>itmuser</user>
</default>
For the DB2 monitoring agent instances to run as the instance owner IDs:
<productCode>ud</productCode>
<instance>
<name>db2inst1</name>
<user>db2inst1</user>
</instance>
<instance>
<name>db2inst2</name>
<user>db2inst2</user>
</instance>
For the Websphere MQ monitoring agent instances to all run as the mqm user
ID, and for the default instance to not be started:
<productCode>mq</productCode>
<default>
<user>mqm</user>
</default>
<instance>
<name>None</name>
<autoStart>no</autoStart>
</instance>
specific user ID.