v On Windows: install_dir\tmaitm6\Kproduct_codeCMA.INI. For example, the
product code for the Monitoring Agent for Windows OS is NT file name for
is KNTCMA.INI.
v On UNIX and Linux: install_dir/config/product_code.ini. For example,
the file name for the Monitoring Agent for UNIX OS is ux.ini.
2. Find the line the begins with CTIRA_HOSTNAME=.
3. Type a new name for host name that is a unique, shorter name for the host
computer. The final concatenated name including the subsystem name, new
host name, and AGENT_CODE, cannot be longer than 32 characters.
Note: You must ensure that the resulting name is unique with respect to any
existing monitoring component that was previously registered with the Tivoli
Enterprise Monitoring Server.
4. Save the file.
5. Restart the agent.
Issues with starting and stopping an agent as a non-Administrator
user
You might experience issues with starting and stopping an agent as a
non-Administrator user. This issue is caused because of improper permissions set
for the hostname_pc.run file.
That file is created or modified every time an instance is started or stopped. All
instances must use the same user ID.
UNIX-based systems Log agent was deployed, configured, and started
but returns the KFWITM290E error
The Tivoli Enterprise Monitoring Server is timing out waiting for deployment
action to complete. The default timeout is 600 seconds. You can change the timeout
setting to KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT in kfwenv.
KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT=1000
KDY1024E error is displayed when configuring the run-as user name
for an agent
The error message KDY1024E is displayed when configuring the run-as user name
for an agent when the UNIX-based systems monitoring agent was installed as a
non-root user. For UNIX-based systems, you can only configure the run-as user
name if the UNIX-based systems/UNIX-based systems monitoring agent was
installed using the root user. In this case, leave the entry for the run-as user blank
or set the run-as user to the same user ID used to install the UNIX-based systems
monitoring agent.
Interface unknown messages in ras1 logs
Interface unknown messages appear in the ras1 log. For example:
(46CB65C1.0001-F:kdcsdrq.c,466,"do_request") Interface unknown
684152a852f9.02.c6.d2.2d.fd.00.00.00, activity
c638270e4738.22.02.09.2a.15.06.28.a2, 7509.0 These are issued to alert you that
some set components are driving RPC requests to a server that is not setup to
handle that request. Often, this occurs when the Warehouse Proxy Agent is not
Chapter 10. Monitoring agent troubleshooting 193
To Next Page
Loading...
Need help?
General
