Ignite backup failing on pax. patch installed

[GK_5]

Hi

The ignite backup on two of my servers failing when it is testing pax. The output of ignite is like this

cp: Warning: cannot cpacl to /var/tmp/ign_configure/include_exclude24629:
* Testing pax for needed patch
pax: /var/tmp/pax_test : Optional ACL entries are not backed up.
pax: /var/tmp/pax_test/foo : Optional ACL entries are not backed up.
ERROR: /sbin/pax failed, cannot use it
WARNING: The version of pax on the system to be archived needs to be
patched with one of the following patches or newer ones. If you do not
load the pax patch some files will not be correctly archived
(See the Ignite-UX release notes for details):

System OS Patch needed
--------- ------------
10.01 PHCO_11975
10.10 PHCO_11976
10.20 PHCO_20388
10.30 PHCO_11978
11.00 PHCO_25418
11.11 PHCO_26422

you can get patches over the web from the patch database
(http://itresourcecenter.hp.com) or directly from the FTP server
(ftp://us-ffs.external.hp.com).

This is on HPUX 11.00 and the patch PHCO_25418 is installed. The output of "swlist -l patch | grep 25418" is

PHCO_25418.UX-CORE 1.0 OS-Core.UX-CORE applied
# PHCO_25418 1.0 pax(1) cumulative patch
# PHCO_25418.UX-CORE 1.0 OS-Core.UX-CORE
applied

Any advice?
Thanks

[Jeff Schussele · Accepted solution]

Hi GK,

We see the same thing on one of the last 10.2 systems we have & it DOES have PHCO_20388.
We couldn't figure it out & just fell back to make_recovery - which did work.

You may want to do a

swlist -l patch -a state | grep 25418

to make sure it's in the configured state.

We have ver 4.1.55 of Ignite - if you have the same, I wonder if it's a "feature" - you know the crawly kind ;~))

Rgds,
Jeff

[GK_5]

Thanks Jeff.
The patch is configured. This is on HPUX 11.00 running Ignite 4.3.123
But the same version is working on other 11.00
I'll try make_recovery.

[Steven E. Protter]

That last pax patch lets you pack files up to 8 GB.

You need to see if pax_iux has been upgraded so it can handle files bigger than 2 GB or when you try to restore that file or push a golden image, the transfer will hang.

SEP

[Steven E. Protter]

I'm working with this on a D320 box right now.

4.1.61 was installed and remained installed after installing the pax patch and the 4.3.x release.

With past releases I've been forced to remove the prior Ignite release prior to installing the new one. After this, I had to restore my configurationi files for golden images and such.

make_tape_recovery seems to be working pretty well. I will test make_net_recovery and golden image creation after weekend maintenance.

The pax patch is now PHCO_28414 for 11.11

I do not know how I will test pax_iux, I don't have a machine that needs to load a golden image right now. We really could use some sandbox hardware for our shop. We're a charity and its tax deductible.

:-)

SEP

[Sridhar Bhaskarla]

Hi,

Do a "what /sbin/pax" and see if it lists it as from PHCO_25418. If not, then try

swconfig PHCO_25418 or reinstall it and see if it works.

It may be checking for the binary version of 'pax' than the patch IPD.

-Sri

[Bill Hassell]

Another test is:

type pax

This will report exactly where the current shell will locate the pax file. Make sure it is /usr/bin/pax and that /usr/bin/pax i9s *NOT* a symbolic link. The what command should report:

# what /usr/bin/pax
/usr/bin/pax:
$Revision: 82.13.1.9 $