IBM RS/6000 SP, Руководство по определению проблем

Страница: 240 / 316

This soft copy for use by IBM employees only.
SUP 7.24 (4.3 BSD) for file /tmp/.sf10668 at May 13 12:02:12
SUP Upgrade of user.admin at Mon May 13 12:02:12 1996
SUP Fileserver 7.12 (4.3 BSD) 27302 on sp21cw0
SUP Locked collection user.admin for exclusive access
SUP: Reason:
Unknown user supman
SUP: Improper login to supman account
SUP: Upgrade of user.admin aborted at Mon May 13 12:02:12 1996
SUP: Aborted
Figure 90. Extract f r o m /var/adm/SPlogs/filec/sup5.13.96.12.02r Log File
6. If a
supperupdate <file collection>
command seems to execute without any
errors, but the relevant files are not updated on the nodes, check the
following:
•
The supman ID must have read access to all the files in a file collection.
•
Check that the /var/sysman/sup/<file collection>/scan file is correct
and up-to-date. The
scan file should contain the same file names as
those in the /var/sysman/sup/<file collection>/list file.
•
Ensure that the date and time on all nodes and the Control Workstation
are correct.
•
Make sure that the files are not listed in the /var/sysman/sup/<file
collection>/refuse file. This file lists all the files which were excluded
during the update process. The /var/sysman/sup/refuse file (if it exists)
contains a list of files to be excluded from all the file collections.
•
Verify the contents of the /etc/ssp/server_name file. This tells supper
from which host it should update files.
7.
supper
uses the Ethernet network for its communication. Ensure that TCP/IP
is configured correctly.
8. Remember that boot/install servers use
supperupdate
to request the latest
files from the Control Workstation, and that the nodes use supperupdate to
request the changes from the boot/install servers. Each node executes a
supperupdate every hour (at 10 minutes after the hour) from the root crontab.
This means that a change in a master file on the Control Workstation could
take 2 hours to propagate to every node (assuming that boot/install servers
are being used).
9. Error messages similar to those shown in Figure 91 on page 221 are a result
of a PTF packaging error in PTF 10. There are two missing files in PSSP 2.1
PTF Set 10. They are:
/usr/lpp/ssp/filec/etc/supfilesrv
/usr/lpp/ssp/bin/acctjob
If you are applying PTF Set 10 on a node that has
ssp.sysman at level 2.1.0.4
(PTF U441612 ) or earlier, then you must apply PTF Set 8 before installing
PTF Set 10. Installing PTF Set 11, which is a full PTF, will also fix the
problem. If you are applying PTF Set 10 on a node that has
ssp.sysman at
level 2.1.0.5 (PTF U441818), then you should not experience any problems.
220
SP PD Guide