Hey Martin,
Thanks for explaining it to me. The interesting behavior is that I am
NOT explicitly asking for "--safe" installation and I still get the
following outcome. Am I doing something wrong?:
NOTE: I also get the same result if I use "--norootchk"
# ./pca -X `pwd` -y -i 113434-40.zip
Using /pca/myhost/patchdiag.xref from Aug/22/11
Host: myhost (SunOS 5.9/Generic_122300-60/sparc/sun4u)
List: 113434-40 (1/0)
Patch IR CR RSB Age Synopsis
------ -- - -- --- ---
-------------------------------------------------------
113434 38 < 40 RS- 334 SunOS 5.9: /usr/snadm/lib Library and
Differential Flash Patch
Looking for 113434-40 (1/1)
Found patch file
Installing 113434-40 (1/1)
Unzipping patch
Checking files for safe patch installation
failed file verification:
ERROR: /usr/sbin/flarcreate
modtime <04/27/10 11:35:04 AM> expected <11/18/10 10:48:50 AM>
actual
file size <32320> expected <32420> actual
file cksum <18824> expected <26615> actual
Failed - file verification (10:04:23/00:00:01/00:00:03, 1/1, 0/0/1)
------------------------------------------------------------------------
------
Download Summary: 1 total, 0 successful, 1 skipped, 0 failed
Install Summary : 1 total, 0 successful, 0 skipped, 1 failed
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Martin Paul
Sent: Wednesday, August 24, 2011 12:41 AM
To: PCA (Patch Check Advanced) Discussion
Subject: Re: [pca] Failed File Verification
Coskun, Aydin wrote:
> Can anyone please help me? I get this error :
>
> Checking files for safe patch installation
>
> failed file verification:
>
> ERROR: /usr/sbin/flarcreate
>
> modtime <04/27/10 11:35:04 AM> expected <11/18/10 10:48:50 AM>
actual
> file size <32320> expected <32420> actual
> file cksum <18824> expected <26615> actual
You are running PCA with its "--safe" option. This runs "pkgchk" on
every file
included in a patch before installing the patch, to ensure that a patch
won't
overwrite files with local modifications (patchadd would simply replace
the file
with the version included in the patch zip file).
Sometimes the database with the checksums isn't correct, though, leading
to
false warnings. It's on the admin to decide what to do then: If you're
sure that
the file can be safely overwritten, re-run the patch installation
without "--safe".
In your example it's /usr/sbin/flarcreate which doesn't have the size
and
checksum it's supposed to have. I haven't seen any false warnings with
that
file. Maybe it was indeed modified locally for some reason?
Martin.
