HP-UX 11i v3 Installation and Update Guide, March 2012

Known install and update problems
Table 15 (page 75) describes problems currently known to occur while installing and/or updating
to HP-UX 11i v3.
Table 15 Known install and update problems
Description/actionProblem
When using swinstall to install or update the SATADVD-00 driver, the system
might hang if the /usr/lbin/utild daemon is active. This issue is known to
occur only on rx2800 i2 systems, but might also occur elsewhere.
System might hang if /usr/
lbin/utild is running during
installation or update of
SATADVD-00 driver
What to do
Before updating the SATADVD-00 driver with swinstall, stop /usr/lbin/
utild, then restart it after installing or updating the driver. For further information,
including instructions for halting utild, see SATADVD-00 (satadvd) B.11.31.1203
Mass Storage Driver Release Notes at http://www.hp.com/go/general-io-docs.
If your system is running low on memory and you have a huge number of database
record entries, then upgrade of RAIDSA-PROVIDER, FC-PROVIDER, SAS-PROVIDER,
Upgrade of RAIDSA-PROVIDER,
FC-PROVIDER, SAS-PROVIDER, and
WBEMP-Storage might fail and WBEMP-Storage might fail. You will see a version of the following error in
swagent.log. (The example below is for FC-PROVIDER.)
NOTE: Adding FC Provider monitoring job.
NOTE: Creating the FC log database
ERROR: FC log database setup failed. Aborting install.
ERROR: The "configure" script for "WBEMP-FCP.FCP-NIP-RUN"
failed(exit code "1"). The script location was
"/var/tmp/BAA015943/catalog/WBEMP-FCP/FCP-NIP-RUN/configure".
* This script had errors and the execution of this
fileset cannot proceed until the problem is fixed.
Check the above output from the script for further
details.
What to do
For information on a fix for this problem, see QXCR1001188297 at the HP Support
Center (http://hp.com/go/hpsc). Click Search support knowledge, then select
Search by document ID for your search mode. Enter "ttr_na-SSB_1001188297”
in the box.
When HP SMH is installed, the user hpsmh and group hpsmh are automatically
added to the /etc/passwd file. If you are using LDAP or any other network service
User and group IDs of HP SMH
conflicts with user and group IDs
of LDAP and other network
services
for managing user and group accounts, there is a possibility that the user ID (UID)
and the group ID (GID) of hpsmh are already in use by LDAP-users. The duplication
of user and group IDs results in changes in file ownership. This problem occurs in
HP-UX 11i v3 on Integrity systems.
What to do
As a workaround, before installing HP SMH, you must manually add a local hpsmh
user and group using unique UID and GID. First, determine the available reserved
IDs for the group (say, 130) and the user (say, 125). Ensure these IDs are not in
use by LDAP or other network services. Then add the group using the following
command:
/usr/sbin/groupadd -g 130 hpsmh
After adding the group, add the user using the following command:
/usr/sbin/useradd -u 125 -g hpsmh -d \
/var/opt/hpsmh -c "System Management Homepage" hpsmh
Note: If you do not manually add the group and user before installing HP SMH,
during installation HP SMH creates the group and user using locally available IDs,
which may already be in use on the network.
During installation, HP WBEM Services creates a user cimsrvr and a group
cimsrvr. If you are using Network Information Services (NIS), Lightweight Directory
User and group IDs of HP WBEM
Services conflict with user and
Known install and update problems 75