We were running 4.0D on our 4100 for quite a while until we ran into
some comm problems, which made us realize that we hadn't applied
Firmware rev 5.0 on the machine. After applying it, we had a database
process (Open Ingres 2.0) go into a "U" state every night, required
a daily reboot, not making the customers too happy. DEC said to
install patch kit #1, which we did, and that causes a different DB
program to core immediately upon being called. The "U" state
problem did appear solved, however.
The program worked again after de-installing the patch kit, and
we'll put up with rebooting for now. We took our currently
inactive 2100 and set it up with FW 5.0, DU 4.0D and no patch
kit, and are trying to install without some of the likely problem
patches to see where the DB program does and doesn't core.
However, when not installing the entire patch kit, the whole
install process goes off the deep end. One check can't find
some programs (tar, awk, etc.) which clearly exist. So, we
told dupatch to continue with the items that passed the check,
and every patch gets errors which look like:
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=**
Checking file system space required to install specified subsets:
File system space checked OK.
37 subset(s) will be installed.
Loading 1 of 37 subset(s)....
Patch: NFS V3 mounted AdvFS Patch Correction
Copying from /tmp/v40d-patch1/patch_kit/kit (disk)
tar: - : This doesn't look like a tar archive
tar: - : Skipping to next file...
setld:
File copy to system disk failed.
Subset OSFPAT00008301425 may not have been installed properly on your system
but the rest of the installation will continue.
Verifying
setld:
^GThere were verification errors for "Patch: NFS V3 mounted AdvFS Patch Correc
tion" (OSFPAT00008301425)
Loading 1 of 37 subset(s)....
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=**
Actually this very patch kit had been installed and then de-installed
on this system, so it works when doing the whole kit. The files in
../kit are indeed NOT tar files, so we're rather puzzled what's going
wrong. We've tried running dupatch from the patch_kit directory, and
then from the root directory, with no difference in results.
Any insight would be greatly appreciated.
Thanks,
Michael
mjwatson_at_livenet.net
Received on Fri Jun 05 1998 - 17:53:37 NZST