9.1.2 Failure information during package distribution or file collection
The status of a UNIX machine to which packages are being distributed or from which files are being collected is sent to the managing server as a status code (end status or user status). For the meanings of status codes, see Appendix B. Status Codes.
If a failure occurs at the distribution-destination system, detailed information is also stored in the managing server's job management file. For details about the storage method, see 10.1.2 Formats for messages output during package distribution or during file collection.
Figure 9-1 shows the storage of failure information during package distribution or file collection.
|
For the file names of MAIN.LOGF, PPINS.LOGF, and CF.LOGF, see (2) Checking the local system's failure information.
If you cannot identify the failure cause by referring to the status code, MAIN.LOGF, PPINS.LOGF, or CF.LOGF, you need to acquire the failure information of JP1/IT Desktop Management 2 - Agent on the UNIX machine. For the acquisition method, see 9.3 Acquiring failure information.
- Organization of this subsection
(1) Checking the managing server's failure information
To check the details of the managing server's failure information, you can use one of the commands or the window described below.
- For the Windows version of the managing server
-
Job Status window
(2) Checking the local system's failure information
You can use the cat command or a pager command such as pg and more to check the details of the message log files listed below.
- Important
-
If you refer to the log files of this product by using the vi editor, the text might appear garbled. In that case, refer to the log files by using other tools (the cat command, etc.) than the vi editor.
Functions |
Contents of the message log file |
Message log file name |
---|---|---|
Client services |
Failure information about distribution of user data or user programs and failure information during file collection |
|
Failure information about distribution of program products |
|
|
Failure information about distribution of another company's software |
|
|
Failure information about installing OS patches |
|
|
Failure information about unarchiving OS patches |
|
|
Failure information about applying patches |
|
|
Failure information about external program processing for collection |
|
An example of the MAIN.LOGF file as displayed by the cat command follows.
-
Message output number
Indicates the output location of the message in the message log file.
-
Output date and output time
Indicates the date and time when the message is output. The date and time follow the local standard time and are in the time zone of the parent process that started JP1/IT Desktop Management 2 - Agent, and results adjusted for Daylight Savings Time are stored.
-
Process ID
Indicates the process ID of the JP1/IT Desktop Management 2 - Agent process that output the message.
-
Serial message output number in process
Indicates the serial message output number within the JP1/IT Desktop Management 2 - Agent process.
-
Message
Contains text indicating the nature of the failure. The language type of the message depends on the language environment of the process that activated JP1/IT Desktop Management 2 - Agent.
-
JP1/IT Desktop Management 2 - Agent maintenance information 1
Indicates maintenance information for JP1/IT Desktop Management 2 - Agent.
-
JP1/IT Desktop Management 2 - Agent maintenance information 2
Indicates maintenance information for JP1/IT Desktop Management 2 - Agent.
-
JP1/IT Desktop Management 2 - Agent maintenance information 3
Indicates maintenance information for JP1/IT Desktop Management 2 - Agent.
When JP1/IT Desktop Management 2 - Agent maintenance information 2 contains a system call name, the second number in maintenance information 3 indicates the error number (errno) of the system call.
For distribution of another company's software, the second number in maintenance information 3 indicates the return value of the OS installation command.
(3) Checking the messages in the syslog file
Messages that are output to /NETMRDS/rdsprm/MAIN.LOGF (/var/opt/NETMDMW/rdsprm/MAIN.LOGF in the case of HP-UX) are output to the syslog file. For the storage location of the syslog file, see the manual of the applicable OS.
Messages issued during system shutdown are not output to the syslog file.
The storage format of the syslog file follows.
-
Output date and output time
Indicates the date and time when the message is output. The date and time follow the local standard time and are in the time zone of the parent process that started JP1/IT Desktop Management 2 - Agent, and results adjusted for Daylight Savings Time are stored.
-
Host name
Indicates the host name of the managing server that output the message.
-
Process ID
Indicates the process ID of the JP1/IT Desktop Management 2 - Agent server process that output the message.
-
Message
Contains text indicating the nature of the failure.
If an error occurs during file transfer, the message text that is output to the syslog file is always the same, regardless of the actual source message. Therefore, the message text output to the syslog file does not match the message code. However, message text that correctly matches the message code is output to the MAIN.LOGF file of the distribution-destination system at the file-transfer request source.
The following shows the message text that is output to the syslog file when an error occurs during file transfer.
- KDDM9xxx-*: An error occurred in the file transfer server.
-
- Legend:
-
xxx: Message code
*: Message type