Patch-ID# 101176-06 Keywords: Online Backup security remote tape copilot socket restore recover Synopsis: Online Backup 2.0: Update patch Date: Mar/31/95 Solaris Release: 2.3, 2.4 SunOS Release: 5.3, 5.4 Unbundled Product: Online-Backup Unbundled Release: 2.0 Relevant Architectures: sparc BugId's fixed with this patch: 1036094 1041881 1063799 1066607 1098293 1100259 1109849 1112345 1115648 1117955 1118165 1118379 1120125 1121630 1127421 1128390 1128409 1129139 1129766 1131151 1133209 1133675 1133713 1134716 1135138 1137042 1137499 1139194 1139859 1140162 1144143 1146224 1146228 1149649 1158043 1163499 1171483 1173806 1173908 1175539 1190708 Changes incorporated in this version: 1190708 Patches accumulated and obsoleted by this patch: 100980-01 Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /opt/SUNWhsm/bin/recover /opt/SUNWhsm/include/protocols/dumprestore.h /opt/SUNWhsm/lib/dumpconfrc /opt/SUNWhsm/lib/dumpdf /opt/SUNWhsm/lib/dumpsetup /opt/SUNWhsm/lib/rpc.dumpdbd /opt/SUNWhsm/lib/rpc.operd /opt/SUNWhsm/sbin/dumpconfig /opt/SUNWhsm/sbin/dumpdm /opt/SUNWhsm/sbin/dumped /opt/SUNWhsm/sbin/dumpex /opt/SUNWhsm/sbin/dumpfind /opt/SUNWhsm/sbin/dumptm /opt/SUNWhsm/sbin/fastfs /opt/SUNWhsm/sbin/hsmdump /opt/SUNWhsm/sbin/hsmrestore /opt/SUNWhsm/sbin/opermon /opt/SUNWhsm/sbin/tapedbfix Problem Description: 1036094 dump(8) should not allow verify when dumping to stdout 1041881 Dump with verify option will fail when trying to dump your root partition 1063799 restore(8) doesn't handle empty non level 0 dump files 1066607 problems with long names in interactive restore 1098293 rrestore fails when the archive option is used 1100259 reclaim option for dumpdm does not delete dead records 1109849 (hsm)dump/(hsm)restore fails if filesystem has too many inodes 1112345 "dumpdm -s my -l 8mm pslabel csdhack_t:00000" gives unusable postscript 1115648 mastercycle isn't increased on first dumpex on backup copilot 1117955 remote dump of Backup Copilot system fails with non-root remote dump user 1118165 dumpex requests wrong, (unexpired) tape 1118379 update_data: RPC: Can't encode arguments appears on console 1120125 running remote recover can give problems with tape device naming 1121630 ufsrestore can't display Japanese filename in interactive mode 1127421 hsmdump and dumpdm should fix byte ordering 1128390 llseek() in bread() doesn't detect errors correctly 1128409 Time variable is displayed instead of time value on scheduling screen. 1129139 dumpdm tapelist is not complete when primary hostname is not first in /etc/hosts. 1129766 cannot use remote tape drives on systems with different byte order than your own 1131151 The 'm' option of restore doesn't work 1133209 dumpdm pslabel should support 4mm (DAT) tapes 1133675 hsmdump can dump core if ^C hit at wrong time 1133713 ufsdump, hsmdump say "DUMP: SIGSEGV() ABORTING!" and quit 1134716 hsmdump: 3rd argument to lseek() and llseek() wrong 1135138 bundled online: bacup uses incorrect textdomain 1137042 dumped occasionally causes superfluous characters to be added to the config file 1137499 ufsrestore can infinitely loop if run from disconnected tty 1139194 intermittent cannot open tape device being reported by hsmdump 1139859 recover restores the file with the full path name 1140162 security cleanup on various utilities 1144143 recover does not recognize superuser on host with fully qualified hostname 1146224 dumpfind cannot remove a temp directory because it is the current working directory 1146228 dumpex cannot create tapelist in NFS mounted /var/tmp 1149649 Multiple dumpex processes on one machine have trouble opening database file 1158043 Patch refers to itself as 101176-01 1163499 Online: Backup fails w/Veritas Volume Manager 1171483 hsmdump dumps core and leaves lock if encounters corrupted filesystem 1173806 SGI tapes restored with ufsrestore have corrupted symlinks 1173908 cleanup ufsdump/ufsrestore code 1175539 Backup Copilot has a security problem because it uses utmp 1190708 Online Backup 2.0 only supports 20 tapes per backup Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- None. Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Installpatch will backout the patch
to leave the system in its pre-patched state. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Error message:
Pkgadd of package failed with error code .
Will not backout patch...patch re-installation.
Warning: The system may be in an unstable state!
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
the patch packages failed. Installpatch will NOT backout the
patch. You may manually backout the patch using backoutpatch,
then re-apply the entire patch. Look in the log file for the
reason pkgadd failed. Correct the problem and re-apply the
patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Message:
Re-installing Patch.
Explanation: The patch has already been applied, but there is
at least one package in the patch that could be added. For
example, if you applied a patch that had both Openwindows and
Answerbook components, but your system did not have Answerbook
installed, the Answerbook parts of the patch would not have
been applied. If, at a later time, you pkgadd Answerbook, you
could re-apply the patch, and the Answerbook components of the
patch would be applied to the system.
Message:
Installpatch Interrupted.
Installpatch is terminating.
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files and exit.
Message:
Installpatch Interrupted.
Backing out Patch...
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files, backout the patch, and exit.
Patch Backout Errors:
---------------------
Error message:
prebackout patch exited with return code .
Backoutpatch exiting.
Explanation and corrective action: the prebackout script
supplied with the patch exited with a return code other
than 0. Generate a script trace of backoutpatch to determine
why the prebackout script failed. Correct the reason for
failure, and re-execute backoutpatch.
Error message:
postbackout patch exited with return code .
Backoutpatch exiting."
Explanation and corrective action: the postbackout script
supplied with the patch exited with a return code other than
0. Look at the postbackout script to determine why it failed.
Correct the failure and, if necessary, RE-EXECUTE THE
POSTBACKOUT SCRIPT ONLY.
Error message:
Only one service may be defined.
Explanation and corrective action: You have attempted to specify
more than one service from which to backout a patch. Different
services must have their patches backed out with different
invocations of backoutpatch.
Error message:
The -S and -R arguments are mutually exclusive.
Explanation and recommended action: You have specified both a
non-native service to backout, and a package installation root.
These two arguments are mutually exclusive. If backing out a
patch from a non-native usr partition, the -S option should be
used. If backing out a patch from a client's root
partition (either native or non-native), the -R option
should be used.
Error message:
The service cannot be found on this system.
Explanation and recommended action: You have specified a non-
native service from which to backout a patch, but the
specified service is not installed on your system. Correctly
specify the service when backing out the patch.
Error message:
Only one rootdir may be defined.
Explanation and recommended action: You have specified more than
one package install root using the -R option. The -R option
may be used only once per invocation of backoutpatch.
Error message:
The directory cannot be found on this system.
Explanation and recommended action: You have specified a
directory using the -R option which is either not mounted,
or does not exist on your system. Verify the directory name
and re-backout the patch.
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: You have attempted to backout
a patch that is not applied to this system. If you must
restore previous versions of patched files, you may have to
restore the original files from the initial installation CD.
Error message:
Patch has not been successfully applied to this system.
Will remove directory
Explanation and recommended action: You have attempted to back
out a patch that is not applied to this system. While the
patch has not been applied, a residual
/var/sadm/patch/ (perhaps from an unsuccessful
installpatch) directory still exists. The patch cannot be
backed out. If you must restore old versions of the patched
files, you may have to restore them from the initial
installation CD.
Error message:
This patch was obsoleted by patch .
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: You are attempting to backout
patches out of order. Patches should never be backed-out out
of sequence. This could undermine the integrity of the more
current patch.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used.
The original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev, cpio