Receive A Busy Monitoring Server Message When Using The Getfile, Putfile, Or Executecommand Commands; Reconfiguring An Agent And Then Getting The Deploy Status Yields A Port Number Message; Tacmd Getfile Or Putfile Command Is Failing; Temporary Files Remain When Tacmd Getfile Or Putfile Is Interrupted - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

This behavior might be caused by an OUT OF MEMORY condition on the AIX
system where the command is issued due to specific AIX memory management.
This problem can be solved by setting the environment variable,
LDR_CNTRL=MAXDATA=0x80000000, to be exported in the shell from which the
tacmd command is issued:
export LDR_CNTRL=MAXDATA=0x80000000
Receive a busy monitoring server message when using the getfile,
putfile, or executecommand commands
If you receive a busy monitoring server message, there are too many file transfers
in progress. Wait until some of the transfers complete, and then retry your
command. The following error messages are received for the respective commands:
For the getfile command:
KUIGTF111E: Monitoring server is too busy.
For the putfile command:
KUIPTF111E: Monitoring server is too busy.
For the executecommand command:
KUIPTF111E: Monitoring server is too busy.
Reconfiguring an agent and then getting the deploy status yields a
port number message
When reconfiguring an agent by running the tacmd configuresystem command, a
subsequent tacmd GetDeployStatus command yields a message like the following:
KDY0030E: lookupUAPort failed. Operation to determine the port number used
by Universal Agent agent was not successful.
If installing from images on an NFS mount, the NFS mounts need world execute
permissions to be accessible by the process doing the distribution.

tacmd getfile or putfile command is failing

On UNIX and Linux systems, either of these commands fail if the requested file's
size is larger than the user limit file size defined by the ulimit command. When
using the tacmd getfile command, ensure that the local system's ulimit -f setting
can accommodate the requested file's size. When using the tacmd putfile
command, ensure that the remote system's ulimit -f setting can accommodate the
specified file's size.

Temporary files remain when tacmd getfile or putfile is interrupted

When issuing a tacmd getfile command or tacmd putfile command, the file is
copied as a temporary file to the directory location as specified by the
-d|–destination option. If the command is interrupted (for example, if the session
is closed), this temporary file is left in the specified directory location. On
Windows systems, the temporary file name is prefixed with 'cxm' followed by
random characters and has a '.tmp' filetype (for example, cxm1C.tmp). On UNIX
systems, the temporary file name is prefixed with 'cxp' followed by alphanumeric
characters (for example, cxp5pYmUa. ) Over time, this presence of potentially large
temporary files could present problems that ultimately result in future getfile
Chapter 11. Command troubleshooting
205