HP-UX 11i v3 Installation and Update Guide, September 2010

Table A-2 Known install and update problems (continued)
Description/actionProblem
During installation, HP WBEM Services creates a user cimsrvr and a group
cimsrvr. If you are using Network Information Services (NIS), Lightweight
Directory Access Protocol (LDAP), or any other network service for managing
user and group accounts, there is a possibility that the user ID (UID) and the
group ID (GID) created for HP WBEM Services are already in use by other users.
The duplication of user and group IDs results in a change in file ownership and
can stop applications working correctly.
This issue is only applicable for HP WBEM Services A.02.07 and later versions.
What to do
For systems using LDAP or other network services, before installing HP WBEM
Services, you must manually add a local cimsrvr user and group using a unique
UID and GID. You must first determine the available reserved IDs for the group
(for example, 130) and for the user (for example, 125) ensuring that these IDs are
not in use by LDAP or other network services. Run the following command to
add the group:
/usr/sbin/groupadd -g 130 cimsrvr
After creating the group, run the following command to add the user:
/usr/sbin/useradd -u 125 -g cimsrvr -d \
/var/opt/wbem -c "WBEMServices" cimsrvr
Note: If you do not manually add the group and the user before installing HP
WBEM Services, the installation scripts add a group and user using locally
available IDs, returned by useradd(1M) and groupadd(1M), which may already be
in use on the network.
For systems using NIS, the problem is encountered when HP WBEM Services is
installed as part of a custom bundle that requires a system reboot or if NIS is
stopped for any other reason while the HP WBEM Services installation is
performed. In the former case, this is because the HP WBEM Services configure
phase (when the user and group are created) is run before NIS is up and running
after a system reboot. To avoid this problem on systems that have NIS configured,
install the HP WBEM Services upgrade on its own or as part of a custom bundle
that does not contain updates that require a system reboot.
This problem does not affect new installations where the cimsrvr user and
group are present before NIS, LDAP, or other network services are configured;
or minor upgrades of HP WBEM Services where the cimsrvr user and group
are present from an installation of HP WBEM versions earlier than version A.02.07.
User and group IDs of HP
WBEM Services conflict with
user and group IDs of NIS,
LDAP, and other network
services
When updating from the HP-UX 11i v3 March 2008 OEUR, an error might appear
in swagent.log that indicates AppDiscServer.SERVER-TOMCAT could not
be removed. In addition, swverify might fail because the files of this fileset
have been removed by the Application Discovery server (AppDiscServer)
configure script. There is no functional problem with AppDiscServer.
You will encounter this issue only if the following conditions exist:
• You are performing update-ux.
• You have unmounted file systems.
• You installed AppDiscCMS.AppDiscServer.SERVER-TOMCAT during your
installation of the HP-UX 11i v3 March 2008 OEUR.
• You are updating specifically from HP-UX 11i v3 March 2008 and have not
updated (or removed) AppDiscCMS.AppDiscServer.SERVER-TOMCAT
since your original installation.
What to do
Prior to updating, remove AppDiscServer.SERVER-TOMCAT with the following
command:
swremove -x mount_all_filesystems AppDiscServer.SERVER-TOMCAT
Updates from HP-UX 11i v3
March 2008 might result in
swagent.log error, as well as
swverify failure
Known install and update problems 79