Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX 11i Version 1 Installation and Update Guide: HP Servers and Workstations > Appendix B Known Problems and Troubleshooting

Update Known Problems

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

DMI/SCR Become Unbundled After Update

After updating to the September 2003 release (or later) of HP-UX 11i v1, you may encounter a warning after running the swlist command indicating that DMI/SCR (B6816AA) was unbundled during the update:

#
# Product(s) not contained in a Bundle:
#

DMI                  B.11.11.30    Desktop Management Interface for HP-UX
SCR                   B.11.11.30      System Configuration Repository

How Do You Know If This Affects You?

You will encounter this warning if DMI/SCR (B6816AA) was installed prior to updating.

What To Do

DMI/SCR will continue to work after the update. If you plan to continue using DMI/SCR, HP recommends that you download the latest version of DMI from http://software.hp.com. Starting with the September 2003 release, DMI will no longer be shipped as part of the operating environments. Instead, it will be available and supported as a web-only product.

Unsupported Upgrade of ServiceControl Manager Causes SCR Error During Update

While updating a 10.20 system to either the Foundation, Enterprise or Mission Critical operating environment, you may encounter the following error messages in swagent.log appearing to affect SCR:

ERROR:   [300076] Cannot delete the definition for product "SCR" from
the target "/". The product is not empty, it still contains
filesets.

These error messages are caused by an unsupported upgrade of ServiceControl Manager 3.0 from a version of SCM earlier than version 2.5. SCM 3.0 only supports upgrades from version 2.5 or higher.

Because this is an unsupported upgrade path, no changes will be made to either SCR or ServiceControl Manager.

How Do You Know If This Affects You?

If you are updating a 10.20 system to either the Foundation, Enterprise, or Mission Critical operating environment, and you have a version of ServiceControl Manager earlier than version 2.5, you will encounter these errors.

What To Do

To resolve this problem:

  1. Use the swremove(1M) command to remove the existing ServiceControl Manager bundle from the system

  2. With your HP-UX 11i v1 media, use the swinstall(1M) command to install the latest version of ServiceControl Manager (B8339BA) on your system.

Boot Error Messages Appear After Updating from HP-UX 11.0 (with MirrorDisk/UX Installed) to HP-UX 11i v1 TCOE

If you are updating to HP-UX 11i v1 TCOE from HP-UX 11.0 with MirrorDisk/UX installed, the following error message may appear during the boot process:

/sbin/bcheckrc:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" has been successfully changed.
vgsync: Error, "vgsync" is not a valid LVM command.
vxfs fsck: sanity check: root file system OK (mounted read/write)
Checking hfs file systems
/sbin/fsclean: /dev/vg00/lvol1 (mounted) ok
HFS file systems are OK, not running fsck
Checking vxfs file systems
/dev/vg00/lvol8 :
vxfs fsck: sanity check: /dev/vg00/lvol8 OK
/dev/vg00/lvol3 :
vxfs fsck: sanity check: root file system OK (mounted read/write)
/dev/vg00/lvol4 :
vxfs fsck: sanity check: /dev/vg00/lvol4 OK
/dev/vg00/lvol5 :
vxfs fsck: sanity check: /dev/vg00/lvol5 OK
/dev/vg00/lvol6 :
vxfs fsck: sanity check: /dev/vg00/lvol6 OK
/dev/vg00/lvol7 :
vxfs fsck: sanity check: /dev/vg00/lvol7 OK

Cleaning /etc/ptmp...

How Do You Know If This Affects You?

This error message may appear during reboot after the updating from HP-UX 11.0 with MirrorDisk/UX installed to HP-UX 11i v1 TCOE.

MirrorDisk/UX for HP-UX 11i is not included with TCOE. As a result, when the HP-UX 11.0 version of MirrorDisk/UX is removed from the system, the commands associated with HP MirrorDisk/UX are not properly deleted. This causes the LVM startup script to believe that HP MirrorDisk/UX is installed on the system.

What To Do

To resolve this problem you must purchase and install MirrorDisk/UX for HP-UX 11i v1. See Chapter 8 “Updating Applications” for more information about installing applications after install or updating your system.

ApacheStrong Becomes Unbundled After Update

After updating to the June 2003 release of HP-UX 11i v1, you may encounter a warning after running the swlist command, indicating that ApacheStrong was unbundled during the update:

# 
# Product(s) not contained in a Bundle:
# ApacheStrong 1.3.26.06.09 HP Apache-based Web Server with Strong (128bit) Encryption

How Do You Know If This Affects You?

If you previously installed ApacheStrong 1.3.x ™prior to updating to this release, you may encounter this warning.

What To Do

You can safely disregard this warning. The HP-UX Web Server Suite and ApacheStrong 1.3.x™ will function properly.

parmgr.1m Errors on MCOE Update from HP-UX 11.0 to HP-UX 11i v1

After updating from HP-UX 11.0 to HP-UX 11i v1 MCOE, the following mtime, stime, and permission errors may appear in your swverify.log file:

* [140112] Checking files for fileset
"OS-Core.CORE-JPN-S-MAN,l=/,r=B.11.11".
ERROR: [40258] File "/usr/share/man/ja_JP.SJIS/man1m.Z/parmgr.1m"
         should have mode "444" but the actual mode is "555".
ERROR: [40263] File "/usr/share/man/ja_JP.SJIS/man1m.Z/parmgr.1m"
         should have mtime "974188800" but the actual mtime is
         "1032497544".
ERROR: [40265] File "/usr/share/man/ja_JP.SJIS/man1m.Z/parmgr.1m"
         should have size "3244" bytes but the actual size is "3472"
         bytes.
ERROR: [140113] Fileset "OS-Core.CORE-JPN-S-MAN,l=/,r=B.11.11" had
          file errors.

What To Do

You can disregard these errors. The parmgr(1M) manpage will work correctly.

HP Apache May Hang On Reboot after System Update from Golden System Image (GSI) Depot

When upgrading from a GSI-installed system containing an OE with HP Apache 2.0, some systems may hang while attempting to shutdown the Apache Web Server. The problem is caused by an obsolete PID from the httpd daemon being copied from the GSI Golden Image Depot to the client system.

How Do You Know If This Affects You?

You may be affected if you are upgrading from a GSI HP-UX 11.0 Depot containing HP Apache 2.0 to HP-UX 11i v1.

What To Do

GSI Depot (Server): 

  1. Shut down your HP Apache Web Server before creating the GSI Depot by typing

    /opt/hpapache2/bin/apachectl stop

  2. Verify that the following file has been deleted:

    /opt/hpapache2/logs/httpd.pid

Client System: Delete the following file (if present) after installing the GSI Depot and before an update install:

/opt/hpapache2/logs/httpd.pid

MLIB 8.3 Produces Warning During Update

When updating from MLIB 8.1 (or earlier) to MLIB 8.3 the following warning may appear in the /var/adm/sw/swagent.log:

WARNING: Incomplete definition for the product "MLIBPROD",
beginning at line 44452. The following attributes are not
defined:

filesets the filesets contained in the product

What To Do

You can disregard this warning message; there is no problem with the installation

X11MotifDevKit Produces Incompatible Error After Upgrade from HP-UX 10.20

After updating from HP-UX 10.20 to HP-UX 11i v1, the following errors may appear in your swverify.log:

ERROR:   [140167] The product "X11MotifDevKit,l=/,r=B.10.20.02" is
          not compatible with this system's architecture or
          operating system.

* [140061] Configured X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02

---

[140155] The corequisite "X11.X11R6-SHLIBS,r=B.10.*" for
fileset "X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02" cannot be
successfully resolved.

ERROR: [140151] The dependencies for fileset
"X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02" cannot be
          resolved (see previous lines).

---

* [140112] Checking files for fileset "X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02".
WARNING: [40257] Directory "/" should have mode "555" but the
          actual mode is "755".

WARNING: [40261] Directory "/" should have group,gid "other,1" but
          the actual group,gid is "root,0".WARNING: [40259] Directory "/usr/newconfig" should have owner,uid
          "root,0" but the actual owner,uid is "bin,2".

WARNING: [40261] Directory "/usr/newconfig" should have group,gid
          "other,1" but the actual group,gid is "bin,2".WARNING: [140114] Fileset "X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02"
          had file warnings.

---

ERROR: [140043] Verify failed
X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02

The problem is caused by configuration differences in the X11MotifDevKit between HP-UX 10.20 and HP-UP 11i.

How Do You Know if this Affects You?

You may experience this problem if you are updating from HP-UX 10.20 to HP-UX 11i v1, and have not updated your system with the latest HP-UX 10.20 patch bundles.

What To Do

After you have updated your system to HP-UX 11i v1, you need to re-install the HP-UX 11i v1 Developer’s Kit located in the HP-UX 11i v1 Application Software media kit (CD/DVD).

  • For servers, install B3394BA

  • For workstations, install B3392BA

For more information about installing applications, Chapter 8 “Updating Applications”

OpenView SNMP Agent Produces Error with Upgrade to HP-UX 11i v1

Due to a preinstall script error, customers upgrading to HP-UX 11i v1 may see the following error:

* [140184] Installing fileset "OVSNMPAgent.MASTER,r=B.11.11" (54 of 1293).
* [20255] Running "postinstall" script for fileset "OVSNMPAgent.MASTER".
* [20255] Running "preinstall" script for fileset "OVSNMPAgent.SUBAGT-HPUNIX".

kill: 616: The specified process does not exist.
NOTE: You may need to restart SNMP agents.

The error is caused by the kill command trying to end a process that is already terminated. When the OVSNMPAgent.MASTER fileset is installed, it invokes a kill command to terminate any existing SNMP agents. The next fileset, OVSNMPAgent.SUBAGT-HPUNIX, also attempts to terminate any SNMP Agent processes.

How Do You Know if this Affects You

If you are migrating from HP-UX 10.20 or 11.0 to HP-UX 11i v1, you may receive this error message during the installation of the OpenView SNMP bundle.

What To Do

You can safely ignore this message.

“Initialize of the ITO Control Agent failed” Error During update-ux Session

Beginning in June 2002, the ITO-SE single system event management component was removed from the GlancePlus Pak 2000 product.

How Do You Know If This Affects You?

If you are updating from HP-UX 10.20 or 11.0 and you have a version of GlancePlus Pak 2000 released prior to June 2002, update-ux will try to remove the ITO-SE component prior to updating to a newer GlancePlus Pak. You may encounter the following error when update-ux removes the file sets belonging to the ITO-SE component:

* Beginning the Unconfigure Execution Phase.
* Filesets: 3
* Files: 163
* Kbytes: 15427
* Running remove setup command /usr/lbin/sw/remove_setup.
Error opcctla (Control Agent)(14791) : Initialize of the ITO
Control Agent failed. (OpC30-1036)

Can't lookup servers: Communications failure (dce / rpc). (OpC20-108)
Can't lookup servers: Communications failure (dce / rpc). (OpC20-108)
Stopping all ITO Agent processes... (OpC30-1192)
/usr/bin/ps: couldn't get console device alias
/usr/bin/ps: not enough memory for hash table

What To Do

No action required. The ITOAgent unconfigure script generates the error prior to the file sets being removed.

Firmware Patches Should Not Be Included Cold-Install or Update Session

If you are migrating from either HP-UX 10.20 or HP-UX 11.0, HP strongly recommends you do not include firmware patches while running a cold-install or update session.

How Do You Know If This Affects You?

The following systems are affected:

  • A-Class

  • L-Class

  • N-Class

Many of the HP-UX 11i v1 firmware patches rely on HP-UX 11i v1 tools and system calls. During the cold-install or update process, your system is still running either the 10.20 or 11.0 kernel. The firmware installation fails because of system call differences between the HP-UX 11i v1 kernel and older kernel versions.

What To Do:

HP strongly recommends that you install any firmware patches after you have completed the cold-install or update process and your system is running HP-UX 11i v1. Specific HP-UX 11i v1 firmware patches are available at the following website:

http://itresourcecenter.hp.com

Analyzing Log Files

To help identify a problem with running update-ux, remember that errors are logged in two separate log files:

  • update-ux errors:
    /var/adm/sw/update-ux.log
    and /var/adm/sw/swagent.log

  • swinstall errors:
    /var/adm/sw/swinstall.log
    and /var/adm/sw/swagent.log

SD commands log errors to /var/adm/sw/swagent.log, plus their own log. Simply checking more than one log file may reveal the problem you are troubleshooting.

Update Fails on J2250 Workstation With SCSI Floppy Drive

See “Kernel Build Fails on 64-bit Install”.

Update Fails if nstrpty Kernel Parameter Set as a Formula

If the value of the nstrpty kernel parameter is specified as a formula (for example, nstrpty (NPTY*2)), then updating to 11i will fail with this error:

/var/tmp/BAAa10554/catalog/Streams-TIO/STRTIO-KRN/postinstall[82]:  (NPTY):
The specified number is not valid for this command.
ERROR: The “postinstall” script for “Streams-TIO.STRTIO-KRN” failed (exit code “1”).
The script location was “/var/tmp/BAAa10554/catalog/Streams-TIO/STRTIO-KRN/postinstall”.

To prevent this, convert the value of nstrpty to a number.

How Do You Know If This Affects You?

To check the kernel parameters, run SAM and select: Kernel Configuration -> Configurable Parameters

What To Do

If the nstrpty kernel parameter is specified as a formula, then before you update, use SAM (Kernel Configuration -> Configurable Parameters) to change the formula to a numeric value. You do not need to rebuild the kernel or reboot the system.

Kernel Build Failure

When updating a workstation running on a HP-UX 10.20 32-bit OS to 11i 32-bit OS/OE, the update may fail if a USB driver is configured on the system. This will not occur when updating to 11i 64-bit OS.

If this occurs, update-ux displays this message on the console before quitting:

Loading the kernel...
/usr/ccs/bin/ld: Unsatisfied symbols:
wsio_get_service (code)
Stop...
ERROR: The kernel build failed...

What To Do

Remove the USB drivers and repeat the update:

  1. As root, edit /stand/system:

    vi /stand/system

  2. Find and delete all USB drivers: usbd, hsd, hub, hid

  3. Save the system file and quit the editor.

  4. Continue the update by entering:

    update-ux -kernel_build

X.25 Cards Not Supported on Some Workstations

J3525A and J3526A PCI cards are not supported under HP-UX 11i v1 on these workstations:

  • B1000

  • B2000

  • C3X00

  • J5000

  • J7000

If either of these cards is installed on a workstation listed above, the system will crash during the upgrade. If the workstation is already running 11i, it will crash when you try to add the card. These cards are supported on older B-, C- and J-Class workstations, as well as on L-[123]000, N- and A-Class servers and Superdome servers.

How Do You Know If This Affects You?

To see if these cards are installed in your system, enter:

ioscan -kf | egrep '(10140078)|(1133b921)'

If one or both cards are installed, ioscan will output one or more rows containing the numbers 10140078 or 1133b921.

What To Do

Be sure to remove those cards before updating to 11i.

HP A3740A Fibre Channel PCI Tachyon Not Supported

The HP A3740A Fibre Channel PCI Tachyon adapter is not supported on HP-UX 11i v1. Before you install HP-UX 11i v1, please replace any A3740A PCI adapters in your system with A5158A PCI 1 Gb Tachyon TL adapters or A6795A PCI 2 Gb Tachlite adapters. Then connect any Fibre Channel Mass Storage devices previously connected to A3740A adapters to either of the adapters.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.