
tacmd suggestbaseline command receives an error
When using this command, you receive this message:
" The specified managed
system is not overrideable because it does not have the appropriate
affinity feature bit enabled."
The
tacmd suggestbaseline
command does not support pre-IBM Tivoli Monitoring
v6.2.1 agents.
When using the listSystems command, the last two digits for the
version appear as 'XX'
Extended version information for every agent might not always be available. When
this happens, the last two digits of the version displayed are represented as "XX".
This occurs for subnode agents or when agents are not enabled for Agent Deploy
support.
The command tacmd restartAgent fails if the agent is already stopped
If the
tacmd restartAgent
command is issued against an agent that is stopped, it
will generate an error message:
# /opt/IBM/ITM/bin/tacmd restartagent -n zpmaix13:KUX -t ul
KUICRA006I: Are you sure you want to restart the UL agent(s) that manage
zpmaix13:KUL?
Enter Y for yes or N for no: Y
KUICRA007I: Restarting UL agent(s).
KUICRA009E: A problem occurred while restarting UL - refer to the following error
returned from the server:
The monitoring server encountered an error while restarting the managed system.
If the error information returned from the server is not sufficient to help you
resolve the error, contact IBM Software Support.
The command /opt/IBM/ITM/bin/CandleAgent
-h /opt/IBM/ITM -c stop ul did not start
or stop agent.
The command returned a return code.
Enable Deployment trace logging on the agent machine. Contact Customer Service
for details on this procedure. Collect the following log files
On Windows the log kdsmain.msg log is located in the {CANDLEHOME}\CMS
directory and {hostname}_ms_{timestamp}-XX.log files are located in
CANDLEHOME\logs directory.
On Unix-Based systems the logs {hostname}_{timestamp}.log and
{hostname}_ms_{timestamp}-XX.log is located in the {CANDLEHOME}/logs directory.
On the target Managed System Node machine collect the following log files.
On Windows the logs kdyproc_ras1_{timestamp}.log and {hostname}_nt_kntcma_
{timestamp}-XX.log are located in the {CANDLEHOME}\tmaitm6\logs directory.
On Unix systems the logs kdyproc_ras1_{timestamp}.log and {hostname}_
ux_kuxagent_{timestamp}-XX.log is located in the {CANDLEHOME}/logs directory.
On Linux systems the logs kdyproc_ras1_{timestamp}.log and {hostname}_
lz_klzagent_{timestamp}-XX.log is located in the {CANDLEHOME}/logs directory.
Refer to IBM Tivoli Monitoring v 6.2 Problem Determination Guide
for more information.
The user can verify the agent is stopped by running
tacmd listSystems
:
208
IBM Tivoli Monitoring: Troubleshooting Guide
Содержание E027SLL-H - Tivoli Monitoring - PC
Страница 1: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Страница 2: ......
Страница 3: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Страница 14: ...xii IBM Tivoli Monitoring Troubleshooting Guide...
Страница 16: ...xiv IBM Tivoli Monitoring Troubleshooting Guide...
Страница 18: ...xvi IBM Tivoli Monitoring Troubleshooting Guide...
Страница 22: ...4 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 82: ...64 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 144: ...126 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 164: ...146 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 188: ...170 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 240: ...222 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 262: ...244 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 274: ...256 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 276: ...258 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 284: ...266 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 288: ...270 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 302: ...284 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 308: ...290 IBM Tivoli Monitoring Troubleshooting Guide...
Страница 309: ......
Страница 310: ...Printed in USA GC32 9458 05...