Download Tivoli Workload Scheduler: Troubleshooting Guide

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Transcript
1. Use the evtsize command to increase the Mailbox.msg file. Ensure that the
file system has sufficient space to accommodate the larger file.
2. Delete the corrupt message file.
3. Restart Tivoli Workload Scheduler by issuing the conman start command on
the fault-tolerant agent.
v If you do not think that this is the answer, or are not sure, contact IBM Software
Support for assistance.
Fault-tolerant agents unlink from mailman on a domain
manager
A message is received in the maestro log on the domain manager from mailman
for each of the fault-tolerant agents to which it is connected. The messages are as
follows:
MAILMAN:06:15/ + ++++++++++++++++++++++++++++++++++++++++++++++++
MAILMAN:06:15/ + WARNING: No incoming from <<workstation>>
- disconnecting. [2073.25]
MAILMAN:06:15/ + ++++++++++++++++++++++++++++++++++++++++++++++++
These messages usually occur in the 30 - 60 minutes immediately following
JnextPlan.
Cause and solution:
This problem is normally caused by a false timeout in one of the mailman
processes on the domain manager. During the initialization period immediately
following JnextPlan, the "*.msg" files on the domain manager might become filled
with a backlog of messages coming from fault-tolerant agents. While mailman is
processing the messages for one fault-tolerant agent, messages from other
fault-tolerant agents are kept waiting until the configured time interval for
communications from a fault-tolerant agent is exceeded, at which point mailman
unlinks them.
To correct the problem, increase the value of the mm response and mm unlink
variables in the configuration file ~maestro/localopts. These values must be
increased together in small increments (60-300 seconds) until the timeouts no
longer occur.
Dynamic agent problems
The following problems could be encountered with dynamic agent.
v “The dynamic agent cannot contact the server”
v “V8.5.1 fault-tolerant agent with dynamic capabilities cannot be registered” on
page 112
v “Error message AWKDBE009E is received” on page 112
The dynamic agent cannot contact the server
The dynamic agent cannot communicate with the server.
The dynamic agent cannot contact the Tivoli Workload Scheduler master domain
manager or dynamic domain manager.
Cause and solution:
Chapter 8. Troubleshooting engine problems
111
Document related concepts
no text concepts found