SecurePath V3.0E installation problems on 11i v2 0409

[noldi]

Hello,

I'm having problems installing the SecurePath
V3.0E WEB Kit from
ftp://ftp.compaq.com/pub/products/sanworks/securepath/sphpv30eucd_web.tar.Z
to an rp2470 with HP-UX 11i V2 UD2.

The error message is:
.
.ERROR: The "postinstall" script for "CPQswsp.driver" failed (exit
code "1"). The script location was
"/var/tmp/BAAa05480/catalog/CPQswsp/driver/postinstall".
* This script had errors and the execution of this fileset
cannot proceed until the problem is fixed. Check the above
output from the script for further details.
.

See attachment for full details where
"swinstall" failed.

What could be the problem here?

Thank's & Regards,

Arnold

[Biswajit Tripathy]

It's clear that the "postinstall" script is failing.
To find what the problem is, you need to look for the
exact error message coming from the script (should
be in one of the log files in /var/adm/sw/sw*log).
Also, if you could post the postinstall script here
(location given in the above error message), it might
give some idea (clue: see where exactly in postinstall,
an exit code of 1 is returned).

- Biswajit

[noldi]

Hello Biswajit,

it seems that the SP 3.0e WEB-kit assumes
that LVM is setup as vg00 (excerpt from the
postinstall script):
.
.
/sbin/insf -e >/dev/null

VG=`vgdisplay -v /dev/vg00 |/usr/bin/awk '/PV Name/ {
print $NF}'`
if [ -z "$VG" ]
then ERROR_EXIT
fi
.
.

I guess this calls for escalation to
product support.

Thank's & best Regards,

Arnold

[Biswajit Tripathy]

Yes, it needs to be escalated to product support.

Also, to make sure that this really is the problem, you
could edit the "postinstall" script in the depot itself
and replace "/dev/vg00" with whatever device used
on your system and install from that depot. Note that
there might be multiple copies of "postinstall" file in
the depot; so you need to make the above change in
all the files (use "find" to find all the "postinstall"
copies).

- Biswajit

[noldi]

Hello Biswajit,

the problem is that this postinstall script
is only there for a short while in the
"/var/tmp" directory, and after "swinstall"
found that it produced an error, it is removed
immediately.

I need to find a way to interrupt the
installation stages so I can intervene and
edit it and then finish the installation
proces.

Regards,

Arnold

[noldi]

I've found the proper spot during the
installation to edit the tmp postintstall file
where I commented out the 5 lines in quiestion.

This has helped me to finish the installation
and SecurePath V3.0E is now up and running on
a system without LVM.

Regards, Arnold

[Biswajit Tripathy]

Well, I wasn't suggesting to modify the tmp
postinstall during install; my suggestion was to
modify the file in the depot itself _before_
installation.

You obviously know that commenting postinstall file
is just a temporary solution and you must get in
touch with the HP representative to make sure that
a fix to this available through official channel.

- Biswajit

[noldi]

Hi Biswajit,

> my suggestion was to modify the file in the
> depot itself _before_ installation.
this would mean that I unpack the depot, make
the neccessary changes and build it again.
I'm sure this can be easily done, but I don't
know the HP depot structure well enough in order to do it.

I'm also going to open a service call in order
to feed this information back to HP.

Best Regards,

Arnold

[noldi]

It actually has emerged that SecurePath
connectivity to hsx controllers and
VxVM is mutually exclusive, according to
HP Software Support.

So no VxVM (with root disk support or otherwise) together with SecurePath / EVA
for now.

Regards,

Arnold

[Dave Hutton]

I'm not familiar with the WebPack. I've installed 3.0E on 4-5 servers, they however were HPUX 11.11 that were connected through a SAN to an EVA.

I never had any issues from a CD install. I'm wondering is the webpack a patch to get an older version up to 3.0E?

Did you have an earlier version on the server?

[noldi]

Dave,

you might get away with installing it if your
root VM is LVM.

Anyway, it is not supported. If you read
the release notes carefully, you find only
LVM mentioned as the supported VM.

Attached the details from HP-UX Support.

Best Regards,

Arnold

[vandevoort]

I do not agree that SP is not supported when system disks are not LVM .( Veritas Volume management VXVM in my case )
In my case I got local system disks want to install SP3.0F exits with same error from same postinstall script , But I can not find anything that this is not supported .

[Andrew Scott_3]

I have a call open on the same issue right now.

The postinstall script in my case is trying to run "kmadmin". That tool apparently doesn't exist in 11.23. I don't think this problem has anything to do with VxVM. Looks to me like leftover stuff from 11.11 or 11.00 postinstall scripts.

The Itanium depots don't do this, and the kmadmin program doesn't exist on 11.23 for Itanium either.

I will post results from my support call.

[Andrew Scott_3]

The answer from Support is simply:
"We do not support anything but LVM for the root volume with Securepath."

No explanation as to WHY, especially considering the output from the scripts doesn't point to anything with VxVM being in the way.

[Andrew Scott_3 · Accepted solution]

And... I've fixed it.

Not a problem with VxVM. It's a problem in the postinstall script.

Beginning on line 44, there's an if structure that determines which version of HP-UX it's running on, except it's backwards.

It does:

if [[ -z $(uname -r 2> /dev/null | grep -e B.11.23) ]]
then
OS_RELEASE=11
else
OS_RELEASE=11_23
fi

It selects OS_RELEASE=11 each time, and tries to run tools for 11.00 and sets all the paths to things like awk and grep wrong.

To get SecurePath to install on this PA-RISC with VxVM (USE AT YOUR OWN RISK! THIS IS TOTALLY UNSUPPORTED):

1. Untar the CPQswsp_30F_depot.tar from the SecurePath CD.
2. swinstall -s /CPQswsp.11_23_PI_PA_64.3.0F.00F.00F.depot
3. Select the software and install
4. The install will suspend. View the log file. You'll see a path to a postinstall script under /var/tmp. Open a terminal and edit this file.
5. Near line 44, you'll see the if structure I described above. Either you can fix the if statement so it evaluates correctly, or you can just change it so both cases set OS_RELEASE=11_23
6. Come back to your swinstall window and resume the install.

Again:
THIS IS NOT SUPPORTED BY HP. DO NOT TALK TO THEM OR EVEN ME IF THIS DOESN'T WORK FOR YOU.

[noldi]

Andrew et al.

although there are no aparent reasons
not to support VxVM, fact is that
product management and software support
will not support VxVM together with SP.

I guess that the solution going forward
will be A/A EVA's with VxVM V4.1 and dmp
support, but this is still not available.

I'm also not sure wether older EVA's
(3000/5000) without A/A FW will be supported
with this.

Best Regards,

Arnold Sutter, Tristar/redIT

[Andrew Scott_3]

Okay guys, I just re-ignited this machine with regular LVM on the root VG, and SecurePath 3.0F is doing the same thing.

I'm now getting the error on a supported configuration.