|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback
us-support.external.hp.com)Date: Sun Oct 07 2001 - 09:46:28 CDT
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 700 11.X patch digest
Created: Sun Oct 7 3:05:32 PDT 2001
Table of Contents:
Document ID Title
--------------- -----------
PHSS_24432 s700_800 11.00 OV OB3.00 patch - CC packet
PHNE_25385 s700_800 11.00 Streams Pty cumulative patch
PHKL_25361 s700_800 11.11 vm preemption point, pdc
PHKL_25050 s700_800 11.04 (VVOS) Fixes for short filenames & hang,HFS
PHCO_25063 s700_800 11.04 (VVOS) DLKM configuration tools cumulative
PHSS_25208 s700_800 11.04 VirtualVault 4.0 libproxy fix
PHSS_23690 s700_800 11.00 OV OB3.10 patch - CS packet
PHKL_24743 s700_800 11.11 VM/JFS deadlock; mmap performance
PHSS_25176 s700_800 11.00-11 Fortran90 from B.11.01.40 to B.11.01.43
PHSS_25090 s700_800 11.00 OV ITO6.0X NT Agent Patch A.06.08
PHKL_25375 s700_800 11.11 VM stale icache
PHKL_25212 s700_800 11.11 vm preemption point, mlock/async_io
PHKL_25210 s700_800 11.00 Probe,IDDS,PM,VM,PA-8700,asyncio,T600
PHCO_25393 s700_800 11.11 pax(1) cumulative patch
PHCO_25342 s700_800 11.00 Kernel configuration commands patch
PHSS_25215 s700_800 11.04 VirtualVault 4.0 SpeedCard driver upgrade
PHSS_25139 s700_800 11.11 CDE Base SEP2001 Periodic Patch
PHSS_25138 s700_800 11.00 CDE Runtime SEP2001 Periodic Patch
PHSS_25092 s700_800 11.11 X Font Server SEP2001 Periodic Patch
PHSS_25091 s700_800 11.00 X Font Server SEP2001 Periodic Patch
PHSS_24934 s700_800 11.11 Korean TrueType font patch
PHSS_24933 s700_800 11.00 Korean TrueType font patch
PHSS_24932 s700_800 11.11 Japanese TrueType font patch
PHSS_24931 s700_800 11.00 Japanese TrueType fonts patch
PHNE_25083 s700_800 11.11 Streams Pty cumulative patch
PHKL_25362 s700_800 11.11 shm_lock scaling
PHKL_25352 s700_800 11.00 dump, PSW, PA-8700, printf cumulative fix
PHKL_25351 s700_800 11.11 Socket audit enhancement and acl(audit) fix
PHKL_25209 s700_800 11.11 Psets Enablement, SCHED_NOAGE
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_24432
Date Loaded: 20011005
Title: s700_800 11.00 OV OB3.00 patch - CC packet
Patch Name: PHSS_24432
Patch Description: s700_800 11.00 OV OB3.00 patch - CC packet
Creation Date: 01/08/20
Post Date: 01/10/05
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OmniBackII A.03.00
Filesets:
OMNIBACK-II.OMNI-HPUX-P,fr=A.03.00,fa=HP-UX_B.11.00_32/64,v=HP
OMNIBACK-II.OMNI-OTHUX-P,fr=A.03.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_24432
Symptoms:
PHSS_24432:
Id = JAGad01472
Exit code of omnimm is incorrect.
Id = JAGad30352
"EMC Support" tab is not available in
"Backup Specification - Options" GUI.
Id = NSMex03419
After importing 2.55 tapes, some SAP files cannot be
restored.
Id = NSMex03587, NSMex03475, NSMex03808
Restore GUI does not display SAP objects, if two
SAP instances with the same name are backed up on
different hosts.
Id = NSMex03658
Exit code of omniminit is incorrect.
Id = NSMex03806
Omnir cannot be started with "-r -l" or "-r -p"
options.
Id = NSMex03833
The options under Edit button are not accessible even
if user has the appropriate rights.
PHSS_22037:
Id = NSMex03503
Users with only "Start Backup" privilege can delete
datalists.
Id = NSMex03511
"Send external" method always executes external script
on Cell Manager system.
PHSS_21332:
Id = NSMbb23888, NSMbb33864
Restore of the SAP backup is not possible if there are
two or more equal Oracle SID's on different systems.
Id = NSMbb23993
MoM GUI fails to start with the message:
"Can not access the Manager of Managers server".
Id = NSMbb34111
Windows NT registry restore from incremental backup
fails.
Id = NSMbb34280
MoM server does not save backup templates on client
cell server.
Id = NSMex02374
Dragging host from ITO Node bank and dropping it in
Backup nodes results in an error:
"Backups will not start because there are no Cell
Manager licenses available".
Id = NSMex02387
At the end of restore object stays as "Pending" instead
of "Completed".
Id = NSMex02539, HSLco14279
MoM GUI reports duplicate medium barcodes.
Id = NSMex02757
Object size displayed in the Restore GUI is incorrect.
Id = NSMex02837, NSMex02840, NSMex02841, NSMex02916,
NSMex02447, NSMex02393
Various scheduler problems.
Id = NSMex02954, HSLco14573
Selecting "..." in "To" field of Oracle 7
Restore GUI shows all the session for all
Oracle databases.
Id = NSMex02989
Monitor GUI core dumps when printing all
sessions.
Id = NSMex02991
GUI hangs when initializing media.
Id = NSMex02504
omnib command periodically fails if it is started
with Maestro scheduler.
Id = NSMex02530
When configuring a SAP barlist the message about
missing EMC licenses pops up even when there is no
EMC system in the cell.
Id = NSMex02424
"All Media Available" in Media Management GUI does
not work correctly.
Id = NSMex02716
Parameter file is not loaded in xomnibackup.
Id = NSMex02773
After upgrade from 2.55 to 3.00, objects with capital
hostnames are not accessible with omnir and omnidb
commands, even if the option "noexpand" is used.
PHSS_18696:
ID = NSMex02288
Backups start automatically, although the user
excludes specific days in the backup scheduler.
Id = NSMex02429
The xomnirestore GUI coredumps while configuring
Oracle restore.
Id = NSMex02339
The xomnimom GUI crashes if any combined license
is installed on the cell manager system.
Id = NSMex02295
"omnimm" command incorrectly parses slot range.
Id = NSMex02181
The GUI licensing info shows wrong information when
combined licenses are installed.
Id = NSMbb24161
Exit status of 'omnir' command is 0 even if the
user has aborted it.
PHSS_17302:
Id = NSMex01981, NSMbb22439
Oracle restore GUI gives no usefull info when '...'
button is clicked for the 'To' field.
Id = NSMbb21778
Connecting to session from CLI fails, if session has
been started after 1.1.2000, and short session ID is
used, e.g.: 'omniabort -sess 4'.
Id = HSLco11626
Resizing of some dialogs does not work on systems with
Japanese locale.
Id = NSMex01872
xomniadmin coredumps during the installation.
Id = NSMex01933
Parallel restore doesn't work, using omnir command.
Id = NSMbb22764
Error message with ITO integration:
"Bad Catalog access for message #117 in set 49 !"
Id = NSMex02191, NSMbb23538
Starting 'point in time' restore of Oracle db results
in EBU failing with the message:
'EBU-530: Date is not in expected format: MM/DD/YYYY'
Id = NSMex02296
Restore with EMC/SRDF TimeFinder integration fails with
the message
[Major] From: SYMAhost.domain.com "" Time: <time>
[223:327] SYMA-R2 Could not mount filesystem
/dev/vg01 to /mountpoint.
[Major] From: SYMAhost.domainc.com "" Time: <time>
[223:363] SYMA-R2 Could not prepare mirror disks of obj
/mountpoint
for backup.
([22] Invalid argument)
[Major] From: SYMAhost.domain.com "" Time: <time>
[223:327] SYMA-R2 Could not mount filesystem
/dev/vg01 to /mountpoint.
[Major] From: SYMAhost.domainc.com "" Time: <time>
[223:363] SYMA-R2 Could not prepare mirror disks of obj
/mountpoint
for backup.
([22] Invalid argument)
[Major] From: SYMAhost.domain.com "" Time: <time>
[223:327] SYMA-R2 Could not mount filesystem
/dev/vg01 to /mountpoint.
[Major] From: SYMAhost.domainc.com "" Time: <time>
[223:363] SYMA-R2 Could not prepare mirror disks of obj
/mountpoint
for backup.
([22] Invalid argument)
Defect Description:
PHSS_24432:
Id = JAGad01472
Exit code of omnimm is reported as successful when
the operation itself is not successful.
Resolution:
Omnimm returns correct exit codes.
Id = JAGad30352
"EMC Support" tab is not available in
"Backup Specification - Options" GUI, unless
the "-emc" option is manually added to the cell_info
file for the Cell Manager.
Resolution:
Xomnibackup correctly parses cell_info file and
recognizes EMC clients properly.
Id = NSMex03419
In pre-3.0 versions file names were stored on the tape
in the original upper and lower case letters. Version
OBII 3.0 and later store file names always in lower
case. At restore time it is assumed that all file names
on tape are in lower case. This introduces problems
when, for example, a tape from 2.55 system is imported
into 3.10 system and a restore is run from such tape.
Resolution:
When comparing names of files which were backed
up on the tape, all file names are now converted to
lower case, so this doesn't have any effect on new
backups (they are already in lower case) but enables
restores from pre-3.0 backups.
Id = NSMex03587, NSMex03475, NSMex03808
Restore GUI does not show all SAP objects for hosts if
two SAP instances are backed up with the same name on
two different hosts.
Resolution:
Xomnirestore has been improved to shows all object
correctly.
Id = NSMex03658
Exit code 0 is returned when the medium initialization
fails with error:
"This medium can be initialized only with force
option specified".
Resolution:
Exit code of omniinit for failed operation
is redefined.
Id = NSMex03806
Incorrect parsing of appname and bararg arguments.
Resolution:
Omnir has been modified.
Id = NSMex03833
User rights are not properly interpreted.
Resolution:
User right permissions are properly interpreted.
PHSS_22037:
Id = NSMex03503
User rights are not properly checked.
Resolution:
User rights checking is properly improved.
Id = NSMex03511
Execution of external script can not be prevented.
Resolution:
Omnirpt is changed so that the execution of "Send
external" method can be controlled by adding a line
ExternalScriptMode=<number>
in Global Options file, where <number> means:
- 0, no checking is performed
- 1, script can be executed only in bin directory
- 2, executing of external scripts is not allowed.
PHSS_21332:
Id = NSMbb23888, NSMbb33864
Restore GUI shows only one Oracle SID when there are
two or more equal Oracle SID's on different systems.
Resolution:
Fix is implemented in xomnirestore.
Id = NSMbb23993
MoM GUI can not be started if a user does not have
Admin Access rights.
Resolution:
Any user with OmniBack II Access rights can start MoM
GUI. The limitations are that "Backup All" and
"Installation Administration (Install, Import, Export)"
can be started only by root:sys on MoM server.
Part of the SSPUX300_079.
Id = NSMbb34111
Windows NT registry restore from incremental backup
fails.
Resolution:
Windows NT registry from an incremetal backup is
successfully restored.
Id = NSMbb34280
Backup template created in MoM environment is always
saved on the host from which the GUI was started.
Resolution:
Backup templates are now saved on the specified host.
Id = NSMex02374
Starting xomnibackup with the "datalist" option reports
the following error:
"Backups will not start because there are no Cell
Manager licenses available".
Resolution:
Fix is implemented in xomnibackup.
Id = NSMex02387
If "List from media" restore is executed, the status
of the object at the end of restore is "Pending"
instead of "Completed".
Resolution:
Fix is implemented in Restore GUI.
Id = NSMex02539, HSLco14279
Changing media location for at least two media results
in duplicated media barcodes.
Resolution:
Fix is implemented in MoM GUI.
Id = NSMex02757
Restore GUI reports incorrect size of the object,
if the objects are bigger than 4Gb.
Resolution:
Object size calculation improved.
Id = NSMex02837, NSMex02840, NSMex02841, NSMex02916,
NSMex02447, NSMex02393
Various scheduler problems.
Resolution:
Scheduler fixed.
Part of the SSPUX300_081.
Id = NSMex02954, HSLco14573
Selecting "..." in "To" field of Oracle 7
Restore GUI shows all the session for all
Oracle databases.
Resolution:
Fix is implemented in Restore GUI.
Id = NSMex02989
Monitor GUI core dumps when printing all sessions
if there is a backup host is more than 80
characters long.
Resolution:
Hostname can be up to 120 characters long.
Id = NSMex02991
When initializing media is done from Cell server
console, GUI hangs right after the confirmation
in the dialog box is clicked if the Actions menu
is opened.
Resolution:
Fix is implemented in xomnimm.
Id = NSMex02504
omnib command does not handle Interrupt signal
correctly.
Resolution:
If command is not started from tty, interrupt
signal is ignored.
Part of the SSPUX300_080.
Id = NSMex02530
After installing permanent licenses any attempt to
save a SAP barlist fails with a message:
"The Symmetrix or Time Finder Integration backup will
not start because the EMC SRDF Time Finder extension
license is not available"
even if there is no EMC system in the cell.
Resolution:
GUI shows this message only when EMC Integration is
installed and there are no licenses for this
integration.
Part of the SSPUX300_082.
Id = NSMex02424
"All Media Available" in Media Management GUI does not
display the right values.
Resolution:
Fix is implemented in xomnimm.
Part of the SSPUX300_087.
Id = NSMex02716
If EMC/SAP configuration is used, xomnibackup does not
read SAP parameter file correctly.
Resolution:
Fix is implemented in xomnibackup.
Part of the SSPUX300_087.
Id = NSMex02773
OmniBack II 3.00 internally uses lower case hostnames,
and when running a backup of a upper case hostname,
object names are converted to lower case in the OB2
database. Since this was not a case in OmniBack II 2.55
the objects that contain upper case letters and are
backed up with 2.55 are not recognized and the error:
"Cannot browse from root. Please specify starting
point"
is reported.
Resolution:
Fix is implemented in omnir and omnidb commands.
Part of the SSPUX300_090.
PHSS_18696:
Id = NSMex02288
Dates on which the backups are supposed to be excluded
(not started) are incorrectly written to the backup
specification. This causes backup to be started even
the user explicitly selected days when a backup should
not be started.
Resolution:
Scheduling info written correctly into backup
specification schedule file.
Id = NSMex02429
The xomnirestore GUI can coredump during the
configuration of Oracle restore, if OmniBack II
database contains a lot of Oracle objects.
Resolution:
GUI now correctly handles big amount of Oracle objects.
ID = NSMex02339
When combined licenses are installed on the license
server in a centralized licensing environment, the
xomnimom GUI crashes when user clicks on any cell
manager.
Part numbers of such licenses are:
B6951AA (UNIX Cell Manager + 1 UNIX Single Drive)
B6952AA (UNIX Cell Manager + 1 UNIX Multi Drive Server)
Part of SSPUX300_069
Resolution:
Combined license handling is improved.
NSMex02295
Incorrect parsing of slot range causes the library to
eject/enter wrong media.
Part of SSPUX300_065
Resolution:
Slot parsing fixed.
NSMex02181
The xomniadmin GUI doesn't show combined licenses
correctly. Part numbers of such licenses are:
B6951AA (UNIX Cell Manager + 1 UNIX Single Drive)
B6952AA (UNIX Cell Manager + 1 UNIX Multi Drive Server)
Part of SSPUX300_050
Resolution:
The xomniadmin GUI now shows detailed list of licenses
available.
Id = NSMbb24161
Return status of the omnir command is not updated if
user aborts the execution. Exit value is 0, and this
gives the impression that the command completed
successfuly although it has been interrupted.
Part of SSPUX300_074
Resolution:
Return code is set correctly before exiting.
PHSS_17302:
Id = NSMex01981 and NSMbb22439
An error in the database query results in an empty
output when clicking the '...' button for the 'To'
field in the Oracle Object Restore GUI.
Part of SSPUX300_023.
Resolution:
GUI now passes correct parameters to db query.
Id = NSMbb21778
Any command using short session ID will fail
because of ivalid parsing, if session has been
started after January 1st 2000. If long session
ID is used, the error does not appear.
Resolution:
Session parsing now recognizes short session
ID for next centuries too.
Id = HSLco11626
Resizing of popup dialogs does not work correctly on
systems with Japanese locale.
Part of SSPUX300_004.
Resolution:
The GUI is modified to handle Japanese
locales correctly.
Id = NSMex01872
xomniadmin coredumps if one of the hosts is a NT
MS Wolfpack Cluster Server.
Part of SSPUX300_008.
Resolution:
Parsing of cell_info file is improved.
Id = NSMex01933
"omnir" did not parse options correctly, so that
parallel restore didn't work.
Part of SSPUX300_020.
Resolution::
Fixed options parsing.
Id = NSMbb22764
Within a c-code switch{} statement, a missing
break statement caused execution of additional
code which resulted in displaying this superflous
message.
Resolution:
A break in the switch statement prevents
execution of the superflous code.
Id = NSMex02191, NSMbb23538
The date to which oracle db should be restored to is
sent to EBU in the format 'MM/DD/YY hh:mm:ss', but EBU
expects it the format 'MM/DD/YYYY hh:mm:ss'.
Resolution:
GUI now sends the date in correct format.
Id = NSMex02296
If the EMC restore is started using the command omnir,
the session will fail as described in Symptoms. The
reason is in the omnir command sending misspelled
parameters to RSM.
Resolution:
Correct startup option sent to rsm by omnir.
SR:
H555005554 B554000550 8606132323 H555003728 H555003665
8606161034 B554000716 5003457317 5003459081 8606107308
5003463505 5003455857 1653303180 1653287615 B700029256
1653297853
Patch Files:
OMNIBACK-II.OMNI-HPUX-P,fr=A.03.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux/A.03.00/packet.Z
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.00/
packet.Z
OMNIBACK-II.OMNI-OTHUX-P,fr=A.03.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/ibm/rs6000/aix/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.00/packet.Z
/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.00/
packet.Z
/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.00/
packet.Z
what(1) Output:
OMNIBACK-II.OMNI-HPUX-P,fr=A.03.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.00/
packet.Z:
None
OMNIBACK-II.OMNI-OTHUX-P,fr=A.03.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/ibm/rs6000/aix/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.00/
packet.Z:
None
/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.00/
packet.Z:
None
cksum(1) Output:
OMNIBACK-II.OMNI-HPUX-P,fr=A.03.00,fa=HP-UX_B.11.00_32/64,
v=HP:
2287649809 10157339 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux/A.03.00/packet.Z
2701850050 10354868 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-10/A.03.00/packet.Z
4118643446 12936719 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-1020/A.03.00/packet.Z
OMNIBACK-II.OMNI-OTHUX-P,fr=A.03.00,fa=HP-UX_B.11.00_32/64,
v=HP:
3343976239 3456913 /opt/omni/databases/vendor/cc/ibm/rs6000/
aix-42/A.03.00/packet.Z
940270868 3362457 /opt/omni/databases/vendor/cc/ibm/rs6000/
aix/A.03.00/packet.Z
2603126240 4261677 /opt/omni/databases/vendor/cc/dec/alpha/
osf1-4/A.03.00/packet.Z
4087630626 5162215 /opt/omni/databases/vendor/cc/sgi/mips/
irix-62/A.03.00/packet.Z
1177164897 4254339 /opt/omni/databases/vendor/cc/sgi/mips/
irix/A.03.00/packet.Z
339962317 3363447 /opt/omni/databases/vendor/cc/sco/i386/
sco_sv/A.03.00/packet.Z
2679982976 4203807 /opt/omni/databases/vendor/cc/siemens/
r400/sinix/A.03.00/packet.Z
2397323895 3864913 /opt/omni/databases/vendor/cc/sun/sparc/
solaris/A.03.00/packet.Z
1069802535 6273497 /opt/omni/databases/vendor/cc/sun/sparc/
sunos/A.03.00/packet.Z
3584579088 3959591 /opt/omni/databases/vendor/cc/sequent/
i386/dynix/A.03.00/packet.Z
1654616029 3509959 /opt/omni/databases/vendor/cc/ncr/i386/
mp-ras/A.03.00/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_22037 PHSS_21332 PHSS_18696 PHSS_17302
Equivalent Patches:
PHSS_24431:
s700: 10.00 10.01 10.10 10.20
s800: 10.00 10.01 10.10 10.20
Patch Package Size: 77320 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_24432
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_24432.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_24432. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_24432.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_24432.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_24432.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_24432.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_24432:
NOTE!
Patch has to be installed on the Installation Server host.
The Cell Console packets must be redistributed
to the Cell Manager system and client systems
afterwards to get the fixes into effect.
In order to receive proper messages you must install also
the OMNIBACK II A.03.00 CORE packet patch.
The latest CORE patch is currently PHSS_20843/PHSS_20844,
but may be superseded by a newer version in the future.
Patch includes the following Site Specific Patches:
SSPUX300_004
SSPUX300_008
SSPUX300_020
SSPUX300_023
SSPUX300_050
SSPUX300_065
SSPUX300_069
SSPUX300_074
SSPUX300_079
SSPUX300_080
SSPUX300_081
SSPUX300_082
SSPUX300_087
SSPUX300_090
-----End of Document ID: PHSS_24432------------------------------------------
Document ID: PHNE_25385
Date Loaded: 20011004
Title: s700_800 11.00 Streams Pty cumulative patch
Patch Name: PHNE_25385
Patch Description: s700_800 11.00 Streams Pty cumulative patch
Creation Date: 01/09/26
Post Date: 01/10/04
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
Streams-TIO.STRTIO2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
Streams-TIO.STRTIO2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Streams-TIO.STRTIO-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_25385: PANIC
PHNE_24100: PANIC
PHNE_22086: MEMORY_LEAK
PHNE_21433: PANIC HANG
PHNE_19616: MEMORY_LEAK
PHNE_18878: PANIC
Category Tags:
defect_repair enhancement general_release critical panic
halts_system memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_25385
Symptoms:
PHNE_25385:
System panics in ldtty_intimeout: the message is
panic in ldtty_intimeout+0x18
PHNE_24100:
System panics in ldtty_intimeout: the message is
panic in ldtty_intimeout+0x18 : an ldtty timer deferenced a
closed queue
PHNE_22086:
System hangs due to memory starvation when using pckt
module.
PHNE_21433:
1) System hangs during shutdown.
2) System panic when an application is transfering large
amount of data under raw mode.
PHNE_20094:
When 32bit user application on 64bit platform uses getmsg()
on Streams Pty, a 64bit data structure is returned instead
of expected 32bit data structure.
PHNE_19616:
1) Streams pty causes memory leak when end-user does not
follow the operation procedure of master/slave pair.
2) Streams pty in UP Emulation mode leads worse performance
to applicatons based on Streams Pty, such as rlogind.
3) System winds-down to what appears to be a complete
system hang.
PHNE_18878:
Streams pty will panic under race conditions between
master and slave drivers on MP systems.
PHNE_14976:
Streams pty did not work in UTF8 environment. This patch is
an enhancement that provides UTF8 support
PHNE_16155:
System panic type 15 in pckt_rsrv in the Streams pty code.
Defect Description:
PHNE_25385:
Race window between ldtty_close and ldtty_intimeout
PHNE_24100:
A timer was left active after a close.
PHNE_22086:
Memory leak when processing M_FLUSHR message in pckt module.
Resolution:
Free the undeallocated message used in processing M_FLUSHR
message in pckt module.
PHNE_21433:
1) Application may hang in ldtty close if there is some
data inside ldtty module to drain. Shutdown thread is
blocked and hangs when it tries to access the driver
under ldtty module.
2) Race condition in ldtty module causes ldtty_sendraw
to reuse a message block that has already been freed.
Resolution:
1) Inside ldtty close routine, we add a call to service
routine to drain outstanding data.
2) When a possible race condition is detected, ldtty_sendraw
makes sure that it won't use the old message buffer which
may have already been freed.
PHNE_20094:
When transparent ioctl is called, a M_IOCTL message is
forwarded to Streams Pty master side. The first message
block of M_IOCTL message, which contains iocblk data
structure, is of different size on 32 and 64bit platform.
Resolution:
Add a register function in ptm driver. At STH, when a 32bit
application is detected on 64bit platform, the registered
function is called to convert 64bit iocblk data structure
to 32bit in M_IOCTL msg.
PHNE_19616:
1) When the slave driver is opened before the master driver,
a preallocated message block (eof_msg_mp) is not freed
before return error code.
2) UP Emulation mode of Streams Pty Driver binds Streams
Pty based applications to monarch processor and causes
performance problem.
3) High priority messages are queued in PCKT module by
mistake. When this message are not processed in time,
the module begins consuming huge memory.
Resolution:
1) Check existence of master driver as soon as we try to
open slave driver. Allocate eof_msg_mp only if master is
already opened.
2) Streams Pty module now runs at QueuePair sync level,
using shared/exclusive lock to protect critical data
structure shared among master/slave drivers.
3) Process high priority msg in pckt_rput() function.
PHNE_18878:
The panic was caused by the master and slave drivers running
on different processors and trying to access the same
data structure.
Resolution:
The fix was to mutually exclude the master and slave drivers
so that they cannot run at the same time and thus avoid the
race condition.
PHNE_14976:
This patch is an enhancement for UTF8 support for STREAMS
pty line discipline.
PHNE_16155:
The type 15 panic was caused the b_rptr pointer in the
mblk being overwritten by a bad value when M_FLUSH was
being processed and the system ran out of memory.
SR:
8606207776 4701402487 5003429548 5003448738 5003427641
8606103315 8606128396 8606134024 8606152552 8606187489
Patch Files:
Streams-TIO.STRTIO2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libstrtio.a
Streams-TIO.STRTIO2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libstrtio.a
Streams-TIO.STRTIO-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/conf/strtio/pty.h
/usr/include/sys/eucioctl.h
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(strtio.o)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(strtio.o)
what(1) Output:
Streams-TIO.STRTIO2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libstrtio.a:
PATCH_11.00: pty.o 1.6.118.4 00/03/29 PHNE_21433
PATCH_11.00: pckt.o 1.4.118.5 00/07/25 PHNE_22086
PATCH_11.00: ldtty_euc.o 1.5.118.2 98/05/08 PHNE_1
4976
ldtty.c $Date: 2001/09/26 13:36:18 $Revision: r11ros
/10 PATCH_11.00 (PHNE_25385)
Streams-TIO.STRTIO2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libstrtio.a:
PATCH_11.00: pty.o 1.6.118.4 00/03/29 PHNE_21433
PATCH_11.00: pckt.o 1.4.118.5 00/07/25 PHNE_22086
PATCH_11.00: ldtty_euc.o 1.5.118.2 98/05/08 PHNE_1
4976
ldtty.c $Date: 2001/09/26 13:36:18 $Revision: r11ros
/10 PATCH_11.00 (PHNE_25385)
Streams-TIO.STRTIO-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/conf/strtio/pty.h:
None
/usr/include/sys/eucioctl.h:
eucioctl.h 1.1 8/31/90
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(strtio.o):
None
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(strtio.o):
None
cksum(1) Output:
Streams-TIO.STRTIO2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
2259497368 90956 /usr/conf/lib/libstrtio.a
Streams-TIO.STRTIO2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
4103956710 195422 /usr/conf/lib/libstrtio.a
Streams-TIO.STRTIO-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
1608656746 15146 /usr/conf/strtio/pty.h
3341160391 2931 /usr/include/sys/eucioctl.h
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
1147625056 86052 /usr/conf/lib/libhp-ux.a(strtio.o)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
3295844886 105712 /usr/conf/lib/libhp-ux.a(strtio.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_16155 PHNE_14976 PHNE_18878 PHNE_19616 PHNE_20094 PHNE_21433
PHNE_22086 PHNE_24100
Equivalent Patches: None
Patch Package Size: 530 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHNE_25385
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_25385.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_25385. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHNE_25385.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_25385.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_25385.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_25385.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_25385------------------------------------------
Document ID: PHKL_25361
Date Loaded: 20011004
Title: s700_800 11.11 vm preemption point, pdc
Patch Name: PHKL_25361
Patch Description: s700_800 11.11 vm preemption point, pdc
Creation Date: 01/10/02
Post Date: 01/10/04
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_25361: PANIC
The panic is caused by a Service Guard TOC.
Category Tags:
defect_repair enhancement general_release critical panic
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25361
Symptoms:
PHKL_25361:
( SR:8606194618 CR:JAGad63826 )
On K-Class and slower systems, Service Guard may TOC the
system when a process that uses more than a gigabyte of
memory exits. The stack trace of the TOC may look similar
to the following:
pdc_call+0x174
hversion_pdc_call+0xa4
diag2_ioctl+0x170c
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x1e4
syscall+0x394
syscallinit+0x54c
or...
pdc_call+0x198
pa_generic_psm_pdc_rtc+0x34
psi_rtc+0xb4
checkclock+0x24
invoke_callouts_for_self+0xc0
sw_service+0xb0
mp_ext_interrupt+0x150
ihandler+0x904
splnopreempt+0x8
idle+0x504
swidle+0x20
PHKL_23946:
( SR:8606128017 CR:JAGac78818 )
Time critical functions, such as real-time
heartbeat process threads, may timeout. For
example, ServiceGuard may unexpectedly failover and
other appliations may suddently show reduced
response time when a large database is being
initialized, or when there is significant system
memory pressure.
This problem will most likely be seen on systems
with one or two processors.
Defect Description:
PHKL_25361:
( SR:8606194618 CR:JAGad63826 )
The problem is caused by an exiting process flooding the
bus with cache flush instructions. This in turn may cause
processes executing firmware code to wait until the
exiting process is finished before continuing. If the
Service Guard process is scheduled behind the process
executing the firmware code, the Service Guard process may
not have the chance to run for many seconds, causing it to
TOC the system when it does eventually run.
Resolution:
The exiting process now does its cache flushing less
aggressively and allows processes executing firmware code
to run at the same time. If such processes are allowed to
run, the Service Guard process scheduled after those
processes will be able to maintain contact with the other
Service Guard nodes in the cluster and it will not TOC the
system.
PHKL_23946:
( SR:8606128017 CR:JAGac78818 )
Time critical process threads will not be scheduled
to run until there is an available processor.
There are instances in the kernel where a process
thread may not be scheduled to run even when it is
the highest priority process thread. This occurs
when another process thread is executing on a
processor and must complete a time consuming task
before releasing the processor. There are several
such places in the kernel; this patch addresses one
specific kernel path.
When the system is under memory pressure, the pager
addresses this pressure by freeing a specified
number of pages. The pager will run until the quota
of free pages is met. Similarly, applications
needing to mlock or plock large amounts of memory
will cause mlock/plock to execute until the entire
request has been satisfied.
No other process threads can be scheduled on the
processors executing these threads until the work
is completed. The amount of work performed along
these kernel paths is proportional to the amount of
memory involved (being mlocked, plocked, or paged)
and thus impacts the delay time of waiting process
threads.
Resolution:
This patch enables kernel preemption along a kernel
path shared by the pager, mlock and plock: If a
process thread has been executing within the kernel
for over a specified period of time, the kernel
will preempt this thread and schedule a higher
priority thread to run. The preempted thread will
be placed back on the run queue to resume where it
left off in the kernel once rescheduled.
The scheduler dictates the kernel execution time
allotted to a single process and the policies
governing which process priorities may preempt the
current process.
This enhancement may not necessarily improve
performance or response time for all processes as
the pager or mlocking process thread may not be
executing along these preemptible paths.
SR:
8606128017 8606194618
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvm.a(vm_vfd.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvm.a(vm_vfd.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvm.a(vm_vfd.o):
vm_vfd.c $Date: 2001/09/24 11:29:20 $Revision: r11.1
1/4 PATCH_11.11 (PHKL_25361)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvm.a(vm_vfd.o):
vm_vfd.c $Date: 2001/09/24 11:29:20 $Revision: r11.1
1/4 PATCH_11.11 (PHKL_25361)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
4252360496 16076 /usr/conf/lib/libvm.a(vm_vfd.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
2401883915 38952 /usr/conf/lib/libvm.a(vm_vfd.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_23946
Equivalent Patches:
PHKL_25188:
s700: 11.00
s800: 11.00
Patch Package Size: 80 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_25361
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_25361.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_25361. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_25361.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_25361.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_25361.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
There are three patches providing similar kernel
preemption enhancements: PHKL_23908, PHKL_23944,
PHKL_23946. Each of these may be useful in
preventing a time critical process thread time-out.
However, these patches, installed either
individually or collectively, may not necessarily
improve performance or response time for all
processes as the process threads causing the delay
may not be executing along these preemptible paths.
Each of these patches is independent of the others;
they may be installed separately or in any
combination, and in any order. Each provides
kernel preemption for a specific long running
kernel path.
-----End of Document ID: PHKL_25361------------------------------------------
Document ID: PHKL_25050
Date Loaded: 20011004
Title: s700_800 11.04 (VVOS) Fixes for short filenames & hang,HFS
Patch Name: PHKL_25050
Patch Description: s700_800 11.04 (VVOS) Fixes for short filenames & hang,HFS
Creation Date: 01/09/14
Post Date: 01/10/04
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_25050: HANG
Based on HP-UX Patch PHKL_24117: HANG
PHKL_23014: PANIC
Based on HP-UX Patch PHKL_18798: PANIC
Category Tags:
defect_repair general_release critical panic halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25050
Symptoms:
PHKL_25050:
Ported HP-UX patch PHKL_24117 to VVOS
Based on HP-UX patch PHKL_24117:
( SR: 8606195337 Chart: JAGad64541 )
A hang can occur in HFS due to a deadlock between two
threads operating in the same directory. Following are
possible stack traces of the threads in deadlock:
Trace of thread 1
-----------------
real_sleep+0x234
_sleep+0x14
dvp_sleep+0x58
use_dev_dvp+0x90
ufs_inactive+0
vn_rele+0x1e8
dnlc_rm+0x90
dnlc_purge1+0xec
ieget+0x30c
in_get+0x34
iget+0x14
dirlook_loop+0x3ac
dirlook+0xc4
sdo_lookup+0x64
ufs_lookup+0x24
locallookuppn+0x864
ufs_lookup+0x24
locallookuppn+0x864
lookuppn+0xdc
lookupname+0x30
vn_open+0x5c
copen+0xc8
open+0x20
syscall+0x75c
$syscallrtn+0x0
Trace of thread 2
----------------
_swtch+0x138
real_sleep+0x234
_sleep_one+0x14
ilock+0x80
direnter+0xa8
ufs_rename+0xec
vn_rename+0x234
rename+0x28
syscall+0x75c
$syscallrtn+0x0
PHKL_23014:
Ported HP-UX patch PHKL_18798 to VVOS
Based on HP-UX patch PHKL_18798:
SR: 4701403725 DTS: JAGaa40424
Getting Data Page Fault when moving a subdirectory
to another sub-directory.
stack trace:
trap type 15, pcsq.pcoq = 0.179d08, isr.ior = 0.c
savestate ptr = 0x7ffe73b8, savestate return ptr = 0x179d0c
panic: (display==0xb800, flags==0x0) Data page fault
q4> trace event 0
stack trace for event 0
crash event was a panic
panic+0x10 report_trap_or_int_and_panic+0xe8 trap+0xa48
$call_trap+0x20 dircheckpath+0x368 direnter+0x3c0
ufs_rename+0xec rfs_rename+0x270 rfs_dispatch+0x464
svc_getreqset+0x1f4 svc_run+0x128 nfs_svc+0x18c
syscall+0x1a4
Defect Description:
PHKL_25050:
Ported HP-UX patch PHKL_24117 to VVOS
Based on HP-UX patch PHKL_24117:
( SR: 8606195337 Chart: JAGad64541 )
The thread deadlock results when two threads perform the
following actions:
The first thread is in open() and has locked the directory
inode in dirlook_loop(). Then it calls dnlc_purge1()
because there are no inodes on the inode free list which
subsequently causes the first thread to sleep waiting to
lock the device vnode.
The second thread is doing a mv of a file in the same
directory as the first thread and is in a rename() system
call. It locks the device vnode in ufs_rename() and
proceeds to sleep waiting for the directory inode
held by the first thread.
Resolution:
Avoid calling dnlc_purge1() in the open() path by verifying
the status of inode freelist as soon as we lock the
directory inode. If the free list is empty, purge and
recover inodes at this point. This will avoid calling
dnlc_purge1() further down the open() path.
PHKL_23014:
Ported HP-UX patch PHKL_18798 to VVOS
Based on HP-UX patch PHKL_18798:
SR: 4701403725 DTS: JAGaa40424
The problem will only occur on HFS filesystems using short
filenames. Instead of using the short filename pointer, the
code was incorrectly using the long file name pointer which
at this point had not yet been properly initialized.
Dereferencing this uninitialized pointer caused a data
page fault.
Resolution:
Treat the long and short filenames differently.
SR:
1653182501 4701334839 4701403725 8606195337
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libufs.a(ufs_dir.o)
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libufs.a(ufs_dir.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libufs.a(ufs_dir.o):
$Source: kern/ufs/ufs_dir.c, hpuxsysufs, vvos_rose,
rose0242 $ $Date: 01/09/18 11:37:09 $ $Revis
ion: 1.33.1.6 PATCH_11.04 (PHKL_25050) $
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libufs.a(ufs_dir.o):
$Source: kern/ufs/ufs_dir.c, hpuxsysufs, vvos_rose,
rose0242 $ $Date: 01/09/18 11:37:09 $ $Revis
ion: 1.33.1.6 PATCH_11.04 (PHKL_25050) $
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
596856682 21992 /usr/conf/lib/libufs.a(ufs_dir.o)
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
4121214457 44056 /usr/conf/lib/libufs.a(ufs_dir.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_23014
Equivalent Patches:
PHKL_24117:
s700: 11.00
s800: 11.00
Patch Package Size: 90 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_25050
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_25050.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_25050. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHKL_25050.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_25050.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_25050.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_25050.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_25050------------------------------------------
Document ID: PHCO_25063
Date Loaded: 20011004
Title: s700_800 11.04 (VVOS) DLKM configuration tools cumulative
Patch Name: PHCO_25063
Patch Description: s700_800 11.04 (VVOS) DLKM configuration tools cumulative
Creation Date: 01/09/24
Post Date: 01/10/04
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_25063: PANIC
Based on HP-UX Patch PHCO_22899: PANIC
Category Tags:
defect_repair general_release critical panic
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_25063
Symptoms:
PHCO_25063:
Repackage HP-UX patch PHCO_22899 for VVOS.
Based on HP-UX patch PHCO_22899:
( SR:8606170324 CR:JAGad39588 )
DLKM developer's system may panic if 16-byte data alignment
is crucial (such as in locks) in a DLKM. End-user customers
and system administrators will never see this problem.
Developers will encounter this problem only if the module is
using non-default alignment. We are releasing this patch
specifically for DLKM driver developers.
( SR:8606157299 CR:JAGad26631 )
This is an obscure problem that a customer will not
encounter. The problem is that a 32-bit DLKM module
converted from SOM to ELF will end up with corrupted
debugging information. So developers of kernel debugger
tools may encounter this problem when developing for support
of DLKM for 32-bit systems. To get this far, the developer
needs to hex edit the ELF file and change a byte or two.
This is ABSOLUTELY NOT CUSTOMER VISIBLE. It is being
released to satisfy a development partner.
PHCO_19498:
Repackage base HP-UX patch PHCO_18184 for VVOS.
Based on HP-UX patch PHCO_18184:
som2elf exits with code 8 during config of a
module built with -g
Some 32-bit DLKM modules, when converted
from SOM object file format to ELF, may exit
with "*** Error code 8" during
the "config" process.
A second problem is that some DLKM modules compiled with
debugging information cannot be loaded.
Som2elf was also creating incorrect debugging information
in the .rela.debug_gntt and .rela.debug_lntt sections.
Based on HP-UX patch PHCO_17441:
Some 32-bit DLKM modules, when converted from SOM
object file format to ELF, may cause a system panic
when the module is loaded.
Some 32-bit DLKM modules, when converted from SOM
object file format to ELF, may have a corrupted
unwind table in the ELF object file.
Based on HP-UX patch PHCO_14664:
Some large modules fail to load with the following
error message:
"Overrun of module DLT or long branch stub table
for module."
Defect Description:
PHCO_25063:
Repackage HP-UX patch PHCO_22899 to VVOS.
Based on HP-UX patch PHCO_22899:
( SR:8606170324 CR:JAGad39588 )
Alignment specified for data in a SOM object file is not
honored by som2elf during the conversion to ELF64. This was
noticed by using #pragma align 16
to specify 16-byte alignment for lock_t in a 32-bit driver.
Som2elf converted it with an 8-byte alignment, and the code
panicked when the locking code detected the incorrect
alignment.
Resolution:
The solution is to track the specified alignment in each SOM
data subspace and use the largest value.
( SR:8606157299 CR:JAGad26631 )
32-bit SOM debugging information is not transferred properly
to the ELF64 object by som2elf during conversion.
Resolution:
Fixed by adjusting the copying of debugging information from
the SOM file.
PHCO_19498:
Repackage base HP-UX patch PHCO_18184 to VVOS.
Based on HP-UX patch PHCO_18184:
Three problems are fixed:
Some 32-bit DLKM modules, when converted from SOM
object file format to ELF, may exit with
"*** Error code 8" during
the "config" process. Som2elf aborts while
"processing/translating" the debugging information
from the SOM object file format to the ELF
object file format. Since the module was compiled
with the -g,
debugging information is generated in the SOM object
(for later use by debuggers).
A second problem is that some DLKM modules compiled with
debugging information cannot be loaded.
The module has symbol tables with related debugging
information in the tables. When these tables were
converted from SOM format to
ELF format, the ELF sections are incorrect.
The loader fails when checking these invalid sections
in the symbol tables.
The third problem is that
Som2elf was also creating incorrect debugging information
in the .rela.debug_gntt and .rela.debug_lntt sections.
Resolution:
For problem one the codes were changed to create
debugging contents and relocation information
contents at the same number.
For the second problem a call to the function that
modifies the symbol table was inserted.
For the third problem the length of the relocation
contents was incorrect and has been changed to calculate
the correct length.
Based on HP-UX patch PHCO_17441:
Some 32-bit DLKM modules may cause a system panic
when the module is loaded. The following
conditions only apply to 32-bit SOM relocatable
object files that are converted to the ELF object
format with the following conditions:
1) the module has read-only data of double word in
the SOM relocatable object file format OR
2) The SOM relocatable object file format has more
than 255 subspaces.
The unwind table of an ELF module, that was converted
from SOM to ELF, may be incorrect. This leads to
problems when trying to use some tools on the module.
Resolution:
The alignment of read-only data of double word and
the handling of subspaces was corrected.
The addresses in the unwind section of the ELF module
was fixed to be monotonically increasing with no
overlaps.
Based on HP-UX patch PHCO_14664:
Some large modules fail to load because the Long
Branch Stubs table overflows, corrupting kernel
memory.
SR:
8606170324 8606157299 4701422394 4701413849
Patch Files:
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/sbin/kmchsnm
/usr/sbin/kmsecgen
/usr/sbin/som2elf
what(1) Output:
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/sbin/kmchsnm:
$Revision: 82.13.1.1 $
PATCH_11_00: kmchsnm.o 99/04/14
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/sbin/kmsecgen:
$Revision: 82.15.1.1 $
PATCH_11_00: kmsecgen.o 99/04/14
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/sbin/som2elf:
None
cksum(1) Output:
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
2025494416 28672 /usr/sbin/kmchsnm
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
884312865 24576 /usr/sbin/kmsecgen
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
1183426929 98304 /usr/sbin/som2elf
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHKL_19142
s800: 11.04: PHKL_19142
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_19498
Equivalent Patches:
PHCO_22899:
s700: 11.00
s800: 11.00
Patch Package Size: 170 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_25063
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_25063.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_25063. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHCO_25063.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_25063.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_25063.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_25063.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_25063------------------------------------------
Document ID: PHSS_25208
Date Loaded: 20011003
Title: s700_800 11.04 VirtualVault 4.0 libproxy fix
Patch Name: PHSS_25208
Patch Description: s700_800 11.04 VirtualVault 4.0 libproxy fix
Creation Date: 01/09/16
Post Date: 01/10/03
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
VirtualVault A.04.00
Filesets:
VaultNES.NES-VAULT,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP
VaultTS.VV-CORE-CMN,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25208
Symptoms:
PHSS_25208:
1) libproxy.so fails to record GET HTTP status and length
i.e, access.log shows that GET HTTP status and length
are not recorded.
2) Web browser requests going through VirtualVault return
HTTP 400 error code.
PHSS_24836:
Problems proxying cookies with a combination of
both lower and upper case characters.
PHSS_23526:
Problems proxying HTTP 1.1 connection headers
PHSS_22296:
This patch addresses the following problems
1) The NSAPI plugin versions of the TGA and the java
servlet proxy demonstrate high CPU utilization
under certain conditions.
2) The predefined Server Application Function
"get-client-cert" in a server's obj.conf file
allows client certificates to be passed from
the iPlanet Web Server to back-end applications
for further processing. Certain back-end
applications incorrectly interpret the line feed
characters that are embedded in the certificate
to mean "the end of an HTTP header field".
3) iPlanet Server has memory leak.
4) If a customer is running a CGI script that
continuously sends information every other second,
there may be a long delay before he gets the
response back from the script
PHSS_21259:
The TGA doesn't respond properly after executing a
nonexistent CGI.
PHSS_20733:
1) The TGA configuration did not work for chrooted CGIs
properly.
2) The NSAPI was not supporting CGI redirect with URL
greater than 244 characters in length.
Defect Description:
PHSS_25208:
1) libproxy fails to record the correct content-length
and response-status fields in the outside server
Resolution:
Modify libproxy to correctly record the content-length
and response-status fields in the outside server
access logs
2) Garbled http request-headers are not correctly parsed
by libproxy before sending them to the inside servers
Resolution:
Modify libproxy to correctly parse the garbled incoming
request headers and send them across to inside servers.
PHSS_24836:
Cookies that are passed through the customer's proxy
(on iPlanet 4.1 sp5) are returned to the browser altered,
i.e., missing cookie name, date field truncation, and
other miscellaneous changes to the cookie. The problem
exists only when there are uppercase characters in the
cookie string.
Resolution:
The TGA has been modified so that the characters
contained within a browser cookie are not changed
to lowercase letters.
PHSS_23526:
Some HTTP application servers do not properly handle
"connection" headers in association with HTTP/1.1.
Since the proxy allows these connection headers through,
they can cause errors for the application servers.
Also, the proxy does not send a "connection: close"
HTTP header to prevent persistent connections.
Resolution:
The proxy has been modified to provide the ability
to automatically downgrade HTTP requests from HTTP/1.1
to HTTP/1.0.
The proxy has also been modified so that it always
sends a "connection: close" HTTP header.
PHSS_22296:
This patch addresses the following 4 problems:
1)The NSAPI plugin versions of the TGA and the java
servlet proxy demonstrate high CPU utilization
under certain conditions.
Resolution:
The TGA and Java servlet proxies are being re-released
to remove these conditions.
2) Some applications incorrectly interpret HTTP header
fields with embedded line feeds (a LF, as opposed
to the standard header field-ending CRLF
combination). The iPlanet Web Server correctly
encodes a client certificate in the auth-cert
portion of the request with embedded linefeeds,
but downstream applications may interpret the
resulting header as a series of improperly
constructed request headers.
Resolution:
Since multiple applications may make this mistake,
the iWS libproxy module is an acceptable location to
remove the embedded linefeeds from the client
certificate header, and removal of the linefeeds does
not compromise header or certificate integrity.
3) iPlanet Server has memory leak.
Resolution:
Free up allocated memory.
4) Some CGI programs are not working properly.
Resolution:
NSAPI now take care of small trunk of data.
PHSS_21259:
If user tries to execute a cgi program that doesn't exist,
the server responds with 404 Not Found as it should. After
that the server starts responding "500 Server Error" to a
lot of existing cgi requests.
The server error log:
: for host .... trying to GET /cgi-bin/cgi, vvtga_log
reports: ERROR: setup_connection():
Failed to transfer execution message to slave TGA daemon on
/tmp/tga.1979
If user configures an invalid cgi in tgad.conf (there is no
cgi with that name in the real cgi directory), user never
sees the problem.
Resolution:
The TGA is being re-released to respond to this problem.
PHSS_20733:
1) The TGA configuration did not work under chrooted CGIs
properly.
The chroot directive in tgad.conf file is not working.
we get an error message from tgad saying that it can't
execute the program.
Refer to SR 8606125743 for more detail.
The tgad.log from the working machine:
LEVEL = 3 DATE = Wed Dec 15 10:42:48 1999
AUDIT : Program entry used: */c
Environment entry used: cgi
Mapped pathname: /cgi/cgi
Message: Executing cgi program '/cgi/c'.
And from the other:
LEVEL = 3 DATE = Wed Dec 15 18:59:30 1999
AUDIT : Program entry used: */c
Environment entry used: cgi
Mapped pathname: /cgi/cgi
Message: Could not execute /cgi/cgi
2) A NES NSAPI function did not support a URL with more
than 244 characters for 302 redirects.
Resolution:
1) The TGA configuration interface now supports chrooted
CGIs properly. The TGA daemon performs the access check
after the chroot call.
2) The NES NSAPI function parameters were modified to allow
CGI redirects with URLS greater than 244 characters in
length.
SR:
8606217540 8606213876 8606183510 8606155741 8606157837
8606123993 8606125743 8606131390 8606160635 8606160608
Patch Files:
VaultNES.NES-VAULT,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultTS/lib/libproxy.so
/opt/vaultTS/lib/libvvtga.so
VaultTS.VV-CORE-CMN,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP:
/tcb/lib/tgad
/opt/vaultTS/lib/libvv.sl
what(1) Output:
VaultNES.NES-VAULT,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultTS/lib/libproxy.so:
$Source: proxy.c, vaultNES, vaultNES_4.0 $ $Date: 01
/10/02 07:31:32 $ $Revision: 1.8.1.18 PATCH_
11.04 (PHSS_25208) $
VaultNES.NES-VAULT,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultTS/lib/libvvtga.so:
(#)98 1.28.1.20 src/gateway/cgi2/nsapi/tgansapi.c
, vaultNES, vaultNES_4.0 08/06/01 08:45:25 V
VOS 11.04 PHSS_24836
97 1.14.1.2 src/gateway/cgi2/nsapi/env.c, vaultNES
, vaultNES_4.0 09/01/99 11:23:32
95 1.13 src/gateway/cgi2/nsapi/argv.c, vaultNES, v
aultNES_4.0 06/30/98 18:02:06
65 1.10 src/gateway/cgi2/nsapi/log.c, vaultNES, va
ultNES_4.0 02/15/00 13:47:23
src/gateway/cgi2/nsapi/cgi-audit.c, vaultNES, vaultN
ES_4.0 1.8 02/15/00
93 1.13.3.1 src/gateway/cgi2/iolib/io.c, vaultTS,
vaultTS_4.0, A.04.00.C 06/24/99 11:25:56
VaultTS.VV-CORE-CMN,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP:
/tcb/lib/tgad:
70 1.13 src/gateway/cgi2/daemon/communications.c,
vaultTS, vaultTS_4.0 09/17/98 18:49:18
$Source: src/gateway/cgi2/daemon/configuration.c, va
ultTS, vaultTS_4.0 $ $Date: 00/02/15 12:28:3
5 $ $Revision: 1.10.1.4 PATCH_11.04 (PHSS_20
733) $
$Source: src/gateway/cgi2/daemon/execute.c, vaultTS,
vaultTS_4.0 $ $Date: 00/03/21 15:14:59 $ $R
evision: 1.17.2.8 PATCH_11.04 (PHSS_21259) $
HP VirtualVault, tgad, revision A.04.00
src/lib/swp/setlocale.c, vaultTS, vaultTS_4.0 1.1 0
9/29/97
$Source: lib/libsecalarm/app_audit.c, libsecalarm, v
vos_rose, rose0007 $ $Date: 99/06/03 11:09:4
2 $ $Revision: 1.7 PATCH_11.04 (PHCO_18729)
$
$ PATCH/11.00:PHCO_19491 Aug 9 1999 09:49:32 $
VaultTS.VV-CORE-CMN,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultTS/lib/libvv.sl:
src/lib/vv/vvauth.c, vaultTS, vaultTS_4.0 1.1 06/30
/98
src/lib/vv/vvpriv.c, vaultTS, vaultTS_4.0 1.1 06/30
/98
src/lib/vv/vvlabel_vvos.c, vaultTS, vaultTS_4.0 1.2
11/06/98
src/lib/vv/vvpriv_vvos.c, vaultTS, vaultTS_4.0 1.1
06/30/98
14 1.9 src/lib/vv/vvfile_vvos.c, vaultTS, vaultTS_
4.0 11/19/98 19:06:31
48 1.5 src/lib/vv/vvlabel.c, vaultTS, vaultTS_4.0
11/19/98 13:07:36
src/lib/vv/vvaudit.c, vaultTS, vaultTS_4.0 1.2 11/1
6/98
src/lib/vv/vvutil.c, vaultTS, vaultTS_4.0 1.1 06/30
/98
13 1.8 src/lib/vv/vvfile.c, vaultTS, vaultTS_4.0 1
1/24/98 20:18:25
src/lib/vv/vvauth_vvos.c, vaultTS, vaultTS_4.0 1.3
07/10/98
(#)17 1.4.1.3 vvaudit_vvos.c, vaultTS, vaultTS_4.
0 09/20/00 10:41:08 VVOS 11.04 PHSS_22296
cksum(1) Output:
VaultNES.NES-VAULT,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP:
2462109134 20527 /opt/vaultTS/lib/libproxy.so
VaultNES.NES-VAULT,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP:
2532056152 57470 /opt/vaultTS/lib/libvvtga.so
VaultTS.VV-CORE-CMN,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP:
3209786933 950641 /tcb/lib/tgad
2350911999 41134 /opt/vaultTS/lib/libvv.sl
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_21259 PHSS_20733 PHSS_22296 PHSS_23526 PHSS_24836
Equivalent Patches: None
Patch Package Size: 1090 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25208
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25208.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25208. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25208.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25208.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25208.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25208.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
The updated proxy provides a mechanism to automatically
downgrade HTTP/1.1 requests to HTTP/1.0.
Updates are required in the the obj.conf configuration
file to use this feature. For each Service line in obj.conf
that invokes "send_proxy", add the "autodowngrade=1" field.
Example:
Add autodowngrade="1" to all lines using send_proxy:
Service method="(GET|HEAD|POST|PUT)" type="text/html"
fn="send_proxy" host="127.0.0.1" port="7001"
safeclient="yes" autodowngrade="1"
Service method="(GET|HEAD|POST|PUT)" type="text/jsp"
fn="send_proxy"host="127.0.0.1" port="7001"
safeclient="yes" autodowngrade="1"
Service method="(GET|HEAD|POST|PUT)" type="image/gif"
fn="send_proxy"host="127.0.0.1" port="7001"
safeclient="yes" autodowngrade="1"
Service method="(GET|HEAD|POST|PUT)" type="image/jpeg"
fn="send_proxy"host="127.0.0.1" port="7001"
safeclient="yes" autodowngrade="1"
If automatic downgrade is no longer desired remove the
"autodowngrade=1" from the send-proxy line.
-----End of Document ID: PHSS_25208------------------------------------------
Document ID: PHSS_23690
Date Loaded: 20011003
Title: s700_800 11.00 OV OB3.10 patch - CS packet
Patch Name: PHSS_23690
Patch Description: s700_800 11.00 OV OB3.10 patch - CS packet
Creation Date: 01/09/11
Post Date: 01/10/03
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OmniBackII A.03.10
Filesets:
OMNIBACK-II.OMNI-CS,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_23690
Symptoms:
PHSS_23690:
Id = JAGad36093
Session status indicates "Completed" although one of the
agents failed.
Id = NSMbb37729
Devbra reports:
"[90:11] Unrecognized option "/" => ignored".
Id = NSMex02631
Backup of Informix logs fails with an error:
"Can not read BSM message (IPC Read Error)".
Id = NSMex03425
Backup of SAP archive logs fails with:
"[Major] From: OB2BAR<hostname> <ORASID> Time:<time>
Can not read BSM message (IPC Read Error
System error: [232] Connection reset by peer.)".
Id = NSMex03486
Backup Session Manager is started with Purge
Session Manager parameters.
Id = NSMex03711
Error:
"Hostname is not in IP range."
is reported after service guard fails over to a
secondary host.
Id = NSMex03739
Pre- and post-exec scripts return invalid exit status.
Id = NSMex03894
Host backup fails if host has more than 600
mountpoints.
Id = NSMex03991
Full Oracle backup can be appended to a medium in a
pool with "append incremental only" property.
Id = NSMex04149
If CRS is restarted in cluster aware mode, error:
"-2 starting omnidbutil -clear!"
occurred in cluster.log file.
Id = NSMex03621
Restore does not work correctly after the mount
request confirmation.
Id = NSMex04283
Licensing fails with an error:
"Cell Server host IP is not in IP range"
Id = HSLco20414
Device maintenance from command line is not sufficient.
Id = NSMex04332
Load balancing does not use all expected devices.
Id = NSMex03705
"omnidbutil -purge" fails with error no 227.
PHSS_22167:
Id = JAGad17029
"List from media" ignores "See private objects" option.
Id = NSMex02584
RDS dies due to lack of memory.
Id = NSMex03493
Omnitrig does not pass debugging parameters to omnirpt.
Id = NSMex03419
After importing a tape from 2.55 to 3.x cell some of
the files can not be restored.
Id = NSMex03356
Permanent license shows up as out of IP range.
Id = NSMex03365
Backup session is not logged in the database if file
pattern search is performed in parallel.
Id = NSMex03466
After the upgrade from OmniBack II 3.00 to 3.10, a
warning
"Received connect from BAR backup DA on host
<hostname> that is not specified in CLIENT statement
in barlist."
appears on a client with multiple lan cards.
Id = NSMex03481
A backup of MC/SG can not be aborted after the switch.
Id = NSMex03663
"-dev_server" entry is removed from cell_info file
whenever an update of device server is performed.
Id = NSMex03417
Upgrading OmniBack II from version 2.55 to 3.10 fails.
Id = NSMex03246
Backup Session Manager is sending wrong SNMP messages to
ITO Management server.
Id = JAGad13634
Informix barlists are not converted into a OmniBack II
3.10 format after an upgrade from OmniBack II 2.55.
Id = NSMex03583
OmniBack II ignores the tape loaded after the mount
request for SCSI-II changer device.
Id = NSMex03702
RDS dies during a SAP restore.
Id = NSMex03289
Sessions are disappearing from OmniBack II database.
Id = NSMex03521
OmniBack II database gets corrupted.
PHSS_21651:
Id = NSMex03001
Sessions are disappearing from the database.
Id = NSMex03294
Restarting of a failed backup session results in an
error message:
"Expecting new option when parsing."
Id = NSMex03346
Omnidbutil -readascii fails with the error message:
"ascii file is corrupted."
PHSS_21235:
Id = NSMex02885
BSM reports unexpected close message during backup
preview.
Id = NSMex02929
Bad performance of Informix logical logs restore.
Id = NSMex03097
Copy session of write-protected tape is aborted and
cleaning tape is requested in the source tape drive.
Id = NSMex02931
Too many backup sessions running in parallel.
Id = NSMex02964
License is not recognized on a Cell Manager system
with multiple lan cards although it has been prepared
for one of the lan cards IP address.
Id = NSMex03110
Backup fails with an error:
"Could not connect to inet in order to start BMA".
Id = NSMex02738
Bad backup performance after upgrade from OmniBack II
2.55 or 3.00.
Id = NSMex02639, NSMex03017
"omnirpt -report fs_not_conf" gives incorrect output.
Id = NSMex03144
Mounting of media fails with an error:
"Volume not found of this type".
Id = NSMex03052, JAGac40383
Filesystem disk agents of a host backup are not
started until the pre/post-exec of the host object
is completed.
PHSS_19520:
Id = HSLco16368
HP SureStoreE Disk Array XP256 is not supported by
OmniBack II to perform a split mirror backup. This
patch does not fix any other problem.
Defect Description:
PHSS_23690:
Id = JAGad36093
If one of the agent fails session status should
indicate "Completed/Errors" instead of "Completed".
Resolution:
Session status is correct.
Id = NSMbb37729
Database Session Manager starts Device Browser with
incorrect options.
Resolution:
Structure containing Device Browser options is
initialized before it is filled with the parameters.
Id = NSMex02631
If new backup of logical logs is started at the time
when BSM is waiting for the tape to be ejected,
the backup of Informix logs fails with an error:
"Can not read BSM message (IPC Read Error)"
after the SmWaitForNewClient timeout occurs.
Resolution:
Fix is implemented in BSM.
Id = NSMex03425
Backup of SAP archive logs fails if a backup request
for next archive log comes when Backup Session Manager
is already exiting.
Resolution:
Datalist entries for BAR session are removed.
Id = NSMex03486
Purge Session Manager parameters are passed to Backup
Session Manager without freeing the options string.
Resolution:
Options string is cleaned before any session
manager starts.
Id = NSMex03711
Licensing is not working properly for systems with
more than 20 LAN cards, due to an OmniBack limitation.
Resolution:
Number of LAN cards on a single system can be up to 100.
Id = NSMex03739
Pre- and post-exec scripts return invalid exit status
because of timing problem.
Resolution:
Environment variable OB2EXECTIMEOUT is introduced.
Variable represents timeout (in seconds) after the end
of pre- and post-exec script. Default value is 0.
Recommended value is between 5 and 10 seconds.
Id = NSMex03894
OmniBack II has a 600 mountpoints limitation. Host
backup fails if there are more than 600 mountpoints.
Resolution:
Number of mountpoints per host increased to 50000.
Id = NSMex03991
Backup Session Manager incorrectly appends full
Oracle backups.
Resolution:
Backup Session Manager correctly checks properties
of pool.
Id = NSMex04149
"omnidbutil -clear" return invalid exit status.
Resolution:
Omnidbutil is improved.
Id = NSMex03621
When restoring the data from STK or GRAU library,
wrong medium is loaded into drive after the mount
request confirmation.
Resolution:
Mount request is properly handled.
Part of SSPUX310_046.
Id = NSMex04283
Ioctl function cannot list all interfaces.
Resolution:
Interfaces limitation is increased to 1000.
Id = HSLco20414
Device enabling, disabling and status report cannot be
performed using OmniBack II command line.
Resolution:
New options "-disable_device", "-enable_device" and
"-device" are added to omnimm, omniupload and
omnidownload.
Please see Special Installation Instructions for details
about the usage of mentioned options.
Part of SSPUX310_055.
Id = NSMex04332
During backup not all devices are locked and used.
Resolution:
Backup Session Manager is improved.
Id = NSMex03705
IpcConnectToProcess() is called incorrectly with
the port 0.
Resolution:
Cell Request Server is changed.
PHSS_22167:
Id = JAGad17029
Using "List from media" option in restore context
ignores "See private objects" option. Objects that are
backed up as "Private" are not listed.
Resolution:
Option parsing in restore context is improved.
Id = NSMex02584
Execution of command
"omnidb -filesystem <FS_Object> -file <File_Name>"
causes a memory leak in RDS (approx. 300 bytes). If the
command is started more than 100000 times, it can cause
RDS to die due to a lack of memory.
Resolution:
Fix is implemented in libob2ecdb.sl.
Id = NSMex03493
Scheduled reports are not started with "-debug" option
although omnitrig is.
Resolution:
Command line option parsing is implemented for omnirpt.
Id = NSMex03419
OmniBack II 3.10 objects are case insensitive which is
not true for the SAP objects backed up with 2.55
version. Object tape format is changed with 3.10 as
well. These changes caused some SAP objects not to be
displayed in the Restore GUI after importing the tape
with SAP objects from 2.55 to 3.10.
Resolution:
Names are tape format are converted into OmniBack II
3.10 format after tape import from 2.55.
Part of SSPUX310_028.
See Special Installation Instructions.
Id = NSMex03356
If there are more than 100 network interfaces, ioctl()
call fails.
Resolution:
Buffer for SIOCGIFCONF is increased to support up to
1000 network interfaces.
Id = NSMex03365
When backup and file search sessions are started in
parallel, file search session locks the database.
Backup Session Manager tries to write backup
information into locked database. Since this action can
not be performed, the following messages are logged
in the rds.log:
"11740 [10-Apr-00 17:37:07] error status=5
11741 [10-Apr-00 17:37:07] GROUPLOCK ELEMENT:
userID=4, LockType=6, LockMode= *, RecSetType=10002,
dba=[0:0], odnum=1"
Resolution:
File pattern search is optimized to minimize the
possibilities of group locks.
Id = NSMex03466
System name checking is not performed for systems with
multiple LAN cards. Backup Session Manager is checking
the system names only when looking for clusters.
Resolution:
System name checking is performed when looking for
clusters and systems with multiple LAN cards.
Id = NSMex03481
Aborting backup session is not possible because
Backup Session Manager incorrectly aborts Disk Agents
after the package switch.
Resolution:
Disk Agents are properly aborted.
Id = NSMex03663
A few entries are deleted from cell_info file upon
update.
Resolution:
Existing entries are preserved.
Id = NSMex03417
Some files are not converted to OmniBack II A.03.10
format because of an upgrade script failure.
Resolution:
Fix is implemented in upgrade script.
Part of the SSPUX310_031.
Id = NSMex03246
Normal, Warning and Minor messages can be seen on ITO
Management server even though OVfilter is set up to
forward only Critical messages.
Resolution:
Messages are forwarded according to OVfilter setup.
Part of the SSPUX310_032.
Id = JAGad13634
File /opt/omni/sbin/nb_informix is missing.
Resolution:
File /opt/omni/sbin/nb_informix is added to OMNI-CS
fileset.
Part of the SSPUX310_035.
Id = NSMex03583
Mount request is not properly implemented for SCSI-II
changer devices.
Resolution:
OmniBack II properly handles mount requests.
Part of the SSPUX310_037.
Id = NSMex03702
RDS dies during a large SAP restore due to memory leak
described in NSMex02584.
Resolution:
Fix is implemented in libob2ecbd.sl.
Id = NSMex03289
Media sync does not work properly when table of
exported/recycled media gets too big (>3000 media).
Some new sessions disappear from database. No error is
reported.
Resolution:
Improved error handling logs this event in debug.log.
Part of the SSPUX310_036.
Id = NSMex03521
Database stays in the hot mode after issuing an
"omnidbcheck" command. If a large amount of data is
written before OmniBack II daemons are stopped, it can
happen that hot files are not properly flushed. This
causes corruption of database.
Resolution:
omnidbcheck flushes hot files immediately after
database check.
Part of the SSPUX310_036.
PHSS_21651:
Id = NSMex03001
When exporting tapes from a cell, wrong sessions are
purged.
Resolution:
Sessions not residing on the exported tape are not
purged.
Id = NSMex03294
Additional protection option is not recognized at
session restart.
Resolution:
Bsm now recognizes the option "-protect days <days>".
Id = NSMex03346
Omnidbutil -writeascii does not handle 2GB limit of
ascii files properly. If any ascii file during
writeascii procedure exceeds 2 GB, the file is not
completed properly. Because of that "omnidbutil
-readascii" fails with an error message that ascii
file is corrupted.
Resolution:
When a file exceeds 2GB during the writeascii procedure
then an additional ascii file is created.
Part of SSPUX310_026.
PHSS_21235:
Id = NSMex02885
BSM reports unexpected close message during backup
preview even if Disk Agent was completed successfully.
Resolution:
Counting of processed data size improved.
Id = NSMex02929
There is a consistent delay of 30 seconds between
each logical log restore.
Resolution:
Fix is implemented in Restore Session Manager.
Id = NSMex03097
Copy session is aborted when copying a write-protected
tape. When write-protected tape in the source drive is
checked, the cleaning tape for that drive is requested
and the following message appears:
"Cleaning tape requested by device <device_name>.
Please clean the drive.".
Resolution:
The cleanme signal is now processed correctly.
Id = NSMex02931
It is not possible to have more than 50 sessions
running in parallel with OmniBAck II 3.10.
Resolution:
The maximum number of session running in parallel is
set to 200.
Part of the SSPUX310_004.
Id = NSMex02964
On some systems ioctl command returns 0 as the IP
address of some of the lan cards. This value has been
used as the end of IP address list and OmniBack II
rejects the license if it is prepared for an IP address
that is listed after "0" address.
Resolution:
"0" addresses are not added to the list of valid system
IP addresses. This way license checking searches
complete IP address list until if finds the IP address
that the license has been prepared for.
Id = NSMex03110
If more than one Media Agent is used in one session
and they are located on the same Novell NetWare
client, then the backup fails with an error:
"Could not connect to inet in order to start BMA".
Resolution:
Delay for starting Media Agents increased.
Id = NSMex02738
Performance degrated by up to 50% after upgrade from
OmniBack II 2.55 or 3.10.
Resolution:
Redundant update of the objects removed.
Id = NSMex02639, NSMex03017
"omnirpt -report fs_not_conf" gives incorrect output.
Resolution:
Processing of "allbdf" output changed.
Id = NSMex03144
After the confirmation of mount request for GRAU DAS or
Storage Tek ACS Library, OmniBack II tries to load ""
(empty string) medium. Library returns an error that
such a volume does not exist.
Resolution:
BSM rechecks medium allocation after the mount request
confirmation.
Id = NSMex03052, JAGac40383
If a datalist contains a host object with pre/post-exec
script, disk agents for the filesystem objects of that
host will not start until the script execution is
complete. This is not suitable if the script doesn't
need to be started for all filesystems.
Resolution:
A new global option is introduced in order to control
the behaviour of the pre/post-exec script execution.
See 'Special Installation Instructions' for details
on setting the global option.
Part of SSPUX310_018.
PHSS_19520:
Id = HSLco16368
Currently OmniBack II only supports the Split Mirror
Backup concept with EMC Symmetrix. After the
introduction of the new HP SureStoreE Disk Array
XP256, it was requested that OmniBack II also
supports this disk array with the split mirror backup
concept. This requires to support Oracle 8.0.x and
SAP R/3 in this concept as well and in addition a new
manual is needed.
Resolution:
The SureStoreE Agent (SSEA) was developed for
HP-UX to control the SureStoreE disk array.
The Backup Session Manager, INET on HP-UX,
and the NT GUI were enhanced and in addition
Oracle 8.0.x and SAP integrations are
supported. Also the manual "HP OpenView
OmniBack II HP SureStore E Disk Array XP256
Configuration Guide" will be released.
SR:
H555005697 H555004061 H555003134 H555004027 B555002953
B555008272 H555003831 H555005821 B554000869 H555005149
H555004475 B554000616 B554000841 B554000834 8606144294
8606147687 3100069193 3100205011 8606110994
Patch Files:
OMNIBACK-II.OMNI-CS,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/omni/lbin/bsm
/opt/omni/lbin/crs
/opt/omni/lbin/dbsm
/opt/omni/lbin/msm
/opt/omni/lbin/rsm
/opt/omni/lbin/mmd
/opt/omni/lib/libob2eadm.sl
/opt/omni/lib/libob2ecdb.sl
/opt/omni/lib/libob2emmdb.sl
/opt/omni/lib/libob2ecmn.sl
/opt/omni/sbin/omnidbutil
/opt/omni/sbin/upgrade_from_2.55.sh
/opt/omni/sbin/nb_informix
/opt/omni/sbin/omnidbcheck
/opt/omni/sbin/omnitrig
what(1) Output:
OMNIBACK-II.OMNI-CS,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/omni/lbin/bsm:
[TZ=GMT0 /opt/omni/lbin/bsm -version]
HP OpenView OmniBack II A.03.10: BSM, internal build
PHSS_23689/PHSS_23690, built on Wed Jul 25
11:17:09 2001
/opt/omni/lbin/crs:
[TZ=GMT0 /opt/omni/lbin/crs -version]
HP OpenView OmniBack II A.03.10: CRS, internal build
PHSS_23689/PHSS_23690, built on Wed Jul 25
11:56:01 2001
/opt/omni/lbin/dbsm:
[TZ=GMT0 /opt/omni/lbin/dbsm -version]
HP OpenView OmniBack II A.03.10: DBSM, internal buil
d PHSS_23689/PHSS_23690, built on Wed Jul 25
11:38:43 2001
/opt/omni/lbin/msm:
[TZ=GMT0 /opt/omni/lbin/msm -version]
HP OpenView OmniBack II A.03.10: MSM, internal build
PHSS_23689/PHSS_23690, built on Wed Jul 25
15:37:06 2001
/opt/omni/lbin/rsm:
[TZ=GMT0 /opt/omni/lbin/rsm -version]
HP OpenView OmniBack II A.03.10: RSM, internal build
PHSS_23689/PHSS_23690, built on Wed Jul 25
11:18:45 2001
/opt/omni/lbin/mmd:
[TZ=GMT0 /opt/omni/lbin/mmd -version]
HP OpenView OmniBack II A.03.10: MMD, internal build
PHSS_22166/PHSS_22167, built on Mon Sep 18
14:26:26 2000
/opt/omni/lib/libob2eadm.sl:
None
/opt/omni/lib/libob2ecdb.sl:
None
/opt/omni/lib/libob2emmdb.sl:
None
/opt/omni/lib/libob2ecmn.sl:
None
/opt/omni/sbin/omnidbutil:
[TZ=GMT0 /opt/omni/sbin/omnidbutil -version]
HP OpenView OmniBack II A.03.10: OMNIDBUTIL, interna
l build PHSS_21650, built on Thu May 18 14:1
2:35 2000
/opt/omni/sbin/upgrade_from_2.55.sh:
None
/opt/omni/sbin/nb_informix:
None
/opt/omni/sbin/omnidbcheck:
[TZ=GMT0 /opt/omni/sbin/omnidbcheck -version]
HP OpenView OmniBack II A.03.10: OMNIDBCHECK, intern
al build PHSS_22166/PHSS_22167, built on Mon
Sep 18 14:15:32 2000
/opt/omni/sbin/omnitrig:
[TZ=GMT0 /opt/omni/sbin/omnitrig -version]
HP OpenView OmniBack II A.03.10: OMNITRIG, internal
build PHSS_22166/PHSS_22167, built on Thu Se
p 7 15:06:12 2000
cksum(1) Output:
OMNIBACK-II.OMNI-CS,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
509841601 1166299 /opt/omni/lbin/bsm
2493770743 706368 /opt/omni/lbin/crs
3095471960 1219055 /opt/omni/lbin/dbsm
1476601836 686053 /opt/omni/lbin/msm
831299916 862632 /opt/omni/lbin/rsm
246603417 517732 /opt/omni/lbin/mmd
4234081061 692720 /opt/omni/lib/libob2eadm.sl
2765462869 881364 /opt/omni/lib/libob2ecdb.sl
3961483874 651912 /opt/omni/lib/libob2emmdb.sl
1782008663 804257 /opt/omni/lib/libob2ecmn.sl
188065716 677437 /opt/omni/sbin/omnidbutil
1359022427 28086 /opt/omni/sbin/upgrade_from_2.55.sh
2755861046 353611 /opt/omni/sbin/nb_informix
3452850420 464149 /opt/omni/sbin/omnidbcheck
2570520288 394475 /opt/omni/sbin/omnitrig
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_22167 PHSS_21651 PHSS_21235 PHSS_19520
Equivalent Patches:
PHSS_23689:
s700: 10.00 10.01 10.10 10.20
s800: 10.00 10.01 10.10 10.20
Patch Package Size: 9920 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_23690
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_23690.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_23690. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_23690.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_23690.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_23690.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_23690.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_23690:
NOTE!
Fix for HSLco20414 introduces new options for device
maintenance. The usage of new options is listed below:
To disable/enable specific device and all other devices
with the same lockname, run:
omnimm -disable_device {device name}
omnimm -enable_device {device name}
To disable/enable all devices with the same lockname, run:
omnimm -disable_lockname {lock name}
omnimm -enable_lockname {lock name}
To check if specific device is enabled/disabled, run:
omnidownload -device {device name}
To obtain complete functionality one has to install
PHSS_24423/PHSS_24424 (CORE) and PHSS_23109/PHSS_23110
(Cell Console) or later patches as well.
NOTE!
This Patch has to be installed on the Cell Manager host.
OmniBack II server must be shutdown before installing
the patch. Use the following command for shutting down
the server:
"/opt/omni/sbin/omnisv.sh stop".
After the installation is complete, restart OmniBack II
server using "/opt/omni/sbin/omnisv.sh start".
NOTE!
Fix NSMex03419 is also part of the OMNIBACK_00014
(Windows NT) and PHSS_21644/PHSS_21645 (Cell Console)
general release patch. Its functionality will be
fully available when the mentioned patches that include
this fix are released.
NOTE!
New global option has been introduced with earlier
patches PHSS_21234/PHSS_21235 for solving the problem
NSMex03052 & JAGac40383. With this option, the backup
administrator can decide whether the pre/post-exec script
will be started for one filesystem on the host only, or
should all the filesystem disk agents wait for the
pre/post-exec script to finish before starting up the
filesystem backup.
The option must be set on the Cell Manager system, in the
file /etc/opt/omni/options/global. This is the syntax:
PrePostExecOnEveryVolumeForHostBackup=<0 or 1>
default: 0
If this option is set (=1), Backup Disk Agent (BDA)
for each volume of host object will execute the
pre/post-exec script specified. If this option is not
set (=0), the Backup Session Manager (BSM) will
execute preexec just prior to starting first volume
BDA and postexec after last volume BDA finished.
Note that for the duration of pre/post-exec scripts,
the BSM will not be responding.
NOTE!
The patches PHSS_19519/PHSS_19520 introduce support for
HP SureStore E XP256 disk array.
In order to enable the HP SureStoreE Agent (SSEA)
functionality,a license-to-use (B7023AA) must be
installed. In addition, the following OB2 patches
are required:
PHSS_19523/PHSS_19524 - Core patch
PHSS_20111/PHSS_20112 - Oracle8 integration patch
PHSS_19525/PHSS_19526 - SSEA integration patch
PHSS_21236/PHSS_21237 - SAP integration patch
OMNIBACK_00010 - Windows NT
Some of the patches mentioned above may be superseded
by a newer patch. Please check the HP Electronic
Support Center web page for latest patches available.
For more information regarding the installation procedure
refer to the "HP OpenView OmniBack II HP SureStore E Disk
Array XP256 Configuration Guide"
Patch includes the following Site Specific Patches:
SSPUX310_004
SSPUX310_018
SSPUX310_026
SSPUX310_028
SSPUX310_031
SSPUX310_032
SSPUX310_035
SSPUX310_036
SSPUX310_037
SSPUX310_046
SSPUX310_055
-----End of Document ID: PHSS_23690------------------------------------------
Document ID: PHKL_24743
Date Loaded: 20011003
Title: s700_800 11.11 VM/JFS deadlock; mmap performance
Patch Name: PHKL_24743
Patch Description: s700_800 11.11 VM/JFS deadlock; mmap performance
Creation Date: 01/09/26
Post Date: 01/10/03
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
No (superseded patches were critical)
PHKL_24073: HANG
Category Tags:
defect_repair enhancement general_release critical
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_24743
Symptoms:
PHKL_24743:
( SR:8606205558 CR:JAGad74733 ) Duplicate
( SR:8606204858 CR:JAGad74036 )
Decreased performance for mmap() operations has occasionally
been observed in superdome systems with more than 32 cpus.
These symptoms are not specific to superdomes, but could
possibly occur on other high end systems as well.
PHKL_24073:
( SR:8606189205 CR:JAGad58421 )
A multi-threaded process hangs and cannot be killed. This
process will have been repeatedly mmap()ing parts of the
same file, while at the same time reading or writing to it
with the read(), write(), readv(), or writev() system calls
from a different thread. That file must also be on a JFS
file system.
The Netscape Messaging Server's smtpd process is the only
application we've seen do the particular combination of
operations required to get into this state.
Defect Description:
PHKL_24743:
( SR:8606205558 CR:JAGad74733 ) Duplicate
( SR:8606204858 CR:JAGad74036 )
Unnecessary acquisition and release of region locks in
common execution paths can cause unpredictable performance
degradation.
Resolution:
ltered code path to minimize frequency of region
lock/release in procedures mmap_file_pieces() and
mmap_file_object(). Note that this is only one of the
causes for unpredictable performance degradation in mmap.
PHKL_24073:
( SR:8606189205 CR:JAGad58421 )
This problem was caused by a lock ordering problem between
VM and JFS. JFS can call VM while holding an inode lock;
the routines called may require a vas lock. VM can call JFS
while holding a vas lock; the routines called may require
an inode lock. If we get unlucky, we hit the same vas/inode
lock combination from both directions, and the threads
deadlock. Because the vas lock potentially held by VM is
a per process resource, this situation can only be
encountered by a multithreaded process.
Resolution:
The fix is to have the VM routine drop the vas lock before
calling the file system code; fortunately, the VM routine
can safely drop and reacquire the lock around the call ...
it was mostly holding it to avoid dropping and reacquiring
it repeatedly in a loop.
SR:
8606189205 8606204858 8606205558
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvm.a(vm_mmap.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvm.a(vm_mmap.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvm.a(vm_mmap.o):
vm_mmap.c $Date: 2001/07/24 12:02:44 $Revision: r11.
11/2 PATCH_11.11 (PHKL_24743)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvm.a(vm_mmap.o):
vm_mmap.c $Date: 2001/07/24 12:02:44 $Revision: r11.
11/2 PATCH_11.11 (PHKL_24743)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
4195131276 31924 /usr/conf/lib/libvm.a(vm_mmap.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
3916064584 68640 /usr/conf/lib/libvm.a(vm_mmap.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_24073
Equivalent Patches: None
Patch Package Size: 130 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_24743
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_24743.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_24743. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_24743.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_24743.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_24743.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_24743------------------------------------------
Document ID: PHSS_25176
Date Loaded: 20011002
Title: s700_800 11.00-11 Fortran90 from B.11.01.40 to B.11.01.43
Patch Name: PHSS_25176
Patch Description: s700_800 11.00-11 Fortran90 from B.11.01.40 to B.11.01.43
Creation Date: 01/09/28
Post Date: 01/10/02
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
FORTRAN90 B.11.01.40
FORTRAN90 B.11.01.42
Filesets:
FORTRAN90.FORT90-PRG,fr=B.11.01.40,fa=HP-UX_B.11.00_32/64,v=HP
FORTRAN90.FORT90-PRG,fr=B.11.01.42,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25176
Symptoms:
PHSS_25176:
01)JAGab67472: A problem with strength reduction of 64
bit multiplication by unsigned consants
caused wrong answers.
02)JAGac86637: The compiler errantly reports "invalid arc
calculation" warning.
03)JAGad62170: The +U option needs to support multiple
arguments.
04)JAGad84653: The compiler does not accept 'type' as
a 'print' statement.
05)JAGad85160: Reference to omp_memcpy is unresolved.
06)JAGad85254: The compiler asserts on an OMP intrinsic.
07)JAGad85371: Customer reports need to have more than 256
continuation lines.
08)JAGad85372: Performance for guided scheduling does not
scale well beyond 2 threads.
09)JAGad86385: The compiler aborts with interanl error on
the pack intrinsic.
10)JAGad87340: Compiler aborts with TCG assertion in
in_descriptor.c.
11)JAGad87380: The compiler does not recognize the
+Onoopenmp command-line switch.
12)JAGad87416: Compiler aborts with TCG assertion.
13)JAGad87513: Using $HP$SHARED_COMMON within second
subroutine in a file Is ignored, causing
wrong answers.
14)JAGad88599: Bus error occurs when intrinsic function LOC
is called with a non-subscripted array.
15)JAGad88762: OMP directive is ignored.
16)JAGad89129: Error occurs when implicitly opening a file
with unit number greater than 99.
PHSS_24772:
01)JAGaa68246: Wrong answers with floating point
comparisons using +FPD.
02)JAGab73429: The compiler does not allow the !$ALIAS
directive.
03)JAGad03801: Compiler crashing on end do statements with
no matching do statements.
04)JAGad08183: Run time error with assigned gotos in 64bit
mode
05)JAGad15689: Failure on entry statement that returns a
quadword result.
06)JAGad62340: The +cat option at the end of the compile
line caused compile problems.
07)JAGad73062: Compiler aborts when parallelizing a loop
with an inlined routine.
08)JAGad73370: Wrong answers from libF90 cputime routine.
09)JAGad73465: Code sometimes generated wrong answers at
optimization level +O3.
10)JAGad73529: Garbled "Module not found" error messages.
11)JAGad74647: Open MP parallelization causes segmentation
fault.
12)JAGad77170: SAVE tags an automatic variable, a variable
type not eligible for SAVE causing bogus
compile-time errors.
13)JAGad77176: Compiler abort when an Open MP PRIVATE
variable is from a USEd module.
14)JAGad77883: Compiler abort on interface assignment.
15)JAGad79146: Gdb unable to show the correct f90 source
lines when stepping.
16)JAGad81039: Compiler aborts with "abnormal exit taken
from bridge" with nested routines and
modules.
17)JAGad81737: OMP variable trip count loops not always
correctly parallelized.
18)JAGad81738: Loops with induction variables of type
integer*8 were not transforming the
increment value to be an I*8 constant.
19)JAGad82866: Compiler aborts while generating code for
an array initialization in wide mode.
Defect Description:
PHSS_25176:
01)JAGab67472: Fixed a problem with strength reduction
of 64 bit multiplication by unsigned
consants.
Resolution: Recompile with the new compiler.
02)JAGac86637: Removed an unused warning message
"invalid arc calculation".
Resolution: Recompile with the new compiler.
03)JAGad62170: Added support for multiple arguments to
the +U option.
Resolution: Recompile with the new compiler.
04)JAGad84653: To be consistent with f77, updated the
compiler to accept 'type' as a synonym
for 'print' when not within a declaration.
Resolution: Recompile with the new compiler.
05)JAGad85160: Fixed the compiler to resolve the
omp_memcpy reference.
Resolution: Recompile with the new compiler.
06)JAGad85254: Fixed the OMP intrinsic assertion problem
resulting from parameter mismatch.
Resolution: Recompile with the new compiler.
07)JAGad85371: Enhanced the compiler to allow up to 300
continuation lines.
Resolution: Recompile with the new compiler.
08)JAGad85372: Error in algorithm was causing the
compiler to use workload/2 to guide
scheduling. Changed this to use
workload/numthreads.
Resolution: Recompile with the new compiler.
09)JAGad86385: Fixed the internal compiler error
generated on a pack intrinsic.
Resolution: Recompile with the new compiler.
10)JAGad87340: Fixed the internal compiler error
resulting in TCG in_descriptor.c
assertion.
Resolution: Recompile with the new compiler.
11)JAGad87380: Implemented the +Onoopenmp
command-line switch.
Resolution: Recompile with the new compiler.
12)JAGad87416: Fixed the compiler internal error.
Resolution: Recompile with the new compiler.
13)JAGad87513: Placement of $HP$SHARED_COMMON
directive contrary to documentation
was permitted in F77. Upgraded the
f90 compiler to allow the f77 placement.
Resolution: Recompile with the new compiler.
14)JAGad88599: Fixed problem with intrinsic handling
of dope vector array, resulting in bus
error.
Resolution: Recompile with the new compiler.
15)JAGad88762: Fixed problem so that OMP directives
are not lost.
Resolution: Recompile with the new compiler.
16)JAGad89129: Fixed bug in compiler for implicit
open of file with unit number greater
than 99.
Resolution: Recompile with the new compiler.
PHSS_24772:
01)JAGaa68246: The compiler had a problem with using +FPD
combined with certain optimizations. This
has been fixed.
Resolution: Recompile with the new compiler.
02)JAGab73429: The compiler did not recognize the !$ALIAS
form of the $ALIAS directive. The compiler
has been changed to recognize !$ALIAS
Resolution: Recompile with new compiler.
03)JAGad03801: Compiler expected each end do statement to
have matching do statements. This has been
fixed so that an error message is generated.
Resolution: Recompile with new compiler.
04)JAGad08183: Compiler was incorrectly calculating the
destination address. This has been fixed.
Resolution: Recompile with the new compiler.
05)JAGad15689: Problem with quadword results for entry
statements has been fixed.
Resolution: Recompile with the new compiler.
06)JAGad62340: The compiler included the concatenated
file plus all of the individual files in
the compile and link. This has been fixed.
Resolution: Recompile with the new compiler.
07)JAGad73062: The compiler asserted under some cases
when parallelizing a loop with an inlined
routine. This has been fixed.
Resolution: Recompile with the new compiler.
08)JAGad73370: The cputime routine did not return the
correct value. This has been fixed.
Resolution: Recompile with the new compiler.
09)JAGad73465: The compiler incorrectly removed some code
assuming it was unreachable when it was in
fact needed. This has been fixed.
Resolution: Recompile with the new compiler.
10)JAGad73529: The compiler was built with the wrong version
of the error message file. This has been
fixed.
Resolution: Recompile with the new compiler.
11)JAGad74647: There was a problem with the variable step
transformation. This has been fixed.
Resolution: Recompile with the new compiler.
12)JAGad77170: The compiler generated SAVE tags for an
automatic variable. This has been fixed.
Resolution: Recompile with the new compiler.
13)JAGad77176: The compiler did not clear the USEASSOCIATED
bit for use variables which were privatized.
This has been fixed.
Resolution: Recompile with the new compiler.
14)JAGad77883: An INTERFACE Assignment definition prevented
the compiler from resolving an operator. This
has been fixed.
Resolution: Recompile with the new compiler.
15)JAGad79146: The compiler was using the incorrect variable
hashlinenumber which did not always track
line number. This has been fixed.
Resolution: Recompile with the new compiler.
16)JAGad81039: When propagating type tags from uplevel
imported module to the nested routine,
the compiler was not checking to see if
the type tags had already been set. This
has been fixed.
Resolution: Recompile with the new compiler.
17)JAGad81737: The compiler inadvertantly modified loops
not directly attached to OMP DO directives.
This has been fixed.
Resolution: Recompile with the new compiler.
18)JAGad81738: The compiler was not correctly typing
I*8 induction variables. This has been
fixed.
Resolution: Recompile with the new compiler.
19)JAGad82866: The compiler was incorrectly using the
address of the repetition count instead of
the repetition count. This has been fixed.
Resolution: Recompile with the new compiler.
SR:
0000000000
Patch Files:
FORTRAN90.FORT90-PRG,fr=B.11.01.40,fa=HP-UX_B.11.00_32/64,
v=HP:
FORTRAN90.FORT90-PRG,fr=B.11.01.42,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/fortran90/bin/f90
/opt/fortran90/lbin/f90com32
/opt/fortran90/lbin/f90com64
/opt/fortran90/lib/libF90.a
/opt/fortran90/lib/libF90_parallel.a
/opt/fortran90/lib/nls/C/libF90.cat
/opt/fortran90/lib/nls/msg/C/f90.cat
/opt/fortran90/lib/nls/msg/C/f90com.cat
/opt/fortran90/lib/pa2.0/libF90.a
/opt/fortran90/lib/pa2.0/libF90_parallel.a
/opt/fortran90/lib/pa20_64/libF90.a
/opt/fortran90/lib/pa20_64/libF90_parallel.a
what(1) Output:
FORTRAN90.FORT90-PRG,fr=B.11.01.40,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/fortran90/bin/f90:
HP-UX f90 20010913 (214852) B3907DB/B3909DB PHSS_25
176 B.11.01.43
HP F90 v2.5.4
$ PATCH/11.00:PHCO_95167 Oct 1 1998 13:46:32 $
/opt/fortran90/lbin/f90com32:
HP F90 v2.5.4
HP-UX SLLIC/OPTIMIZER UX.11.01.96 (ROSE): 11/16/98
HP aC++ B3910B X.03.11.10 Classic Iostream Library
HP aC++ B3910B X.03.11.10 Language Support Library
Ucode Code Generator - UX11.01.04(GS IB4) (PACG - No
vember 16, 1998)
HP-UX f90com32 20010921 (111943) B3907DB/B3909DB PH
SS_25176 B.11.01.43
Copyright (c) 1993-2001 HP. All Rights Reserved.
HP Fortran-95 Version F95D4 HP:131200:080240
Ucode-2 Version 2-6
High Level Optimizer - 21-Sep-2001.11:07
$ PATCH/11.00:PHCO_95167 Oct 1 1998 13:46:32 $
/opt/fortran90/lbin/f90com64:
HP F90 v2.5.4
HP-UX SLLIC/OPTIMIZER UX.11.01.96 (ROSE): 11/16/98
HP aC++ B3910B X.03.11.10 Classic Iostream Library
HP aC++ B3910B X.03.11.10 Language Support Library
Ucode Code Generator - UX11.01.04(GS IB4) (PACG - No
vember 16, 1998)
HP-UX f90com64 20010921 (113138) B3907DB/B3909DB PH
SS_25176 B.11.01.43
Copyright (c) 1993-2001 HP. All Rights Reserved.
HP Fortran-95 Version F95D4 HP:131200:080240
Ucode-2 Version 2-6
High Level Optimizer - 21-Sep-2001.11:07
$ PATCH/11.00:PHCO_95167 Oct 1 1998 13:46:32 $
/opt/fortran90/lib/libF90.a:
None
/opt/fortran90/lib/libF90_parallel.a:
None
/opt/fortran90/lib/nls/C/libF90.cat:
None
/opt/fortran90/lib/nls/msg/C/f90.cat:
None
/opt/fortran90/lib/nls/msg/C/f90com.cat:
None
/opt/fortran90/lib/pa2.0/libF90.a:
None
/opt/fortran90/lib/pa2.0/libF90_parallel.a:
None
/opt/fortran90/lib/pa20_64/libF90.a:
None
/opt/fortran90/lib/pa20_64/libF90_parallel.a:
None
cksum(1) Output:
FORTRAN90.FORT90-PRG,fr=B.11.01.40,fa=HP-UX_B.11.00_32/64,
v=HP:
1020462103 884736 /opt/fortran90/bin/f90
2728645705 12636160 /opt/fortran90/lbin/f90com32
3373239917 12709888 /opt/fortran90/lbin/f90com64
3715199534 4056172 /opt/fortran90/lib/libF90.a
4043440094 4561272 /opt/fortran90/lib/libF90_parallel.a
1589122412 9505 /opt/fortran90/lib/nls/C/libF90.cat
411426226 16434 /opt/fortran90/lib/nls/msg/C/f90.cat
2847524481 115163 /opt/fortran90/lib/nls/msg/C/f90com.cat
1264473203 4339960 /opt/fortran90/lib/pa2.0/libF90.a
3193735808 4836680 /opt/fortran90/lib/pa2.0/
libF90_parallel.a
2272478615 5699318 /opt/fortran90/lib/pa20_64/libF90.a
2722705683 6366850 /opt/fortran90/lib/pa20_64/
libF90_parallel.a
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_24772
Equivalent Patches: None
Patch Package Size: 54960 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25176
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25176.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25176. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25176.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25176.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25176.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25176.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_25176------------------------------------------
Document ID: PHSS_25090
Date Loaded: 20011002
Title: s700_800 11.00 OV ITO6.0X NT Agent Patch A.06.08
Patch Name: PHSS_25090
Patch Description: s700_800 11.00 OV ITO6.0X NT Agent Patch A.06.08
Creation Date: 01/10/02
Post Date: 01/10/02
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OpenView IT/Operations 6.0
Filesets:
OVOPC-CLT.OVOPC-NT-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_25090
Symptoms:
PHSS_25090:
- SR: 8606179902
During (de)installation of the NT agent
the installation might abort with error messages
saying that it can't remove libopc.dll or opcapi.dll.
This can occur when you have installed VP-IS.
- SR: 8606205415
opcsetup might report an error during manual NT agent
installation when the value for [Setup Drive] contains
trailing spaces in opcsetup.inf.
- SR: 8606206616
opcntprocs.exe or itoprocs.exe may hang on the agent
system, therefore the process monitoring will fail.
- SR: 8606208283
The NT user privilege "Increase Quota" needs to be
assigned to the 'HP ITO account', which is not done
during the agent installation. If this is missing, the
agent may not be able to perform a full user switch with
password to a different account. This could result in
problems when executing tools or scheduled commands on
the managed node that require full network access.
- SR: 8606212295
The agent deployment/installation on a Windows NT/2000
node might fail, because files are locked or agent
processes can't be stopped.
- SR: 8606213476
The distribution to nodes may hang or fail. This is more
likely to happen while distributing to Windows NT/2000
nodes rather than on UNIX nodes. On Windows NT/Windows
2000 nodes the control agent may produces a Dr. Watson
error.
- SR: B555009193
VBscript.dll delivered with Windows NT/ Windows 2000
VPO/VPW agent has wrong version and doesn't work with the
Script Engine of VPO/VPW
- SR: B555009481
The process monitor itoprocs.exe/opcntprocs.exe doesn't
report correct values with the first call when the
process name is longer than 15 characters.
- SR: B555009745
The template default of the object field of a monitor
template is not used.
- SR: B555010038
After installing SPI templates (e.g. DB SPI) and then
after reinstalling the agent, the agent may not find
commands.
- SR: B555010620
Some messages are missing in the Japanese message
catalog. You get a Cannot generate message error.
- SR: B555010819
opcsetup aborts in case the opcsetup.inf file
has unix ascii format, the problem are the different
line ends between UNIX and Windows.
- SR: B555010879
opctrapi aborts during template distribution if
conditions with the 'Suppress Identical Output Messages'
features are used
- SR: B555010948
Nested alternatives were not handled correctly in the
pattern matching algorithm, e.g. the pattern '[a|b]c|d'
was handled like '[a|b|d]c'.
- SR: B555010980
Traps without a SNMP variable are not matched because
server patch adds an extra attribute to the template.
- SR: B555011256
The agent process opcle.exe may crash on Windows 2000
nodes while monitoring the new event logs coming with
Windows 2000.
- SR: B555011422
opcragt/opcagt -stop and opcagt -kill might fail
when a subagent process can't be killed or stopped
- SR: B555011436
When monitoring real time performance data with the
Windows NT/Windows 2000 agent, there may be a number of
"Perflib" messages created in the application event log.
These "Perflib" messages will occur when you don't want
to monitor the object the messages are created by. On
some systems it may happen that OvNtDiag.exe/itodiag.exe
hangs while retrieving system information.
- SR: B555011497
Trap interceptor aborts after reboot - can't open SNMP
session
- SR: B555011510
opcle might create a DrWatson when the path to an Event
log message (usually a DLL) on Windows NT/Windows 2000 is
divisible by four.
- SR: B555011540
The VPW agent installation is not aware of existing VPO
and ITO installations, and the VPO agent installation is
not aware of existing VPW installations. The old agent
binaries installed by the other OpenView management
software (VPO/VPW/ITO) are not removed from the system.
- SR: B555011594
The original message text of a logfile encapsulator
message is wrong if <$LOGPATH> or <$LOGFILE> is used.
- SR: R555011075
The control agent aborts when calling 'opctemplate -d -
all'.
PHSS_24051:
- SR: 8606171814
itodiag.exe causes NT security event log messages on
remote PC when checking for diskspace on network drives
where the HP ITO account has no permissions to.
- SR: 8606180891
The template default for the service name is not used.
- SR: 8606181988
the event interceptor doesn't forward on
"forward unmatched" if a "supress unmatched" condition
is used in a second template
- SR: 8606183491
itodiag reports wrong values for diskspace
- SR: 8606188773
When issuing an opcragt -distrib to an NT node the
command doesn't exit until the distribution is completed
on the NT node, this behavior is in opposite to the UNIX
nodes, where it returns after just starting the
distribution process on the node.
- SR: B555009120
message from NT 4.0 nodes might have wrong time
in the time created on managed node field after
after changing the TZ on such a node
- SR: B555009740
When using the agent message logging with multibyte
character messages you might get wrong formats.
- SR: B555009756
When creating a template with an automatic action e.g.:
progx.exe \\<node>\share-x
And taking the <node> as variable it isn't replaced with
the correct value.
- SR: B555010012
The HP ITO Installation Server service might fail.
- SR: B555010186
When using the VPO application Virtual Term PC in the
group NT Tools and sending CTRL+C to this terminal window
on the UNIX side it might be, that the cmd.exe and
opcvterm.exe doesn't stop on the NT side. Cmd.exe instead
starts using a lot of CPU.
- SR: B555010324
The command "opcagt -kill" might not kill all VPO
processes on a NT node.
- SR: B555010449
The agent deinstallation doesn't remove the registry
keys:
HKEY_LOCAL_MACHINE/SOFTWARE/Hewlett-Packard/Openview and
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa/M
SV1_0
even when they are empty.
- SR: B555010563
The monitor agent often reports 'Can't start monitor
script for object 'Process_msdev'. Script still running.
(OpC30-610)'. Sometimes this is caused by a hanging
monitor binary.
PHSS_22884:
- Automatic Actions can't start applications that display a
user interface.
- The Event Interceptor might get into a looping state when
running on an NNM system and the ovtrapd is stopped.
- Multiple issues with the agent on MS Terminal Server
systems running on NT 4.0.
- Perl script might show strange behavior when called
as monitor.
- Logfile encapsulator might report an access violation
when reading EventLog message.
- Agent has to run as 'HP ITO account' user.
- Agent installation might fail with 'Error from
InformManager' when the Management Server is a multi
homed host.
- Agent installation adds the agent path to the system
environment without checking if it's already there. Agent
deinstallation doesn't remove this path at all.
- Japanese messages might have wrong characters.
PHSS_22009:
- ITO requires the setting of all IP addresses in
opc.hosts for NT multi homed hosts.
- The control agent aborts when the /usr/OV/tmp/OpC/bin
directory does not exist.
- The installation aborts with the NetGetDCName API
failing: network path not found.
- The event correlation agent might abort.
- In some situations the the source IP address of an
incoming trap has the wrong byte ordering.
- When there are many quickly incoming traps, the Event
Interceptor does not handle them but instead buffers
until there are new traps arriving.
- Event Interceptor aborts when running on an NNM system
and an invalid trap is received.
- After distributing of templates to NT system, sometimes
there is a message in the errorlog about failures while
suspending threads.
- Several changes for firewall environments. For detailed
information refer to the VPO Firewall Configuration
White Paper version 3.0
- The 'Processes' application on Windows 2000 produces a
Dr.Watson window.
- Event Interceptor aborts after receiving trap with
unresolvable IP address.
- If buffer file size limitation is enabled, the agent may
discard low-severity messages even if there is still
space in the buffer file.
- The execution of monitors or applications might try to
execute a directory.
Defect Description:
PHSS_25090:
- SR: 8606179902
During (de)installation the set-up replaces/removes
some DLLs which can be accessed via API calls and
therefore be locked outside of VPO agent and so they
can't be replaced. This may happen with SPIs
(e.g. VP-IS).
In order to avoid this, it is necessary to stop all
services and processes which use the DLLs.
Now the set-up process stops and then restarts all
affected services.
- SR: 8606205415
Using a drive letter with trailing blanks causes
problems with NT API calls, and problems also
occur when generating paths based on this drive letter.
To avoid this opcsetup cuts the trailing blanks during
reading the values from opcsetup.inf.
- SR: 8606208283
When the user 'HP ITO Account' (or any other
user set that the agent runs as) does not have the
privilege "Increase Quotas" and also the group does not
have, the agent can't perform a full switch user with
password check. The privilege is now assigned to the
agent user during agent installation time.
- SR: 8606212295
Removal and copying of files is not possible while
they are in use under Windows NT/Windows 2000.
To ensure the correct remove and copy operation,
all known agent processes and other agent
programs which are likely to hang, or take longer will be
stopped before files are copied or removed.
If the copy or remove still fails, there is a list
of processes running on the system in the inst.log.
It might be that one of these processes caused the
problem. This list is for troubleshooting purposes.
- SR: 8606213476
While the agent receives several RPC calls, like "Start
Distribution", "Execute Action" or "Set Primary Manager"
in parallel, it may happen that the call results in a
conflict within the control agent, which causes the
control agent to bring a Dr. Watson window.
This conflict can also occur on UNIX but the control
agent doesn't die, rather the RPC request may fail.
With this version the RPC calls which could cause
conflicts are serialised.
- SR: B555009481
The process monitor itoprocs.exe/opcntprocs.exe does not
report any value for processes with names longer than 15
characters with the first call.
This problem is fixed in the new process monitor,
which uses different API layers.
This should avoid masses of PerfLib messages seen
when the process monitor is running.
On some systems it has shown that the start of the
process monitor might cause System Event Log Messages
with the following content:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10002
Date: 2/22/2001
Time: 2:11:52 PM
User: <ComputerName>\HP ITO account
Computer: <ComputerName>
Description: Access denied attempting to launch a DCOM
Server. The server is: {0C0A3666-30C9-11D0-8F20-
00805F2CD064} The user is HP ITO account
This event is generated by the Machine Debug Manager DCOM
object which is coming with Microsoft IIS 4.0 or 5.0
to avoid this messages please see the following Microsoft
article:
Q290398
http://support.microsoft.com/support/kb/articles/Q290/3/9
8.ASP
- SR: B555010038
When SPIs change the environment variable PATH in the
way that by adding (for example) \usr\OV\bin\OpC\test or
similar this path is changed/removed during the
(de)installation of the agent.
Now the set-up program searches for the complete path
correctly ended so that it doesn't overwrite or remove
the wrong paths.
- SR: B555010879
When freeing the allocated memory, a wrong frunction was
used.
- SR: B555010948
The grammar was changed to allow nested alternatives and
process it correctly.
- SR: B555011436
The reoccurring "PerfLib" messages is due to the agent
always reading all performance data of the machine.
With this patch the monitor agent and also
itodiag.exe/ovntdiag.exe are changed to use a different
API layer of Microsoft APIs.
Querying of performance data is dedicated
to the required object and counter.
itodiag.exe/ovntdiag.exe is made independent from other
libraries delivered with the agent.
PLEASE NOTE:
There will still be other "PerfLib" and also other
messages regarding to the performance counters in the
application Event Log, but the number of these messages
is no higher than if you start perfmon.
IMPORTANT: These messages are generated after each
start of an application which reads performance data.
This means each time itodiag.exe/ovntdiag.exe or the
agent is started you will get these messages.
Event message Event ID: 3101 might also occur on systems
running Windows 2000 with Service Pack 1 or below.
Please see the following Microsoft article and web page
for detailed information:
Q257760
(http://support.microsoft.com/support/kb/articles/Q257/7/
60.ASP)
With Windows 2000 it has been seen that the LogicalDisk
Performance Counter doesn't show: C:, D: and so on but
instead HarddriveVolume1, HarddriveVolume2.
The result of this will be that the template/policies
which are monitoring the LogicalDisk object might not
work any longer. There are no additional information, why
this name change has been done.
- SR: B555011497
The trap interceptor may abort during a reboot of a
Windows NT/Windows 2000 node with the message "can't
open SNMP session". The reason is that the SNMP service
just takes to long to start.
Now the agent waits at maximum 30 seconds for the SNMP
service to start till this error message is generated.
- SR: B555011540
The agent installation of VPO/VPW only removes agent
components which currently reside in the target
installation directory. This patch the installation
checks whether there are old agents entered in the
NT/Win2k Registry and removes them.
for SR's not listed in this section please see
the list of symptoms
PHSS_24051:
- SR: 8606171814
A new command line option "/nonwdrives" is added for
itodiag.exe. When sepcifying this option for itodiag.exe
it doesn't collect information about name, file system
and total and free disk space of any mapped network
drives.
- SR: B555009756
The handling of special characters like "<" and ">" is
changed when a "\<" is found in the text for an automatic
action the behavior depends on the next ">" when this
character is masked with "\" as well everything is taken
as normal text, otherwise a variable is searched.
- SR: B555010449
The implementation of the deinstallation assumed that
these keys are always used by other applications as well.
Therefore they were not removed. Now it is checked
whether there are other keys/values below this
registration keys and if not they are removed.
for SR's not listed in this section please see
the list of symptoms
PHSS_22884:
- The ITO agent can now run as non 'HP ITO account' user.
This also includes the 'SYSTEM' account.
Installation instruction:
Use the manual installation. Before calling the
'opc_inst.bat' script, an additional entry can be added to
the 'opcsetup.inf' file to specify the run user for the
agent:
[Agent User]
SYSTEM
Instead of 'SYSTEM', any other name could be specified. In
this case the user account is created.
If 'SYSTEM' is given, no user account is created (no
'opc_op' either).
NOTE: User names may not contain space characters.
If a user name is specified in 'opcsetup.inf', the agent
will be installed using this account name, no matter if
there was already an agent installed using another
account.
If a different user is specified in 'opcsetup.inf', the
account created by the existing agent is not removed but
left on the system. It has to be removed manually.
If no user name is specified in 'opcsetup.inf', the
installation will check if there is already an agent
installed. If it finds one, the same user will be used.
If a user is specified or found to be used by an old
agent, and the password specified was not correct for this
account, the user is removed and re-created. It has the
same name afterwards but a different internal user ID.
Applications:
-------------
- All applications configured to run as 'opc_op' or
'HP ITO account' have to be changed to specify a user
that exists on the system.
- All monitoring executables will be run as the specified
account. This might restrict some of the access rights
to monitored applications.
- The 'SYSTEM' account does not have any network access
capabilities.
Remote installation:
--------------------
- On Domain Controllers there is the Installation Server
service that executes the installation on remote systems
in this domain. If this service is modified to run as
'SYSTEM', the remote installation is not possible at all
(the 'SYSTEM' account does not have any access rights
for remote systems).
- If remote execution is wanted, the Installation Server
service can be configured to run as a domain user that
has Domain Admin user rights.
PHSS_22009:
check the list of the symptoms
SR:
R555011075 R555003313 B555011594 B555011540 B555011510
B555011497 B555011436 B555011422 B555011256 B555011108
B555010980 B555010948 B555010879 B555010819 B555010620
B555010563 B555010449 B555010324 B555010186 B555010038
B555010012 B555009756 B555009745 B555009740 B555009712
B555009553 B555009481 B555009412 B555009388 B555009360
B555009201 B555009193 B555009153 B555009120 B555009099
B555008912 B555008754 B555008729 B555008663 B555008526
B555008314 B555008309 B555008180 B555007966 B555007883
B555007847 B555007840 B555007752 B555007619 B555007602
B555007549 B555007478 B555007056 B555005125 8606214799
8606213476 8606212295 8606208283 8606206616 8606205415
8606188773 8606183491 8606181988 8606180891 8606179902
8606171814 8606161695 8606140211
Patch Files:
OVOPC-CLT.OVOPC-NT-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/opc_pkg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/unzip.exe
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/unzip.txt
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/opc_inst.bat
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/opc_pre.bat
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/opcsetup.inf
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/monitor/itoprocs.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/monitor/sms_chk.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/monitor/mf_service.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/mfluse.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itomserv.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itoreg.cfg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/opcdf.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/opcps.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itodiag.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itokill.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itoreg.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itosdown.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itouser.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/opcprfls.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/mf_app.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
AgentPlatform
what(1) Output:
OVOPC-CLT.OVOPC-NT-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/opc_pkg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/unzip.exe:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/unzip.txt:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/opc_inst.bat:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/opc_pre.bat:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/opcsetup.inf:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/monitor/itoprocs.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/monitor/sms_chk.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/monitor/mf_service.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/mfluse.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itomserv.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itoreg.cfg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/opcdf.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/opcps.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itodiag.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itokill.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itoreg.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itosdown.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/itouser.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/opcprfls.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.08/RPC_DCE_TCP/cmds/mf_app.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
AgentPlatform:
None
cksum(1) Output:
OVOPC-CLT.OVOPC-NT-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
155291690 6227396 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/opc_pkg.Z
3162183940 113152 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/unzip.exe
1939298735 508 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/unzip.txt
4115030442 1664 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/opc_inst.bat
2405569119 1715 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/opc_pre.bat
3935660743 133 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/opcsetup.inf
2308228395 5969 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/monitor/
itoprocs.exe.Z
345227238 132 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/monitor/
sms_chk.bat.Z
3876037765 129 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/monitor/
mf_service.bat.Z
1725316368 3926 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
mfluse.exe.Z
3449332142 49794 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
itomserv.exe.Z
1586237090 188 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
itoreg.cfg.Z
2003580432 38 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
opcdf.bat.Z
849569434 41 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
opcps.bat.Z
87736109 22377 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
itodiag.exe.Z
3971048870 6866 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
itokill.exe.Z
4127818733 13779 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
itoreg.exe.Z
399848878 46674 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
itosdown.exe.Z
2790118563 51630 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
itouser.exe.Z
1677651285 10113 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
opcprfls.exe.Z
1588307382 751 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.08/RPC_DCE_TCP/cmds/
mf_app.bat.Z
650047820 6469 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/AgentPlatform
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_24051 PHSS_22884 PHSS_22009
Equivalent Patches:
ITOSOL_00113:
sparcSOL: 2.6 2.7 2.8
PHSS_25089:
s700: 10.20
s800: 10.20
Patch Package Size: 6490 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_25090
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_25090.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_25090. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_25090.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_25090.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_25090.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_25090.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
BEFORE LOADING THIS PATCH...
o It provides bug fixes and enhancements for the
VPO A.06.00 Management Server system.
o DO NOT use this patch with older releases of ITO,
for example versions A.05.00, A.05.11 or A.05.30
(A) Patch Installation Instructions
-------------------------------
(A1) Install the patch, following the standard
installation instructions.
For backing up the system before installing
a patch, you may use opc_backup(1m)
NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
ADDRESSED BY THIS PATCH IS DISTRIBUTED
(either from the VPO Administrator's GUI
or from command line using inst.sh) WHILE
RUNNING SWINSTALL.
Don't be afraid of the '-x autoreboot=true'
option above. There won't be a reboot due
to this VPO patch.
You can skip this option if you like.
NOTE: This patch must be installed on the VPO Management
Server system, NOT on an VPO Managed Node directly.
Changes will take effect on managed nodes by means of
VPO Software Distribution (using 'Force Update' if
there is already an agent installed on the managed
node). See chapter 2 of the VPO Administrator's
Reference manual for more information.
- The ITO agent can now run as non 'HP ITO account' user.
This also includes the 'SYSTEM' account.
Installation instruction:
Use the manual installation. Before calling the
'opc_inst.bat' script, an additional entry can be added to
the 'opcsetup.inf' file to specify the run user for the
agent:
[Agent User]
SYSTEM
Instead of 'SYSTEM', any other name could be specified. In
this case the user account is created.
If 'SYSTEM' is given, no user account is created (no
'opc_op' either).
NOTE: User names may not contain space characters.
If a user name is specified in 'opcsetup.inf', the agent
will be installed using this account name, no matter if
there was already an agent installed using another
account.
If a different user is specified in 'opcsetup.inf', the
account created by the existing agent is not removed but
left on the system. It has to be removed manually.
If no user name is specified in 'opcsetup.inf', the
installation will check if there is already an agent
installed. If it finds one, the same user will be used.
If a user is specified or found to be used by an old
agent, and the password specified was not correct for this
account, the user is removed and re-created. It has the
same name afterwards but a different internal user ID.
Applications:
-------------
- All applications configured to run as 'opc_op' or
'HP ITO account' have to be changed to specify a user
that exists on the system.
- All monitoring executables will be run as the specified
account. This might restrict some of the access rights
to monitored applications.
- The 'SYSTEM' account does not have any network access
capabilities.
Remote installation:
--------------------
- On Domain Controllers there is the Installation Server
service that executes the installation on remote systems
in this domain. If this service is modified to run as
'SYSTEM', the remote installation is not possible at all
(the 'SYSTEM' account does not have any access rights
for remote systems).
- If remote execution is wanted, the Installation Server
service can be configured to run as a domain user that
has Domain Admin user rights.
(B) Patch Deinstallation Instructions
---------------------------------
(B1) To deinstall the patch PHSS_25090 run swremove:
NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
ADDRESSED BY THIS PATCH IS DISTRIBUTED (either
from the ITO Administrator's GUI or from
command line using inst.sh) WHILE RUNNING
SWREMOVE.
# swremove PHSS_25090
-----End of Document ID: PHSS_25090------------------------------------------
Document ID: PHKL_25375
Date Loaded: 20011002
Title: s700_800 11.11 VM stale icache
Patch Name: PHKL_25375
Patch Description: s700_800 11.11 VM stale icache
Creation Date: 01/09/27
Post Date: 01/10/02
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_25375: ABORT
Category Tags:
defect_repair general_release critical halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25375
Symptoms:
PHKL_25375:
( SR:8606208152 CR:JAGad77330 )
During normal operation random process core dumps may occur.
Defect Description:
PHKL_25375:
( SR:8606208152 CR:JAGad77330 )
The VM subsystem was not correctly handling self-modifying
code pages that were not initially mapped with execute
access. There was a possibility that execute access could
be removed, leaving stale data in the instruction cache.
When the page was subsequently reused by another process,
it would fault on the stale instruction cache data.
Resolution:
If a page has execute access, retain the execute access when
adding a new translation. This ensures the data is flushed
from the instruction cache upon page deallocation.
SR:
8606208152
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvm-pdk.a(hdl_trans.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvm-pdk.a(hdl_trans.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvm-pdk.a(hdl_trans.o):
hdl_trans.c $Date: 2001/09/25 07:53:51 $Revision: r1
1.11/1 PATCH_11.11 (PHKL_25375)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvm-pdk.a(hdl_trans.o):
hdl_trans.c $Date: 2001/09/25 07:53:51 $Revision: r1
1.11/1 PATCH_11.11 (PHKL_25375)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
2777256603 15316 /usr/conf/lib/libvm-pdk.a(hdl_trans.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
758092797 34248 /usr/conf/lib/libvm-pdk.a(hdl_trans.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHKL_24612:
s700: 11.00
s800: 11.00
Patch Package Size: 70 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_25375
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_25375.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_25375. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_25375.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_25375.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_25375.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_25375------------------------------------------
Document ID: PHKL_25212
Date Loaded: 20011002
Title: s700_800 11.11 vm preemption point, mlock/async_io
Patch Name: PHKL_25212
Patch Description: s700_800 11.11 vm preemption point, mlock/async_io
Creation Date: 01/09/26
Post Date: 01/10/02
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
ProgSupport.C-INC,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_25212: CORRUPTION
Category Tags:
defect_repair enhancement general_release critical
corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25212
Symptoms:
PHKL_25212:
( SR:8606194602 CR:JAGad63810 )
Data corruption can occur when Hyperfabric networking
interface or async I/O driver is being used in the system.
PHKL_23944:
( SR:8606128017 CR:JAGac78818 )
If an application uses mlock or plock to lock a
large segment of system memory (i.e. a large
database application), other processes may not be
scheduled to run while the mlock/plock function is
executing. Depending on the amount of work that the
mlocking thread has to perform, time critical
functions such as realtime heartbeat process
threads may timeout. For example, applications such
as ServiceGuard may unexpectedly failover and other
appliations may suddenly show reduced response
time when a large database is being initialized.
This problem will most likely be seen on systems
with one or two processors.
Time critical process threads will not be scheduled
to run until there is an available processor.
There are instances in the kernel where a process
thread may not be scheduled to run even when it is
the highest priority process thread. This occurs
when another process thread is executing on a
processor and must complete a time consuming task
before releasing the processor. There are several
such places in the kernel; this patch addresses one
specific kernel path.
Defect Description:
PHKL_25212:
( SR:8606194602 CR:JAGad63810 )
Kernel subsystems such as the Hyperfabric Networking
Interface and Async I/O, expect to be notified about
translation changes that may occur for memory pages they
are using for DMA. The virtual memory system uses the
cluster-interconnect flag to determine if such subsystems
should be notified when the translation changes. If there
are two different kernel-locked ranges in the same
largepage, unlocking of first locked range causes the
cluster-interconnect flag for that page to be cleared
even though there is another locked range in the same
page. This could cause a DMA operation to occur on the
wrong page, resulting in data corruption.
Resolution:
A check has been added to see if there are other
kernel-locked ranges in the same largepage before
clearing the cluster-interconnect flag.
PHKL_23944:
( SR:8606128017 CR:JAGac78818 )
Long running mlock or plock kernel paths are
causing delays in scheduling of other process
threads. No other process threads can be scheduled
on these processors while the long kernel paths are
executing. The amount of work performed along these
kernel paths is propotional to the amount of memory
involved (being mlocked or plocked) and thus
impacts the delay time of waiting process threads.
This problem will most likely be seen on systems
with one or two processors when all processors are
executing along these long kernel paths.
Resolution:
This patch enables kernel preemption along the
mlock and plock kernel paths: If a process thread
has been executing within the kernel mlock or plock
paths for over a specified period of time, the
kernel will preempt this process thread and
schedule a higher priority process thread to run.
The preempted process thread will be placed back on
the run queue to resume where it left off in the
kernel once rescheduled.
The scheduler dictates the kernel execution time
allotted to a single process and the policies
governing which process priorities may preempt the
current process.
This enhancement may not necessarily improve
performance or response time for all processes as
mlock or plock may not be executing along these
preemptible paths.
SR:
8606128017 8606194602
Patch Files:
OS-Core.CORE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/conf/sys/vm_mlock.h
ProgSupport.C-INC,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/include/sys/vm_mlock.h
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvm.a(vm_clic.o)
/usr/conf/lib/libvm.a(vm_memlock.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvm.a(vm_clic.o)
/usr/conf/lib/libvm.a(vm_memlock.o)
what(1) Output:
OS-Core.CORE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/conf/sys/vm_mlock.h:
vm_mlock.h $Date: 2001/09/11 16:51:29 $Revision: r11
.11/1 PATCH_11.11 (PHKL_25212) */
ProgSupport.C-INC,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/include/sys/vm_mlock.h:
vm_mlock.h $Date: 2001/09/11 16:51:29 $Revision: r11
.11/1 PATCH_11.11 (PHKL_25212) */
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvm.a(vm_clic.o):
vm_clic.c $Date: 2001/09/11 16:50:09 $Revision: r11.
11/1 PATCH_11.11 (PHKL_25212)
/usr/conf/lib/libvm.a(vm_memlock.o):
vm_memlock.c $Date: 2001/09/11 16:52:50 $Revision: r
11.11/4 PATCH_11.11 (PHKL_25212)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvm.a(vm_clic.o):
vm_clic.c $Date: 2001/09/11 16:50:09 $Revision: r11.
11/1 PATCH_11.11 (PHKL_25212)
/usr/conf/lib/libvm.a(vm_memlock.o):
vm_memlock.c $Date: 2001/09/11 16:52:50 $Revision: r
11.11/4 PATCH_11.11 (PHKL_25212)
cksum(1) Output:
OS-Core.CORE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1006741377 12659 /usr/conf/sys/vm_mlock.h
ProgSupport.C-INC,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1006741377 12659 /usr/include/sys/vm_mlock.h
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
4007025904 4656 /usr/conf/lib/libvm.a(vm_clic.o)
2412668956 11936 /usr/conf/lib/libvm.a(vm_memlock.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
991197597 9904 /usr/conf/lib/libvm.a(vm_clic.o)
2457758331 30416 /usr/conf/lib/libvm.a(vm_memlock.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_23944
Equivalent Patches:
PHKL_23857:
s700: 11.00
s800: 11.00
Patch Package Size: 120 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_25212
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_25212.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_25212. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_25212.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_25212.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_25212.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
There are three patches providing similar kernel
preemption enhancements: PHKL_23908, PHKL_23944,
PHKL_23946. Each of these may be useful in
preventing a time critical process thread time-out.
However, these patches, installed either
individually or collectively, may not necessarily
improve performance or response time for all
processes as the process threads causing the delay
may not be executing along these preemptible paths.
Each of these patches is independent of the others;
they may be installed separately or in any
combination, and in any order. Each provides
kernel preemption for a specific long running
kernel path.
-----End of Document ID: PHKL_25212------------------------------------------
Document ID: PHKL_25210
Date Loaded: 20011002
Title: s700_800 11.00 Probe,IDDS,PM,VM,PA-8700,asyncio,T600
Patch Name: PHKL_25210
Patch Description: s700_800 11.00 Probe,IDDS,PM,VM,PA-8700,asyncio,T600
Creation Date: 01/09/27
Post Date: 01/10/02
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_25210: PANIC CORRUPTION
PHKL_25188: PANIC
PHKL_25164: PANIC
PHKL_24612: ABORT
PHKL_24457: PANIC
PHKL_24273: PANIC
The system panics when r_refcnt overflows
PHKL_24116: OTHER
Hung, Unkillable Process
PHKL_24015: PANIC
PHKL_23857: CORRUPTION
PHKL_23813: PANIC
PHKL_23812: HANG
PHKL_23406: OTHER
Hung, Unkillable Process
PHKL_23183: OTHER
A program that uses probe instruction will cause
signal handler to be removed. It will cause a
non-access reference to an invalid virtual memory
address causing SIGSEGV handler to be removed.
So, the application's signal handler is not
invoked and it does not know what to do.
PHKL_22493: PANIC
PHKL_21775: HANG
PHKL_21507: PANIC
PHKL_20439: PANIC MEMORY_LEAK
PHKL_22744: PANIC
PHKL_22549: PANIC
PHKL_22380: PANIC HANG
PHKL_22126: PANIC
PHKL_21781: PANIC CORRUPTION
PHKL_21624: HANG
PHKL_21600: PANIC
PHKL_20647: HANG
PHKL_20449: PANIC
PHKL_20223: PANIC
PHKL_21354: PANIC
PHKL_20335: CORRUPTION
PHKL_20222: MEMORY_LEAK
PHKL_20017: OTHER
Causing degradation in I/O performance of the
system.
PHKL_19314: HANG
PHKL_19201: HANG
PHKL_20836: PANIC
PHKL_20515: PANIC
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic halts_system corruption
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25210
Symptoms:
PHKL_25210:
( SR:8606216082 CR:JAGad85253 )
During normal operation, the system may experience a
"freevas: vas cnt 0, but still pointing to pregions"
panic. The panic stack trace may be similar to:
panic+0x14
freevas+0x140
freeproc+0x204
wait1+0x21c
waitpid+0x34
syscall+0x1c8
$syscallrtn+0x0
( SR:8606188767 CR:JAGad57983 )
When mmap is used with both the MAP_ANONYMOUS and MAP_GLOBAL
flags, addresses allocated are in the 3rd quadrant instead
of being in the 4th quadrant (shared quadrant) as requested
by the MAP_GLOBAL flag.
PHKL_25188:
( SR:8606194618 CR:JAGad63826 )
On K-Class and slower systems, Service Guard may TOC the
system when a process that uses more than a gigabyte of
memory exits. The stack trace of the TOC may look similar
to the following:
pdc_call+0x174
hversion_pdc_call+0xa4
diag2_ioctl+0x170c
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x1e4
syscall+0x394
syscallinit+0x54c
or
pdc_call+0x198
pa_generic_psm_pdc_rtc+0x34
psi_rtc+0xb4
checkclock+0x24
invoke_callouts_for_self+0xc0
sw_service+0xb0
mp_ext_interrupt+0x150
ihandler+0x904
splnopreempt+0x8
idle+0x504
swidle+0x20
( SR:8606137149 CR:JAGad06267 )
The system panics with a data memory protection fault when
mmap(2) is used. The stack trace would look similar to the
following:
panic+0x14
report_trap_or_int_and_panic+0x84
trap+0x4b8
nokgdb+0x8
b_sema_enqueue+0x38
<... various other entries ...>
hdl_changerange+0x238
hdl_mprotect+0x150
smmap_hole_anonymous+0x26c
smmap_common+0x3bc
smmap+0x1c0
syscall+0x9fc
$syscallrtn+0x0
PHKL_25164:
( SR:8606204721 CR:JAGad73900 )
A HPMC may occur on T600 (9000/893) systems when cache flush
code is executing. A stack trace may looks similar to the
following:
fdc_one_page_2_0+0x180
fdcache_conditionally+0x90
pdd_large_page2_0+0x1f0
pddpage+0x2d4
hdl_deletetrans+0xbc
do_deltransc+0x118
for_val2+0xb4
foreach_chunk+0x3c
hdl_detach+0x210
detachreg+0x80
kissofdeath+0x64
freethread+0x14c
thread_deallocate+0x94
thread_free+0x94
wait1+0x244
waitpid+0x38
syscall+0x200
syscallinit+0x54c
PHKL_24971:
( SR:8606195331 CR:JAGad64535 )
Doing memory management activities on a large memory segment
which was registered using asynchronous I/O driver, would
take higher number of CPU cycles.
PHKL_24826:
( SR: 8606185728 CR: JAGad54930 )
Narrow mode (32bit) HP-UX 11.00 programs cannot mmap64() any
part of a large file beyond the first 2GB.
PHKL_24612:
( SR: 8606198933 CR: JAGad68122 )
Random process core dumps.
PHKL_24457:
( SR: 8606180059, CR: JAGad49281 )
When using the asyncio driver, applications may exhibit slow
startup time.
( SR: 8606179580, CR: JAGad48804 )
A system panic occurs on process termination, if the process
had registered private memory segment with asyncio driver.
The stack trace will appear as follows:
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x84
trap+0xd9c
nokgdb+0x8
asyncdsk_close+0x94
call_open_close+0x1f8
closed+0xb0
spec_close+0x54
vn_close+0x48
vno_close+0x20
closef+0x64
exit+0x1108
psig+0x244
syscall+0x810
$syscallrtn+0x0
( SR: 8606195629, CR: JAGad64833 )
Slow application startup when using asyncio driver
( SR: 8606199485, CR: JAGad68671 )
On systems experiencing low memory conditions, applications
registering memory segments with asyncio driver may get
"Not owner" (EPERM) error.
PHKL_24273:
( SR:8606199847 CR:JAGad69033 )
A user creates a 64-bit program which mmaps a file
65536 times, then exists. It caused data page fault
in freereg() when referencing the region whose
r_refcnt overflowed since it's already freed and
its fields are not valid any more.
Stack trace looks like:
panic+0x14
report_trap_or_int_and_panic+0x84
trap+0xd9c
nokgdb+0x8
hdl_vfault+0x50
vfault+0xf8
trap+0x2a0
nokgdb+0x8
PHKL_24116:
( SR: 8606192498 DTS: JAGad61711 )
When the debugger is killed or sent a signal when trying to
attach to a process, that process will be left in a hung
state.
PHKL_24015:
( SR: 8606192072 DTS: JAGad61280 )
When using memory windows and shared memory (IPC_SHARE32)
between 32 and 64bit processes, the system may panic with
an "hdl_pfault: invalid DBD for intransit page" panic. The
stack trace may look like:
panic+0x14
hdl_pfault+0x638
pfault+0x104
trap+0x724
thandler+0xd20
PHKL_23857:
( SR: 8606178349 DTS: JAGad47576 )
Data corruption can occur when Hyperfabric networking
interface or async I/O driver is being used in the system.
PHKL_23813:
( SR: 8606188675 DTS: JAGad57891 )
When booting 11.00 on a PA-8700 system, the system panics
with the following message :
panic: set_machine_parameters_64: Unidentified cpu type
returned from PDC_MODEL
Panic stack trace:
PC-Offset Stack Trace (read down, top of stack is 1st):
panic+0x54
set_machine_parameters_64+0x1f8
rm_setmachineparams_64+0x40
DoCalllist+0x50
RDB_patch_int_trap+0xb0
End Of Stack
WARNING: Space ID hashing is disabled
PHKL_23812:
(SR: 8606183443 CR: JAGad52656)
A multi-threaded process hangs and cannot be killed. This
process will have been repeatedly mmap()ing parts of the
same file, while at the same time reading or writing to it
with the read(), write(), readv(), or writev() system calls
from a different thread. That file must also be on a JFS
file system.
The Netscape Messaging Server's smtpd process is the only
application we've seen do the particular combination of
operations required to get into this state.
PHKL_23628:
(SR: 8606146888 CR: JAGad16231)
If the process core file's size limit has been set to 0 in
setrlimit(), when the process aborts, the core processing
is incorrect.
PHKL_23406:
(SR: 8606103740 CR: JAGab70789)
(SR: 8606159451 CR: JAGad28779)
A multi-threaded process being executed over NFS can become
hung and unkillable while performing either a fork, core,
setrlimit, SIGSTOP, or debugger operations.
PHKL_23183:
(SR: 8606169539 CR: JAGad38814)
An application trying to do a PROBE instruction
results in non-access reference to an invalid
virtual memory address that causes the SIGSEGV
handler to be removed.
This makes an application program's own
error-recovery useless and results in database
crashes.
PHKL_22843:
(SR: 8606162188 CR: JAGad31504)
The output of "ps -f" shows the name of the script being
runs instead of the name of the '#!' interpreter.
(SR: 8606168950 CR: JAGad38228)
When the user exec a script w/o providing the arguments,
the kernel does not exec the shell as it should be
expected to do.
For example,
execve("./t.sh", 0) will not work.
t.sh:
~~~
#!/bin/ksh
echo t.sh script executed OK.
PHKL_22493:
(SR: 8606141875 CR: JAGad11229)
When not running as root, adb will panic the system when
an attempt is made to debug a kernel-threaded application
in which the first thread is in a ZOMBIE state.
panic: Data page fault
stack trace for event 0
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
handle_ooc_requests+0x2bc
perform_trace_request+0x260
ttrace1+0x13c
ptrace+0x78
syscall+0x480
$syscallrtn+0x0
PHKL_22032:
(SR: 8606146888 CR: JAGad16231)
Once-setuid/setgid processes could create corefiles or be
attached to with a debugger.
(SR: 8606146889 CR: JAGad16232)
IDDS generated incorrect records in certain cases
PHKL_21775:
Some processes (eg . created by Shared LVM) never get
reaped leading to proc table being filled and leading
to a system hang.
PHKL_21507:
( SR: 8606113684 CR: JAGac07198 )
system panics when doing crfree
panic: crfree: freeing free credential struct
Stack trace for crash event was :
q4> trace event 0
stack trace for event 0
crash event was a panic
panic+0x14
crfree+0xc4
kthread_shared_objects_update+0x30
syscall+0x594
$syscallrtn+0x0
PHKL_21358:
( SR: 8606132621 CR: JAGad01770 )
The Praesidium IDS/9000 product requires this patch in order
to run. This patch has no impact on systems without the
Praesidium IDS/9000 product installed and enabled.
PHKL_21350:
( SR: 8606132613 CR: JAGad01762 )
The Praesidium IDS/9000 product requires this patch in order
to run. This patch has no impact on systems without the
Praesidium IDS/9000 product installed and enabled.
PHKL_20439:
( SR: 8606109770 DTS: JAGaa45170 )
While running an MPI-based program, the system panics with a
"Data page fault" or other memory-related fault.
PHKL_20226:
( SR: 8606107525 DTS: JAGab77768 )
This patch is one of 8 patches necessary to add support
for the 3 Gb private address space feature.
PHKL_21535:
( SR: 8606100830 CR: JAGab39185 )
Application core files do not include the process' attached
shared memory segments.
PHKL_21357:
( SR: 8606132620 CR: JAGad01769 )
The Praesidium IDS/9000 product requires this patch in order
to run. This patch has no impact on systems without the
Praesidium IDS/9000 product installed and enabled.
PHKL_22744:
( SR: 8606161365 CR: JAGad30681 )
A system may experience a data page fault panic with the
following stack trace:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
thread_pcb_reinit+0x30
thread_alloc+0xe8
thread_create+0x2ac
_lwp_create+0xdc
syscall+0x480
$syscallrtn+0x0
PHKL_22549:
( SR: 8606128066 DTS: JAGab24436 )
Data page fault when trying to flush buffers
which have already been invalidated:
bwrite+0x44
bxwrite+0x44
syncip_flush_cache+01x1dc
vx_flushdev+0x14
vx_fsync+0x248
spec_fsync+0x254.
PHKL_22440:
( SR: 8606154274 CR: JAGad23592 )
When trying to attach to a process that has been swapped
out, both the tracing process and traced process hang and
remain in an unkillable state.
PHKL_22380:
(SR: 8606130240 DTS: JAGac95111)
Kernel paniced with data memory protection fault. This
could happen when using direct I/O on JFS version 3.3
or in other situations.
(SR:8606139945 DTS: JAGad09268)
MP System hang under heavy I/O load.
PHKL_22126:
( SR: 8606155209 DTS: JAGad24526 )
This patch is a replacement for the recalled patch
PHKL_21624 which addressed a system hang caused by memory
scrubber operating on shared memory segment used by the
async I/O driver. The following problems were introduced by
PHKL_21624 and are resolved by this patch.
1. System panic when both Hyperfabric networking interface
and async I/O driver are used on the same system with
PHKL_21624 installed.
2. Applications fail when trying to register shared
segments with async I/O driver. On failure errno is set to
EPERM.
( SR: 8606143996 DTS: JAGad13329 )
Excessive delay in database connect time for database user
processes.
PHKL_21781:
(SR: 8606137220 DTS: JAGad06338)
when a user application makes a large number (over 65535)
of mprotect(2) calls, it fails with ENOSPC - No space left
on device.
(SR: 8606136222 DTS: JAGad05348)
When sendfile_max is configured to be > 0, and when using
ftp or rcp to transfer data, we encounter a spinlock
deadlock panic in sendfile_hold().
A stack trace will look similar to:
panic
spin_deadlock_failure
deadlock_check
sl_pre_check
spinlock
sendfile_hold
sosendfile
sendfile
syscall
PHKL_21624:
(SR: 8606124290 DTS: JAGac39673)
Memory scrubber (memlogd) causes system hang while scrubbing
pages locked by async driver. The async driver is typically
used by database applications.
( SR: CR: JAGab16247 )
HP-UX does not support an interface that allows a driver to
lock user space memory on behalf of a user process in such
a way that prevents the user process from unlocking the
memory. Such a mechanism is required to enable DMA to user
space memory by the operating system (a driver).
PHKL_21600:
(SR: 8606134430 DTS: JAGad03565)
When using mmap with a negative offset or an offset greater
than 2^43, the system panics.
PHKL_20647:
(SR: 8606107024 DTS: JAGab76631)
System hang in b_sema_get_queue() when doing an munmap().
PHKL_20449:
(SR: 8606106816 DTS: JAGab76230)
Incorrect implementation of mmap(2) can cause system panics.
PHKL_20223:
( SR: 8606103245 DTS: JAGab69733)
The system will panic with the following message:
panic: Returning ID that is already free.
( SR: 8606107525 DTS: JAGab77768)
This patch is one of 8 patches necessary to add support
for the 3 Gb private address space feature.
PHKL_21532:
( SR: 8606131990 CR: JAGad01139 )
Approximately every 22 minutes, the system, or one cpu of a
multi-processor system, appears to hang for several minutes.
Then the problem goes away. This primarily affects larger
memory systems.
PHKL_21354:
( SR: 8606132598 CR: JAGad01747 )
After PHKL_21003 is installed on a V2500 or V2600 with at
least 24 CPUs and at least 24 GB of memory, the system fails
to boot. One symptom that has been observed is the
following message displayed during the boot process:
Error found :
- mem_toc zero error encountered.
( SR: 8606132617 CR: JAGad01766 )
The Praesidium IDS/9000 product requires this patch in order
to run. This change has no impact on systems without the
Praesidium IDS/9000 product installed and enabled.
PHKL_21024:
( SR: 8606112164 DTS: JAGab84450 )
Enhancement: Performance changes for corner case in RTSCHED
scheduling. This patch has no impact on most systems.
PHKL_21003:
( SR: 8606112473 CR: JAGab84822 )
V2500 with more than 24GB of memory and more than 24
processors takes a long time (>30min) to boot.
PHKL_20335:
( SR: 8606106466 DTS: JAGab75600)
Unlinked files within NFS filesystems sometimes leave behind
.nfsXXX files which are unremovable until after the system
is rebooted.
( SR: 8606107384 DTS: JAGab77587)
Panic or data corruption due to buffer cache buffers being
released multiple times.
( SR: 8606108724 DTS: JAGab78191)
Memory corruption after copying growing files over the
network multiple times.
PHKL_20222:
( SR: 8606107507 DTS: JAGab77743)
This patch adds support for the PA-8600 processor.
( SR: 8606107525 DTS: JAGab77768)
This patch is one of 8 patches necessary to add support for
the 3 Gb private address space feature.
PHKL_20102:
( SR: 8606106969 DTS: JAGaa45096 )
On systems with 5GB of memory or more, the system will
allocate memory for a static table that it does not use.
This affects 64-bit systems only.
PHKL_20017:
( SR: 8606104415 DTS: JAGab71916)
After installing PHKL_19314, I/O performance of the system
drops substantially.
( SR: 8606103778 CR: JAGab70853 )
64bit systems with large amount of memory (e.g. 32Gb) and
having large buffer cache (e.g. 8Gb) configured find the
syslog is flooded with the following error message:
vmunix : bufmap : rmap : ovflo, lost [xx..)(xx..]
PHKL_19314:
( SR: 4701426775 DTS: JAGab17440 )
On a system with a large number of processors (more than 14)
a hang can occur during boot and after displaying the
following messages:
Starting the STREAMS daemons-phase1
Checking root filesystem
log replay in progress
replay complete - marking super-block clean
Root check done
Create STCP device files
( SR: 8606101604 DTS: JAGab15954)
Attempting to resume from a breakpoint when running a
program under a debugger will cause the program to get a
segmentation violation. This has been seen on G-class
systems but it can occur on any system with block-tlb.
PHKL_19201:
SR: 8606100898 DTS: JAGab39707
A user sees a hang while using snapshot file systems.
Stack trace:
_swtch+0xd4
_sleep_one+0x538
vx_sleep_lock+0xd0
vx_snap_bpcopy+0xf4
vx_snap_copyblk+0x144
vx_snap_copy+0x50
vx_snap_strategy+0x280
vx_buf_strategy+0x24
bwrite+0xe0
getnewbuf+0x918
allocbuf1+0x234
brealloc1+0x5c
getblk1+0x2fc
vx_snap_getblk+0x2c
vx_snap_getblkbp+0x140
vx_snap_lookup+0x1c
vx_snap_bpcopy+0x110
vx_snap_copyblk+0x144
vx_snap_copy+0x50
vx_snap_strategy+0x280
vx_buf_strategy+0x24
bwrite+0xe0
getnewbuf+0x918
ogetblk+0x110
getblk1+0x290
vx_getblk+0x50
vx_bread+0x68
vx_iread+0x88
vx_real_iget+0x398
vx_iget+0x3c
vx_dirlook+0x23c
vx_lookup+0x120
locallookuppn+0xd4
lookuppn+0xf8
lookupname+0x40
vn_open+0x68
copen+0xd0
open+0x3c
syscall+0x480
$syscallrtn+0x0
PHKL_17038:
The system will trap 15 data page fault when tracing for
leaks without also tracing for corruption.
PHKL_20945:
( SR: 8606112164 DTS: JAGab84450 )
Enhancement: Performance changes for corner case in RTSCHED
scheduling. This patch has no impact on most systems.
PHKL_20995:
( SR: 8606127692 CR: JAGac78494 )
Programs using "memory windows" (started via setmemwindow)
will not be able to allocate more than 1 Gb of shared memory
(1 Gb total for all memory windows processes, i.e. this is
not a per process limit). This patch is a replacement for
PHKL_20227, which introduced the bug that this patch
fixes.
PHKL_20836:
( SR: 8606106781 CR: JAGab76169 )
Application issuing large amount of mmap calls to
map multiple virtual addresses to the same physical
page (using flags MAP_SHARED|MAP_FILE|MAP_FIXED)
may cause system panic with the follow stack trace:
panic: hdl_zero_page: page not mapped
panic+0x14
hdl_zero_page+0xc8
virtual_fault+0x418
vfault+0x118
trap+0x280
nokgdb+0x8
Trace on other processor shows:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xde8
nokgdb+0x8
allocpfd_from_pond+0x134
allocate_page+0x68
lgpg_vfdfill+0x4c
virtual_fault+0xc3c
vfault+0x118
trap+0x280
nokgdb+0x8
PHKL_20227:
( SR: 8606107525 CR: JAGab77768 )
This patch is one of 8 patches necessary to add support
for the 3 Gb private address space feature.
PHKL_20224:
( SR: 8606107525 CR: JAGab77768 )
This patch is one of 8 patches necessary to add support
for the 3 Gb private address space feature.
PHKL_20515:
(SR: 8606101315, CR: JAGab46368)
System hang while using async I/O module through database
applications with new large block I/O feature when system
is low on memory resources.
(SR: 8606100970, CR: JAGab39977)
Data pagefault during async I/O operations when an I/O is
being done to an unregistered (private) memory.
(SR:8606103126, CR: JAGab69473)
System hang can occur during async I/O operations when an
IO is being done to an unregistered (private) memory
segment designated by the user's IO buffer.
(SR: 8606102862, CR: JAGab68892)
Async driver can hang during async IO with requests larger
than MAXPHYS (allowing async I/O larger than MAXPHYS is a
new feature available in this patch, where MAXPHYS = 256KB).
(SR: 8606108814, CR: JAGab81517)
Async driver I/O completion notifications don't work when
used in conjunction with select(2) system call.
PHKL_20426:
When a multithreaded process does file I/O concurrently with
mmap() or munmap() on the same file, it can result in a
single process deadlock. This process is not killable.
Defect Description:
PHKL_25210:
( SR:8606216082 CR:JAGad85253 )
The vas was corrupted due to unprotected modifications of
the vas reference count on a vfork.
Resolution:
Lock the vas during modification of the vas reference
count.
( SR:8606188767 CR:JAGad57983 )
The mmap system call does not take the MAP_GLOBAL flag into
account when used in combination with the MAP_ANONYMOUS
flag.
Resolution:
Check for the MAP_GLOBAL flag in mmap when the MAP_ANONYMOUS
flag is used, and allocate the address in the proper
quadrant (4th).
PHKL_25188:
( SR:8606194618 CR:JAGad63826 )
The problem is caused by an exiting process flooding the
bus with cache flush instructions. This in turn may cause
processes executing firmware code to wait until the
exiting process is finished before continuing. If the
Service Guard process is scheduled behind the process
executing the firmware code, the Service Guard process may
not have the chance to run for many seconds, causing it to
TOC the system when it does eventually run.
Resolution:
The exiting process now does its cache flushing less
aggressively and allows processes executing firmware code to
run at the same time. If such processes are allowed to run,
the Service Guard process scheduled after those processes
will be able to maintain contact with the other Service
Guard nodes in the cluster and it will not TOC the system.
( SR:8606137149 CR:JAGad06267 )
There is an invalid boundary check in the mmap(2) system
call that allows protections to be set outside a valid range
of pages. This causes a panic when subsequent mmap(2),
mprotect(2), or munmap(2) calls are made on the same range
of adresses.
Resolution:
The mmap(2) system call now correctly checks the boundaries
of the range of adresses before applying a mprotect
operation on them.
PHKL_25164:
( SR:8606204721 CR:JAGad73900 )
This defect is caused by JAVA chip arbitration bug. This
bug favors the sequential cache flush code over memory
access requests and outstanding I/O requests (from FWSCSI)
will time out and cause an HPMC.
Resolution:
The sequential cache flush code was modified to periodically
provide a time slot for the I/O requests to finish.
PHKL_24971:
( SR:8606195331 CR:JAGad64535 )
Upon removing the last process reference to a shared memory
segment on a memory unlock, the segment is demoted from
64MB pages to 4K pages. Any subsequent attempts to manage
this segment take considerable amount of time as the
number of page management structures has now been increased
by 16K times.
Resolution:
Do not demote the largepages on doing a memory unlock.
PHKL_24826:
( SR: 8606185728 CR: JAGad54930 )
The kernel code was limited by design to allow narrow
mode mmap64() to 2GB or less only.
Resolution:
The kernel was enhanced to remove this limitation. Narrow
mode mmap64() can now map up to 4GB.
PHKL_24612:
( SR: 8606198933 CR: JAGad68122 )
The VM subsystem was not correctly handling self-modifying
code pages that were not initially mapped with execute
access. There was a possibility that execute access could
be removed, leaving stale data in the instruction cache.
When the page was subsequently reused by another process,
it would fault on the stale instruction cache data.
Resolution:
If a page has execute access, retain the execute access
when adding a new translation. This ensures the data is
flushed from the instruction cache upon page deallocation.
PHKL_24457:
( SR: 8606180059, CR: JAGad49281 )
Before starting I/O's through the asyncio driver,
applications must register shared memory segments with the
driver. As part of the registration, the driver locks the
memory. If this operation needs to be done for a very
large memory segment, the locking may take a significant
amount of time, resulting in slow application startup.
Resolution:
The async driver now supports a new device file minor number
256. If an application uses the async device file with this
new minor number, the driver will defer locking the memory
until I/O's are issued. This avoids the overhead of memory
setup time and thus reduces the application startup time.
Note: This minor number should only be used on systems that
have enough physical memory so that paging is avoided.
Paging can cause serious performance degradation with this
new enhancement. On systems where paging is an issue, this
minor number should not be used.
( SR: 8606179580, CR: JAGad48804 )
When process that registered private memory with asyncio
driver terminates, the memory management subsystem cleans
the associated data structure. The asyncio driver tries to
dereference a pointer to one of these data structures that
has already been freed causing the system to panic.
Resolution:
The driver returns bad address (EFAULT) if any application
tries to register a private memory segment.
( SR: 8606195629, CR: JAGad64833 )
The asyncio driver checks for the user access rights
twice. This duplication of access rights check
contributes to slow application startup.
Resolution:
The redundant access rights check is removed.
( SR: 8606199485, CR: JAGad68671 )
The asyncio driver propagates the wrong error code to the
application when a memory locking function fails due to
low memory conditions.
Resolution
The appropriate error code is returned to the application.
PHKL_24273:
( SR:8606199847 CR:JAGad69033 )
The system panic's while trying to mmap() more than
the maximum allowed limit of pregions to a shared
region. (limited by r_refcnt, which is of type
ushort). This was caused by r_refcnt overflow which
caused it to reset. If a program mmap's more than
this limit, the counter r_refcnt overflow which
causes the system to panic.
Resolution:
The fix is to check for the overflow and return ENOMEM.
PHKL_24116:
( SR: 8606192498 DTS: JAGad61711 )
If the debugger is interrupted while trying to attach to a
single threaded process that is sleeping uninterruptibly,
it will return to the user without unsuspending the
debuggee so the debuggee's suspend count is not decremented
and the debuggee will be suspended forever.
Resolution:
ttrace_prepare_attach() now checks the return from the
sleep of the debugger. If the sleep returns an error, we
know that the debugger has been interrupted by someone
else other than the debuggee so we decrement the suspend
count of the debuggee.
PHKL_24015:
( SR: 8606192072 DTS: JAGad61280 )
A 64bit process cannot map into a private memory window -
it can only map into the global memory window of the
32bit virtual space. A 32bit process needing to share
with a 64bit process must either be mapped into the
global memory window or the object to be shared must
be marked IPC_GLOBAL. These rules were not being
enforced, resulting in incorrect space id assignment
for shared memory (IPC_SHARE32) allocated in a private
memory window.
Resolution:
Shared memory (IPC_SHARE32) allocated in a private memory
window is now remapped into the global memory window when
sharing with a 64bit process.
PHKL_23857:
( SR: 8606178349 DTS: JAGad47576 )
Kernel sub-systems such as Hyperfabric networking
interface and async I/O expect to be notified when a
translation for a page changes that they are using
for DMA. The virtual memory system uses the
cluster-interconnect flag to determine if such sub-systems
should be notified when the translation changes. If there
are two different kernel-locked ranges in the same
largepage, the unlocking of first locked range causes the
cluster-interconnect flag for that page to be cleared, even
though there is another locked range in the same page. This
could cause a DMA operation to occur on the wrong page,
resulting in data corruption, if sub-systems continued to
do DMA on that page.
Resolution:
A check is added to see if there are other kernel-locked
ranges in the same largepage before clearing the
cluster-interconnect flag.
PHKL_23813:
( SR: 8606188675 DTS: JAGad57891 )
11.00 does not recognize the PA-8700 processor.
Additionally, the PA-8700 processor is not IO-PDIR coherent.
Resolution:
This patch, PHKL_23813, is one of three 11.00 PA-8700
enablement patches. The other 11.00 PA-8700 enablement
patches are PHKL_23814 & PHKL_23815. To support 11.00 on
PA-8700, the following changes were made :
- Added code to recognize the PA-8700 processor.
- Added code to check if non-coherent IO-PDIR is set and
performed flushes and syncs whenever IO-PDIR is changed.
- Fixed inverted space hash mask to enable the PA-8700
processor.
PHKL_23812:
(SR: 8606183443 CR: JAGad52656)
This problem was caused by a lock ordering problem between
VM and JFS. JFS can call VM while holding an inode lock;
the routines called may require a vas lock. VM can call JFS
while holding a vas lock; the routines called may require an
inode lock. If we get unlucky, we hit the same vas/inode
lock combination from both directions, and the threads
deadlock. Because the vas lock potentially held by VM is a
per process resource, this situation can only be encountered
by a multithreaded process.
Resolution:
The fix is to have the VM routine drop the vas lock before
calling the file system code; fortunately, the VM routine
can safely drop and reacquire the lock around the call ...
it was mostly holding it to avoid dropping and reacquiring
it repeatedly in a loop.
PHKL_23628:
(SR: 8606146888 CR: JAGad16231)
If the process core file's size limit has been set to 0 in
setrlimit(), when the process aborts, the core processing
is incorrect.
Resolution:
If the process core file size limit has been set to zero,
don't create a core file.
PHKL_23406:
(SR: 8606103740 CR: JAGab70789)
(SR: 8606159451 CR: JAGad28779)
A thread acquires a lock and then sleeps interruptibly. The
interruptible sleep permits the thread to be stopped. Any
other thread attempting to acquire this lock will sleep
uninterruptably until the lock is available. This
uninterruptable thread is also unkillable. This introduces
a deadlock potential in multi-threaded processes: when a
thread holding the lock, a thread desiring the lock, and a
third thread doing one of fork, setrlimit, core, SIGSTOP, or
debugger optionations, all occur at the same time in the
same process, the deadlock is reached. The only way to
resolve the deadlock is to reboot the system.
This patch is part of a set of four patches (PHKL_23406,
PHKL_23407,PHKL_23408,PHKL_23409) that enable P_NOSTOP, a
new feature that prevents a process from being unkillable.
Each patch is independantly installable. Without all four
installed, P_NOSTOP will be unavailable.
In order to prevent the process executed over NFS from
becoming unkillable, NFS must use the P_NOSTOP feature. An
NFS patch using P_NOSTOP, PHNE_23249, will be released in
Spring of 2001.
Resolution:
If a thread acquires a lock and then sleeps interruptably,
it is not permitted to be stopped if P_NOSTOP is set. This
prevents this thread from becoming unkillable and prevents
the deadlock.
PHKL_23183:
(SR: 8606169539 CR: JAGad38814)
The check to unblock the signal handler was being done
too early inside grow(). This resulted in removal of the
signal handler specified by the application program.
Resolution:
The fix is to move the unblock signal out of grow() into
hdl_vfault() which then calls grow() at a later stage.
PHKL_22843:
(SR: 8606162188 CR: JAGad31504)
When an interpreter is invoked via a shell script, the
script name is mistakenly passed to the kernel as the first
argument (argv[0) instead of the interpreter name.
Resolution:
When an interpreter was being invoked via a shell script,
we passed the interpreter to the kernel as the first
argument instead of passing user's argv[0], which is
the script name.
(SR: 8606168950 CR: JAGad38228)
When user exec a shell script w/o supplying arguments
at all, the kernel failed to account for the extra
argument for the name of the script into the number
of arguments to be passed to the kernel. Also,
it failed to pass the interpreter to the kernel as
the first argument to be executed.
Resolution:
When user exec a shell script w/o supplying arguments
at all, the kernel bumps up argc by 1, to account for
the extra argument that we will be adding later via
via the function setup_shell_argv(). It also passes
the shell name to the kernel as the first argument,
instead of the script name.
PHKL_22493:
(SR: 8606141875 CR: JAGad11229)
When the debugged process initializes each thread's
data pointer, if the thread is in a ZOMBIE state,
that thead is not initialized, leaving the data
pointer NULL. Later, adb attempts to dereference
the NULL pointer, causing a data page fault panic.
Resolution:
Initialize the data pointer for all debugged threads,
including those in a ZOMBIE state.
PHKL_22032:
(SR: 8606146888 CR: JAGad16231)
If a setuid/setgid process completely dropped privileges,
it could create a core file on a subsequent error, and could
be attached to with a debugger.
(SR: 8606146889 CR: JAGad16232)
Some process management system calls generated incorrect
IDDS records.
Resolution:
(SR: 8606146888 CR: JAGad16231)
Remember that the process was once setuid/setgid, and
disallow corefiles and debugger attaches.
(SR: 8606146889 CR: JAGad16232)
Fix the generated records.
PHKL_21775:
Resolution :PM internal function prepare_to_reap_proc in
kern_exit.c changed to reap system processes correctly .
PHKL_21507:
( SR: 8606113684 CR: JAGac07198 )
Analysis of dump showed that we are attempting to free a
credential structure but credential refrence count
is already 0 indicating it was already freed.
Resolution:
Locking of credentials operations were protected by
sched_lock so that credential operations are done properly.
PHKL_21358:
( SR: 8606132621 CR: JAGad01770 )
This patch is one of 16 patches (PHKL_21348-PHKL_21363)
required by the Praesidium IDS/9000 product. These patches
enable the collection and tracking of information from
various system calls. Unless all of the enabling patches
(or their successors) and the product are installed, and the
product is enabled, this patch has no impact on the system.
Resolution:
This patch enables the gathering of information from the
various uid and gid related system calls.
PHKL_21350:
( SR: 8606132613 CR: JAGad01762 )
This patch is one of 16 patches (PHKL_21348-PHKL_21363)
required by the Praesidium IDS/9000 product. These patches
enable the collection and tracking of information from
various system calls. Unless all of the enabling patches
(or their successors) and the product are installed, and the
product is enabled, this patch has no impact on the system.
Resolution:
This patch enables the gathering of information from the
exec*() and exit() system calls.
PHKL_20439:
( SR: 8606109770 DTS: JAGaa45170 )
In the process to process memory copy routines, there were a
number of race conditions and memory leaks. These led to
system panics.
Resolution:
Made structural changes to locking logic to avoid these
race conditions and fixed the memory leaks.
PHKL_20226:
( SR: 8606107525 DTS: JAGab77768 )
This is one of 8 patches necessary to add support for the
3 Gb private address space feature. This feature allows a
process to have a private 3rd quadrant (normally the 3rd
quadrant, which is a 1 Gb range of address space from
0x80000000 to 0xC0000000, is used for shared objects). The
chatr command must be used to enable this feature for an
executable (chatr +q3p enable <a.out>). Note that this
feature is only enabled for 32 bit processes running on the
64 bit version of HP-UX.
The other 7 patches necessary to enable this feature are
PHKL_20222, PHKL_20223, PHKL_20224, PHKL_20225, PHKL_20227,
PHKL_20228 and PHKL_20229. Each patch may be installed
independently of the others - if enabling the 3 Gb private
address space feature is not desired. If fewer than all 8
patches are installed, the 3 Gb private address space
feature will not be enabled. The code in this patch that is
part of this feature will not have any impact on the system
until all 8 patches are installed.
Resolution:
A subset of the code to support the 3 Gb private address
space feature was added. When all 8 patches are installed
the following code changes to support this feature will
have been added:
1) Code to recognize the request for a private 3rd
quadrant (Q3) during exec() of an executable.
An executable that requests a private 3rd
quadrant will be referred to as a q3p process
below.
2) Code to prevent allocation of shared objects
in q3p processes.
3) Code to allow data to extend over the 2nd/3rd
quadrant boundary for q3p processes.
4) Code to put the stack for the primary thread
in the 3rd quadrant for q3p processes.
5) Code to map a shared library into the private
address space if there is no more room in the
4th shared quadrant for q3p processes.
PHKL_21535:
( SR: 8606100830 CR: JAGab39185 )
This patch corrects application core dump behavior by
allowing dumping of a process' attached shared memory
segments to the application core file. This patch has no
impact on the system unless shared memory dumping is
enabled. See the Special Installation Instructions section
for details on how to enable shared memory dumping after
installing this patch.
A word of caution:
After shared memory dumping is enabled, the new system-wide
core dump behavior for applications will be to include
attached shared memory segments to application core files.
This may not be the desired behavior if you have
applications that use large shared memory segments running
on the system. (eg database applications). If those
applications core dump, the core files will include their
attached shared memory segments. Thus, they can be very
large files. Do not enable shared memory dumping after
installing this patch if you do not want this behavior.
Resolution:
This patch enables shared memory dumping in the coredump
generation code when kernel global variables
core_addshmem_read and/or core_addshmem_write are set to 1.
If both of these variables are set to 0, their default
value, this patch has no impact on the system.
PHKL_21357:
( SR: 8606132620 CR: JAGad01769 )
This patch is one of 16 patches (PHKL_21348-PHKL_21363)
required by the Praesidium IDS/9000 product. These patches
enable the collection and tracking of information from
various system calls. Unless all of the enabling patches
(or their successors) and the product are installed, and the
product is enabled, this patch has no impact on the system.
Resolution:
This patch enables the gathering of information from the
corefile generation code.
PHKL_22744:
( SR: 8606161365 CR: JAGad30681 )
A pregion lookup is done based on the thread id. Thread
id's are cached, so on systems with many threads configured
and running, the thread id may be stale, i.e. reused by
another thread. In this case, the wrong pregion is
returned.
Resolution:
Use the thread pregion pointer to access the pregion
instead of the thread id.
PHKL_22549:
( SR: 8606128066 DTS: JAGab24436 )
When syncing buffers for a particular device the routine
that scans the cache for dirty buffers was not checking
whether the buffers were valid. Those buffers that were
invalid would no longer have a vnode pointer associated
with them which in turn would cause a data page fault when
they were passed to bwrite().
Resolution:
The routine responsible for flushing buffers corresponding
to an individual inode will now ensure that only valid
buffers are attempted to be flushed.
PHKL_22440:
( SR: 8606154274 CR: JAGad23592 )
The kernel debug thread is responsible for receiving and
executing the debugger commands. This is a daemon thread
which is invisible to the user application and is not part
of the thread list of the proc stucuture. Hence while the
process is being swapped this thread is not put on the run
queue even if it were in run state. Since the debug thread
is not reactivated when the procces it is attached to is
swapped back in, both it and the attached process hang.
Resolution:
Explicitly start the debug thread (if it has been created)
when the process is swapped in.
PHKL_22380:
(SR: 8606130240 CR: JAGac95111)
The kernel driver creates an anonymous private mapping
with read-only protection and calls mprotect() to change
the access right to 'read-write'.
Before the dirver tries to write, it calls vaslockpages
to lock those pages down. vaslockpages did not set the
correct access right for the mprotected pages.
Resolution:
Changed kernel to set up the translation with corrent
access right.
(SR:8606139945 DTS: JAGad09268)
In the original design, when allocating/freeing a buffer,
it only does a sleep/wakeup on the list for the current
CPU. Processes sleeping from another CPU will not be
awakened. The result, seen in the dump of a hang, is
dozens of processes sleeping on an empty per-processor
queue.
Resolution:
The design has been changed as follows: When allocating
a buffer, first try to allocate from the cpu's own list,
if fail, allocate from global list, if still fail, steal
from each processor's list back to global list, then
&n