IBM RS/6000 SP, Problem Determination Manual

Page: 239 / 316

This soft copy for use by IBM employees only.
9.4.1 Using File Collections
If f i l e c = t r u e (use
splstdata -e
to confirm) then the following sequence will start
the supfilesrv daemon on the Control Workstation.
1. /etc/rc.sp is started from /etc/inittab
2. /usr/lpp/ssp/install/bin/services_config is called from /etc/rc.sp
3. /usr/lpp/ssp/install/bin/file_config is called from services_config
4. Finally, startsrc -s supfilesrv is executed from filec_config
Note: Older versions of filec_config added an entry for supfilesrv to /etc/inittab.
To allow support for multiple Control Workstations, the supfilesrv daemon is now
under System Resource Controller (SRC) control.
root@sp21cw0 / > lssrc -s supfilesrv
Subsystem
Group PID Status
supfilesrv 14734 active
Figure 88. Output f r o m lssrc -s supfilesrv C o m m a n d
9.4.2 supper Hints and Tips
1. If you have problems with the
supper
command, check the log files in the
/var/adm/SPlogs/filec directory. Alternatively, rerun the command using the
-v
option.
2. Error messages similar to those shown in Figure 89 are most likely a result
of mismatched levels of PSSP code on the Control Workstation and the
nodes. Ensure that PSSP components are at the same level on all nodes
and the Control Workstation.
root@sp21cw0 / > supper update user.admin
Updating collection user.admin from server sp21cw0
supper: 0018-258 Update of collection user.admin failed.
supper: 0018-276 Login failed.
Figure 89. supper Error Messages When PSSP Code Is Mismatched
3. Use
lssrc -s supfilesrv
to check that the supfilesrv daemon is active on the
Control Workstation and on the boot/install servers. This daemon responds
to requests from the nodes to update collections of files.
4. Remember that
supper
is a
pull operation. That is, the command is executed
on the nodes (not on the Control Workstation) and the files are pulled from
the Control Workstation to the nodes.
5. File collections require a unique, unused user ID: supman. If this ID does not
exist, then supper will fail with the same error messages as those shown in
Figure 89. Use the log files in /var/adm/SPlogs/filec on the nodes to obtain
more detailed error messages.
Chapter 9. User and Services Management
219