|
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-mail.external.hp.com)Date: Sun Jul 07 2002 - 10:49:21 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 800 11.X patch digest
Created: Sun Jul 7 3:05:06 PDT 2002
Table of Contents:
Document ID Title
--------------- -----------
PHSS_27371 s700_800 11.04 Virtualvault 4.5 OWS update
PHSS_27361 s700_800 11.04 Virtualvault 4.6 OWS update
PHSS_27354 s700_800 11.00 OV SA1.0X Consol Patch June2002
PHNE_26387 s700_800 11.00 ONC/NFS General Release/Performance Patch
PHSS_27367 s700_800 11.11 Shared libF90 B.11.01.12
PHSS_27366 s700_800 11.00-10 Shared libF90 B.11.01.12
PHSS_27363 s700_800 11.00-11 Fortran90 from B.11.01.40 to B.11.01.54
PHSS_27166 s700_800 11.11 Support Tool Manager Mar 02 Patch
PHSS_27107 s700_800 11.11 LIBCL patch
PHSS_27106 s700_800 11.X LIBCL patch
PHSS_27016 s700_800 11.00 OV ITO6.0X MPE Agent Patch A.06.01
PHNE_26988 s700_800 11.X RFC-NETBIOS cumulative patch Jun2002
PHKL_27351 s700_800 11.00 creat(2) ENOENT, syscall, signal, umask
PHSS_27407 s700_800 11.00 Ignite-UX make_medialif patch
PHSS_27406 s700_800 11.11 Ignite-UX make_medialif patch
PHSS_27265 s700_800 11.00 Support Tool Manager Mar 02 Patch
PHSS_27167 s700_800 11.00 Support Tool Manager Jun 2002 Patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_27371
Date Loaded: 20020704
Title: s700_800 11.04 Virtualvault 4.5 OWS update
Patch Name: PHSS_27371
Patch Description: s700_800 11.04 Virtualvault 4.5 OWS update
Creation Date: 02/06/25
Post Date: 02/07/04
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
Virtualvault A.04.50
Filesets:
VaultWS.WS-CORE,fr=A.04.50,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_27371
Symptoms:
PHSS_27371:
Apache Outside Web Server may exhibit unexpected behavior.
PHSS_27227:
1. The Outside Web Server does not set the
Connection:close header in proxy requests
or responses even though it does not support
persistence. This violates the HTTP/1.1
protocol.
PHSS_26802:
1. Apache SSL and Error log files grow
continuously when client certificates are
required.
2. The Apache server exhibits unexpected
behavior for some absolute URI GET
requests.
PHSS_26525:
1. Unexpected behavior in the outside server when
the client certificates are enabled.
PHSS_26309:
1. When the SSLSessionCache directive in
httpd.conf file for an outside server
is set to 'shmcb' the web server stops
responding after a few hours.
2. SSL cache aging does not work. Though the
browser is actively used, the user is prompted
to give the client certificate password after
the timeout(SSLSessionCacheTimeout) period.
3. User gets the http status code 200(OK) instead
of 304(Not Modified). The browser displays a
blank page instead of displaying the page in
the local cache.
PHSS_25838:
1. Apache web server reprompts for certificate
during same SSL session.
2. Apache web server can not pass client
certificate information through proxy like
previous Virtualvault versions.
PHSS_24052:
1. Outside Apache web servers do not support SpeedCard
on N, R, L, A, K and D class servers.
2. The SSLSessionCache directive does not support
shared memory (shm).
Defect Description:
PHSS_27371:
Apache Outside Web Server may exhibit unexpected behavior.
Resolution:
Corrected the Apache Outside Web Server to function
as expected.
PHSS_27227:
1. When using the proxy module (libproxy.so) in
the Outside Web Server, the proxy module does
not add in the Connection:close header for
HTTP/1.1 requests and responses as required
for HTTP proxies that do not support
persistent connections. This could cause some
clients to incorrectly assume a persistent
connection to the proxy.
Resolution:
1. Per section 14.10 of RFC2616, HTTP/1.1
applications that do not support persistent
connections MUST include the "close"
connection option in every message. Therefore,
the outside web server proxy module will include
the "close" connection header in proxy
requests and responses.
PHSS_26802:
1. During SSL negotiation with client certificates,
some browsers cause the generation of non-fatal
SSL negotiation errors that are recorded at the
logging level "error", and cause error logs to
grow continuously over time.
2. Specially constructed URIs might be allowed to
connect to listening inside processes.
Resolution:
1. Allow the web administrator to configure the
reclassification of the repetitious non-fatal
errors from the "error" level to the "warn" level.
2. A new directive is created, VVAllowAbsoluteURI,
to make the immediate propagation of absolute
URIs by the proxy module a configurable action.
PHSS_26525:
1. Unexpected behavior in the outside server when
the client certificates are enabled.
Resolution:
1. This corrects an unexpected behavior in the outside
server when the client certificates are enabled.
PHSS_26309:
1. When the SSLSessionCache directive in
httpd.conf file for an outside server
is set to 'shmcb' the web server stops
responding after a few hours.
2. SSL cache aging does not work. Though the
browser is actively used, the user is prompted
to give the client certificate password after
the timeout(SSLSessionCacheTimeout) period.
3. User gets the http status code 200(OK) instead
of 304(Not Modified). The browser displays a
blank page instead of displaying the page in
the local cache.
Resolution:
1. The webserver responds continuously under shmcb.
2. A second parameter called 'inactive' for the directive
'SSLSessionCacheTimeout' is now added that retains
the certificate information if the session is active.
3. When apache server is attempting to see if any
processing needs to be done for this request, it
correctly recognizes that the page the browser is
requesting has not been modified, but it fails to
correctly set the request status in the request
structure to the 304 condition status. We are simply
adding code to set the status before the function
returns.
PHSS_25838:
1. Apache web server reprompts for certificate
during reused SSL session after a
client/server disconnect.
2. Apache web server can not pass client
certificate information through proxy like
previous Virtualvault versions.
Resolution:
1. If the Apache server has previously
verified a client certificate and the current
session context/cache has not recorded
a verification error, the client is allowed to
continue on the session without complete
SSL session renegotiation.
2. The outside server can pass client information
via HTTP headers in proxy requests.
PHSS_24052:
1. SpeedCard support is needed on N, R, L, A, K and D class
servers. To gain support for these servers, the outside
Apache web server needs to be migrated from version
1.3.14 to version 1.3.19.
2. Currently there is no shared Memory SSLSessionCache
support.
Resolution:
1. Migrate the Apache outside web server from version
1.3.14 to 1.3.19 and include SpeedCard support.
2. Include the open source Shared Memory Library
(mm.1.1.3) to provide shared memory SSL caching
for Apache.
This patch contains files specific to the Virtualvault 4.5
release.
SR:
8606266194 8606251280 8606244998 8606238946 8606237045
8606227054 8606195978 8606256280 8606263367
Patch Files:
VaultWS.WS-CORE,fr=A.04.50,fa=HP-UX_B.11.04_32/64,v=HP:
/etc/auth/system/files.fcdb/25.patches/27227_PHSS.fcdb
/etc/auth/system/files.fcdb/25.patches/24052_PHSS.fcdb
/etc/auth/system/files.fcdb/25.patches/26525_PHSS.fcdb
/opt/vaultWS/bin/ows_create
/opt/vaultWS/install/bin/ab
/opt/vaultWS/install/bin/apxs
/opt/vaultWS/install/bin/dbmmanage
/opt/vaultWS/install/bin/htdigest
/opt/vaultWS/install/bin/htpasswd
/opt/vaultWS/install/bin/httpd
/opt/vaultWS/install/bin/logresolve
/opt/vaultWS/install/bin/rotatelogs
/opt/vaultWS/install/conf/httpd.conf
/opt/vaultWS/install/conf/httpd.conf.default
/opt/vaultWS/install/libexec/httpd.exp
/opt/vaultWS/install/libexec/libhttpd.ep
/opt/vaultWS/install/libexec/libhttpd.sl
/opt/vaultWS/install/libexec/libhttpd.sl.1
/opt/vaultWS/install/libexec/libhttpd.sl.1.3
/opt/vaultWS/install/libexec/libhttpd.sl.1.3.19
/opt/vaultWS/install/libexec/libproxy.so
/opt/vaultWS/install/libexec/libssl.so
/opt/vaultWS/install/libexec/mod_access.so
/opt/vaultWS/install/libexec/mod_actions.so
/opt/vaultWS/install/libexec/mod_alias.so
/opt/vaultWS/install/libexec/mod_asis.so
/opt/vaultWS/install/libexec/mod_auth.so
/opt/vaultWS/install/libexec/mod_auth_anon.so
/opt/vaultWS/install/libexec/mod_auth_dbm.so
/opt/vaultWS/install/libexec/mod_autoindex.so
/opt/vaultWS/install/libexec/mod_cern_meta.so
/opt/vaultWS/install/libexec/mod_cgi.so
/opt/vaultWS/install/libexec/mod_define.so
/opt/vaultWS/install/libexec/mod_digest.so
/opt/vaultWS/install/libexec/mod_dir.so
/opt/vaultWS/install/libexec/mod_env.so
/opt/vaultWS/install/libexec/mod_expires.so
/opt/vaultWS/install/libexec/mod_headers.so
/opt/vaultWS/install/libexec/mod_imap.so
/opt/vaultWS/install/libexec/mod_include.so
/opt/vaultWS/install/libexec/mod_info.so
/opt/vaultWS/install/libexec/mod_jserv.so
/opt/vaultWS/install/libexec/mod_log_config.so
/opt/vaultWS/install/libexec/mod_mime.so
/opt/vaultWS/install/libexec/mod_mime_magic.so
/opt/vaultWS/install/libexec/mod_negotiation.so
/opt/vaultWS/install/libexec/mod_rewrite.so
/opt/vaultWS/install/libexec/mod_setenvif.so
/opt/vaultWS/install/libexec/mod_speling.so
/opt/vaultWS/install/libexec/mod_status.so
/opt/vaultWS/install/libexec/mod_tga.so
/opt/vaultWS/install/libexec/mod_unique_id.so
/opt/vaultWS/install/libexec/mod_userdir.so
/opt/vaultWS/install/libexec/mod_usertrack.so
/opt/vaultWS/install/libexec/mod_vhost_alias.so
/opt/vaultWS/install/libexec/speedcard/libssl.so
/opt/vaultTS/lib/libmm.a
/opt/vaultTS/lib/libmm.la
/opt/vaultTS/lib/libmm.sl
/opt/vaultTS/lib/libmm.sl.11
/opt/vaultTS/lib/libmm.sl.11.23
what(1) Output:
VaultWS.WS-CORE,fr=A.04.50,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultWS/bin/ows_create:
(#)87 1.29.1.1 src/scripts/ows_create, vaultWS, v
aultWS_4.5 07/02/02 02:32:19 PATCH_11.04 (PH
SS_27371)
/opt/vaultWS/install/bin/ab:
None
/opt/vaultWS/install/bin/apxs:
None
/opt/vaultWS/install/bin/dbmmanage:
None
/opt/vaultWS/install/bin/htdigest:
None
/opt/vaultWS/install/bin/htpasswd:
None
/opt/vaultWS/install/bin/httpd:
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
/opt/vaultWS/install/bin/logresolve:
None
/opt/vaultWS/install/bin/rotatelogs:
None
/opt/vaultWS/install/conf/httpd.conf:
23 1.20.1.4 src/config/vvhttpd.conf, vaultWS, vaul
tWS_4.5 06/27/02 10:13:50, PHSS_27371
/opt/vaultWS/install/conf/httpd.conf.default:
23 1.20.1.4 src/config/vvhttpd.conf, vaultWS, vaul
tWS_4.5 06/27/02 10:13:50, PHSS_27371
/opt/vaultWS/install/libexec/httpd.exp:
None
/opt/vaultWS/install/libexec/libhttpd.ep:
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
/opt/vaultWS/install/libexec/libhttpd.sl:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.5 $ $Date: 01/10/26 05:44:34 $ $R
evision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.5 $ $Date: 01/10/26 05:39:42 $ $Rev
ision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.5 $ $Date: 02/06/25 12:38:40 $
$Revision: 1.7 PATCH_11.04 (PHSS_27371) $
src/apache/src/main/http_request.c, vaultWS, vaultWS
_4.5 1.4 10/26/01
$Source: src/apache/src/main/util_script.c, vaultWS,
vaultWS_4.5 $ $Date: 02/02/21 15:05:54 $ $R
evision: 1.1.1.3 PATCH_11.04 (PHSS_26309) $
/opt/vaultWS/install/libexec/libhttpd.sl.1:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.5 $ $Date: 01/10/26 05:44:34 $ $R
evision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.5 $ $Date: 01/10/26 05:39:42 $ $Rev
ision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.5 $ $Date: 02/06/25 12:38:40 $
$Revision: 1.7 PATCH_11.04 (PHSS_27371) $
src/apache/src/main/http_request.c, vaultWS, vaultWS
_4.5 1.4 10/26/01
$Source: src/apache/src/main/util_script.c, vaultWS,
vaultWS_4.5 $ $Date: 02/02/21 15:05:54 $ $R
evision: 1.1.1.3 PATCH_11.04 (PHSS_26309) $
/opt/vaultWS/install/libexec/libhttpd.sl.1.3:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.5 $ $Date: 01/10/26 05:44:34 $ $R
evision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.5 $ $Date: 01/10/26 05:39:42 $ $Rev
ision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.5 $ $Date: 02/06/25 12:38:40 $
$Revision: 1.7 PATCH_11.04 (PHSS_27371) $
src/apache/src/main/http_request.c, vaultWS, vaultWS
_4.5 1.4 10/26/01
$Source: src/apache/src/main/util_script.c, vaultWS,
vaultWS_4.5 $ $Date: 02/02/21 15:05:54 $ $R
evision: 1.1.1.3 PATCH_11.04 (PHSS_26309) $
/opt/vaultWS/install/libexec/libhttpd.sl.1.3.19:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.5 $ $Date: 01/10/26 05:44:34 $ $R
evision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.5 $ $Date: 01/10/26 05:39:42 $ $Rev
ision: 1.8 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.5 $ $Date: 01/11/06 03:58:37 $ $Rev
ision: 1.25 PATCH_11.04 (PHSS_24052) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.5 $ $Date: 02/06/25 12:38:40 $
$Revision: 1.7 PATCH_11.04 (PHSS_27371) $
src/apache/src/main/http_request.c, vaultWS, vaultWS
_4.5 1.4 10/26/01
$Source: src/apache/src/main/util_script.c, vaultWS,
vaultWS_4.5 $ $Date: 02/02/21 15:05:54 $ $R
evision: 1.1.1.3 PATCH_11.04 (PHSS_26309) $
/opt/vaultWS/install/libexec/libproxy.so:
$Source: src/apache/src/modules/proxy/mod_proxy.c, v
aultWS, vaultWS_4.5 $ $Date: 02/04/19 10:55:
27 $ $Revision: 1.6.1.3 PATCH_11.04 (PHSS_26
802) $
$Source: src/apache/src/modules/proxy/proxy_http.c,
vaultWS, vaultWS_4.5 $ $Date: 02/06/05 09:04
:44 $ $Revision: 1.9.1.2 PATCH_11.04 (PHSS_2
7227) $
src/apache/src/modules/proxy/proxy_http.c, vaultWS,
vaultWS_4.5 1.9.1.2 06/05/02
/opt/vaultWS/install/libexec/libssl.so:
$Source: src/apache/src/modules/ssl/mod_ssl.c, vault
WS, vaultWS_4.5 $ $Date: 02/04/12 11:34:37 $
$Revision: 1.4 PATCH_11.04 (PHSS_26802) $
mod_ssl/2.8.2
src/apache/src/modules/ssl/mod_ssl.c, vaultWS, vault
WS_4.5 1.4 04/12/02
$Source: src/apache/src/modules/ssl/ssl_engine_confi
g.c, vaultWS, vaultWS_4.5 $ $Date: 02/04/11
17:19:17 $ $Revision: 1.4.1.3 PATCH_11.04 (P
HSS_26802) $
src/apache/src/modules/ssl/ssl_engine_config.c, vaul
tWS, vaultWS_4.5 1.4.1.3 04/11/02
$Source: src/apache/src/modules/ssl/ssl_engine_init.
c, vaultWS, vaultWS_4.5 $ $Date: 02/02/07 23
:02:30 $ $Revision: 1.2 PATCH_11.04 (PHSS_26
309) $
src/apache/src/modules/ssl/ssl_engine_init.c, vaultW
S, vaultWS_4.5 1.2 02/07/02
$Source: src/apache/src/modules/ssl/ssl_engine_kerne
l.c, vaultWS, vaultWS_4.5 $ $Date: 02/04/11
17:44:10 $ $Revision: 1.2.1.2 PATCH_11.04 (P
HSS_26802) $
$Source: src/apache/src/modules/ssl/ssl_engine_io.c,
vaultWS, vaultWS_4.5 $ $Date: 02/04/11 17:3
6:03 $ $Revision: 1.2 PATCH_11.04 (PHSS_2680
2) $
src/apache/src/modules/ssl/ssl_engine_io.c, vaultWS,
vaultWS_4.5 1.2 04/11/02
$Source: src/apache/src/modules/ssl/ssl_engine_mutex
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:31:00 $ $Revision: 1.5 PATCH_11.04 (PHSS_2
4052) $
$Source: src/apache/src/modules/ssl/ssl_engine_pphra
se.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03
08:26:52 $ $Revision: 1.9 PATCH_11.04 (PHSS
_24052) $
src/apache/src/modules/ssl/ssl_engine_pphrase.c, vau
ltWS, vaultWS_4.5 1.9 05/03/01
$Source: src/apache/src/modules/ssl/ssl_scache.c, va
ultWS, vaultWS_4.5 $ $Date: 01/05/03 08:32:5
8 $ $Revision: 1.4 PATCH_11.04 (PHSS_24052)
$
$Source: src/apache/src/modules/ssl/ssl_scache_dbm.c
, vaultWS, vaultWS_4.5 $ $Date: 02/03/05 09:
50:39 $ $Revision: 1.6 PATCH_11.04 (PHSS_265
25) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmht
.c, vaultWS, vaultWS_4.5 $ $Date: 02/03/05 0
9:50:41 $ $Revision: 1.6 PATCH_11.04 (PHSS_2
6525) $
src/apache/src/modules/ssl/ssl_scache_shmht.c, vault
WS, vaultWS_4.5 1.6 03/05/02
$Source: src/apache/src/modules/ssl/ssl_scache_shmcb
.c, vaultWS, vaultWS_4.5 $ $Date: 02/02/20 1
2:03:50 $ $Revision: 1.6 PATCH_11.04 (PHSS_2
6309) $
src/apache/src/modules/ssl/ssl_scache_shmcb.c, vault
WS, vaultWS_4.5 1.6 02/20/02
$Source: src/apache/src/modules/ssl/ssl_util_table.c
, vaultWS, vaultWS_4.5 $ $Date: 02/02/07 23:
02:34 $ $Revision: 1.2.1.1 PATCH_11.04 (PHSS
_26309) $
src/apache/src/modules/ssl/ssl_util_table.c, vaultWS
, vaultWS_4.5 1.2.1.1 02/07/02
/opt/vaultWS/install/libexec/mod_access.so:
None
/opt/vaultWS/install/libexec/mod_actions.so:
None
/opt/vaultWS/install/libexec/mod_alias.so:
None
/opt/vaultWS/install/libexec/mod_asis.so:
None
/opt/vaultWS/install/libexec/mod_auth.so:
None
/opt/vaultWS/install/libexec/mod_auth_anon.so:
None
/opt/vaultWS/install/libexec/mod_auth_dbm.so:
None
/opt/vaultWS/install/libexec/mod_autoindex.so:
None
/opt/vaultWS/install/libexec/mod_cern_meta.so:
None
/opt/vaultWS/install/libexec/mod_cgi.so:
None
/opt/vaultWS/install/libexec/mod_define.so:
None
/opt/vaultWS/install/libexec/mod_digest.so:
None
/opt/vaultWS/install/libexec/mod_dir.so:
None
/opt/vaultWS/install/libexec/mod_env.so:
None
/opt/vaultWS/install/libexec/mod_expires.so:
None
/opt/vaultWS/install/libexec/mod_headers.so:
None
/opt/vaultWS/install/libexec/mod_imap.so:
None
/opt/vaultWS/install/libexec/mod_include.so:
None
/opt/vaultWS/install/libexec/mod_info.so:
None
/opt/vaultWS/install/libexec/mod_jserv.so:
None
/opt/vaultWS/install/libexec/mod_log_config.so:
None
/opt/vaultWS/install/libexec/mod_mime.so:
None
/opt/vaultWS/install/libexec/mod_mime_magic.so:
None
/opt/vaultWS/install/libexec/mod_negotiation.so:
None
/opt/vaultWS/install/libexec/mod_rewrite.so:
$Source: src/apache/src/modules/standard/mod_rewrite
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:29:12 $ $Revision: 1.6 PATCH_11.04 (PHSS_2
4052) $
/opt/vaultWS/install/libexec/mod_setenvif.so:
None
/opt/vaultWS/install/libexec/mod_speling.so:
None
/opt/vaultWS/install/libexec/mod_status.so:
None
/opt/vaultWS/install/libexec/mod_tga.so:
93 1.13.1.3 src/gateway/cgi2/iolib/io.c, vaultTS,
vaultTS_4.5 06/24/99 11:25:36
/opt/vaultWS/install/libexec/mod_unique_id.so:
None
/opt/vaultWS/install/libexec/mod_userdir.so:
None
/opt/vaultWS/install/libexec/mod_usertrack.so:
None
/opt/vaultWS/install/libexec/mod_vhost_alias.so:
None
/etc/auth/system/files.fcdb/25.patches/27227_PHSS.fcdb:
27227_PHSS.fcdb, vaultWS, vaultWS_4.5 1.1 06/06/02
/etc/auth/system/files.fcdb/25.patches/24052_PHSS.fcdb:
src/host/24052_PHSS.fcdb, vaultWS, vaultWS_4.5 1.2
03/21/02
/etc/auth/system/files.fcdb/25.patches/26525_PHSS.fcdb:
src/host/26525_PHSS.fcdb, vaultWS, vaultWS_4.5 1.1
03/21/02
/opt/vaultWS/install/libexec/speedcard/libssl.so:
$Source: src/apache/src/modules/ssl/mod_ssl.c, vault
WS, vaultWS_4.5 $ $Date: 02/04/12 11:34:37 $
$Revision: 1.4 PATCH_11.04 (PHSS_26802) $
mod_ssl/2.8.2
src/apache/src/modules/ssl/mod_ssl.c, vaultWS, vault
WS_4.5 1.4 04/12/02
$Source: src/apache/src/modules/ssl/ssl_engine_confi
g.c, vaultWS, vaultWS_4.5 $ $Date: 02/04/11
17:19:17 $ $Revision: 1.4.1.3 PATCH_11.04 (P
HSS_26802) $
src/apache/src/modules/ssl/ssl_engine_config.c, vaul
tWS, vaultWS_4.5 1.4.1.3 04/11/02
$Source: src/apache/src/modules/ssl/ssl_engine_init.
c, vaultWS, vaultWS_4.5 $ $Date: 02/02/07 23
:02:30 $ $Revision: 1.2 PATCH_11.04 (PHSS_26
309) $
src/apache/src/modules/ssl/ssl_engine_init.c, vaultW
S, vaultWS_4.5 1.2 02/07/02
$Source: src/apache/src/modules/ssl/ssl_engine_kerne
l.c, vaultWS, vaultWS_4.5 $ $Date: 02/04/11
17:44:10 $ $Revision: 1.2.1.2 PATCH_11.04 (P
HSS_26802) $
$Source: src/apache/src/modules/ssl/ssl_engine_io.c,
vaultWS, vaultWS_4.5 $ $Date: 02/04/11 17:3
6:03 $ $Revision: 1.2 PATCH_11.04 (PHSS_2680
2) $
src/apache/src/modules/ssl/ssl_engine_io.c, vaultWS,
vaultWS_4.5 1.2 04/11/02
$Source: src/apache/src/modules/ssl/ssl_engine_mutex
.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03 0
8:31:00 $ $Revision: 1.5 PATCH_11.04 (PHSS_2
4052) $
$Source: src/apache/src/modules/ssl/ssl_engine_pphra
se.c, vaultWS, vaultWS_4.5 $ $Date: 01/05/03
08:26:52 $ $Revision: 1.9 PATCH_11.04 (PHSS
_24052) $
src/apache/src/modules/ssl/ssl_engine_pphrase.c, vau
ltWS, vaultWS_4.5 1.9 05/03/01
$Source: src/apache/src/modules/ssl/ssl_scache.c, va
ultWS, vaultWS_4.5 $ $Date: 01/05/03 08:32:5
8 $ $Revision: 1.4 PATCH_11.04 (PHSS_24052)
$
$Source: src/apache/src/modules/ssl/ssl_scache_dbm.c
, vaultWS, vaultWS_4.5 $ $Date: 02/03/05 09:
50:39 $ $Revision: 1.6 PATCH_11.04 (PHSS_265
25) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmht
.c, vaultWS, vaultWS_4.5 $ $Date: 02/03/05 0
9:50:41 $ $Revision: 1.6 PATCH_11.04 (PHSS_2
6525) $
src/apache/src/modules/ssl/ssl_scache_shmht.c, vault
WS, vaultWS_4.5 1.6 03/05/02
$Source: src/apache/src/modules/ssl/ssl_scache_shmcb
.c, vaultWS, vaultWS_4.5 $ $Date: 02/02/20 1
2:03:50 $ $Revision: 1.6 PATCH_11.04 (PHSS_2
6309) $
src/apache/src/modules/ssl/ssl_scache_shmcb.c, vault
WS, vaultWS_4.5 1.6 02/20/02
$Source: src/apache/src/modules/ssl/ssl_util_table.c
, vaultWS, vaultWS_4.5 $ $Date: 02/02/07 23:
02:34 $ $Revision: 1.2.1.1 PATCH_11.04 (PHSS
_26309) $
src/apache/src/modules/ssl/ssl_util_table.c, vaultWS
, vaultWS_4.5 1.2.1.1 02/07/02
/opt/vaultTS/lib/libmm.a:
MM 1.1.3 (01-Jul-2000)
/opt/vaultTS/lib/libmm.la:
None
/opt/vaultTS/lib/libmm.sl:
MM 1.1.3 (01-Jul-2000)
/opt/vaultTS/lib/libmm.sl.11:
MM 1.1.3 (01-Jul-2000)
/opt/vaultTS/lib/libmm.sl.11.23:
MM 1.1.3 (01-Jul-2000)
cksum(1) Output:
VaultWS.WS-CORE,fr=A.04.50,fa=HP-UX_B.11.04_32/64,v=HP:
569980634 17792 /opt/vaultWS/bin/ows_create
1262687632 49259 /opt/vaultWS/install/bin/ab
4197983697 21154 /opt/vaultWS/install/bin/apxs
3811743186 10939 /opt/vaultWS/install/bin/dbmmanage
2658800727 36960 /opt/vaultWS/install/bin/htdigest
3650905660 73896 /opt/vaultWS/install/bin/htpasswd
4220021220 57446 /opt/vaultWS/install/bin/httpd
2174728145 24642 /opt/vaultWS/install/bin/logresolve
105961534 28733 /opt/vaultWS/install/bin/rotatelogs
137152192 49071 /opt/vaultWS/install/conf/httpd.conf
137152192 49071 /opt/vaultWS/install/conf/httpd.conf.default
779068524 8304 /opt/vaultWS/install/libexec/httpd.exp
71333771 24637 /opt/vaultWS/install/libexec/libhttpd.ep
1436058028 1059469 /opt/vaultWS/install/libexec/libhttpd.sl
1436058028 1059469 /opt/vaultWS/install/libexec/
libhttpd.sl.1
1436058028 1059469 /opt/vaultWS/install/libexec/
libhttpd.sl.1.3
1436058028 1059469 /opt/vaultWS/install/libexec/
libhttpd.sl.1.3.19
2611906110 221481 /opt/vaultWS/install/libexec/libproxy.so
2708374658 2687758 /opt/vaultWS/install/libexec/libssl.so
2993986834 20509 /opt/vaultWS/install/libexec/mod_access.so
4152718123 16406 /opt/vaultWS/install/libexec/mod_actions.so
4275050123 20526 /opt/vaultWS/install/libexec/mod_alias.so
528682144 12299 /opt/vaultWS/install/libexec/mod_asis.so
3683990203 20506 /opt/vaultWS/install/libexec/mod_auth.so
3794250761 12321 /opt/vaultWS/install/libexec/
mod_auth_anon.so
1677672897 20504 /opt/vaultWS/install/libexec/
mod_auth_dbm.so
319691963 65627 /opt/vaultWS/install/libexec/
mod_autoindex.so
2798274003 20509 /opt/vaultWS/install/libexec/
mod_cern_meta.so
210476963 32807 /opt/vaultWS/install/libexec/mod_cgi.so
1024512365 20509 /opt/vaultWS/install/libexec/mod_define.so
3044190853 24605 /opt/vaultWS/install/libexec/mod_digest.so
1669345403 16404 /opt/vaultWS/install/libexec/mod_dir.so
2265636880 12312 /opt/vaultWS/install/libexec/mod_env.so
3842010989 24607 /opt/vaultWS/install/libexec/mod_expires.so
2069023418 12312 /opt/vaultWS/install/libexec/mod_headers.so
839220256 45112 /opt/vaultWS/install/libexec/mod_imap.so
3166651693 90215 /opt/vaultWS/install/libexec/mod_include.so
2843506832 40997 /opt/vaultWS/install/libexec/mod_info.so
29912906 188828 /opt/vaultWS/install/libexec/mod_jserv.so
515123627 45190 /opt/vaultWS/install/libexec/
mod_log_config.so
149726227 36921 /opt/vaultWS/install/libexec/mod_mime.so
1556557527 53334 /opt/vaultWS/install/libexec/
mod_mime_magic.so
585247284 69742 /opt/vaultWS/install/libexec/
mod_negotiation.so
1993355012 151761 /opt/vaultWS/install/libexec/
mod_rewrite.so
3452651814 20511 /opt/vaultWS/install/libexec/
mod_setenvif.so
2440657301 24605 /opt/vaultWS/install/libexec/mod_speling.so
1153359535 45085 /opt/vaultWS/install/libexec/mod_status.so
3542298083 49222 /opt/vaultWS/install/libexec/mod_tga.so
2614241357 20497 /opt/vaultWS/install/libexec/
mod_unique_id.so
515178063 20498 /opt/vaultWS/install/libexec/mod_userdir.so
462504356 28708 /opt/vaultWS/install/libexec/
mod_usertrack.so
3544776369 20506 /opt/vaultWS/install/libexec/
mod_vhost_alias.so
2976698727 602 /etc/auth/system/files.fcdb/25.patches/
27227_PHSS.fcdb
926685209 1395 /etc/auth/system/files.fcdb/25.patches/
24052_PHSS.fcdb
4168816505 1390 /etc/auth/system/files.fcdb/25.patches/
26525_PHSS.fcdb
3488338658 2693911 /opt/vaultWS/install/libexec/speedcard/
libssl.so
3847374939 35628 /opt/vaultTS/lib/libmm.a
1063204636 648 /opt/vaultTS/lib/libmm.la
2375588202 45194 /opt/vaultTS/lib/libmm.sl
2375588202 45194 /opt/vaultTS/lib/libmm.sl.11
2375588202 45194 /opt/vaultTS/lib/libmm.sl.11.23
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_24052 PHSS_25838 PHSS_26309 PHSS_26525 PHSS_26802 PHSS_27227
Equivalent Patches:
PHSS_27361:
s700: 11.04
s800: 11.04
Patch Package Size: 8420 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_27371
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27371.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27371. 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_27371.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_27371.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27371.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27371.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_27371:
Since "shmcb" SSLSessionCache is more stable than
"shmht", it is recommended to use "shmcb" SSLSessionCache.
The user is recommended to set the SSLSessionCache to
"shmcb" in httpd.conf file manually, for the existing
outside Apache web servers.
All outside Apache web servers created after the
application of this patch, will have SSLSessionCache
directive set to "shmcb" as default.
PHSS_26802:
To permit the reclassification of the
repetitious errors from the "error" level
to the "warn" level, the directive
SSLVVDowngradeLogLevel should be set to "On"
in the VirtualHost section of the server's
configuration file. The configuration file
is usually located at
/opt/vaultWS/servers/<servname>/conf/httpd.conf,
where <servname> is the name of the server.
By default, absolute URI GET requests will be
disallowed. If it is necessary to reactivate absolute
URIs to the inside compartment, then the directives
"ProxyRequests" and "VVAllowAbsoluteURI" must both be
set to "On" in the server's configuration file.
PHSS_26309:
To allow the Apache server to continue
to use a verified client certificate even
after the session cache time elapses if
the session is active, the directive
SSLSessionCacheTimeout should include a
second parameter called 'inactive'.
PHSS_25838:
To allow the Apache server to utilize a
previously verified client certificate
in a cached/reused SSL session after a
client/server disconnect without full
SSL session renegotiation, the container
(Server, Directory or Location) that is
requiring the certificate must include
+VVOptRenegotiate in the SSLOptions
directive of that container."
-----End of Document ID: PHSS_27371------------------------------------------
Document ID: PHSS_27361
Date Loaded: 20020704
Title: s700_800 11.04 Virtualvault 4.6 OWS update
Patch Name: PHSS_27361
Patch Description: s700_800 11.04 Virtualvault 4.6 OWS update
Creation Date: 02/06/25
Post Date: 02/07/04
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
Virtualvault A.04.60
Filesets:
VaultWS.WS-CORE,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP
VaultTS.VV-CORE-CMN,fr=A.04.60,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_27361
Symptoms:
PHSS_27361:
Apache Outside Web Server may exhibit unexpected behavior.
PHSS_27228:
1. The Outside Web Server does not set the
Connection:close header in proxy requests
or responses even though it does not support
persistence. This violates the HTTP/1.1
protocol.
PHSS_27117:
Experimental OpenSSL Engine module is not provided with
Virtualvault 4.6
Defect Description:
PHSS_27361:
Apache Outside Web Server may exhibit unexpected
behavior.
Resolution:
Apache Outside Web Server has been upgraded to 1.3.26
to fix the problem.
PHSS_27228:
1. When using the proxy module (libproxy.so) in
the Outside Web Server, the proxy module does
not add in the Connection:close header for
HTTP/1.1 requests and responses as required
for HTTP proxies that do not support
persistent connections. This could cause some
clients to incorrectly assume a persistent
connection to the proxy.
Resolution:
1. Per section 14.10 of RFC2616, HTTP/1.1
applications that do not support persistent
connections MUST include the "close"
connection option in every message. Therefore,
the outside web server proxy module will include
the "close" connection header in proxy
requests and responses.
PHSS_27117:
The experimental OpenSSL Engine module required to support
cryptographic hardware devices is not provided in
Virtualvault 4.6
Resolution:
Provide a new libssl.so DSO module utilizing the
OpenSSL/mod_ssl experimental engine support for hardware
cryptographic devices for the Virtualvault.
SR:
8606266977 8606263367 8606261102
Patch Files:
VaultWS.WS-CORE,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
/etc/auth/system/files.fcdb/25.patches/27228_PHSS.fcdb
/opt/vaultWS/install/conf/httpd.conf
/etc/auth/system/files.fcdb/25.patches/27117_PHSS.fcdb
/opt/vaultWS/bin/ows_create
/opt/vaultWS/install/bin/ab
/opt/vaultWS/install/bin/apxs
/opt/vaultWS/install/bin/dbmmanage
/opt/vaultWS/install/bin/htdigest
/opt/vaultWS/install/bin/htpasswd
/opt/vaultWS/install/bin/httpd
/opt/vaultWS/install/bin/logresolve
/opt/vaultWS/install/bin/rotatelogs
/opt/vaultWS/install/libexec/ApacheJServ.jar
/opt/vaultWS/install/libexec/httpd.exp
/opt/vaultWS/install/libexec/libhttpd.ep
/opt/vaultWS/install/libexec/libhttpd.sl
/opt/vaultWS/install/libexec/libhttpd.sl.1
/opt/vaultWS/install/libexec/libhttpd.sl.1.3
/opt/vaultWS/install/libexec/libhttpd.sl.1.3.26
/opt/vaultWS/install/libexec/libproxy.so
/opt/vaultWS/install/libexec/libssl.so
/opt/vaultWS/install/libexec/mod_access.so
/opt/vaultWS/install/libexec/mod_actions.so
/opt/vaultWS/install/libexec/mod_alias.so
/opt/vaultWS/install/libexec/mod_asis.so
/opt/vaultWS/install/libexec/mod_auth.so
/opt/vaultWS/install/libexec/mod_auth_anon.so
/opt/vaultWS/install/libexec/mod_auth_dbm.so
/opt/vaultWS/install/libexec/mod_autoindex.so
/opt/vaultWS/install/libexec/mod_cern_meta.so
/opt/vaultWS/install/libexec/mod_cgi.so
/opt/vaultWS/install/libexec/mod_define.so
/opt/vaultWS/install/libexec/mod_digest.so
/opt/vaultWS/install/libexec/mod_dir.so
/opt/vaultWS/install/libexec/mod_env.so
/opt/vaultWS/install/libexec/mod_expires.so
/opt/vaultWS/install/libexec/mod_headers.so
/opt/vaultWS/install/libexec/mod_imap.so
/opt/vaultWS/install/libexec/mod_include.so
/opt/vaultWS/install/libexec/mod_info.so
/opt/vaultWS/install/libexec/mod_jserv.so
/opt/vaultWS/install/libexec/mod_log_config.so
/opt/vaultWS/install/libexec/mod_mime.so
/opt/vaultWS/install/libexec/mod_mime_magic.so
/opt/vaultWS/install/libexec/mod_negotiation.so
/opt/vaultWS/install/libexec/mod_rewrite.so
/opt/vaultWS/install/libexec/mod_setenvif.so
/opt/vaultWS/install/libexec/mod_speling.so
/opt/vaultWS/install/libexec/mod_status.so
/opt/vaultWS/install/libexec/mod_tga.so
/opt/vaultWS/install/libexec/mod_unique_id.so
/opt/vaultWS/install/libexec/mod_userdir.so
/opt/vaultWS/install/libexec/mod_usertrack.so
/opt/vaultWS/install/libexec/mod_vhost_alias.so
/opt/vaultWS/install/libexec/speedcard/libssl.so
/opt/vaultWS/install/libexec/engine/libssl.so
/opt/vaultWS/install/man/man1/dbmmanage.1
/opt/vaultWS/install/man/man1/htdigest.1
/opt/vaultWS/install/man/man1/htpasswd.1
/opt/vaultWS/install/man/man8/ab.8
/opt/vaultWS/install/man/man8/apachectl.8
/opt/vaultWS/install/man/man8/apxs.8
/opt/vaultWS/install/man/man8/httpd.8
/opt/vaultWS/install/man/man8/logresolve.8
/opt/vaultWS/install/man/man8/rotatelogs.8
VaultTS.VV-CORE-CMN,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultTS/bin/openssl
what(1) Output:
VaultWS.WS-CORE,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
/etc/auth/system/files.fcdb/25.patches/27228_PHSS.fcdb:
27228_PHSS.fcdb, vaultWS, vaultWS_4.6 1.1 06/06/02
/opt/vaultWS/install/conf/httpd.conf:
23 1.28 vvhttpd.conf, vaultWS, vaultWS_4.6 07/03/0
2 10:41:06, PHSS_27361
/etc/auth/system/files.fcdb/25.patches/27117_PHSS.fcdb:
98 1.4 src/host/27117_PHSS.fcdb, vaultWS, vaultWS_
4.6 05/24/02 10:08:31, PHSS_27117
/opt/vaultWS/bin/ows_create:
(#)87 1.33 ows_create, vaultWS, vaultWS_4.6 07/02
/02 02:21:47 PATCH_11.04 (PHSS_27361)
/opt/vaultWS/install/bin/ab:
None.
/opt/vaultWS/install/bin/apxs:
None.
/opt/vaultWS/install/bin/dbmmanage:
None.
/opt/vaultWS/install/bin/htdigest:
None.
/opt/vaultWS/install/bin/htpasswd:
None.
/opt/vaultWS/install/bin/httpd:
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:35 $ $Rev
ision: 1.32 PATCH_11.04 (PHSS_27361) $
/opt/vaultWS/install/bin/logresolve:
None.
/opt/vaultWS/install/bin/rotatelogs:
None.
/opt/vaultWS/install/libexec/ApacheJServ.jar:
None.
/opt/vaultWS/install/libexec/httpd.exp:
None.
/opt/vaultWS/install/libexec/libhttpd.ep:
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:35 $ $Rev
ision: 1.32 PATCH_11.04 (PHSS_27361) $
/opt/vaultWS/install/libexec/libhttpd.sl:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.6 $ $Date: 02/06/27 14:25:09 $ $R
evision: 1.13 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:48 $ $Rev
ision: 1.13 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_log.c, vaultWS, va
ultWS_4.6 $ $Date: 02/06/27 14:26:23 $ $Revi
sion: 1.8 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:35 $ $Rev
ision: 1.32 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.6 $ $Date: 02/06/27 15:03:45 $
$Revision: 1.4.1.5 PATCH_11.04 (PHSS_27361)
$
$Source: src/apache/src/main/util_script.c, vaultWS,
vaultWS_4.6 $ $Date: 02/06/27 14:27:16 $ $R
evision: 1.4 PATCH_11.04 (PHSS_27361) $
/opt/vaultWS/install/libexec/libhttpd.sl.1:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.6 $ $Date: 02/06/27 14:25:09 $ $R
evision: 1.13 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:48 $ $Rev
ision: 1.13 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_log.c, vaultWS, va
ultWS_4.6 $ $Date: 02/06/27 14:26:23 $ $Revi
sion: 1.8 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:35 $ $Rev
ision: 1.32 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.6 $ $Date: 02/06/27 15:03:45 $
$Revision: 1.4.1.5 PATCH_11.04 (PHSS_27361)
$
$Source: src/apache/src/main/util_script.c, vaultWS,
vaultWS_4.6 $ $Date: 02/06/27 14:27:16 $ $R
evision: 1.4 PATCH_11.04 (PHSS_27361) $
/opt/vaultWS/install/libexec/libhttpd.sl.1.3:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.6 $ $Date: 02/06/27 14:25:09 $ $R
evision: 1.13 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:48 $ $Rev
ision: 1.13 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_log.c, vaultWS, va
ultWS_4.6 $ $Date: 02/06/27 14:26:23 $ $Revi
sion: 1.8 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:35 $ $Rev
ision: 1.32 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.6 $ $Date: 02/06/27 15:03:45 $
$Revision: 1.4.1.5 PATCH_11.04 (PHSS_27361)
$
$Source: src/apache/src/main/util_script.c, vaultWS,
vaultWS_4.6 $ $Date: 02/06/27 14:27:16 $ $R
evision: 1.4 PATCH_11.04 (PHSS_27361) $
/opt/vaultWS/install/libexec/libhttpd.sl.1.3.26:
$Source: src/apache/src/main/http_config.c, vaultWS,
vaultWS_4.6 $ $Date: 02/06/27 14:25:09 $ $R
evision: 1.13 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_core.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:48 $ $Rev
ision: 1.13 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_log.c, vaultWS, va
ultWS_4.6 $ $Date: 02/06/27 14:26:23 $ $Revi
sion: 1.8 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_main.c, vaultWS, v
aultWS_4.6 $ $Date: 02/06/27 14:24:35 $ $Rev
ision: 1.32 PATCH_11.04 (PHSS_27361) $
$Source: src/apache/src/main/http_protocol.c, vaultW
S, vaultWS_4.6 $ $Date: 02/06/27 15:03:45 $
$Revision: 1.4.1.5 PATCH_11.04 (PHSS_27361)
$
$Source: src/apache/src/main/util_script.c, vaultWS,
vaultWS_4.6 $ $Date: 02/06/27 14:27:16 $ $R
evision: 1.4 PATCH_11.04 (PHSS_27361) $
/opt/vaultWS/install/libexec/libproxy.so:
$Source: src/apache/src/modules/proxy/mod_proxy.c, v
aultWS, vaultWS_4.6 $ $Date: 02/06/27 14:25:
57 $ $Revision: 1.12 PATCH_11.04 (PHSS_27361
) $
$Source: src/apache/src/modules/proxy/proxy_http.c,
vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14:25
:36 $ $Revision: 1.16 PATCH_11.04 (PHSS_2736
1) $
/opt/vaultWS/install/libexec/libssl.so:
$Source: src/apache/src/modules/ssl/mod_ssl.c, vault
WS, vaultWS_4.6 $ $Date: 02/06/27 14:27:00 $
$Revision: 1.2.1.2 PATCH_11.04 (PHSS_27361)
$
mod_ssl/2.8.9
$Source: src/apache/src/modules/ssl/ssl_engine_confi
g.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27
14:26:44 $ $Revision: 1.9.1.2 PATCH_11.04 (P
HSS_27361) $
$Source: src/apache/src/modules/ssl/ssl_engine_init.
c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14
:27:08 $ $Revision: 1.4 PATCH_11.04 (PHSS_27
361) $
$Source: src/apache/src/modules/ssl/ssl_engine_kerne
l.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27
14:26:53 $ $Revision: 1.5.1.3 PATCH_11.04 (P
HSS_27361) $
$Source: src/apache/src/modules/ssl/ssl_engine_io.c,
vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14:2
7:22 $ $Revision: 1.2 PATCH_11.04 (PHSS_2736
1) $
$Source: src/apache/src/modules/ssl/ssl_engine_mutex
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:25:23 $ $Revision: 1.4.1.4 PATCH_11.04 (PH
SS_27361) $
src/apache/src/modules/ssl/ssl_engine_pphrase.c, vau
ltWS, vaultWS_4.6 1.8.1.3 01/11/02
src/apache/src/modules/ssl/ssl_scache.c, vaultWS, va
ultWS_4.6 1.3.1.3 01/11/02
$Source: src/apache/src/modules/ssl/ssl_scache_dbm.c
, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14:
25:50 $ $Revision: 1.4.1.7 PATCH_11.04 (PHSS
_27361) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmht
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:26:16 $ $Revision: 1.3.1.9 PATCH_11.04 (PH
SS_27361) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmcb
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:26:10 $ $Revision: 1.3.1.8 PATCH_11.04 (PH
SS_27361) $
src/apache/src/modules/ssl/ssl_util_table.c, vaultWS
, vaultWS_4.6 1.6 01/24/02
/opt/vaultWS/install/libexec/mod_access.so:
None.
/opt/vaultWS/install/libexec/mod_actions.so:
None.
/opt/vaultWS/install/libexec/mod_alias.so:
None.
/opt/vaultWS/install/libexec/mod_asis.so:
None.
/opt/vaultWS/install/libexec/mod_auth.so:
None.
/opt/vaultWS/install/libexec/mod_auth_anon.so:
None.
/opt/vaultWS/install/libexec/mod_auth_dbm.so:
None.
/opt/vaultWS/install/libexec/mod_autoindex.so:
None.
/opt/vaultWS/install/libexec/mod_cern_meta.so:
None.
/opt/vaultWS/install/libexec/mod_cgi.so:
None.
/opt/vaultWS/install/libexec/mod_define.so:
None.
/opt/vaultWS/install/libexec/mod_digest.so:
None.
/opt/vaultWS/install/libexec/mod_dir.so:
None.
/opt/vaultWS/install/libexec/mod_env.so:
None.
/opt/vaultWS/install/libexec/mod_expires.so:
None.
/opt/vaultWS/install/libexec/mod_headers.so:
None.
/opt/vaultWS/install/libexec/mod_imap.so:
None.
/opt/vaultWS/install/libexec/mod_include.so:
None.
/opt/vaultWS/install/libexec/mod_info.so:
None.
/opt/vaultWS/install/libexec/mod_jserv.so:
None.
/opt/vaultWS/install/libexec/mod_log_config.so:
None.
/opt/vaultWS/install/libexec/mod_mime.so:
None.
/opt/vaultWS/install/libexec/mod_mime_magic.so:
None.
/opt/vaultWS/install/libexec/mod_negotiation.so:
None.
/opt/vaultWS/install/libexec/mod_rewrite.so:
$Source: src/apache/src/modules/standard/mod_rewrite
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:25:44 $ $Revision: 1.5.1.5 PATCH_11.04 (PH
SS_27361) $
/opt/vaultWS/install/libexec/mod_setenvif.so:
None.
/opt/vaultWS/install/libexec/mod_speling.so:
None.
/opt/vaultWS/install/libexec/mod_status.so:
None.
/opt/vaultWS/install/libexec/mod_tga.so:
$Source: src/apache/src/modules/extra/mod_tga/mod_tg
a.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27
14:24:23 $ $Revision: 1.12 PATCH_11.04 (PHSS
_27361) $
93 1.13.1.3 src/gateway/cgi2/iolib/io.c, vaultTS,
vaultTS_4.6 06/24/99 11:25:36
/opt/vaultWS/install/libexec/mod_unique_id.so:
None.
/opt/vaultWS/install/libexec/mod_userdir.so:
None.
/opt/vaultWS/install/libexec/mod_usertrack.so:
None.
/opt/vaultWS/install/libexec/mod_vhost_alias.so:
None.
/opt/vaultWS/install/libexec/speedcard/libssl.so:
$Source: src/apache/src/modules/ssl/mod_ssl.c, vault
WS, vaultWS_4.6 $ $Date: 02/06/27 14:27:00 $
$Revision: 1.2.1.2 PATCH_11.04 (PHSS_27361)
$
mod_ssl/2.8.9
$Source: src/apache/src/modules/ssl/ssl_engine_confi
g.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27
14:26:44 $ $Revision: 1.9.1.2 PATCH_11.04 (P
HSS_27361) $
$Source: src/apache/src/modules/ssl/ssl_engine_init.
c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14
:27:08 $ $Revision: 1.4 PATCH_11.04 (PHSS_27
361) $
$Source: src/apache/src/modules/ssl/ssl_engine_kerne
l.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27
14:26:53 $ $Revision: 1.5.1.3 PATCH_11.04 (P
HSS_27361) $
$Source: src/apache/src/modules/ssl/ssl_engine_io.c,
vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14:2
7:22 $ $Revision: 1.2 PATCH_11.04 (PHSS_2736
1) $
$Source: src/apache/src/modules/ssl/ssl_engine_mutex
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:25:23 $ $Revision: 1.4.1.4 PATCH_11.04 (PH
SS_27361) $
src/apache/src/modules/ssl/ssl_engine_pphrase.c, vau
ltWS, vaultWS_4.6 1.8.1.3 01/11/02
src/apache/src/modules/ssl/ssl_scache.c, vaultWS, va
ultWS_4.6 1.3.1.3 01/11/02
$Source: src/apache/src/modules/ssl/ssl_scache_dbm.c
, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14:
25:50 $ $Revision: 1.4.1.7 PATCH_11.04 (PHSS
_27361) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmht
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:26:16 $ $Revision: 1.3.1.9 PATCH_11.04 (PH
SS_27361) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmcb
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:26:10 $ $Revision: 1.3.1.8 PATCH_11.04 (PH
SS_27361) $
src/apache/src/modules/ssl/ssl_util_table.c, vaultWS
, vaultWS_4.6 1.6 01/24/02
/opt/vaultWS/install/libexec/engine/libssl.so:
$Source: src/apache/src/modules/ssl/mod_ssl.c, vault
WS, vaultWS_4.6 $ $Date: 02/06/27 14:27:00 $
$Revision: 1.2.1.2 PATCH_11.04 (PHSS_27361)
$
mod_ssl/2.8.9
$Source: src/apache/src/modules/ssl/ssl_engine_confi
g.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27
14:26:44 $ $Revision: 1.9.1.2 PATCH_11.04 (P
HSS_27361) $
$Source: src/apache/src/modules/ssl/ssl_engine_init.
c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14
:27:08 $ $Revision: 1.4 PATCH_11.04 (PHSS_27
361) $
$Source: src/apache/src/modules/ssl/ssl_engine_io.c,
vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14:2
7:22 $ $Revision: 1.2 PATCH_11.04 (PHSS_2736
1) $
$Source: src/apache/src/modules/ssl/ssl_engine_kerne
l.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27
14:26:53 $ $Revision: 1.5.1.3 PATCH_11.04 (P
HSS_27361) $
$Source: src/apache/src/modules/ssl/ssl_engine_mutex
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:25:23 $ $Revision: 1.4.1.4 PATCH_11.04 (PH
SS_27361) $
src/apache/src/modules/ssl/ssl_engine_pphrase.c, vau
ltWS, vaultWS_4.6 1.8.1.3 01/11/02
src/apache/src/modules/ssl/ssl_scache.c, vaultWS, va
ultWS_4.6 1.3.1.3 01/11/02
$Source: src/apache/src/modules/ssl/ssl_scache_dbm.c
, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 14:
25:50 $ $Revision: 1.4.1.7 PATCH_11.04 (PHSS
_27361) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmcb
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:26:10 $ $Revision: 1.3.1.8 PATCH_11.04 (PH
SS_27361) $
$Source: src/apache/src/modules/ssl/ssl_scache_shmht
.c, vaultWS, vaultWS_4.6 $ $Date: 02/06/27 1
4:26:16 $ $Revision: 1.3.1.9 PATCH_11.04 (PH
SS_27361) $
src/apache/src/modules/ssl/ssl_util_table.c, vaultWS
, vaultWS_4.6 1.6 01/24/02
/opt/vaultWS/install/man/man1/dbmmanage.1:
None.
/opt/vaultWS/install/man/man1/htdigest.1:
None.
/opt/vaultWS/install/man/man1/htpasswd.1:
None.
/opt/vaultWS/install/man/man8/ab.8:
None.
/opt/vaultWS/install/man/man8/apachectl.8:
None.
/opt/vaultWS/install/man/man8/apxs.8:
None.
/opt/vaultWS/install/man/man8/httpd.8:
None.
/opt/vaultWS/install/man/man8/logresolve.8:
None.
/opt/vaultWS/install/man/man8/rotatelogs.8:
None.
VaultTS.VV-CORE-CMN,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultTS/bin/openssl:
None.
cksum(1) Output:
VaultWS.WS-CORE,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
1479785143 602 /etc/auth/system/files.fcdb/25.patches/
27228_PHSS.fcdb
1078856035 51632 /opt/vaultWS/install/conf/httpd.conf
3730891934 805 /etc/auth/system/files.fcdb/25.patches/
27117_PHSS.fcdb
4166758644 17868 /opt/vaultWS/bin/ows_create
4114015756 81948 /opt/vaultWS/install/bin/ab
234138700 22955 /opt/vaultWS/install/bin/apxs
4148411484 10944 /opt/vaultWS/install/bin/dbmmanage
1517433823 36887 /opt/vaultWS/install/bin/htdigest
712284330 73751 /opt/vaultWS/install/bin/htpasswd
3752925612 57446 /opt/vaultWS/install/bin/httpd
82491161 24598 /opt/vaultWS/install/bin/logresolve
3572824998 28695 /opt/vaultWS/install/bin/rotatelogs
51092686 85434 /opt/vaultWS/install/libexec/ApacheJServ.jar
2282771475 8373 /opt/vaultWS/install/libexec/httpd.exp
1012205746 24637 /opt/vaultWS/install/libexec/libhttpd.ep
2510829821 1088171 /opt/vaultWS/install/libexec/libhttpd.sl
2510829821 1088171 /opt/vaultWS/install/libexec/
libhttpd.sl.1
2510829821 1088171 /opt/vaultWS/install/libexec/
libhttpd.sl.1.3
2510829821 1088171 /opt/vaultWS/install/libexec/
libhttpd.sl.1.3.26
628858434 262461 /opt/vaultWS/install/libexec/libproxy.so
3405034455 2924449 /opt/vaultWS/install/libexec/libssl.so
663953869 20509 /opt/vaultWS/install/libexec/mod_access.so
2812636452 16406 /opt/vaultWS/install/libexec/mod_actions.so
902507076 20526 /opt/vaultWS/install/libexec/mod_alias.so
1091331301 12299 /opt/vaultWS/install/libexec/mod_asis.so
3039722321 24602 /opt/vaultWS/install/libexec/mod_auth.so
1953699355 12321 /opt/vaultWS/install/libexec/
mod_auth_anon.so
1027260143 20504 /opt/vaultWS/install/libexec/
mod_auth_dbm.so
2078084152 65627 /opt/vaultWS/install/libexec/
mod_autoindex.so
3739477711 20509 /opt/vaultWS/install/libexec/
mod_cern_meta.so
3092330798 32807 /opt/vaultWS/install/libexec/mod_cgi.so
648217017 20509 /opt/vaultWS/install/libexec/mod_define.so
2004171961 24605 /opt/vaultWS/install/libexec/mod_digest.so
1979779660 16404 /opt/vaultWS/install/libexec/mod_dir.so
2404858742 12312 /opt/vaultWS/install/libexec/mod_env.so
3374676617 24607 /opt/vaultWS/install/libexec/mod_expires.so
1933309525 12312 /opt/vaultWS/install/libexec/mod_headers.so
3969520592 45112 /opt/vaultWS/install/libexec/mod_imap.so
2271461491 90215 /opt/vaultWS/install/libexec/mod_include.so
2661410469 40997 /opt/vaultWS/install/libexec/mod_info.so
2202234224 188828 /opt/vaultWS/install/libexec/mod_jserv.so
3452167443 45190 /opt/vaultWS/install/libexec/
mod_log_config.so
1526080894 36921 /opt/vaultWS/install/libexec/mod_mime.so
1251985380 53334 /opt/vaultWS/install/libexec/
mod_mime_magic.so
3459115852 73838 /opt/vaultWS/install/libexec/
mod_negotiation.so
1803452845 151761 /opt/vaultWS/install/libexec/
mod_rewrite.so
3999905470 20511 /opt/vaultWS/install/libexec/
mod_setenvif.so
3452798370 24605 /opt/vaultWS/install/libexec/mod_speling.so
924661911 49181 /opt/vaultWS/install/libexec/mod_status.so
1529927465 49222 /opt/vaultWS/install/libexec/mod_tga.so
1665072064 20500 /opt/vaultWS/install/libexec/
mod_unique_id.so
426210871 20498 /opt/vaultWS/install/libexec/mod_userdir.so
392000080 32811 /opt/vaultWS/install/libexec/
mod_usertrack.so
2187858876 20507 /opt/vaultWS/install/libexec/
mod_vhost_alias.so
4101776647 2698009 /opt/vaultWS/install/libexec/speedcard/
libssl.so
681712920 2133096 /opt/vaultWS/install/libexec/engine/
libssl.so
1380561203 6579 /opt/vaultWS/install/man/man1/dbmmanage.1
3511286166 4199 /opt/vaultWS/install/man/man1/htdigest.1
2179082024 9000 /opt/vaultWS/install/man/man1/htpasswd.1
2281762912 9253 /opt/vaultWS/install/man/man8/ab.8
59814857 5443 /opt/vaultWS/install/man/man8/apachectl.8
3529686359 12289 /opt/vaultWS/install/man/man8/apxs.8
497249655 6617 /opt/vaultWS/install/man/man8/httpd.8
2164766055 3736 /opt/vaultWS/install/man/man8/logresolve.8
1165073178 4150 /opt/vaultWS/install/man/man8/rotatelogs.8
VaultTS.VV-CORE-CMN,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
2208910851 1890500 /opt/vaultTS/bin/openssl
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_27117 PHSS_27228
Equivalent Patches:
PHSS_27371:
s700: 11.04
s800: 11.04
Patch Package Size: 12720 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_27361
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27361.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27361. 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_27361.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_27361.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27361.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27361.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_27361:
Since "shmcb" SSLSessionCache is more stable than "shmht"
(that was given as default SSLSessionCache for the
Virtualvault 4.6 release), it is recommended to use "shmcb"
SSLSessionCache.
The user is recommended to set the SSLSessionCache to
"shmcb" in httpd.conf file manually, for the existing
outside Apache web servers.
All outside Apache web servers created after the
application of this patch, will have SSLSessionCache
directive set to "shmcb" as default.
PHSS_27228:
This patch stops all executing OUTSIDE Webservers.
OUTSIDE Webservers can be restarted by issuing
the command:
/opt/vaultWS/bin/owsctl start
This command must be issued from an account that
holds hostadmin authorization.
PHSS_27117:
This patch provides a new Apache DSO libssl.so module
that contains the OpenSSL/mod_ssl EXPERIMENTAL engine code
for utilizing hardware cryptographic devices. This patch
does not modify existing servers. To utilize the
engine-enabled libssl.so in new and existing servers follow
the steps below:
1) Comment out existing LoadModule directives in the
httpd.conf for existing libssl.so modules.
2) Add or enable the LoadModule line in the httpd.conf
for the experimental engine library as:
LoadModule ssl_module libexec/engine/libssl.so
This patch also provides the openssl binary
(/opt/vaultTS/bin/openssl), that includes the SSL Engine
functionality. This binary can be used to test the
cryptographic hardware device.
For Example:
openssl speed -engine <hardware accelerator id>
Your hardware accelerator may need this command to be run
at "system outside" sensitivity level and may also need
the hardware specific shared library to be present in the
same location as the openssl binary .ie . at
/opt/vaultTS/bin
NOTE:
The Apache group and modssl projects declare code portions
as "EXPERIMENTAL" when the code portions have not been
tested in depth and are undocumented. The general code
required to support hardware cryptographic devices in the
libssl.so apache module is still bounded by "EXPERIMENTAL"
source code delimiters. Hardware cryptographic device
providers may require this "engine" version of the
libssl.so module compiled with the "EXPERIMENTAL" code in
order to access their devices. Generally, they require the
end user to compile/create the module on the destination
platform. In the case where the end user compiles/creates
the module, it would be abundantly clear to the end user
that the necessary code is declared as "EXPERIMENTAL".
The module provided in this patch is being offered to
facilitate the use of hardware cryptographic devices on
the Virtualvault. It is provided with the same
understanding of the nature of the code contained in
the module as it would mean to a end user who would
build it himself.
-----End of Document ID: PHSS_27361------------------------------------------
Document ID: PHSS_27354
Date Loaded: 20020704
Title: s700_800 11.00 OV SA1.0X Consol Patch June2002
Patch Name: PHSS_27354
Patch Description: s700_800 11.00 OV SA1.0X Consol Patch June2002
Creation Date: 02/06/26
Post Date: 02/07/04
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Service Assurance 1.0X Orbplus
Filesets:
ORB-CORE.ORB-CORE-RUN,fr=C.02.63,fa=HP-UX_B.11.00_PA2.0_700/800,v=HP
ORB-CORE.ORB-CORE-SHLIB,fr=C.02.63,fa=HP-UX_B.11.00_PA2.0_700/800,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_27354
Symptoms:
PHSS_27354:
Cumulative Consolidated Patch
PHSS_27353:
PTSfc02846:
Ams_Server core dumps in 2 Node setup.
PTSfc02002:
PM crashes when MSD_Thread create throws an exception due
to an EAGAIN error during pthread_create.
PHSS_26791:
PTSfc02523:
tp_server leaked memory and eventually core
dumped during continous operations with liborbplus.sl
patch PHSS_25239
PTSfc02615:
When Client application holding a persistent
and valid object reference,makes a request to object
locator when just starting the ORB library linked to it
will throw an OBJECT_NOT_EXIST exception instead of a
transient object.
PHSS_26513:
Consolidated Patch
PHSS_25517:
Consolidated Patch
PHSS_25239:
The ams server coredump in ungrab() call at Verizon with
the liborbplus.sl patch PHSS_22729.
PHSS_24819:
PM crashes when MSD_Thread create throws an exception due
to an EAGAIN error during pthread_create.
PHSS_24735:
The ams server came to an infinite loop at verizon with
the liborbplus.sl patch PHSS_22729
PHSS_24523:
Inconsistent time taken by the client to connect to servers
in a setup with downed servers.
PHSS_24406:
Fmsmosvr uses 100% CPU in CHO testing phase
PHSS_24048:
Accept call to the listen socket returns ENOBUF twice
PHSS_22729:
Fmsprobsvr core dumps, on calling destroy_impl.
Defect Description:
PHSS_27354:
Cumulative Consolidated Patch
Resolution:
Cumulative Consolidated Patch
PHSS_27353:
PTSfc02846:
AMS_Sever core dumps due to thread synchronisation problem,
while deleting SOA objects in 2-Node setup.Deletion of SOA
objects is not mutexed.
Resolution:
A new linked list class is introduced which is
used to store the SOA object pointers.Insertion into the
linked list takes place at SOA object construction.Deletion
of SOA objects from address space is preceded by a check of
the SOA pointer in the linked list.Only if SOA pointer is
present in Linked List, deletion of SOA object takes place.
Removal of SOA pointers from Linked List is mutexed.
PTSfc02002:
PM crashes when an MSD_Thread constructor throws an
exception due to an EAGAIN error during pthread_create().
Some of the errors could not be transient in nature.
Resolution:
Modify MSD_Thread to perform a retry internally
PHSS_26791:
PTSfc02523:
Some of the corba objects were not getting
deleted in the _SOA_Call destructor which resulted in
memory leak.
Resolution:
Changes have been done to _SOA_Call destructor
to delete all corba objects & prevent any memory leaks.
PTSfc02615:
The ORB library linked to the server side
application throws up an OBJECT_NOT_EXIST exception,
the object locator process has not yet completed the
initialization.
Resolution:
The fix makes sure that the object_locator
accepts requests only when initialization of the obj_
locator is completed and hence would not result in
throwing OBJECT_NOT_EXIST Exception.
PHSS_26513:
Consolidated Patch
PHSS_25517:
Consolidated Patch
PHSS_25239:
Defect Description:
Verizon's ams_server coredump with Horsetooth-patch6.
Resolution:
soa_localsurrogate object due to synchronization
problem.Now grabbing and ungrabbing will check whether the
object is available in soa_object_table or not.If it is not
available,it will create the object for grabbing.
PHSS_24819:
Resolution:
Modify MSD_Thread to perform a retry internally
PHSS_24735:
Resolution:
Used the overloaded function for unreference so that
the mutex is locked as per the sequence of operations
done.
PHSS_24523:
Resolution:
libiiop is fixed with changes to transport layer.
PHSS_24406:
Resolution:
libiiop is fixed with changes to transport layer.
PHSS_24048:
Resolution:
libiiop is fixed with changes to transport layer
PHSS_22729:
Resolution:
liborbplus is fixed with changes to SOA layer
SR:
F333002846 F333002002 F333002523 F333002615 F333002069
F333002033 F333001986 F333001830 F333001672 F333001077
Patch Files:
ORB-CORE.ORB-CORE-RUN,fr=C.02.63,
fa=HP-UX_B.11.00_PA2.0_700/800,v=HP:
/opt/orbplus/lbin/obj_locator
ORB-CORE.ORB-CORE-SHLIB,fr=C.02.63,
fa=HP-UX_B.11.00_PA2.0_700/800,v=HP:
/opt/orbplus/lib/liborbplus.3
/opt/orbplus/lib/libmsdthread_ptk10.3
/opt/orbplus/lib/libmsdthread_pt4.3
/opt/orbplus/lib/libiiop.3
what(1) Output:
ORB-CORE.ORB-CORE-RUN,fr=C.02.63,
fa=HP-UX_B.11.00_PA2.0_700/800,v=HP:
/opt/orbplus/lbin/obj_locator:
None
HP ORB Plus, obj_locator, revision C.02.63 (2002/06/
21 16:48:48 IST) [Za_bl029 Za_c044 hp-ux.PA2
0.11.00.aCC.ndb]
PATCH PHSS_26791, 20020425, DFIX10014
ORB-CORE.ORB-CORE-SHLIB,fr=C.02.63,
fa=HP-UX_B.11.00_PA2.0_700/800,v=HP:
/opt/orbplus/lib/liborbplus.3:
None
HP ORB Plus, liborbplus, revision C.02.63 (2002/06/2
1 16:23:58 IST) [Za_bl029 Za_c044 hp-ux.PA20
.11.00.aCC.ndb]
None
HP ORB Plus, liborblite, revision C.02.63 (2002/06/2
1 16:23:38 IST) [Za_bl029 Za_c044 hp-ux.PA20
.11.00.aCC.ndb]
PATCH PHSS_22729, 20001114, DFIX10007
PATCH PHSS_24735, 20010814, DFIX10012
PATCH PHSS_25239, 20010919, DFIX10013
PATCH PHSS_26791, 20020425, DFIX10014
PATCH PHSS_27353, 20020621, DFIX10015
HP ORB Plus, libcorba, revision C.02.63 (2002/06/21
16:17:43 IST) [Za_bl029 Za_c044 hp-ux.PA20.1
1.00.aCC.ndb]
None
HP ORB Plus, JACL, revision C.02.63 (2002/06/21 15:5
9:46 IST) [Za_bl029 Za_c044 hp-ux.PA20.11.00
.aCC.ndb]
None
/opt/orbplus/lib/libmsdthread_ptk10.3:
None
HP ORB Plus, MSD Threads (pthreads), revision C.02.6
3 (2002/06/21 15:59:13 IST) [Za_bl029 Za_c04
4 hp-ux.PA20.11.00.aCC.ndb]
PATCH PHSS_27353,20020621, DFIX10015
/opt/orbplus/lib/libmsdthread_pt4.3:
None
HP ORB Plus, MSD Threads (pthreads), revision C.02.6
3 (2002/06/21 15:59:03 IST) [Za_bl029 Za_c04
4 hp-ux.PA20.11.00.aCC.ndb]
PATCH PHSS_24819,20010806, DFIX10011
/opt/orbplus/lib/libiiop.3:
None
HP ORB Plus, libiiop.sl, revision C.02.63 (2002/06/2
1 16:33:55 IST) [Za_bl029 Za_c044 hp-ux.PA20
.11.00.aCC.ndb]
PATCH PHSS_24048,20010509, DFIX10008
PATCH PHSS_24406,20010611, DFIX10009
PATCH PHSS_24523,20010627, DFIX10010
cksum(1) Output:
ORB-CORE.ORB-CORE-RUN,fr=C.02.63,
fa=HP-UX_B.11.00_PA2.0_700/800,v=HP:
1309152756 1150976 /opt/orbplus/lbin/obj_locator
ORB-CORE.ORB-CORE-SHLIB,fr=C.02.63,
fa=HP-UX_B.11.00_PA2.0_700/800,v=HP:
1760612563 8290304 /opt/orbplus/lib/liborbplus.3
3469177049 81920 /opt/orbplus/lib/libmsdthread_ptk10.3
3699427356 90112 /opt/orbplus/lib/libmsdthread_pt4.3
911210490 548864 /opt/orbplus/lib/libiiop.3
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_27353 PHSS_26791 PHSS_26513 PHSS_25517 PHSS_25239 PHSS_24819
PHSS_24735 PHSS_24523 PHSS_24406 PHSS_24048 PHSS_22729
Equivalent Patches: None
Patch Package Size: 9960 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_27354
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27354.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27354. 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_27354.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_27354.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27354.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27354.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
BEFORE LOADING THIS PATCH...
1.Stop the GUIC.
2.Stop the GUIS using the guisstop.
3.Stop the FMS-Integrated CORBA Applcations including
the Remedy and Metrica Adaptors.
4.Stop the FMS using the fmsstop
5.Stop the Corba using ovcoba_admin_stop.
6.Stop the Notification Servers using the ovnsls_admin
- stop
7.Stop the Orbplus using the ovcorba_orb - stop
Install the patch
Restart all the processes that were shutdown earlier.
Start the Orbplus using ovcorba_orb -start
Start the Notification Servers using the ovnsls_admin
- start
Start the FMS using fmsstart
Start the FMS-Integrated CORBA Applications including
the Remedy and Metrica Adaptors.
Start the GUIS using the guisstart.
Start the GUIC using the guicstart.
In case , you are installing this patch on a HA cluster,
then please refer the release notes for more
instructions.
This patch supersedes one or more previous patches. If the
superseded patches included special installation
instructions those instructions can be found below.
PHSS_26513:
Consolidated Patch
PHSS_25517:
Consolidated Patch
-----End of Document ID: PHSS_27354------------------------------------------
Document ID: PHNE_26387
Date Loaded: 20020703
Title: s700_800 11.00 ONC/NFS General Release/Performance Patch
Patch Name: PHNE_26387
Patch Description: s700_800 11.00 ONC/NFS General Release/Performance Patch
Creation Date: 02/07/02
Post Date: 02/07/03
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
NFS.NFS-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
NFS.NFS-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
OS-Core.CORE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-CLIENT,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-PRG,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.KEY-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NISPLUS-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-SERVER,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NIS-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NIS-CLIENT,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NIS-SERVER,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
InternetSrvcs.INETSVCS-INETD,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-64ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_26387: PANIC
PHNE_25626: HANG ABORT
PHNE_25484: ABORT
PHNE_24909: HANG
PHNE_24034: HANG ABORT CORRUPTION
PHNE_23833: PANIC HANG ABORT
PHNE_23249: HANG
PHNE_22642: ABORT PANIC
PHNE_17586: PANIC
Data Page Fault
PHNE_17247: PANIC
Data Page Fault
PHNE_16599: PANIC HANG
Assertion Failure/vn_rele Panic
System hang/semaphore deadlock
PHNE_14919: CORRUPTION
Data destroyed on Server (with warning)
PHNE_14620: PANIC
Data memory protection fault
PHNE_13208: HANG
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_26387
Symptoms:
PHNE_26387:
libautofs.a
SR: 8606248624
DTS: JAGae15022
AutoFS causes a system panic with the panic string
"rm_autonode: No entry for <<address>>".
PHNE_25626:
automount
SR: 8606219527
DTS: JAGad88667
On a client system, the old automounter is trying to
access a non-existent entry in the NIS map and that is
generating an excessive number of packets over the
network which causes slow response time.
libautofs.a
SR: 8606221217
DTS: JAGad90351
The "ll" command hangs in the case of an automounted
file system if the server is down.
libnfs.a
SR: 8606237277
DTS: JAGae06322
NFS PV2 client does not properly show the quota exceeded
error.
libnfs.a
SR: 8606228306
DTS: JAGad97363
A file has an unusual timestamp when created with open(2)
using O_EXCL flag.
libnsl.1/a
SR: 8606204999
DTS: JAGad74175
The ttsyncd process loops, occupying much of the CPU
usage and causing the system to slow down.
libnsl.1/a
SR: 8606218377
DTS: JAGad87526
A multi-threaded server leaks file descriptors under
heavy load if clients are running on the same box.
libnss_nisplus.1
SR: 8606221102
DTS: JAGad90236
Reactivating a user account that has been disabled on a
trusted NIS+ client fails.
librpc.a
SR: 8606172908
DTS: JAGad42168
When an HANFS package is manually failed over
back-and-forth between two different cluster server nodes
within a period of time shorter than five minutes, then
on any NFS client which has the HANFS package filesystem
mounted over TCP, NFS access to that filesystem can
appear hung for a relatively long period of time -
usually more than four minutes, with no apparent response
from the server. Also the NFS client issues the error
message "NFS server XXXXXXX not responding still trying",
about every 30 seconds.
nsswitch.conf.4
SR: 8606188628
DTS: JAGad57842
The man page for nsswitch.conf does not reflect ldap as
an additional database source for nss backends.
rpc.rusersd
SR: 8606225120
DTS: JAGad94209
rpc.rusersd core dumps if more than 180 users have
logged in.
rpc.statd
SR: 8606224657
DTS: JAGad93745
File lock recovery fails when the server reboots if the
server has multiple network interfaces and the client
has mounted the file system with an interface name
different than the server's hostname.
rpcgen
SR: 8606230660
DTS: JAGad99710
A Server stub generated by rpcgen logs error messages to
/dev/console.
ypserv
SR: 8606226735
DTS: JAGad95797
The inetd is unable to resolve services.
PHNE_25484:
rpc.lockd
SR: 8606245747
DTS: JAGae12206
rpc.lockd core dumps with a SIGBUS error during heavy
NFS file locking.
PHNE_24909:
libnfs.a
SR: 8606222617
DTS: JAGad91730
If NFS loopback mounts are used, potentially all nfsd
processes may get stuck in an NFS deadlock situation.
libnfs.a
SR: 8606205013
DTS: JAGad74189
The mount option 'grpid' does not return the correct
'gid' value on NFS PV2 and PV3.
libnsl.1/a
SR: 8606205779
DTS: JAGad74954
The automountd (AUTOFS) hangs/cores while attempting
to automount exported FS and reports 100% CPU
utilization.
libnsl.1/a
SR: 8606212242
DTS: JAGad81430
When a customer specifies a username with leading
blank characters as an argument to nispasswd and
passwd(1), nispasswd modifies the username to
include those leading blanks in the NIS+ passwd
table and trusted table.
libnss_nisplus.1
SR: 8606216548
DTS: JAGad85717
A password expires unexpectedly in an NIS+
environment.
libnss_nisplus.1
SR: 8606219558
DTS: JAGad88698
During the login process, NIS+/trusted clients
force NIS+ users to modify their password when
their password is expired but fail to un-expire
the password when their password is changed.
Users will always be forced to modify their
password as soon as it has expired.
yppasswdd.1m
SR: 8606199444
DTS: JAGad68631
The yppasswd command updates fields other than the user
password field in an NIS map.
PHNE_24034:
automountd
SR: 8606152534
DTS: JAGad21864
AutoFS can mishandle unmounts when a server is down,
which may appear as bdf command anomalies.
automountd
SR: 8606196567
DTS: JAGad65770
AutoFS cannot unmount a cachefs type file system.
automountd
SR: 8606160777
DTS: JAGad30096
AutoFS can not unmount hfs or cdrom file system types.
libautofs.a
SR: 8606176017
DTS: JAGad45257
AutoFS directories are empty under heavy NFS load.
libautofs.a
SR: 8606193515
DTS: JAGad62727
Duplicate entries for direct AutoFS mounts show up in the
/etc/mnttab file.
libnfs.a
SR: 8606197003
DTS: JAGad66201
Walk through large size buffer cache causes file access
performance degradation.
libnfs.a
SR: 8606203242
DTS: JAGad72416
A process sequentially reading a large file across an NFS
mount runs extremely slow if, at the same time, there is
another process sequentially writing a large file to an
NFS mounted directory, and one or more biods are running
on the system.
libnfs.a
SR: 8606146332
DTS: JAGad15675
The I/O throughput on a locked file is low compared to
the throughput on an unlocked file.
libnsl.1/a
SR: 8606207461
DTS: JAGad76637
rpcbind crashes with signal 10, Bus error (SIGBUS).
librpc.a
SR: 8606197306
DTS: JAGad66499
An NFS client becomes hung while performing many
lock operations on files in NFS mounted directories.
It also receives "bindresvport: loop_twice port
assigned 512" messages in the message buffer.
librpc.a
SR: 8606168123
DTS: JAGad37405
An NFS/TCP client operation receives "NFS server not
responding still trying" messages while attempting to
access the server, even though the server system is up.
In this case, NFS/TCP on the server shows many TCP
connections for local address port 2049 in a CLOSE_WAIT
state when performing a "netstat -an" command.
nfs.client
SR: 8606181688
DTS: JAGad50904
On a system with active lofs mounts managed by AutoFS,
the "/sbin/shutdown" command may hang when the file
systems are unmounted.
nis.client, ypbind, ypinit, ypinit.1m, ypserv.1m
SR: 8606201620
DTS: JAGad70794
n SUN's NIS clients, it is possible to specify a list
of available NIS Servers for a given domain. HP's NIS
clients do not provide this functionality.
rpc.lockd
SR: 8606184904
DTS: JAGad54106
rpc.lockd can cause a user process to hang, if a
loopback mount is specified with an alias hostname.
rpc.lockd
SR: 8606202370
DTS: JAGad71544
NFS locks remain when killing NFS loopback mounted client
applications.
rpc.statd
SR: 8606208446
DTS: JAGad77633
NFS file lock recovery fails because rpc.statd matches
the wrong hostname.
rpcbind
SR: 8606164889 8606173448
DTS: JAGad34186 JAGad42706
Customer Symptoms:
rpcbind core dumps with SIGBUS or SIGSERV.
PHNE_23833:
automount
SR: 8606175862
DTS: JAGad45102
Mount points of automounter directories are not
visible when executing the "ls" command.
automount
SR: 8606169011
DTS: JAGad38290
The automount process hangs, making automounter
mount points inaccessable.
automountd
SR: 8606160596
DTS: JAGad29916
The /var/adm/automount.log file fills up the /var
file system.
exportfs
SR: 8606171662
DTS: JAGad40926
exportfs sometimes does not work correctly when
invalid host names are present in a host list
in the /etc/exports file.
fsirand.1m
SR: 1653311530
DTS: JAGab46804
Unable to use fsirand() on JFS file system.
libnfs.a
SR: 8606178998
DTS: JAGad48223
Unnecessary NFS read before write is causing severe
decreases in write performance.
libnfs.a
SR: 8606165859
DTS: JAGad35150
Data page fault panic while copying a file using
NFS V3 between an HP-UX client and an NT InterDrive
server where the target filesystem is full.
libnfs.a
SR: 8606178618
DTS: JAGad47845
The rename() system call always fails when trying
to rename a directory in a cachefs-mounted file
system, if the target directory name exists.
'errno' gets set to EPERM ("Not Owner").
libnfs.a
SR: 8606175781
DTS: JAGad45021
The 'du' output is eight times higher over NFS
with an HP server / Sun Client configuration when
compared to an HP server / HP Client configuration.
libnsl.1/a
SR: 8606183171
DTS: JAGad52387
UDP packets sent by remote users can cause RPC
applications to abort.
libnsl.1/a
SR: 8606186548
DTS: JAGad55752
RPC server running in TCP multithreading
mode develops a file descriptor leak when
clients are on same machine as the server.
Eventually the server fails to process
clients' requests when the process limit
is attained.
libnss_nis.1
SR: 8606179951
DTS: JAGad49173
getservbyname() using NIS returns NULL when
trying to resolve service aliases.
libnss_nisplus.1
SR: 8606172747
DTS: JAGad42007
Changing an NIS+ user's password with nispasswd() or
passwd() while the system is in trusted mode without
specifying the dot "." notation (non fully qualified
domain) results in an incorrect sub-domain being
created.
nfsstat.1m
SR: 8606173363
DTS: JAGad42623
The "man nfsstat" command does not display all of the
statistical data fields.
rpc.lockd
SR: 8606180764 8606180765
DTS: JAGad49985 JAGad49986
rpc.lockd causes user process to hang.
rpc.lockd
SR: 8606174017
DTS: JAGad43270
rpc.lockd drops the lock request from same process
for a different file.
rpc.lockd
SR: 8606185238
DTS: JAGad54440
Partial record unlocking in NFS does not work
properly.
rpc.lockd
SR: 8606179200
DTS: JAGad48424
rpc.lockd core dumps when user process is
interrupted with "control-c".
rpc.mountd
SR: 8606176384
DTS: JAGad45622
The boot process of a Linux client fails due to
rpc.mountd not allowing AUTH_NULL authentication.
ypxfr
SR: 8606164133
DTS: JAGad33433
The ypxfr command fails with the error message:
"ypxfr: bind_to_server clntudp_create error:
RPC unknown host".
PHNE_23249:
libautofs.a, libnfs.a, librpc.a
SR: 8606103740 8606159451
DTS: JAGab70789 JAGad28779
A multithreaded process can hang when performing NFS
file operations and concurrently writing core, forking,
performing debugger attachment or undergoing job
control.
PHNE_23247:
{Site Specific Patch}
PHNE_22642:
automount
SR: 8606155592
DTS: JAGad24909
Automount (automounter) coredumps when sent SIGUSR1
to force it to update the automaps.
automountd
SR: 8606160808
DTS: JAGad30127
When using AutoFS, NFS mount points do not enforce
quotas.
libautofs.a
SR: 8606135856
DTS: JAGad04988
Panic occurs when trying to umount a ufs filesystem
which is still in the process of mounting.
libautofs.a
SR: 8606159736
DTS: JAGad29062
Unexpected delay in unmounting of Autofs mounts.
libnfs.a
SR: 8606179269
DTS: JAGad48493
Poor NFS pv3 performance on 64-bit (V-class) on 11.0.
libnfs.a
SR: 8606161701
DTS: JAGad31017
When reopening an NFS file right after closing it,
file attribute related inconsistencies can occur.
libnfs.a
SR: 8606158230
DTS: JAGad27560
Unmount of an nfs file system causes a panic.
libnfs.a
SR: 8606163247
DTS: JAGad32551
Unable to remove an NFS tmp file, .nfsXXXX after
failing to create or write a file which has exceeded
the disk quota limit.
libnfs.a
SR: 8606166314
DTS: JAGad35601
Process using NFS can not be killed or stopped by
sending the process a signal (SIGKILL or SIGSTOP).
libnsl.1/a
SR: 8606140609
DTS: JAGad09968
Core dump occurs when user belongs to more than
16 groups.
libnsl.1/a
SR: 8606160400
DTS: JAGad29722
On installing PHSS_20014 and PHSS_21947, 100% CPU
is used up by 2 processes - opcmsgrd and opcdistm.
librpc.a
SR: 8606169796
DTS: JAGad39062
Data page fault panic due to bad machine name
length in NFS request.
librpc.a,nfsd
SR: 8606167053
DTS: JAGad36339
An NFS/TCP client operation receives "NFS server
not responding still trying" messages while
attempting to access the server even though the
server system is up. In this case, NFS/TCP on
the server has become inoperable due to a hang.
newkey
SR: 8606157592
DTS: JAGad26923
Newkey does not recognize the root password of the
remote machine and returns an error, "ERROR,
passwd differs from login passwd".
PHNE_22125:
libautofs.a
SR: 8606143877
DTS: JAGad13210
Using autofs, mount points become inaccessible
after a series of mount/unmount cycles.
libnfs.a
SR: 8606128739
DTS: JAGac86286
File corruption over NFS when NFS file server is
TOC'ed.
libnfs.a
SR: 8606144881
DTS: JAGad14221
HP NFS client performance is degraded as shown by
"nfsstat -c", it makes unnecessary GETATTR calls
for each read or write on files opened with
synchronous I/O flags set; and synchronous I/O
mode remains in effect for subsequent opens on an
NFS file opened once with synchronous I/O flags
set.
libnfs.a
SR: 8606147198
DTS: JAGad16541
CPU time is wasted by unnecessary calls to
compare_cred function in NFS PV3 client code.
libnfs.a
SR: 8606145970
DTS: JAGad15306
The stat() system call on NFS directories
shows a non-existent ACL.
libnfs.a
SR: 8606128493
DTS: JAGac84458
System panic when running "du -s" or
"find -name" on a 64 bit machine.
libnfs.a, librpc.a
SR: 8606160097
DTS: JAGad29423
Mount an NFS file system with non-interruptible
options remains interruptible.
libnfs.a
SR: 8606144617
DTS: JAGad13957
Using NFS, a read-only file open by one
process causes a "Permission denied"
error in an on-going write operation on
the same file by another process.
libnfs.a, librpc.a, nfsd
SR: 8606145517
DTS: JAGad14853
If NFS is stopped and restarted, the nfsd
processes do not get re-registered with rpcbind,
and rpcinfo commands fail.
libnfs.a, nfsd
SR: 8606146885
DTS: JAGad16228
nfsd unregisters a running nfsd process on
startup.
librpc.a
SR: 8606155004
DTS: JAGad24321
When a server is down, an NFS/TCP client process
e.g. a bdf command can hang.
librpc.a
SR: 8606143872
DTS: JAGad13205
NFS/TCP mounting and unmounting eventually hangs.
librpc.a
SR: 8606144478
DTS: JAGad13818
NFS/TCP connections are not torn down when the
peer sends a FIN.
nfs.core
SR: 8606159847
DTS: JAGad29173
File permission change on /etc/services file.
rpc.lockd
SR: 8606145476
DTS: JAGad14812
Lockd/statd client crash recovery does not work.
rpc.mountd
SR: 8606127276
DTS: JAGac68822
A failing mount request may return a wrong error
code.
rpc.statd
SR: 8606143409
DTS: JAGad12739
A looping problem in rpc.statd occurs between the
server and SGI clients.
ypserv
SR: 8606155843
DTS: JAGad25155
YPSERV fails to return all groups for id/group
command when concurrent access is allowed to maps.
PHNE_21376:
automountd
SR: 8606128485
DTS: JAGac84450
Automountd not triggered for mounts
anymore when autonode has NULL flag.
exportfs
SR: 8606108804
DTS: JAGab78579
When a user attempts to mount an exported
filesystem which is a symbolic link to an
actual directory or filesystem on an NFS
server, a "Permission Denied" error occurs.
This occurs after installing patch PHNE_18221.
libautofs.a
SR: 8606128485
DTS: JAGac84450
Automountd not triggered for mounts
anymore when autonode has NULL flag.
libnsl.1/a
SR: 8606134593
DTS: JAGad03728
automountd coredumps in the NIS+ environment.
libnsl.1/a
SR: 8606143750
DTS: JAGad13073
When using the TCP loopback transport a
memory leak may occur.
libnsl.1/a, rpc.nisd
SR: 8606107751
DTS: JAGab78042
When using NIS+ with TCP, as the number of open
file descriptors increases, file table overflow
errors occur in the syslog.log file and user
information is not recognized.
rpc.lockd
SR: 8606131496
DTS: JAGad00646
Failover occurs with the serviceguard NFS package because
the rpc.lockd daemon fails (terminates) during periods of
high memory usage (running out of memory).
rpc.statd
SR: 8606131366
DTS: JAGad00517
The rpc.statd daemon core dumps during high memory
utilization (when available memory runs low).
rpc.statd
SR: 8606136063
DTS: JAGad05198
rpc.statd aborted with memory leak due to unresolved
host requests.
rpcbind
SR: 8606131978
DTS: JAGad01128
Rpcbind exhibits wrong behavior on shutdown.
ypserv
SR: 8606134296
DTS: JAGad03431
ypserv becomes unavailable for the local ypbind and
for the other yp clients.
PHNE_20627:
libnfs.a
SR: 8606134214
DTS: JAGad03354
Extremely slow performance of commands or utilities
operating on large directories over NFS.
SR:8606109663
DTS:JAGab82363
Removing an NFS file causes a file named ".nfsXXXX"
(where XXXX is a pid) to be created.
SR:8606135799
DTS:JAGad04931
The i-node for the ".." directory entry of a subdirectory
is not updated on an NFS client after that subdirectory
is moved up one directory level on the NFS client,
ie - moved to "..".
SR:8606135800
DTS:JAGad04932
Output from "tail -f" on an NFS file does not reflect any
appends made to the file on the NFS server if a "umount"
is performed on the NFS file system while the "tail -f"
is being executed.
PHNE_20371:
autofs/mount
SR: none
DTS: JAGab68200
Autofs/mount can fail when the system
hostname is longer than 8 characters.
automount
SR: none
DTS: JAGab68200
Autofs/automount can fail when the system
hostname is longer than 8 characters.
automount,automountd
SR: 8606106692
DTS: JAGab76019
automount with stalemounts causing duplicate
mnttab entries & lock problems.
symptoms of automount are: stale nfs handles are
seen in mnttab after an unmount and when the
mount is repeated (in this case a cdrom...) the
mnttab contains two entries for the device. One
of which is invalid. This second (stale) handle
causes subsequent locking problems.
automountd
SR: none
DTS: JAGab68200
Autofs/automountd can fail when the system
hostname is longer than 8 characters.
automountd
SR: 8606107366
DTS: JAGab77563
Autofs exhibits wrong behavior in processing
executable maps.
automountd
SR: 8606107274
DTS: JAGab77060
automount option -proto=udp causes mounts to fail
libautofs.a
SR: 8606107122
DTS: JAGab76805
autofs - shell gets intermittent "cannot execute"
libautofs.a
SR: 8606106938
DTS: JAGab76453
automounter hangs when trying to mount cachefs
filesystem (reported on HP-UX 10.20)
libnsl.1/a
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
libnsl.1/a
SR: none
DTS: JAGab68200
NIS and other ONC/NFS systems can fail when
libnsl does not provide support for a system
hostname longer than 8 characters.
libnsl.1/a
SR: 8606107366
DTS: JAGab77563
Autofs exhibits wrong behavior in processing
executable maps.
libstraddr.1
SR: none
DTS: JAGab68200
Libstraddr routines can fail when the system
hostname is longer than 8 characters.
make.script
SR: 8606107068
DTS: JAGab76707
ypmake and Makefile failed
on some mail.aliases file and mail.aliases map
is corrupted.
mount
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
nfs.core
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
nfs/mount
SR: none
DTS: JAGab68200
Nfs/mount can fail when the system
hostname is longer than 8 characters.
nfsstat
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
nisplus/nisserver
SR: none
DTS: JAGab68200
Nisplus can fail when the system hostname
is longer than 8 characters.
rpcinfo
SR: none
DTS: JAGab68200
Rpcinfo can fail when the system hostname
is longer than 8 characters.
rpc.lockd
SR: 5003459362
DTS: JAGab12595
file locks hang when NFS server uses
fully-qualified hostname
rpc.lockd
SR: 8606113678
DTS: JAGac07192
Application hangs on client when obtaining NFS
lock on server
setoncenv
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
ypmake
SR: 8606107068
DTS: JAGab76707
ypmake and Makefile failed
on some mail.aliases file and mail.aliases map
is corrupted.
PHNE_20344:
libnfs.a librpc.a nfs_iface.o
SR:N/A
DTS:JAGac42842
NFS version 3 only supports up to 8k read/write
transfer size.
libnfs.a
SR:8606110199
DTS:JAGab82902
Memory leak in NFS version 3 at rfs3_readdirplus().
libnfs.a
SR: 8606125471
DTS: JAGac40861
Poor NFS performance relative to SPECsfs97 benchmark.
libnfs.a
SR:8606107676 8606124555
DTS:JAGab77944 JAGac39938
NFS performance problems with NFS client
readdir cache.
libnfs.a
SR:8606126860
DTS:JAGac59701
"do_readdirplus" variable not available in the NFS
kernel.
PHNE_19759:
1.fuser -f on a file does not return pid of opener
2.compress command on a SUN client fails due to invalid
name length returned by NFS pathconf from HP Server
3.getmount_entry() returns down status for all hard
mounted NFS file systems
PHNE_19620:
automountd
DTS: JAGab72053
NFS - autofs (11.0) hangs when unmount from down server
SR: 8606103364
DTS: JAGab70009
replicated automounts fail if system parameter
maxfiles > 2048
libautofs.a
DTS: JAGab73529
autofs w/cachefs can panic in cachefs_root()
SR: 8606105077
DTS: JAGab72920
AutoFS failure with cdrom.
The failure occurs in two ways:
- Hangs if indirect mount
- Error if direct mount
libnsl.1/a
SR: 8606104454
DTS: JAGab41115
rpcinfo gets error "can't contact rpcbind: RPC:
Program not registered" from remote rpcbind on
RPCB_GETADDR/RPCB_DUMP request for list of services.
libnss_nis.1
SR: 5003465898
DTS: JAGab20796
getservbyname() is slow.
librpcsvc.a
SR: 8606103503
DTS: JAGab70329
rpc.mountd dies with SIGSEGV if rmtab is large and
showmount -a is done.
rpc.lockd
SR: 8606105833
DTS: JAGab74177
Virtual nfs servers have locking problems.
DTS: JAGab45462
rpc.lockd uses port numbers within reserved port
range, 600 to 1024.
DTS: JAGab15223
Processes waiting to lock an nfs file which has been
deleted do not get woken up, resulting in a hang.
DTS: JAGaa45544
Locks hang and rpc.lockd logs error messages about
the local and remote lock tables being inconsistent.
rpc.lockd causes lock queue corruption with loopback
mounts.
rpc.mountd
DTS: JAGab45462
rpc.mountd uses port numbers within reserved port
range, 600 to 1024.
rpc.statd
DTS: JAGab45462
rpc.statd uses port numbers within reserved port
range, 600 to 1024.
PHNE_18221:
libautofs.a
SR: 1653298828 5003458299 1653299826 5003462911
SR: 1653304972
DTS: JAGab00144 JAGab03833 JAGab11283 JAGab16597
DTS: JAGab18083
JAGab00144 - AutoFS is not triggering re-mount
JAGab03833 - AutoFS hangs even with PHNE_17200
JAGab11283 - cp(1) fails to inactive direct mount
JAGab16597 - mv command fails in AutoFS direct mnt
JAGab18083 - getcwd() fails with AutoFS filesys
libnsl.1/a
SR: 5003463992
DTS: JAGab17512
Applications fail to create a server side RPC
endpoint due to a failure to obtain a reserved port.
libnsl.1/a
SR: 5003465880
DTS: JAGab20797
A multi-threaded application which calls
getservbyname() failed.
libnss_compat.1
SR: none
DTS: JAGab03573
64-bit application using 'getgrent' fails if
nsswitch.conf uses group:compat
rpc.lockd
SR: 5003446203
DTS: JAGaa46687
rpc.lockd runs out of file descriptors
and returns the following error in
its log file:
RPC: Remote system error
rpc.mountd
SR: 5003439471 5003463331
DTS: JAGaa42795 JAGab17386
ER for share(1M) options and defect in "showmount -e"
rpc.mountd
SR: none
DTS: JAGaa44896 JAGaa24142
rpc.mountd - server allows mounts not on access list
rpc.pcnfsd
SR: 5003460030
DTS: JAGab13451
rpc.pcnfsd does not accept '~' for
file names.
rpc.statd
SR: 5003446195
DTS: JAGaa46688
rpc.statd fails on fopen when more than
260 entries are in /var/statmon/sm.
PHNE_17586:
1. Huge directory reads take too long and client system
performance degrades as NFS IO activity increases.
2. System panics with data page fault when 0 len UDP
pkt received by NFS server system.
3. Root users are denied access to valid root exported
file systems on 11.0 server.
4. Root users on NFS PV3 client who do not have file
permissions for read/write are allowed to open file
successfully but denied access when reading or
writing the file.This behaviour is inconsistent
with non-root users who are denied access at file
open time.
5. NFS requests from anonymous NT clients are rejected.
6. Large file reads on a 32 bit NFS client does not work,
file copy completes without errors but no data is copied
to the target file.
7. When copying large file from local disk to NFS
file system,more bytes than necessary are copied to
the file and the resulting file size is bigger.
8. Buffering of data on NFS file is permanently
turned off by the client system even after releasing
all file locks and closing all file descriptors.
9. Exportfs prints debug messages in syslog.log.
10. When a file is opened with O_CREAT|O_TRUNC|O_EXCL
flags set and the file does not already exist,open is
expected to succeed but for NFS V3 files,open seems to
fail with EACCES.
11. When file has Mandatory lock mode set,HP NFS V3
allows file read/write access when no locks exist on
the file,but NFS V2 denies file read/write access.
Also,NFS V3 client hangs application when locks exist
on the file.This behaviour is inconsistent with SUN's,
where NFS V3 and V2 access is denied consistently at
file open time when file has mandatory lock mode set.
12. Data page fault panic in mvfs due to NFS server
initialization corrupting global memory at boot up.
PHNE_17247:
1. Data page fault panic due to NFS server
initialization corrupting global memory at boot up.
2. Large file reads on a 32 bit NFS client does not work,
file copy completes without errors but no data is copied
to the target file.
3. When copying large file from local disk to NFS
file system,more bytes than necessary are copied to
the file and the resulting file size is bigger.
PHNE_17200:
Makefile
SR: none
DTS: JAGaa73221
When rpc.mountd tries to match a hostname
in netgroup, the given hostname has to be
the exact same as it is stored in the
netgroup.
automount
SR: 5003450916
DTS: JAGaa93190
automount loops using replicated server
automount
SR: 5003362707
DTS: JAGaa25720
automount fails to mount all exported
file systems.
automountd
SR: 1653267377
DTS: JAGaa24193
autofs holding lock on /etc/.mnttab.lock.
automountd
SR: none
DTS: JAGaa95626
Logging information is hard to
read.
automountd
SR: none
DTS: JAGaa40567
executable map processing may grant
caller additional privileges.
libautofs.a
SR: 5003445601
DTS: JAGaa46003
NFS - autofs hangs when manual unmounts used
nfs.core
SR: none
DTS: JAGaa43075
rexd does not start since it cannot find
/var/spool/rexd on system.
nis.server
SR: none
DTS: JAGaa94166
nis.server script won't run correctly unless the
new namesvrs is installed at the same time.
rpc.mountd
SR: 5003454371
DTS: JAGaa94274
rpc.mountd deadlock with automount
rpc.mountd
SR: 5003447003
DTS: JAGaa45940
NFS - rpc.mountd MOUNT performance is very slow
rpc.nispasswdd
SR: 1653286955
DTS: JAGaa44956
when rpc.nispasswdd is running with "-g"
option, it corrupts the credential of a
user who has a credential and changes
password.
rpc.pcnfsd
SR: 5003405118 5003336198
DTS: JAGaa26176 JAGaa25473
1) PC users fail to authenticate when trusted
system is enabled.
2) pcnfsd stops responding to all requests when
a request is made to printer that is down.
rpc.pcnfsd
SR: 1653293043
DTS: JAGaa93189
User authentication fails for users who
do not use a shell that ends with "sh".
rpc.rstatd
SR: 5003442574
DTS: none
The amount of memory associated with the
rpc.rstatd process continues to grow
without ever being returned to the system.
rpc.statd
SR: 5003445858
DTS: JAGaa45938
rpc.statd core dumps with SIGSEGV.
rpcbind
SR: none
DTS: JAGaa92935
rpcb_unset() does not remove all registration
entries from rpcbind.
rpcgen
SR: none
DTS: JAGaa57297
rpcgen generated makefiles fail to build targets
rpcgen
SR: 1653291484 1653291500
DTS: JAGaa57208 JAGaa57209
rpcgen generated file fails to compile.
stdhosts
SR: none
DTS: JAGaa94167
stdhosts command fails on lines longer
than 256 char.
ypinit
SR: none
DTS: JAGaa41361
ypinit has warning message.
ypmake
SR: none
DTS: JAGaa73221
When rpc.mountd tries to match a hostname
in netgroup, the given hostname has to be
the exact same as it is stored in the
netgroup.
ypserv
SR: 5003448159
DTS: JAGaa46689
ypserv is running out of file descriptors
due to not releasing them.
ypserv
SR: none
DTS: JAGaa41159
ypserv core in svc_freeargs ( a rpc routine)
after nslookup for a period of time.
ypxfr_1perday
SR: none
DTS: JAGaa43641
vhe_list should not be in the script.
PHNE_17101:
autofs
SR: none
DTS: none
Autofs fails to start on a 64-bit OS
unless PHNE_15638 has already been
installed.
nfsstat
SR: 5003444745
DTS: JAGaa44646
nfsstat -m exited with an error that it
could not open the mount table
PHNE_16599:
1. NFS server system panics with assertion failure
in vn_rele sometimes during NFS file locking/unlocking.
2. Too much rnode memory allocated resulting in gradual
shortage of free memory resource on the system.
3. NFS Version 3 mounted directories may appear to be
empty on the NFS client even though the directories exist
on the server file system.
4. A touch command to change the modification time stamp
of NFS file may cause system hang.
5. Some NFS clients may experience poor NFS Read
performance with HP servers when using NFS Version 3 mounts.
6. Invalid file system id returned to Statfs of
NFS Version 2 mounted file set.
PHNE_16470:
Makefile
SR: none
DTS: INDaa30982
vhe_list is no longer supported by NIS.
It needs to be removed from ypinit,
ypmake and /var/yp/Makefile.
automount
SR: none
DTS: JAGaa26320, JAGaa26354
Made debug logging change and checked
in the change for setmntent for read locks.
automount
SR: none
DTS: JAGaa40906
automount tries to remount already mounted directory
automount
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
automountd
SR: 5003431353, 5003434654
DTS: none
1. duplicate entries in /etc/mnttab error
message in syslog
2. AutoFS will not unmount LOFS mounts
exportfs
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
libautofs.a
SR: none
DTS: JAGaa24180
1. HOME env set to autofs directory on 64-bit 9808
system hangs gpm help.
2. Autofs hangs when running Netscape.
3. Autofs hangs when remounting hierarchical mounts.
libnsl.1/a
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
libnsl.1/a
SR: 5003429845
DTS: INDaa31432
Compile of application using archived libraries
files with duplicate symbol __nss2herrno
libnsl.1/a
SR: 5003429456
DTS: INDaa31422
rpc.mountd stops running
libnsl.1/a
SR: none
DTS: JAGaa24798
CDE logins fail when user belongs to more then
16 groups.
libnsl.1/a
SR: none
DTS: INDaa30681
The performance of a 64-bit application
slows down when it uses the 32-bit cache
information in the ypbind file.
libnss_nisplus.1
SR: none
DTS: JAGaa40026
getxxxent leaks memory when using NIS+
libnss_nisplus.1
SR: 5003418210
DTS: JAGaa24152
Module ngetprpwent is missing
from libnss_nisplus.
librpcd_util.a
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
librpcsoc.1
SR: none
DTS: INDaa30814
on command fails with the messages
on: failed to reach <host> at address <host address>
mknetid
SR: none
DTS: INDaa30115
mknetid cores when a user is in more that 20 groups
namesvrs
SR: none
DTS: INDaa30072
nis.server script fails if IBM is NIS master to
HP slave.
nfs.client
SR: none
DTS: JAGaa27109
Non-busy NFS mounts are frequently not
unmounted during nfs.client stop.
nfs.server
SR: none
DTS: JAGaa24199
local file systems are mounted when NFS client restarts
nfs_umount
SR: none
DTS: JAGaa27067
/sbin/fs/nfs/umount -aF nfs does not unmount
all NFS file systems.
nfsstat
SR: none
DTS: INDaa31388
Executable hangs.
nis.server
SR: none
DTS: INDaa30072
nis.server script fails if IBM is NIS master to
HP slave.
on
SR: 5003420992
DTS: INDaa30864
on fails when home directory is mounted via
autofs.
rpc.lockd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.lockd
SR: none
DTS: JAGaa40591
Lock failure caused data corruption
rpc.lockd
SR: none
DTS: JAGaa26538
logged messages causes file system to fill
rpc.lockd
SR: 1653254474, 5003417998
DTS: JAGaa26354, JAGaa26221, JAGaa26257
The rpc.lockd tracing was improper format.
Loss of UDP NFS file locking packets resulted
in a growing message queue. rpc.lockd processes
control C (NLM_CANCEL) incorrectly when the server is
a SUN system.
rpc.mountd
SR: none
DTS: JAGaa24186
Believes there is a problem
in the way the daemon checks to see if it is up.
rpc.mountd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.mountd
SR: 1653266148
DTS: INDaa31024
valid clients in the NFS server's export list
can not mount the NFS server.
rpc.pcnfsd
SR: 1653272484
DTS: JAGaa26373
Validity checks not performed on printer and
system name.
rpc.rexd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.rquotad
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.rquotad
SR: none
DTS: INDaa31358
Executable hangs.
rpc.rstatd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.rusersd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.sprayd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.statd
SR: none
DTS: JAGaa26538
logged messages causes file system to fill
rpc.statd
SR: 4701392027
DTS: JAGaa26354, JAGaa26276
The debug logging needs change.
rpc.walld
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.yppasswdd
SR: none
DTS: INDaa31524
If a password contains a ":", it cannot be changed
via NIS.
rpc.yppasswdd
SR: none
DTS: INDaa31380
rpc.yppasswdd does not update NIS maps when ptmp
and maps on diff file system.
rpcbind
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
ypbind
SR: none
DTS: INDaa31412
ypbind cache file sometimes is not created
due to the value in an uninitialized time
stamp. The performance of NIS degrades
when cache file is absent.
ypbind
SR: none
DTS: INDaa31381
ypbind cache file cannot be created
due to a missing compilation flag.
The performance of NIS degrades
when cache file is absent.
ypinit
SR: none
DTS: INDaa30982
vhe_list is no longer supported by NIS.
It needs to be removed from ypinit,
ypmake and /var/yp/Makefile.
ypmake
SR: none
DTS: INDaa30982
vhe_list is no longer supported by NIS.
It needs to be removed from ypinit,
ypmake and /var/yp/Makefile.
ypmake
SR: none
DTS: INDaa31440
When a new map is made on the Master with
NOPUSH=1 option, on the Slave, transferring
the new map fails sometimes.
ypserv
SR: none
DTS: INDaa29252
ypserv stops answering some queries for
entries outside domain on a slow system.
ypxfr
SR: 5003418160
DTS: JAGaa24144
ypmake on the YP master reports a failure
when contacting a slave server
ypxfr
SR: none
DTS: none
Incorrect parameter declaration for the
function ypxfrd_getdbm.
PHNE_16017:
1. The setting of NFS file/directory modification and access
time stamps is inconsistent.
2. An HP NFS server does not permit NFS file/directory time
stamps to be set from a non-HP NFS client.
3. Copying a file from a 64-bit client causes the file
timestamp to be incorrectly set to Dec 31, 1969.
4. Poor NFS performance over 100BT.
PHNE_15638:
automountd:
1. No autofs support on HP-UX.
mount:
1. No autofs support on HP-UX.
umount:
1. No autofs support on HP-UX.
rup:
error exit code incorrect
libnsl:
rpcbind has memory leak
bindreserveport fails
rpc.statd:
gethostbyname called incorrectly.
rpc.lockd:
No support for shares and non-monitored locks in NLM
version 4
automount:
Messages written to syslog file without verbose option
nfs.client:
rpc.lockd does not reclaim locks after a server reboots.
PHNE_14919:
1. NFS write performance may be slow, and may be
particularly poor when large files are being closed or
synchronized.
2. NFS Server files may be accessed and possibly destroyed
when their permissions should not allow access.
3. NFS Remounts may fail with a "device busy" error.
4. Locking large files (> 2 GBytes) may encounter errors.
PHNE_14800:
NFS Performance as measured by the SPECsfs benchmark
gives an inadequate number of IOPS on the initial 11.0
system release.
PHNE_14772:
N/A
PHNE_14746:
rpcgen:
1. rpcgen displays an incorrect usage string
2. C++ applications fail to compile due to non-existent
header file. <sysent.h>
nfs.core:
1. rpcbind cannot receive messages on ticotsord device
rpc.nisd:
1. NISPLUS server can not resolve hostname using DNS for
NIS client.
(SR/DTS: 5003-395731/INDaa28803)
2. NIS+ clients sometimes get "NIS+ unreachable" message
when in fact NIS+ server(rpc.nisd) is up and running.
(SR/DTS: 5003-395558/INDaa29132)
nisaddent:
1. nisaddent adds empty passwd fields on a trusted system.
(DTS: INDaa28982)
nisserver:
1. nisserver creates unnecessary environment variables -
NIS_MASTER and NIS_SLAVE, and adds them into
/etc/rc.config.d/namesvrs file.
(SR/DTS: 5003-395582/INDaa29138)
2. nisserver script does not set up NIS+ server correctly
if
- NIS compat mode is not set, and if,
- nisserver was previously executed with NIS
compat mode set.
(SR/DTS: 5003-395582/INDaa29138)
nisclient:
1. nisclient has illegal grep syntax for hp
(DTS: INDaa28804)
2. nisclient -u script reports success even when
chkey fails
(SR/DTS: 5003-397422/INDaa29242)
nispopulate:
1. nispopulate has illegal grep syntax for hp
(DTS: INDaa28804)
libnss_nisplus.1:
1. 64-bit gethostbyname() returns 0.0.0.0 for the IP
address of a valid host stored in the NISPLUS table
hosts.org_dir.
(DTS: INDaa29686)
nisdefaults:
1. nisdefaults does not indicate if a principal is not
authenticated.
(SR/DTS: 5003-396655/INDaa29212)
nisstat:
1. nisstat -H hostname does not work.
(SR/DTS: 5003-395541/INDaa29137)
automount:
1. Old automount daemon conflicts with New automount
command
2. Automount daemon does not use NIS master map
rpc:
1. no entry for rpc.nisd_resolv
2. no entry for automountd
nfsconf:
1. No support for AutoFS
nfs.client:
1. No support for AutoFS
libstraddr.1:
1. 64-bit application can not send request on loopback
transport.
2. 64-bit library does not exist
libnsl.1:
1. Can not generate new thread after the 65th has been
created.
2. Can not create RPC MT Servers.
3. netdir_getbyname() returns different error message
for non-existent hosts.
4. 64-bit Cannot use loopback transports over RPC.
5. Can not create 64-bit RPC MT Servers.
6. 64-bit netdir_getbyname() returns different
error message for non-existent hosts.
libnsl.a:
1. Can not generate new thread after 65th has been
created
2. Can not create RPC MT Servers
3. netdir_getbyname() returns different error message
for non-existent hosts.
4. 64-bit application cannot use loopback transports
over RPC.
5. Can not create 64-bit RPC MT Servers.
6. 64-bit netdir_getbyname() returns different
error message for non-existent hosts.
vhe_altlog:
1. Obsoleted product vhe is still available.
vhe_getlist:
1. obsoleted product vhe is still available.
vhe_list:
1. obsoleted product vhe is still available.
vhe_mounter:
1. obsoleted product vhe is still available.
vhe_script:
1. obsoleted product vhe is still available.
config:
1. Loopback transport configuration files not moved
to correct location
unconfig:
1. Loopback transport files left after deinstall.
netconfig:
1. Customer configured information lost in /etc/netconfig
hosts:
1. Customer configured information lost in
/etc/net/[ticlts|ticots|ticotsord]/hosts
services:
1. Customer configured information lost in file
/etc/net/[ticlts|ticots|ticotsord]/services
rpc.rstatd:
1. When run from the command line, rpc.rstatd dies after 10
minutes.
keyserv:
1. keyserv registers a UDP port with rpcbind
nis_cachemgr:
1. nis_cachemgr registers a UDP port with rpcbind
(DTS: INDaa29627)
rpcbind:
1. Can not send request over loopback transport devices
to rpcbind
rpc.mountd:
rpc.mountd denies access to valid netgroup.
PHNE_14620:
1. System panics with a data memory protection fault
2. NFS unmounts may take several minutes with large
memory systems
PHNE_13208:
1.Processes hung when doing NFS file IO
2.NFS sub-system failed to respond under 2 way NFS IO stress
3.Sometimes returned invalid error during NFS Read/Write
Defect Description:
PHNE_26387:
libautofs.a
JAGae15022
There was a race condition in the AutoFS code which
could result in an autonode hierarchy being removed
twice. When this happens the system panics.
Resolution:
The code which could cause the hierarchy to be
removed a second time has been removed.
PHNE_25626:
automount
JAGad88667
The performance problem is caused by the automounter
generating a tremendous number of NIS packets over the
network. This is caused by a series of infinite
recursive calls to access a non-existent entry in the
NIS map.
Resolution:
Infinite recursive calls were stopped by implementing
a function that checks whether the file causing the
problem was already opened.
libautofs.a
JAGad90351
If "control-c" is pressed within 75 seconds of issuing
an "ll" command across an automounted file system when
the server is down, the command is interrupted properly.
However, if another "ll" command is performed at least
75 seconds after the first "ll" command, the command
hangs forever. In both cases, a "server not found"
message should be returned and terminate the "ll"
command if the command is not manually terminated with
"control-c" in 75 seconds.
Resolution:
Remove the stale autonode from the autonode list in
autofs after a forced remount.
libnfs.a
JAGae06322
An NFS client does not return an error message when a
user's write(cp) operation exceeds its assigned quota
limit on a server's PV2 mounted file system.
Resolution:
If an NFS client exceeds the quota limit assigned on a
server's PV2 mounted file system during a write
operation, it will get a quota exceeded error message.
libnfs.a
JAGad97363
An unusual timestamp is set for files created with
exclusive mode flag O_EXCL on pv3 mounted file systems
for Linux or Network Appliance servers. These servers do
not support exclusive mode for creating files and the
client does not correct the timestamp.
Resolution:
The client resets the unusual timestamp returned by the
server to the correct 'server time'.
libnsl.1/a
JAGad74175
When the NIS+ server becomes busy and an NIS+ client
contacts the server, the client should create another
handle to contact the server since the server is invalid.
When this repeats more than a few iterations, the client
uses the same handle to contact the server again and
again, even though the server is busy. This is because
the checking for a valid server is done only if the
number of failures is less than the hard-coded limit.
Resolution:
Check whether or not the NIS+ server handle is valid
before checking for the number of failed iterations.
libnsl.1/a
JAGad87526
When an RPC server receives the last packet from the
client, it should flag the connection as dead and close
the file descriptor. The XPRT flag was set on the parent,
but checking is performed on the child's XPRT flag. The
SVC_FAILED flag was copied to the parent's XPRT flag and
not to the child's XPRT flag. The server develops a file
descriptor leak and eventually fails to process the
client requests when the process limit is reached.
Resolution:
Change to copy the parent XPRT flag to the child XPRT
flag once the connection is dead.
libnss_nisplus.1
JAGad90236
The user account being reactivated remains locked on
trusted NIS+ clients.
Resolution:
NIS+ locks are now detected in the PAM module instead
of the NIS+ backend library.
librpc.a
JAGad42168
If an HANFS package has been failed back to its original
server in a period of less than five minutes after it
was failed over to a new node, and a given client has
been trying to access the package over TCP the entire
time, then the TCP connection the client will try to
communicate over will still exist on the original server
host, but its state will be stale relative to the
client's TCP connection endpoint. This results in
multiple retransmissions over TCP, timeouts in
client-side RPC, and RPC call retries by NFS.
Resolution:
Have the client's RPC monitor its TCP connections more
intelligently, and initiate brand new TCP connections
over a different port when it receives indication that
transport has failed due to a peer reset by the server.
nsswitch.conf.4
JAGad57842
Additional source support for nss backends from the ldap
directory server has been released since March 2000. The
man page for nsswitch.conf needs to have ldap added as an
additional source for nss backends.
Resolution:
The ldap information is added into the nsswitch.conf man
page.
rpc.rusersd
JAGad94209
rpc.rusersd supports a maximum of 180 users. rpc.rusersd
code did not check for this limit and thus caused the
program to abort when memory outside of the structures
that kept track of the user information was accessed.
Resolution:
In rpc.rusersd code, a check is made on the number of
users whose information is read and stored. If that
number exceeds 180, further reading of user information
is stopped.
rpc.statd
JAGad93745
The server's statd process sends a notify message with
its hostname only. If the client mounted the file
system using an interface name different than the
server hostname, then it will reject the notify message
since its monitor entry does not match the server
hostname. As a result the client file lock recovery
will not take place.
Resolution:
The server's statd process was modified to build a list
of all local interface names during startup and send
notify message to all the names in the list when a
reboot occurs. The client accepts the notify message
matching with its monitor entry and notifies the lockd.
The lockd recovers all the locks on the server.
rpcgen
JAGad99710
Excessive error messages are logged to the console
device.
Resolution:
Open the null special file instead of the console and
redirect the stderr and stdout to the null special file.
ypserv
JAGad95797
An HP-UX server does not allow a blank entry in the map,
whereas a Solaris server does. When the /etc/services
map contains blank lines, a Solaris server creates blank
entries in the map. When the master server is Solaris
and the slave server is HP-UX, then the slave server
clients are unable to resolve the services after the
blank entry in the map.
Resolution:
The check for a blank entry is removed on the server
side.
PHNE_25484:
rpc.lockd
JAGae12206
rpc.lockd can core dump, with PHNE_24034 or
PHNE_24909 installed, if a local variable has not
been initialized.
Resolution:
Changed routine to initialize the local variable.
PHNE_24909:
libnfs.a
JAGad91730
Under certain conditions (memory pressure, file
system full), when a system is configured as an NFS
client and server using NFS-loopback mounts, a
deadlock condition can occur. NFS buffers remaining
in buffer cache that have active vnodes are re-used.
Resolution:
Dependency on PHKL_25525.
When writing dirty buffers, added "B_ASYNC" to ensure
buffer is eventually invalidated.
libnfs.a
JAGad74189
The mount option 'grpid' does not return the correct
'gid' value for the 'touch' command on HFS files sytems,
or for the 'mkdir' command on HFS and VxFS file systems.
Resolution:
Modified NFS client code to set the correct 'gid' value
when the file system is mounted with the 'grpid' mount
option.
libnsl.1/a
JAGad74954
The problem occurs when /etc/exports contains either
a large number of -access options for an exported
file system or a large number of exported file systems.
The recursive nature of XDR calls causes the process
to be unable to extend thread stack size, which leads
to the hanging/coring of automountd.
Resolution:
Increase the default RPC thread stack size at time
of thread creation.
libnsl.1/a
JAGad81430
The function called by passwd and nispasswd to
search for an entry in any NIS+ table skips any
leading blank characters in the search value.
Then, passwd/nispasswd obtains the new passwd from
the user and updates the NIS+ tables with the
username containing leading blanks.
Resolution:
Modified the function to include the leading blanks
in the search value.
libnss_nisplus.1
JAGad85717
The shadow password field is modified when a
user changes the password in an NIS+ trusted
environment. The new value causes getpwent
to assume that password aging is enabled.
This also occurs when a new NIS+ user is
added with SAM. This is because certain
values in the shadow password field are
interpreted incorrectly.
Resolution:
If an invalid character is encountered in the
shadow password field, set the field value so
that password aging is disabled.
libnss_nisplus.1
JAGad88698
Default system attributes are not assigned to
NIS+ users that log on to trusted NIS+ clients
for the first time.
Resolution:
The NIS+ name service switch library,
libnss_nisplus.1, was modified to set system
default attributes for NIS+ users that have
never logged on to the trusted NIS+ client.
yppasswdd.1m
JAGad68631
There are some command-line options for yppasswdd:
"-nogecos -noshell -nopw -nohome". If these options are
used, then those fields may not be changed remotely
using passwd(1). The -nohome option was not documented
in the yppasswdd man page.
Resolution:
Added the -nohome option to the yppasswdd man page.
PHNE_24034:
automountd
JAGad21864
During unmount operations, automountd incorrectly returns
a success error code to the kernel, which causes the
kernel to remove autonode data structures. Subsequent
events then cause autonodes to be created with partial
data, which results in the bdf command anomaly.
Resolution:
Fix automountd so it returns the correct error code to
the kernel during unmount operations.
automountd
JAGad65770
The unmount command failed for a mounted cachefs type
file system when trying to unmount with AutoFS
automountd. The cachefs unmount command was missing a
parameter that unmount included.
Resolution:
Added the new parameter for the cachefs unmount command.
automountd
JAGad30096
The AutoFS automountd caused the unmount command to fail
for mounted hfs and cdrom type file systems.
Resolution:
Added a new parameter for the hfs and cdrom unmount
commands.
libautofs.a
JAGad45257
Due to a race condition in AutoFS, autonodes are getting
created with NULL mount flags. The affected AutoFS mount
points show empty directories. A system reboot is
required to clear the condition.
Resolution:
Modified the code to eliminate the race condition.
libautofs.a
JAGad62727
For direct mounts, AutoFS did not wait for mounts to
complete when the direct mount point was accessed. This
triggered a second mount, creating a duplicate entry in
the /etc/mnttab file.
Resolution:
Added code in AutoFS to wait for mounts in progress for
direct mount points.
libnfs.a
JAGad66201
File access performance is slow on systems with large
memory and buffer cache.
Resolution:
Restore the performance version of the NFS code to walk
through buffer cache. The problem described in
JAGad32551 is also fixed.
libnfs.a
JAGad72416
If there are biods running in the system, asynchronous
reads are done by the kernel on behalf of the reader
process, and asynchronous writes are done on behalf of
the writer process. The problem with this is that
asynchronous write requests will be enqueued faster than
asynchronous read requests, thus monopolizing the biods,
and hence causing starvation for the asynchronous read
requests.
Resolution:
Modified the NFS read logic to avoid doing read-ahead
(asynchronous reads) if the biods are "too busy".
However, this fix is disabled by default. In order to
enable it, the kernel parameter
'async_read_avoidance_enabled' must be set to one, by
patching the vmunix file and rebooting, or by patching
the kernel image in memory. To patch the vmunix file
(survives a reboot), use this command:
echo 'async_read_avoidance_enabled?W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
To patch the in-memory kernel (does not survive a
reboot), use this command:
echo 'async_read_avoidance_enabled/W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
A kernel regeneration will require these steps to be
done again.
libnfs.a
JAGad15675
The code does synchronous I/O when the file is locked.
This means that the biods are bypassed and the I/O is
performed by the calling thread.
Resolution:
Do not set the RNOCACHE flag for a whole-file lock.
Also, flush the buffer cache for each lock/unlock
request. Thus, fresh data is read at lock time and all
data is written before releasing the lock. Note that
for partial locks, the behavior remains unchanged. This
fix is disabled by default. In order to enable it, the
kernel flag 'nfs_new_lock_code' needs to be turned on,
by either patching the vmunix file and rebooting, or by
patching the kernel image in memory. To patch the
vmunix file (survives a reboot), use the following
commands:
echo 'nfs_new_lock_code?W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
To patch the in-memory kernel (does not survive a
reboot), use the following commands:
echo 'nfs_new_lock_code/W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
A kernel regeneration will require these steps be done
again.
libnsl.1/a
JAGad76637
rpcbind and other RPC/XDR applications can be adversely
affected with SIGBUS.
Resolution:
Added code to address the problem.
librpc.a
JAGad66499
The system is running out of reserved ports.
Hundreds of processes are trying to gain access to
such ports (ie, perform a lock through lock manager).
Since the lock invocation (via a lockf or fcntl
system call) tries to use reserved ports 512 to 1023
to communicate with the local lock manager, these
ports are taken by the first lockers. If these are
all busy then subsequent lock invocations just loop
trying to get the next available reserved port. The
loop to get the next available reserved port is a
tight hard loop with a one-second delay between
activity to check whether any of the 512 reserved
ports are available. These lock invocations are the
ones actually starving the processes that first
obtained the reserved ports and they are sending
the messages to the message buffer. Thus, a virtual
deadlock occurs.
Resolution:
A backoff for the delay between successive attempts
at obtaining a reserved port is now provided. The
delay is progressive in that it starts at 1 second
and is doubled until it is 32 seconds. This allows
for those processes with a reserved port to run and
complete, and therefore give up their reserved port
to the processes waiting for one.
librpc.a
JAGad37405
NFS/TCP incorrectly handles the case where incoming
messages are being processed for a stream, as that
stream is being closed by the nfsd associated with TCP.
In this case, replies to messages being processed do not
get sent down the stream due to the close. However,
the stream cannot complete the close until all the
messages have had replies sent. Thus, the nfsd
associated with TCP hangs in its close.
Resolution:
NFS/TCP changed to not wait for all messages to have
replies sent before closing a stream. No data is lost
since messages are retransmitted if the client didn't
receive a reply.
nfs.client
JAGad50904
There is a window of time between the "Stop NFS client
subsystem" and "Unmount file systems" steps during
system shutdown. If there are active lofs mounts managed
by AutoFS, and an autofs unmount request is sent during
this window, shutdown will hang at the "Unmount file
systems" step. This is because automountd is killed at
the "Stop NFS client subsystem" step and thus cannot
process mount and unmount requests. The unmount request
pends forever.
Resolution:
In the nfs.client script, prior to killing automountd,
increase the AutoFS unmount timeout to a very large
value so that no detrimental unmount requests are
initiated before shutdown concludes.
nis.client, ypbind, ypinit, ypinit.1m, ypserv.1m
JAGad70794
NIS clients do not have a mechanism to bind to a
particular NIS server.
Resolution:
Modified the ypinit script to include a new option
"-c" for construction of an NIS servers list. The NIS
servers list is constructed by invoking "ypinit -c"
and is stored in /var/yp/binding/<domain_name>/ypservers.
The list of NIS servers should be in the order of
preference that ypbind can try to bind.
The fix for JAGad70794 is not enabled unless the ypinit
script is copied from /usr/newconfig/usr/sbin to
/usr/sbin/. To backup the current ypinit script and
enable the new ypinit script, do the following steps:
mv /usr/sbin/ypinit /usr/sbin/ypinit.bak
cp -p /usr/newconfig/usr/sbin/ypinit /usr/sbin/ypinit
When disabling the fix for JAGad70794 and migrating
back to the previous ypinit script, the file
/var/yp/binding/<domain_name>/ypservers will need
to be deleted:
mv /usr/sbin/ypinit.bak /usr/sbin/ypinit
rm /var/yp/binding/<domain_name>/ypservers
rpc.lockd
JAGad54106
rpc.lockd doesn't use NLM messages in the case of a
loopback mount with a hostname and directly modifies
msg_q entries. In the case of a loopback mount with
an alias hostname, the lockd mistakenly treats it as
a loopback mount with a hostname and modifies the
msg_q entries which causes the process to hang, as
lockd doesn't find the entry when NLM messages are
received.
Resolution:
Added checking for whether the loopback mount is with
a hostname or alias hostname. Do not modify msg_q
entries in the case of a loopback mount with an alias
hostname.
rpc.lockd
JAGad71544
When one process is holding a lock on a file, another
process is waiting for the lock on the same file, and the
two processes are killed at the same time, the lock
remains held by one of the processes.
Resolution:
In the CANCEL request handling routine local_cancel(),
code was added to delete the lock upon a CANCEL request
if the lock is found in the granted queue. This prevents
the lock from remaining after the process is killed.
rpc.statd
JAGad77633
The server's rpc.statd process sends the notify message
to the client's rpc.statd process with the server's
hostname. When the client's rpc.statd tries to match
the hostname with its monitor entry it checks for four
possible names used to mount the server: short name,
long name, alias name, and IP address. The current
algorithm to check the short name and long name in one
step matches the wrong monitor entry, thus causing
problems in file lock recovery.
Resolution:
Separated the short name and long name checking into
two steps, checking only for short name and then
checking for long name.
rpcbind
JAGad34186 JAGad42706
Customer Symptoms:
rpcbind core dumps with SIGBUS or SIGSERV.
rpcbind core dumps with SIGBUG or SIGSEGV due to memory
corruption in the internal linked list of registered
programs. This list is abnormally terminated by memory
corruption and when the invalid node is accessed,
rpcbind can core. This has been noticed on several
occassions including NIS+ startup and random buffer
overflow under heavy load.
Resolution:
The core of memory corruption is in netbufdup().
Changed the malloc to valloc() to increase the required
buffer allocation.
PHNE_23833:
automount
JAGad45102
When automounter triggers new mounts a symbolic
link is added to the automounter vnode. After the
link was added the modification time of the vnode
was not being updated. Since the modification
time of the vnode never changed the rddir cache
was never invalidated.
Resolution:
Add code in the automounter to update the
modification time of the automounter vnodes
whenever new symbolic links are added.
automount
JAGad38290
If an automounter map contains a mount point
which is a symbolic link that points to a
non-existant directory, automounter will hang.
Resolution:
During automounter initialization, add a check
which will ignore these invalid map entries and
log an error message to syslog.
automountd
JAGad29916
Automountd will log "Rmdir" error messages to
/var/adm/automount.log even if automountd was
started without the "-T" option.
Resolution:
Add code to check for tracing before logging the
error message.
exportfs
JAGad40926
Invalid host names in a root option's host list are
not handled correctly. They cause invalid entries
to be created in the root access host list for the
corresponding filesystem. The same type of defect
occurs for the 'rw' option.
Resolution:
Changed the logic that processes the 'root' and
'rw' options, in order to completely ignore invalid
host names.
fsirand.1m
JAGab46804
The manpage does not mention that fsirand is not
supported on a JFS file system.
Resolution:
Added a line to the "fsirand" man page stating
that the fsirand command is only supported on HFS
file systems.
libnfs.a
JAGad48223
Server reads are occurring unnecessarily when a
client is only doing writes.
Resolution:
Removed the read operation that occurred before
the write operation.
libnfs.a
JAGad35150
NFS incorrectly handles a return from a write
operation having a 0 status (NFS3_OK) and a
count of bytes written that is not reflective
of the number of bytes actually written (that is,
a large negative number). By not rejecting such
values, it attempts to use the count of bytes
written to offset into memory causing the panic.
A negative count of bytes written is allowed
because it is cast as signed.
Resolution:
NFS interprets the count of bytes written as
unsigned, thus eliminating any negative values.
libnfs.a
JAGad47845
Function nfs3rename() is implementing the
"unlink-open-file" semantics for the target
name (when it exists), without checking that it
should only do so if the target is not a directory.
Resolution:
Modify function nfs3rename() to only implement the
"unlink-open-file" semantics if the target name
is not a directory.
libnfs.a
JAGad45021
The calculation for determining the size of a file
was using an incorrect constant value.
Resolution:
NFS PV3 calculates the size occupied by a file.
This calculation was based on MAXBSIZE, which is
8192 instead of DEV_BSIZE which is 1024. So it
was eight times too high. Changed this to base
the calculation on DEV_BSIZE.
libnsl.1/a
JAGad52387
Remote users can cause denial of RPC services.
Resolution:
In __svcauth_sys(), change the local variables
strlen, gid_len and i from type integer to
unsigned integer.
libnsl.1/a
JAGad55752
File descriptors used by the TCP connections
are released too soon so that they confuse the
polling thread to create more file descriptors.
The wrongly created file descriptors are never
closed.
Resolution:
In svc_vc_getargs(), comment out the call to
svc_args_done(). This will keep the file
descriptors until the RPC service routine is
totally complete.
libnss_nis.1
JAGad49173
getservbyname() first searches the NIS map
servi.bynp, which can only resolve official
service names. getservbyname() never gets to
call YP_ALL as a last resort to parse through
the other NIS map services.byname for the
service alias.
Resolution:
If getservbyname() cannot resolve the service
name passed to it, call YP_ALL and parse through
the NIS map services.byname.
libnss_nisplus.1
JAGad42007
When in trusted mode, the passwd change should
always create a fully qualified domain name even
if one was not passed into the command.
Resolution:
New code was added to libnss_nisplus.1 to fully
qualify domain names if they are passed non-fully
qualified.
nfsstat.1m
JAGad42623
The nfsstat man page does not have a description
for the badverfs, cantconn, nomem, interrupts, and
cantsend fields.
Resolution:
Added these fields to the nfsstat man page.
rpc.lockd
JAGad49985 JAGad49986
rpc.lockd rejects NLM_GRANTED_MSG when it is
received out of order with NLM_LOCK_RES
(blocked). rpc.lockd ignores NLM_GRANTED_MSG
when it is received out of order with
NLM_UNLOCK_RES.
Resolution:
Modified the processing algorithm for NLM_
GRANTED_MSG. When NLM_GRANTED_MSG is
received ahead of NLM_LOCK_RES(blocked),
it is treated as if NLM_LOCK_RES(granted)
was received. When NLM_GRANTED_MSG is
received ahead of NLM_UNLOCK_RES it is
treated as if NLM_UNLOCK_RES was received.
rpc.lockd
JAGad43270
rpc.lockd puts the lock requests in msg_q while
waiting for a response from the server. If a
process lock request for file 'f1' is
waiting in msg_q, subsequent lock requests from
same process are ignored even if it is for
different file. This can happen with
multi-threaded processes where two threads can
send lock requests for two different files.
Resolution:
Added checking for the file handle in determining
the uniqueness of lock. This enables lockd to
distinguish between requests from same process
for different files.
rpc.lockd
JAGad54440
When a client tries to unlock the first part of
a locked area in an NFS file, the whole lock is
removed in the server.
Resolution:
Fixed the delete_reclock() function to use the
proper argument when calling the
delete_kernel_lock() function.
rpc.lockd
JAGad48424
rpc.lockd logs messages to a log file by
calling the LOG_MSG function. The LOG_MSG
function is being called with incorrect
parameters in lockd when it is logging messages
related to "control-c" interrupt processing.
Resolution:
Corrected the parameters being passed to the
LOG_MSG function.
rpc.mountd
JAGad45622
When booting a diskless Linux client, the
process fails when mounting the root file system.
This happens because the mount request uses the
AUTH_NULL authentication type and rpc.mountd does
not allow this. The mount request fails with a
"permission denied" error.
Resolution:
Allowed rpc.mountd to accept mount requests with
AUTH_NULL authentication type.
ypxfr
JAGad33433
After a map transfer, ypxfr sends a YPPROC_CLEAR
to the local ypserv if ypxfr is not invoked with
a "-c" option. If the local host name is greater
than 8 characters then the call to bind_to_server()
fails with the error "ypxfr: bind_to_server
clntudp_create error: RPC unknown host".
Resolution:
Increased the size of the array local_host_name
from 8 to MAXHOSTNAMELEN characters.
PHNE_23249:
libautofs.a, libnfs.a, librpc.a
JAGab70789 JAGad28779
Threads in a multithreaded process sleeping
interruptibly while holding a non-interruptible
resource are susceptible to deadlock.
Resolution:
NFS threads are placed in a "nonstop" mode in
sections of code where non-interruptible resources
are being held during interruptible sleeps. There
are four other patches which must be installed to
enable the "nonstop" mode: PHKL_23406, PHKL_23407,
PHKL_23408, and PHKL_23409. These patches will be
released in the Spring of 2001.
PHNE_23247:
{Site Specific Patch}
PHNE_22642:
automount
JAGad24909
The function (which loads a direct map file)
involved in the call sequence for handling the
SIGUSR1 signal, was being called with incorrect
arguments which would result in a "segmentation
fault" and coredump when executed.
Resolution:
The function call which was causing the coredumps
was modified to reference the proper argument set.
automountd
JAGad30127
The automountd code simply was not parsing the
quota option out of the options string.
Resolution:
Added a hasmntopt call to check for the quota
option and set the quota flag as needed.
libautofs.a
JAGad04988
Race condition between mount and umount with ufs
filesystems.
Resolution:
Check VFS_MOUNTING flag in make_unmount_list and
get_hierarchical_mounts.
libautofs.a
JAGad29062
When an unmount request comes in to the automountd,
it stats each file system to find the entry with
the matching file system id. The stat command updates
the reference times of the autonodes, preventing them
from unmounting when they should.
Resolution:
AutoFS now uses an existing macro to make sure that
the calling process is not automountd before updating
the reference times of autonodes.
libnfs.a
JAGad48493
Extremely poor performance on a 64-bit (V-class) 11.0
from NFS pv3. All processes accessing NFS were in
_psema_miss except for one that was running in
cpu. This is the same problem this customer had
as described in JAGad16541 (8606147198) NFS
performance problem due to bad compare_cred()
logic in nfs3_vnops.c.
Resolution:
The current calculation sizeof(*cr1) -
sizeof(cr1->cr_ref) - sizeof(cr1->cr_pag) yields
100 bytes. However, cr1->cr_pag is an 8-byte
structure in a 64 bit OS. Since it is 8-byte
alligned, there are 4 bytes between cr1->cr_ref
and cr1->cr_pag that were unaccounted for.
The fix is to #define a size of 96 and use it
in the comparison.
libnfs.a
JAGad31017
The NFS client does not get new attributes during
close-to-open when a file is not cached.
Resolution:
The NFS client now gets new attributes from the
server at file open time if close-to-open
consistency (i.e. MI_NOCTO is overridden at
mount time) is desired.
libnfs.a
JAGad27560
Panic occurs when vfs lock is improperly unlocked
and an attempt to unlock it occurs.
Resolution:
Code modified to check the return value of
vfs_lock and if it is busy, sleep for some time
and try to acquire the lock again.
libnfs.a
JAGad32551
v_count was not decremented properly in the
NFS_BLKINVALFREE macro. In the case of removing
the file, instead of sending the remove rfscall
to the server, the client renames the file to
another name and the file remains.
Resolution:
The fix is to call the routine binvalfree() instead
of the NFS_BLKINVALFREE macro in order to decrement
v_count properly.
libnfs.a
JAGad35601
By masking SIGKILL and SIGSTOP it is not possible to
kill an NFS client process if the server goes down.
Also, SIGKILL and SIGSTOP are non-maskable signals in
HP-UX, hence they should not be masked.
Resolution:
Unmask SIGKILL and SIGSTOP in masked_sigs in
the routine, nfs_subr.c.
libnsl.1/a
JAGad09968
The function authunix_create() calls abort()
if more than 16 groups are passed in args (gids).
Resolution:
Replaced abort() code with return(NULL). This
prevents code from dumping.
libnsl.1/a
JAGad29722
A thread walks off its stack due to a very large
stack variable (struct pollfd svc_pollset) in
svc_run.c, thereby resulting in the corruption
of unrelated memory.
Resolution:
1) Removed the explicit initialization of fd_set
svc_fdset in rpc_comdata.c.
2) Changed the array sizes of svc_pending_fds and
svc_pollset to kernel tunable parameter
maxfiles_lim, and dynamically allocated both
arrays.
3) Reduced FD_SETSIZE in svc_vc.c's
__svc_nisplus_purge_since() to 1024.
librpc.a
JAGad39062
NFS incorrectly handles a machine name length
that is negative by not rejecting such a value
and then attempting to use it as an offset into
an array. A negative machine name length is
allowed because it is declared as signed.
Resolution:
NFS interprets the machine name length as unsigned,
thus eliminating any negative values.
librpc.a,nfsd
JAGad36339
NFS/TCP incorrectly handles the case where a new
thread cannot be created by the NFS TCP kernel
daemon (nfsktcpd). In such cases, it allows data
to come in to be processed though there is no
thread to do such. On the close of the data
stream, the nfsd associated with TCP hangs
waiting for the incoming data to be processed.
Resolution:
NFS/TCP immediately closes the data stream when
its associated thread cannot be created.
newkey
JAGad26923
In changing a public/secret key pair for the
privileged user of a given hostname on the master
server with "newkey", this command fails with
error message, "ERROR, passwd differs from
login passwd". "Newkey" prompts for the root
password of the given hostname, but compares
the given password with the root password of
the master server.
Resolution:
The prompt to ask the root password of the given
hostname is inserted if the password supplied is
different from that of the master server.
PHNE_22125:
libautofs.a
JAGad13210
The root cause involves an atypical use of a for
loop in the force_remount() function of the module
auto_subr.c. Using the for loop to traverse a
linked list, the increment or looping expression
assigned to a pointer variable was a variable that
had previously been assigned to the next item in
the list. The problem here is that the value of
the next pointer may be altered by a different
thread during the execution of the for loop's body.
When this happened, the next loop iteration was
then processing an item that had been released
from use and no longer part of the list. This
situation manifests itself in the above symptom.
Resolution:
Change the code so the for loop's increment
expression does the incrementing.
libnfs.a
JAGac86286
While testing a large (25MB or more) file
transfer from an NFS client to an NFS server,
the NFS server is TOC'ed during the copy.
The client hard mounts the NFS server, so
the copy command will hang waiting for the
NFS file server to come back up. When the
NFS server comes back up, the copy
continues and eventually completes. When
you do a cksum on the local file and the
remote file, the values are different.
Data is missing from the remote file.
Resolution:
Record the write verifier before
collecting the buffers instead of
sending time. Every time when the buffer
is not used, just clear all of its links.
libnfs.a
JAGad14221
HP NFS makes 2 GETATTR RPC calls for each
synchronous read and 1 GETATTR RPC call for
each synchronous write on a file opened with the
O_RSYNC|O_SYNC flags set, while SUN NFS makes 1
GETATTR RPC call per synchronous read and 0
GETATTR RPC calls per synchronous write. An rnode
for an NFS file with the RNOCACHE flag set gets
put on the rnode free list after the file is
closed, and a subsequent open of the same NFS
file will pick up the same rnode from the free
list with RNOCACHE flag set, causing I/O mode to
be synchronous for this subsequent open even
though the O_RSYNC|O_SYNC flags were not set.
Resolution:
Extraneous GETATTR calls in the NFS synchronous
read/write path have been removed. The synchronous
flag RNOCACHE for an rnode is now turned off
during NFS file close to eliminate persistent
synchronous I/O mode across system calls.
libnfs.a
JAGad16541
The compare_cred function was unnecessarily
checking the cr_ref and cr_pag of the cred
structure. It was also redundantly checking
the groups' array.
Resolution:
Removed checking of cr_ref, cr_pag and redundant
check of groups' array.
libnfs.a
JAGad15306
The tar command complains about "Optional
ACL entries". An ll command shows some "+"
signs in the mode bits. A second ll command
shows no more "+" signs. This is caused by
uninitialized bit field va_aclv.
Resolution:
Since NFS does not support ACL's, initialize
va_aclv to 0.
libnfs.a
JAGac84458
A 64-bit machine may panic when executing
a command over nfs hits the path that
calls makenfsnode or makenfs3node. This
happens only on a 64-bit machine and is
caused by an assignment in these routines
that causes non 8-byte alignment.
Resolution:
Remove this assignment that causes non 8-byte
alignment in makenfs3node and makenfsnode.
libnfs.a, librpc.a
JAGad29423
NFS is not working properly for a mount option
specified as interruptible or non-interruptible.
An example, non-interruptible is interruptible
in NFS/UDP.
Resolution:
Fixed the mount intr/nointr option so that it
behaves as expected.
libnfs.a
JAGad13957
NFS incorrectly checks the filemode
flags when opening a file for read-only
access. Because of this, it mistakenly
views the access as writable and
modifies the write credentials. This
causes the "Permission denied" error
in the write operation.
Resolution:
NFS correctly checks the filemode flags
when opening a file. In particular, it
checks the filemode against FWRITE
instead of O_WRONLY and O_RDWR.
libnfs.a, librpc.a, nfsd
JAGad14853
When NFS is stopped and re-started, the nfsd
transport table can reach a state where the table
is full and the new nfsd daemons start faster
than the old nfsd daemons stop. The only way to
get the table to a correct state is to reboot the
system.
Resolution:
Fix the code that controls the nfsd transport
table.
libnfs.a, nfsd
JAGad16228
When NFS is stopped and restarted, and then
additional nfsd processes are started, the
nfsd processes which were started first are
no longer registered with rpcbind. This
causes the rpcinfo command to fail.
Resolution:
Modify the return errno from EINVAL to EIDRM
which will be used in nfsd.
librpc.a
JAGad24321
If a client mounts an NFS file system with an
interruptible mount over TCP when the server is
down, the client is expected to try for a period
of time and quit with an RPC time out error
message. This does not happen in RPC/TCP path,
and the client is hung.
Resolution:
The RPC/TCP code was fixed so it does not sleep
on cv_wait() for a soft interruptible mount.
librpc.a
JAGad13205
This was traced to a 64-bit only issue. On a
64-bit system, a particular arithmetic expression
always resulted in a non-negative result. The
subsequent test for a negative result always
failed therefore sending actual negative results
down the wrong code path. Repeated occurrences
eventually caused the system to hang.
Resolution:
A variable in the arithmetic expression was
changed to type int so the arithmetic could
correctly result in a negative number.
librpc.a
JAGad13818
If for some reason the peer wants to tear the
TCP connection, it sends us a FIN, but then
nothing happens. The TCP connection remains in
the CLOSE_WAIT state and we keep sending NFS
requests on this connection. Eventually the
local inactivity timeout will pop which will
remove this connection. This problem happens on
64-bit machines only.
Resolution:
Changed data types from unsigned long to
unsigned int so that messages such as FIN are
not dropped.
nfs.core
JAGad29173
After installing PHNE_20371 or PHNE_21376 on a
system with a default umask which does not allow
universal read permission, the /etc/services file
permissions are set per the default umask and
non-root processes cannot read the file.
Resolution:
Modify the "/sbin/init.d/nfs.core" script to
preserve original permissions and ownership of
"/etc/services" in the case where it operates on
"/etc/services" to add a service entry for
NFS/TCP, by using "cp -p" on "/etc/services" to
create a working copy for editing, and then
using "mv" to overwrite the original
"/etc/services" with the changed version.
rpc.lockd
JAGad14812
When a client crashes and does recovery after
locking a remote file, the server does not grant
the lock held by the crashed client to other
clients waiting for the lock.
Resolution:
In recovery, server releases the lock information
held by the crashed after waking up a client
waiting for the lock.
rpc.mountd
JAGac68822
The mount function returns the ENOENT error, without
checking the existence of the file in the mount table,
when the realpath() function does not find the path
entry for the file.
Resolution:
The function call "mount_enoent_error" is added to
check the existence of the file or the existence
of a the file name entry in the mount table and
return the error appropriately, when the realpath()
in the mount function fails with the ENOENT error.
rpc.statd
JAGad12739
When the server receives SM_NOTIFY protocol,
the send_notice() in the rpc.statd is looking
for a client from the monitor list.
Then the looping problem between clients and
server occurs which is caused by the excessive
amount of time spent in gethostbyname()
in send_notice()
Resolution:
The lookup procedure in send_notice() is changed.
Instead of calling gethostbyname(),
IP addresses are compared.
ypserv
JAGad25155
When more then two processes execute the
"id/group" command simultaneously, the ypserv
fails to return group information to all
processes.
Resolution:
A local data structure is defined where a
buffer is allocated to keep the nextkey or
firstkey.
PHNE_21376:
automountd
JAGac84450
Some mount points become inactive and cannot be
re-mounted (they are seen as empty directories).
For example, if /sys is an indirect map, we may
end up with ls /sys which shows a directory
"srv_spool", but ls /sys/srv_spool returns an
empty directory (it should trigger an NFS mount).
Resolution:
Two problems were resolved - one in automountd
and one in libautofs.a (see below). The
automountd process was modified to detect
duplicate requests in a more reliable fashion.
exportfs
JAGab78579
During the mount process rpc.mountd on the NFS
server resolves the requested mount path to its
actual path, then it verifies export permission
for this path against the list of export entries.
Previously rpc.mountd would resolve each path
entry in the exports list before verification
comparison, now it no longer does; and exportfs
exports directory paths exactly as specified to
it without resolving linked paths.
Resolution:
exportfs resolves symbolic links to real
directory paths and exports the real directory
paths.
libautofs.a
JAGac84450
Some mount points become inactive and cannot be
re-mounted (they are seen as empty directories).
For example, if /sys is an indirect map, we may
end up with ls /sys which shows a directory
"srv_spool", but ls /sys/srv_spool returns an
empty directory (it should trigger an NFS mount).
Resolution:
Two problems were resolved - one in automountd
(see above) and one in libautofs.a.
The libautofs.a routines were modified to
wakeup all threads sleeping on the mount
regardless of whether the first requestor has
been interrupted, and to preserve partially
mounted autonodes when an interrupt occurs to
allow the mount to complete.
libnsl.1/a
JAGad03728
Since the default stack size for pthread is 64 K bytes,
the large stack usage in functions like nis_cast()
ultimately causes the pthread stack overflow.
Resolution:
Moved the automatic variables which take up a large
stack space to the heap area by malloc'ing the variables.
libnsl.1/a
JAGad13073
The library functions svc_vc_create() and
svc_vc_xprtcopy() incorrectly made duplicate calls
to t_alloc which causes the memory leak.
Resolution:
Removed the second t_alloc() call from both functions.
libnsl.1/a, rpc.nisd
JAGab78042
rpc.nisd forks a child to handle existing connections
when it does checkpointing (nisping -Ca). The child
may close some of these connections. But the descriptors
still stay open in the parent process.
Resolution:
Added a mechanism to clean up the idle file descriptors
periodically in the svc_run() forever loop. The clean up
functions are defined in the libnsl/rpc.
rpc.lockd
JAGad00646
There are routines that call "xmalloc()" but do not
check the value returned. A "NULL" pointer is
returned from "xmalloc()" when no memory is available.
A "NULL" pointer value will cause a "core dump" if used
to access data.
Resolution:
Check the return value of xmalloc() in prot_nlm_share(),
prot_nlm4_share(), new_sxx() and new_sxx4().
Log the reason of failure in these routines.
rpc.statd
JAGad00517
There are routines that call "xmalloc()" but do not
check the value returned. A "NULL" pointer is
returned from "xmalloc()" when no memory is available.
A "NULL" pointer value will cause a "core dump" if used
to access data.
Resolution:
Check the return value of xmalloc() in insert_name() and
log the reason of failure in this function.
rpc.statd
JAGad05198
When an unknown host requests a file lock, rpc.statd
in the server site can not add this client to the
monitor queue as the hostname was not resolved.
So the lock request would be failed. But the unknown
host keeps sending lock requests, which causes the
memory region of rpc.statd to be used up and finally
abort.
Resolution:
The insert_mon() in rpc.statd is called to add a client
to the monitor queue. In case that this routine fails,
free the memory area allocated before this routine is
called.
rpcbind
JAGad01128
Rpcbind writes warm-start RPC service registration
information on shutdown to files in an unsafe way.
Resolution:
Rpcbind modified to handle shutdown file writes properly.
ypserv
JAGad03431
ypserv closes its own UDP socket when it receives the
YPPROC_ALL request.
Resolution:
Added the check in the ypall function to make sure that
the only TCP server handle gets destroyed and not the
UDP server handle.
PHNE_20627:
libnfs.a
JAGad03354
The NFS server "readdirplus" directory read routine was
packing data into its RPC directory information buffer
beyond its 8Kb size, resulting in corrupt directory data
being returned to the RPC layer causing delays in NFS
server response to NFS client readdirplus calls.
Resolution:
The NFS server calculation of directory information size
during packing for response to "readdirplus" calls was
corrected.
JAGab82363
On an NFS client an extra buffer and buffer cache entry
was allocated by read/write path routines when reading
NFS files with size a multiple of the NFS read window;
when such files were removed on the NFS client the extra
buffer was not removed and continued to hold a reference
count on the file vnode causing the vnode subsystem to
think the file was kept open by NFS and the kernel to
create an arbitrary file entry, ".nfsXXXX" for the
vnode.
Resolution:
The NFS client read/write path routines were modified
so that if it appears that an NFS file is going to be
read past EOF, then the cached attributes for the file
are validated and a re-check for read past EOF is done;
which prevents allocation of an extra buffer cache entry
for files with size a multiple of the NFS read window.
JAGad04931
On an NFS client when a directory move was done, the dnlc
entry for the ".." directory entry became invalid but was
not being removed.
Resolution:
The NFS client rename routines were modified to remove
the invalid dnlc entry for ".." for a directory when a
directory move was done.
JAGad04932
On an NFS client the read/write path routines would
return immediately without validating cached file
attributes if a read past EOF was attempted; so, any
unmount attempted flushed the buffer cache entries causing
the NFS client to not know that file size had changed and
a "tail -f" command on the NFS client showed no change in
the file even though it was being appended to on the NFS
server.
Resolution:
The NFS client read/write path routines were modified
so that if it appears that an NFS file is going to be
read past EOF, then the cached attributes for the file
are validated followed by a re-check for read past EOF;
so the NFS client will always see an updated size for
a given file and a "tail -f" command on an NFS file
would follow any appends to the file done on the NFS
server.
PHNE_20371:
autofs/mount
When the system hostname is longer than 8
characters uname() reports the nodename as
"unknown", and ONC/NFS subsystems using this
call fail because the local hostname cannot
be determined.
Resolution:
Replace uname() calls for system hostname with
gethostname().
automount
When the system hostname is longer than 8
characters uname() reports the nodename as
"unknown", and ONC/NFS subsystems using this
call fail because the local hostname cannot
be determined.
Resolution:
Replace uname() calls for system hostname with
gethostname().
automount,automountd
automount with stalemounts causing duplicate
mnttab entries & lock problems.
Resolution:
Automount and automountd code was revised to
handle this situation. we now check the mnttab
for 'stale' entries and then remove them.
automountd
When the system hostname is longer than 8
characters uname() reports the nodename as
"unknown", and ONC/NFS subsystems using this
call fail because the local hostname cannot
be determined.
Resolution:
Replace uname() calls for system hostname with
gethostname().
automountd
Automountd processes executable maps incorrectly.
Resolution:
Automountd modified to handle executable maps
correctly.
automountd
When an autofs map entry specifies the
mount option "proto=udp", an attempt to
mount that entry fails to mount and prints
a message "udp protocol not allowed".
Resolution:
Allow the specification "proto=udp".
User modules: autod_main.c, autod_nfs.c
libautofs.a
When an autofs link is part of a shell pipe,
it can intermittently fail to generate a mount
request. It happens primarily on MP boxes.
Resolution:
Add SIGINTR/SIGUNINTR() calls to mask lower-priority
signals (e.g., SIGCLD) to prevent a race to interrupt
an daemon request while in progress. High priority
signals such as SIGINT and SIGHUP are unaffected.
Modules affected:
auto_vnops.c
auto_subr.c
libautofs.a
autofs controlling cachefs indirect map
may hang on mount or unmount.
Resolution:
Improve detection logic to allow automountd
detection logic to detect mount calling mount
or umount calling umount.
Change applied to AUTOFS_PROCESS_IS_AUTOMOUNTD
macro in kernel.
libnsl.1/a
NFS protocol on HP-UX was originally designed
only to use UDP.
Resolution:
Provide support for the NFS protocol over
TCP.
libnsl.1/a
When the system hostname is longer than 8
characters uname() reports the nodename as
"unknown", and ONC/NFS subsystems using this
call fail because the local hostname cannot
be determined.
Resolution:
Replace uname() calls for system hostname with
gethostname().
libnsl.1/a
Automountd processes executable maps incorrectly.
Resolution:
Libnsl modified to provide RPC functionality to
support the correct handling of executable maps
by autofs/automountd.
libstraddr.1
When the system hostname is longer than 8
characters uname() reports the nodename as
"unknown", and ONC/NFS subsystems using this
call fail because the local hostname cannot
be determined.
Resolution:
Replace uname() calls for system hostname with
gethostname().
make.script
When mail.aliases contains no space around ":",
makemap, which is called by ypmake fails.
Resolution:
changed sed in Makefile to substitute a space
in place of a colon.
mount
NFS protocol on HP-UX was originally designed
only to use UDP.
Resolution:
Provide support for the NFS protocol over
TCP.
nfs.core
NFS protocol on HP-UX was originally designed
only to use UDP.
Resolution:
Provide support for the NFS protocol over
TCP.
nfs/mount
When the system hostname is longer than 8
characters uname() reports the nodename as
"unknown", and ONC/NFS subsystems using this
call fail because the local hostname cannot
be determined.
Resolution:
Replace uname() calls for system hostname with
gethostname().
nfsstat
NFS protocol on HP-UX was originally designed
only to use UDP.
Resolution:
Provide support for the NFS protocol over
TCP.
nisplus/nisserver
When the system hostname is longer than 8
characters "uname -a" reports the nodename as
"unknown", and ONC/NFS subsystems using this
call fail because the local hostname cannot
be determined.
Resolution:
Replace "uname -a" command for system hostname with
"hostname".
rpcinfo
When the system hostname is longer than 8
characters uname() reports the nodename as
"unknown", and ONC/NFS subsystems using this
call fail because the local hostname cannot
be determined.
Resolution:
Replace uname() calls for system hostname with
gethostname().
rpc.lockd
rpc.lockd is not able to correctly identify
the case where a lock is local or remote and
take the appropriate action.
Resolution:
Made the changes to remote_data(), the
function that is used to determine if
data being locked/unlocked is at remote side
or not. Put in additional checking when
strcmp() against two host names not the same,
if short name of two hosts are the same,
comparing IP addresses to determine the
result. Also fixed not able to perform wakeup
after doing the local unlock (fix is in
overlap()).
rpc.lockd
The root cause to this problem was that
rpc.lockd retrieves/caches the port number of
remote end after dealing with the LOCK, UNLOCK,
TEST and CANCEL requests, however it only
adds the monitor entry for LOCK requests.
It should monitor that remote end when caches
info for the requests because it would use the
cached info later without knowing that remote
end state changes and its cached port number
is not up-to-date any more.
Resolution:
Made the change to call add_mon() that
regardles of the KLM request we add the
monitor entry.
setoncenv
NFS protocol on HP-UX was originally designed
only to use UDP.
Resolution:
Provide support for the NFS protocol over
TCP.
ypmake
When mail.aliases contains no space around ":",
makemap, which is called by ypmake fails.
Resolution:
changed sed in Makefile to substitute a space
in place of a colon.
PHNE_20344:
libnfs.a librpc.a nfs_iface.o
Reads and writes for NFS version 3 are currently
limited to 8kB.
Resolution:
Enhanced NFS version 3 to support the full 32k
read/write block size.
libnfs.a
rfs3_readdirplus() calls kmem_alloc() even when
the allocation request size is zero, which causes
a minimum of 32 bytes of memory to be allocated
each time.
Resolution:
rfs3_readdirplus() modified to check for and avoid
calling kmem_alloc() when the allocation request
size is zero.
libnfs.a
NFS server code path flow through readdirplus() is
a SPECsfs97 performance bottleneck.
Resolution:
The readdirplus() code path was optimized to get
a much better IOPs number for SPECsfs97.
libnfs.a
On the NFS client an incorrect algorithm for gauging
"memory pressure" and an "nfs_do_purge_rddir_cache"
with a default setting of 1, cause the readdir cache
to be purged too often, reducing performance.
Resolution:
Replaced the MEMORY_PRESSURE macro with a call to
thrashing(). We are interested in purging the
client cache and reusing client cache entries if
and only if we are under high system load. Memory
pressure was not an accurate indicator but the
thrashing call is exactly the correct indicator.
libnfs.a
The HP-specific kernel variable "do_readdirplus" was
removed from NFS server kernel code in a previous
NFS kernel patch.
Resolution:
"do_readdirplus" and support code added back into NFS
readdirplus() code.
PHNE_19759:
1.fuser -f on a NFS file on the client does not show
pids of openers of this file due to missing update
to vnode fid on the client (JAGab68768,JAGab54207) .
Resolution:
The file attribute cache is updated with fid
received from server but is not copied to
the vnode field.This leads to fuser file id
comparision failure.This has been fixed.
2.Invalid name length is returned by NFS pathconf
from HP Server on regular files because HP's local file
system does not support Pathconf on regular files
and when SUN's compress command generates Pathconf
on regular files, server replies with name length
of zero ( JAGab20794) .
Resolution:
On the server,Pathconf() oprn to local FS now
specifies the file directory,rather than the
file itself.This works.
3.getmount_entry() returns down status for all hard
mounted NFS file systems (JAGab69071) ,
Resolution:
An invalid logical bitwise operation of the
mount flags resulted in an invalid mount
status return from a kernel function.
This has been fixed.
PHNE_19620:
automountd
JAGab72053
When an existing autofs mount of a remote NFS
server times out, and the server is unavailable,
the unmount attempt from autofs results in an
indefinite suspension of autofs service.
Resolution:
Put code into autod_mount.c to "ping"
the host before attempting a stat() call.
If the "ping" times out, abandon this
unmount request.
JAGab70009
On a system which has a system setting
of maxfiles > 2048, if replicated automounts
are used, the automountd function nfs_cast()
will return EBADF and fail to mount.
Resolution:
Limit the size of the select() block
to FD_SETSIZE entries or less.
Routine modified: nfs_cast.c::nfs_cast()
-----
libautofs.a
JAGab73529
autofs with cachefs under stress testing
can panic in cachefs_root(). Reported
originally on 10.20.
Resolution:
Additional autonode state testing
in autofs::hpauto_trigger_mount()
prior to calling VFS_ROOT().
Module affected is auto_vnops.c
JAGab72920
When autofs is used with a non-NFS mount
point (such as cdrom), it call fail to
mount when it uses the "mount" command.
Resolution:
Fix detection logic for automountd versus
normal client lookup. Detects if either
process is "automountd" or it is a "mount"
command spawned by "automountd".
Kern modules: hpautofs.h, hpautofs.c
User modules: autod_mount.c
-----
libnsl.1/a
JAGab41115
The address "merging" on a host performed by
rpcbind when it receives and executes its
RPCB_GETADDR procedure can fail if the host
has multiple network addresses.
Resolution:
Modify the function "inet_netdir_mergeaddr"
in libnsl/nss/netdir_inet_sundry.c which
performs address merging to use a better
algorithm by calling a newly added function
get_best_match(), which uses the matching
algorithm from ONC+ v2.2 to perform address
matching.
-----
libnss_nis.1
JAGab20796
getservbyname() looks up a HP non-supported
map "services.byservicename and calls
yp_all when the lookup fails.
yp_all would get the whole map over the
network which is time consuming.
Resolution:
Add a lookup to servi.bynp to avoid the yp_all call.
-----
librpcsvc.a
JAGab70329
If the number of active remote mounts becomes
sufficiently large (approx 23000+), rpc.mountd
will terminate with SIGSEGV when "showmount -a"
is requested of the server.
Resolution:
Modify routine librpcsvc.a::xdr_mountlist()
to traverse a linked list without recursion.
-----
rpc.lockd
JAGab74177
An 11.0 client fails to lock files on a
virtual NFS server if the answer to the
getport call from NLM comes from a different
IP address than the virtual IP address of
the server (i.e., from the address of the
current physical server).
Resolution:
Fix rewriting of address in routine
recv_from_pmap() to:
- Preserve the cached address (if any)
- Use the client handle address rather
than the address of the client reply
when generating a new cached address.
Module affected is pmap.c.
JAGab45462
Using the reserved port number is a common
symptom to all of our RPC services because
we check all possible port numbers within
reserved port range, 600 to 1024.
Resolution:
Use XTI-based API, svc_tli_create() which
triggers kernel to provide the random port
number automatically.
JAGab15223
The lockf() system call, when issued
on a remote file, can permanently hang
if the remote file gets removed.
Resolution:
Within wakeup(), the function to be called
when a delete is successful or when an
exclusive lock is downgraded to a shared lock,
before wakeup taking place make sure that
nfs_fcntl() succeeds or the errno set by
nfs_fcntl() is equal to ESTALE, i.e.
Stale NFS file handle.
JAGaa45544
The root of the problem is when the NFS server
is mounting one of it's local filesystems to
itself using a server hostname other than the
local hostname. This causes both the client-side
and server-side portions of rpc.lockd to
add/delete/enqueue/dequeue entries from the
single set of queues. The end result is that the
client-side rpc.lockd code ends up dequeuing
entries that the server enqueued and vice-versa.
This is what leads to the "lock table
inconsistent" messages.
Resolution:
Within add_wait(), before declaring a reclock
is a match to an existing blocking lock, make
sure that the server is the same as well.
Within wakeup(), removing remote_clnt() to
send a callback to a blocked loopback NFS lock.
-----
rpc.mountd
JAGab45462
Using the reserved port number is a common
symptom to all of our RPC services because
we check all possible port numbers within
reserved port range, 600 to 1024.
Resolution:
Use XTI-based API, svc_tli_create() which
triggers kernel to provide the random port
number automatically.
-----
rpc.statd
JAGab45462
Using the reserved port number is a common
symptom to all of our RPC services because
we check all possible port numbers within
reserved port range, 600 to 1024.
Resolution:
Use XTI-based API, svc_tli_create() which
triggers kernel to provide the random port
number automatically.
PHNE_18221:
libautofs.a
=== JAGab00144 - AutoFS is not triggering re-mount ===
Running AutoFS with very short node timeout (e.g.
"automount -t0") can cause failures to access files
which are present.
=== JAGab03833 - AutoFS hangs even with PHNE_17200 ===
AutoFS with a short node timeout with a script
using manual umounts in a tight loop can hang autofs
after 10-15 minutes.
=== JAGab11283 - cp(1) fails to inactive direct mount ===
When a command is given to copy a file to the
top of an unmounted direct mount point, 'cp' fails
with "Operation not supported".
== JAGab16597 - mv command fails in AutoFS direct mnt ==
When the 'mv' command is used to rename a file
from the current directory and it is a direct mount
point, it will fail if the direct mount is not already
active (mounted), with error ENOSYS.
=== JAGab18083 - getcwd() fails with AutoFS filesys ===
A 64-bit mode compiled program which calls getcwd()
&nb