Install PHCO_37620 to Avoid Core Dump in libc | After cold installation, the pwgrd(1M) daemon creates the file "/var/spool/pwgr/status" with zero size and initializes
it with status information. There is a small window between file creation
and initialization in which file size is zero. If any application
calls getpw*() or getgr*() APIs
during this window, they will dump core in libc. What To Do Install PHCO_37620 to fix this problem. For availability of
this patch, please check the HP IT Resource Center site: http://itrc.hp.com. |
Cannot Access /.secure/etc/*
Error Message | Updating from
the HP-UX 11i v2 December 2007 release to the HP-UX 11i v3 March 2008
release may cause the following error to appear in the swagent.log: cp: cannot access /.secure/etc/*: No such
file or directory What
To Do You can safely ignore this message. |
Application Discovery Agent
Does Not Correctly Trap and Format Messages | The Application Discovery agent does not correctly trap
and format messages when an unconfigure action is taken. This results
in messages that display inappropriately within columns designated
for Software Distributor (SD) within the swagent.log file. What To Do When analyzing Software Distributor messages in the swagent.log file, you can safely ignore the following
lines because they apply to Application Discovery agent and not to
Software Distributor: * Stopping the
agent daemon * Running
"unconfigure" script for product AppDiscMN * Removing WBEM provider * Removing the AmgrAgentProvider * Removing ssl directories |
| Error Message When Updating to HP-UX
11i v3 | When updating your system to
HP-UX 11i v3, you may encounter the following warning message in the /var/adm/sw/swagent.log file: ln: Warning! dld.sl.orig and dld.sl are identical What To Do You can safely ignore this message. Install patch PHSS_37493 to fix this problem. For availability of this patch, please check
the HP IT Resource Center site: http://itrc.hp.com |
Unloading device driver for
critical resource may cause next system boot to fail | If you attempt to dynamically unload an I/O
interface device driver assigned to a system critical resource, the
unload does not succeed. However, the driver is marked as unused and
it is removed from the kernel configuration for the next system boot.
For example: # kcmodule drivername=unused ERROR: Unload
of the module 'drivername' failed. - Critical Usages detected for the
module. - More details
can be found in /var/adm/cra.log. NOTE: The requested changes could not be applied to the currently
running system, for the following reasons: - The module 'drivername' cannot support the requested operation. * The requested changes have been saved, and will
take effect at next boot. What To Do Before rebooting your
system, run kcmodule -D to see what modules will
be removed at the next boot. For example: Module State Cause Notes drivername (now) loaded best loadable, unloadable (next boot) unused
If the driver controls a system critical
resource, run kconfig -H to discard all changes
pending for the next boot. For example: # kconfig -H * All changes
being held for next boot have been discarded. # kcmodule -D NOTE: There are no module state changes being
held for next boot. |
| Warning Messages on Reboot of HP-UX
11i v3 System | Upon reboot of your HP-UX
11i v3 system, the following warning messages may appear in the /etc/rc.log file: *Finish containment
subsystem configuration Output from "/sbin/rc2.d/S480sec_late_init
start": setfilexsec:
warning: Ignored the entry for file > "/opt/ids/lbin/idssysdsp": No such file or directory > setfilexsec:
warning: Ignored the entry for file "/opt/ids/lbin/idscor": No such file or directory > setfilexsec:
warning: Ignored the entry for file "/opt/ids/bin/idsagent": No such file or directory > setfilexsec:
warning: Ignored the entry for file > "/opt/ids/lbin/updaterc": No such file or directory ERROR CODE
1 > "/sbin/rc2.d/S480sec_late_init start" FAILED What To Do You can safely ignore these warning messages as these messages do
not affect the functionality of HIDS or other products installed on
the system. However, these warning messages may continue to appear
in /etc/rc.log file upon every reboot of the
system when the product is installed and then later removed. If you
want to stop receiving these warning messages, execute the following
set of commands to clear entries related to HIDS from the containment
product's configuration file ( /etc/priv-apps/all-apps ): /usr/sbin/setfilexsec -D /opt/ids/lbin/idssysdsp /usr/sbin/setfilexsec -D /opt/ids/lbin/idscor /usr/sbin/setfilexsec -D /opt/ids/bin/idsagent /usr/sbin/setfilexsec -D /opt/ids/lbin/updaterc |
| Configuring vPar with Low Base Memory
Results in System Hang or Slow Performance | Configuring a vPar with a low amount of base memory can result
in system hang or lead to slow system performance. What To Do Configure vPars with
enough base memory as per the below guidelines: If there is 1 GB to 8 GB total memory assigned to
the Virtual Partition: make sure the minimum base memory is 1/2 of
total memory. If there is 8 GB to 16 GB total memory assigned to
the Virtual Partition: make sure the minimum base memory is 4 GB. If there is over 16 GB total memory assigned to the
Virtual Partition: make sure the minimum base memory is 1/4 of the
total memory.
|
| Online Diagnostics are no Longer
Started by Default | With the HP-UX 11i
v3 March 2008 release, Online Diagnostics are no longer started by
default. Traditionally, ISEE depends on Online Diagnostics (EMS listener)
for event detection, however, if it is not started and you notice
anomalies in ISEE operation especially with regard to which events
are submitted, you must consult the ISEE Installation and
Configuration Guide. What To Do To check which version of diagnostics
is running, run the following command: sfmconfig
-w -e The preceding command switches the diagnostics
mode to "EMS". In this mode, EMS Hardware Monitors are enabled and SysFaultMgmt does not monitor any devices. If the results show that only System Fault Manager is running without
Online Diagnostics (EMS listener) on your HP-UX device, and anomalies
exist in ISEE operation especially with regard to which events are
submitted, please consult the ISEE Installation and Configuration
Guide for additional information and instructions at: www.hp.com/learn/isee |
| Use Latest Version of Ignite-UX
and Update-UX to install HP-UX patches | The
Software Manager (swm) product used with the
Ignite-UX and Update-UX tools from the HP-UX 11i v3 February 2007
OE release may fail to select or configure all HP-UX 11i v3 September
2007 patches. What To Do Use the Ignite-UX and Update-UX tools from the HP-UX 11i v3
OE September 2007 release for the correct selection and configuration
of all HP-UX 11i v3 patches. Tools from the HP-UX 11i v3 September
2007 OE release include an updated Software Manager product that correctly
handles all HP-UX 11i v3 patches. |
| Patches May Appear Unbundled when
using the HP-UX 11i v3 February 2007 version of Ignite-UX and Update-UX | If you are using the HP-UX 11i v3 February 2007 version
of either Ignite-UX or Update-UX to cold-install or update a system
with a source depot that contains HP-UX 11i v3 with September 2007
patches, some patches may appear unbundled after installation. What To Do Patches with file sets that are common to two or more patch bundles
become unbundled during selection. To work around this issue, you
can manually install the bundle wrapper after cold installing or updating
your system: swinstall -s source_depot bundle_tag . the
'.' after the bundle tag indicates to only install the wrapper. For example, the FEATURE11i and HWEnable11i bundles could have different patches with
the same file sets in the September 2007 OE media (source depot),
but a default swlist report shows only the patches
and not the bundles. After installing the HWEnable11i (bundle_tag) and FEATURE11i (bundle_tag) wrappers,
a swlist report will show these bundles, instead
of all of the patches. Note that patches associated with these bundles
were previously installed, and the problem is fixed by installing
the bundle_tag wrappers. |
| Patches May Not Install Correctly
when using the HP-UX 11i v3 February 2007 version of Ignite-UX and
Update-UX | If you are using the HP-UX 11i
v3 February 2007 version of either Ignite-UX or Update-UX to cold-install
or update a system with a source depot that contains HP-UX 11i v3
with September 2007 patches, some patches may not install correctly. What To Do The messages in the log file pertaining to the failure are logged
as 'NOTE's: NOTE: The patch fileset patch fileset,r=1.0 cannot be installed because its base fileset product fileset,|=/,r=B.11.31 is being updated in this session. Patch
fileset patch fileset,r=1.0 will be excluded. where patch, fileset, and product vary depending on which
patches are included in the source depot. One of two methods
can be used to identify this problem after the install of HP-UX 11i
v3 completes: Look for the above message in /var/adm/sw/swagent.log Execute the /usr/contrib/bin/check_patches utility. It will identify patches with missing file sets with a
message similar to: patch is missing patch fileset fileset
To work around the problem, reinstall the affected
patches. |
| Patches May Not be Configured when
using the HP-UX 11i v3 February 2007 version of Ignite-UX and Update-UX | If you are using the HP-UX 11i v3 February 2007 version
of either Ignite-UX or Update-UX to cold-install or update a system
with a source depot that contains HP-UX 11i v3 with September 2007
patches, certain patches may not be configured. What To Do The following is an
example of /var/adm/sw/swagent.log output during
the configure step when this occurs: *
Checking product and fileset dependencies. * The software "PHKL_36054.CORE2-KRN,l=/,r=1.0"
is not in the correct state (AVAILABLE, INSTALLED, or CONFIGURED).
You will need to recopy, reinstall or configure this software before
operating on software that depends on it. Then, during the swverify step, these error messages
are displayed: * The software "PHKL_36054.CORE2-KRN,l=/,r=1.0"
is not in the correct state (AVAILABLE, INSTALLED, or CONFIGURED).
You will need to recopy, reinstall or configure this software before
operating on software that depends on it. The corequisite "PHKL_36054.CORE2-KRN,l=/,r=1.0"
for fileset "PHKL_36241.CORE2-KRN,l=/,r=1.0" cannot be successfully
resolved. ERROR: The
dependencies for fileset "PHKL_36241.CORE2-KRN,l=/,r=1.0" cannot be
resolved (see previous lines). To identify
any patches that are not configured after an install, enter the following
command: swlist -l fileset -a state Look for any file sets that are not in the configured
state and manually enter the swconfig command,
for those patches that are not in the configured state. |
| Install PHCO_36356 to avoid failure
with FC card | Critical Resource Analysis (CRA)
may unexpectedly fail during Online Replacement (OLR), Online Deletion
(OLD), or dynamic unload of a Fibre Channel driver module. OLR occurs
when doing a replacement operation with either the olrad command, PCI attention button, or the Systems Management Homepage
(SMH) on systems with this OLR feature. OLD occurs when doing a delete
operation with the olrad command, or the Systems
Management Homepage (SMH) on systems with this OLD feature. A dynamic
unload of a module can occur with kcmodule, swinstall, or swremove commands. OLR, OLD, or dynamic unload of a DLKM capable Mass Storage driver,
might unexpectedly fail during Critical Resource Analysis (CRA) causing
a core dump. If the CRA fails in this way during a swinstall or swremove operation the system will automatically
reboot to complete the requested operation. If the CRA fails during
a kcmodule mod=unused operation, the unload action
will not occur until the system is manually rebooted. What To Do Install PHCO_36356 to fix this problem. For availability of the
patch, please check the HP IT Resource Center site: http://itrc.hp.com. |
HP
Service Control Manager (SCM) not supported on HP-UX 11i v3 | The HP Service Control Manager
(HP SCM) is not supported on HP-UX 11i v3. If your system is running
SCM, you must migrate to HP System Insight Manager (HP SIM) version
4.2 BEFORE updating to HP-UX 11iv3; otherwise the update may fail. What To Do Remove
HP SCM before updating to HP-UX 11iv3. If you are updating your system
to HP-UX 11i v3 and HP SCM is installed on your current system and
you do not want to run it in the future, you must remove the HP SCM
product before you update to HP-UX 11i v3. Uninstall HP
Servicecontrol Manager using the following command: swremove
–x enforce_dependencies=false ID where
ID is the product or bundle ID as shown in the following example syntax: swremove –x enforce_dependencies=false B8339BA Remove the old product sub-directories by executing
the following command: rm -fr /opt/mx /etc/opt/mx You can also remove the database for Service Control
Manager, mysql, by executing the following command: swremove
mysql You may also choose to migrate HP SCM
version 3.0 to HP SIM version 4.2 before updating to HP-UX 11iv3.
You must be running HP SCM version 3.0 to perform this update. If
you are running an earlier version you will need to update HP SCM
to version 3.0 before updating to HP SIM version 4.2. For more information on migrating from HP SCM to HP SIM version 4.2
please see the HP Systems Insight Manager 5.1 Installation
and User Guide. |
Secure
Path not supported on HP-UX 11i v3 | Secure Path is not supported on HP-UX 11i v3. If
your system is running Secure Path, upon update to HP-UX 11i v3, a
migration script will execute and perform the following actions: Uninstall the HP StorageWorks Secure Path driver for
Active-Passive disk arrays Uninstall the HP StorageWorks Secure Path driver for
Active-Active disk arrays Map the pseudo DSFs provided to LUNs by Secure Path
(for Active-Passive disk arrays) to their corresponding LUN WWN Map the virtual aliases provided to the LUNs by Secure
Path 3.0F SP2 (for Active-Active disk arrays) to their corresponding
HP-UX 11i v3 disk device special file Update the /etc/fstabwith HP-UX
11i v3 disk device special file by replacing the virtual aliases provided
by Secure Path 3.0F SP2 (Active-Active disk arrays), but the filesystems
will not be automatically mounted Update all the Secure Path virtual aliases with the
new style device special files
If the virtual aliases provided by Secure Path
3.0F SP2 (Active-Active disk arrays) are used in the /etc/fstab file, the entries are automatically replaced with the corresponding
new style dsfs. Only active-active disk arrays supported by the version
of Secure Path (active/active) installed on the system will be migrated.
For example, if Secure Path for HP-UX 3.0F is installed, EVA-GL (active/active)
LUNs cannot be migrated because EVA-GL is supported only from Secure
Path for HP-UX 3.0F SP1. What To
Do After the cold-install or update to HP-UX
11i v3 is complete, manually mount the file systems. For more information,
see the white paper called, Migrating from HP StorageWorks
Secure Path for Active-Active Disk Arrays to Native Multipathing in
HP-UX 11i v3 available at: http://docs.hp.com |
JavaOOB Installation Errors | Updating from the HP–UX 11i v2
September 2006 release to the HP–UX 11i v3 September 2007 release
may cause the following errors to appear in the console
log, dmesg.log and syslog from the Java Out-of-Box (JavaOOB) installation: ERROR: The proposed values for nfile (4097) and maxfiles_lim (4096)do
not meet t he constraint of (nfile >= (2 * maxfiles_lim)). ERROR: The stored value (4097) for the tunable
'nfile' is not valid. The system will use the default value instead. What To Do You can safely ignore this message. |
NIS+ not supported on HP-UX
11i v3 | The NIS+ product is not
supported on HP-UX 11i v3. If a system is running NIS+, you must migrate
to LDAP BEFORE updating to HP-UX 11i v3; otherwise the update may
fail.The NIS+ to LDAP-UX migration tool uses NIS+ commands and utilities
for migration. Since the NIS+ commands and utilities will not be available
on HP-UX 11iv3, the migration tools will not run on a system that
has been updated to HP-UX 11i v3. What To Do Migrate NIS+ servers and clients
to LDAP before updating to HP-UX 11i v3. |
NFS*MAN
filesets Produce swverify Errors During Install/Update or Removal | After an HP-UX 11i v3 install/update,
the swverify command may report that one or more
of the following ONCplus.NFS manpage files is
missing: /usr/share/man/man1m.Z/portmap.1m /usr/share/man/man1m.Z/umount_nfs.1 /usr/share/man/ja_JP.eucJP/man1m.Z/umount_nfs.1m /usr/share/man/ja_JP.SJIS/man1m.Z/umount_nfs.1m The hard links to the affected manpages were incorrectly
removed by the install/update process. What To Do As superuser, recreate the missing
links by executing the following commands, as needed: # cd /usr/share/man/man1m.Z # ln rpcbind.1m portmap.1m # ln
mount_nfs.1m umount_nfs.1m # cd /usr/share/man/ja_JP.eucJP/man1m.Z # ln mount_nfs.1m umount_nfs.1m # cd /usr/share/man/ja_JP.eucJP # ln mount_nfs.1m umount_nfs.1m |
Third-Party
Product Installation Scripts Fail to Launch | For some third-party product installation
scripts, dtksh is required for scripts to launch
license-acceptance dialogs for Mozilla. What To Do Either install CDE to enable the
script to run as expected, or execute /opt/mozilla/mozilla and manually accept the Mozilla license. |
Warning
Message When Performing swcopy, swlist, or swverify | If you are on an HP-UX 11i v1 system
and perform swcopy, swlist,
or swverify on a depot containing HP-UX 11i v2
or HP-UX 11i v3 software, you may encounter the following warning
message: WARNING: Ignoring duplicate information
for the keyword “dynamic_module” at line. What To Do For swlist or swverify on HP–UX
11i v1, you can safely ignore this message. For swcopy on HP–UX 11i v1, install patch PHCO_28848 (or a superseding patch) on the HP–UX 11i v1 system, then
re-run the swcopy command with "-x reinstall=true". |
Updating
to HP-UX 11i v3 from HP-UX 11iv2 with VxFS 5.0 | If VxFS 5.0 has been used to create file
systems with disk layout version 7, those disks will not be readable
by the VxFS 4.1 for HP-UX 11i v3. What To Do Make sure you copy data from your
DLV 7 file systems onto file systems created at layout version 5 or
6 before updating to HP-UX 11iv3. |
Updating to HP-UX 11i v3 from
HP-UX 11iv2 with VxFS 4.1 | If
you have created any VxFS file system with disk layout version 2 or
version 3, these file systems cannot be mounted under VxFS 4.1 on
HP-UX 11i v3. What To Do Use the vxfsconvert command to upgrade
the disk layout to version 4 before upgrading to VxFS 4.1 on HP-UX
11i v3. See the Veritas 4.1 Installation Guide for more information on VxFS 4.1. |
CPU Monopolized By evacd daemon
During Tape Archiving | The evacd daemon
can monopolize the CPU on a small vPar configured with floating/ejectable
memory. On such a system with a workload which exhausts the file cache,
the workload may run slower than expected. A backup to tape is one
such workload. What To Do You can try any of the following: Reduce the tunable
filecache_max from the default of 50 percent to 25 percent. If the
problem still occurs, reduce the tunable further. Remove
the floating/ejectable memory from the vPar using vparmodify before
starting the operation that exhausts file cache. The memory can be
added back after the operation that exhausts file cache completes. Install the patches PHKL_35899 and PHKL_35900. For information
on these patches, go to the HP IT Resource Center Web site: http://itrc.hp.com. |
Third-Party Storage | If third-party (non-HP) storage will be connected
to your HP-UX 11i v3 system, HP recommends that you contact your third-party
storage vendor to determine the compatibility of the storage with
HP-UX 11i v3. Check with your third-party storage vendor for information
about any pre-requisites and limitations with the storage on HP-UX
11i v3. |
/dev/random
or /dev/urandom Errors During Update | When updating your system to HP-UX 11i v3, you may
encounter the following error message in the /var/opt/swm/swm.log file:
*Running "/var/adm/sw/pre_update/RNG-DKRN.100".
ERROR: The /dev/random or /dev/urandom device special files may not be in use during
update-ux. Use the fuser(1M) command to identify these processes, then terminate them.
ERROR: The script "/var/adm/sw/pre_update/RNG-DKRN.100" returned a value of "1" (ERROR)
*Running "/var/adm/sw/pre_update/RNG-DKRN.100" failed with 2 errors
|
What To Do Run fuser /dev/random or fuser /dev/urandom to retrieve a list of process IDs that are using the special device
files. Use the process ID along with the ps command to determine what
processes are using the special device files. If you
find mxdtf, mxdomainmgr,
or mxinventory as part of these processes, then
run /opt/mx/bin/mxstop to stop all HP SIM activities
before updating to HP-UX 11i v3. If you find smbd as part of these processes, then run /sbin/init.d/sambastop to stop all CIFS/Samba server processes before updating to HP-UX
11i v3. If you find named as part of these processes,
then run /sbin/init.d/named stop and /usr/sbin/rndc
stop to stop all DNS/BIND server processes before updating
to HP-UX 11i v3. If you find sshd as
part of these processes, then run /sbin/init.d/secsh stop to stop all HP Secure Shell server processes before updating to
HP-UX 11i v3. |
Printable version
