9.2.1 Failures in the client services
- Organization of this subsection
(1) Failures during program product setup
Phenomena |
Method of investigation |
Causes and corrective actions |
---|---|---|
The end status of the package status file of JP1/IT Desktop Management 2 - Manager is AF |
The distributed program product is not installed properly. This is recorded as an error job in both the package status file and in the job management file. In this case, investigate the cause of the failure using the following procedure.
|
If the version of the prerequisite program product is incorrect, re-distribute just the applicable version of the program product. The program product that resulted in the error does not need to be re-distributed. |
(2) Installation failure during system stop
Phenomena |
Method of investigation |
Causes and corrective actions |
---|---|---|
Package installation failure |
Because power is shut off immediately after this failure, the failure cannot be checked at that time. At the next startup of the system, a message appears showing up to ten packages for which installation failed. The number of these packages is also displayed. See the following log files for failure information.
|
Resolve the problem and retry. |
Program product installation failure |
The package that failed installation cannot be used during the next system startup, because this package might prevent the daemon process from being started. See the following log files for failure information.
|
Perform one of the following according to the failure information.
|
(3) Failures in the recovery facility
Phenomena |
Method of investigation |
Causes and corrective actions |
---|---|---|
Recovery failed |
The execution results of recovery, and the storage status of backup, are notified to the job management file and package status file of the managing server as the recovery status. For details on the recovery status, see Appendix B. Status Codes. |
The procedure for retrying recovery is as follows:
If it is not possible to retry recovery from the managing server, retry recovery or check the storage status of backup using the following procedure:
|
Insufficient free space in the backup directory |
N/A |
Use one of the following methods to delete unnecessary backup data to acquire free disk space.
|
- Legend:
-
N/A: Not applicable