install product on hpux

[sam kim_1]

i am trying to install f-secure product on hpux 11.x for testing purpose:

1) i have a file 'ssh2132.tar' in root directory (i transferred this file from NT to HP using ftp)

2) then, i just did
# tar xvf ssh2132.tar

[result is:
x fisecure-ssh-2.0.13.2-dss-hpux11TCB/postinstall.sh, 140 bytes, 1 tape blocks

vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)

tar: f-secure-ssh-2.0.13.2-dss-hpux11TCB/
postinstall.sh: HELP - extract write error]

3) i am not exactly sure what that means and how to fix this problem in order to install this product

sam.

[Rick Garland]

The install is wanting to use the / filesystem as a temporary holding place. You did not tell it to install there I hope.

One method is to use a tmp directory for the installation.

TMPDIR=/
export TMPDIR

[Tracey]

Try moving that file to a directory that has alot of space, as it seems it is trying to untar all the files in the / directory and it doesn't have enough room.

[Rita C Workman]

What it's telling you is that when you go to expand this with the tar xvf command there is not enough room to write everything under root.
Maybe you could move the file to another file system where you have more room and put it under a directory and do the tar again...then move it to where it should go.
Is this something that requires putting it under / root?.....
Usually software is going to be moved afterwards to /opt.

Hope this helps,

[Rick Garland]

Go with Tracey. Move the file to another location and do the un-tar.

[John Palmer]

Sam,

You've filled up your root filesystem trying to extract the file(s) from the tarball.

First find a filesystem that has more room in it with 'bdf'.

Then 'cd' to an appropriate directory in that filesystem (where do you want the files to end up?) and untar the contents with 'tar xvf /ssh2132.tar'

The extracted tar files will be created relative to your current directory.

Regards,
John

[sam kim_1]

1) i just did:

# bdf
[result is: / avail 0 kb, ....,
/opt avail 85644 kb, ...

# mv ssh2132.tar /opt

# ls
[ssh2132.tar is here]

# tar xvf ssh2132.tar
[resultis:
x f-secure-ssh-2.0.13.2-dss-hpux11TCB/postinstall.sh, 140 bytes 1 tape blocks

x f-secure-ssh-2.0.13.2-dss-hpux11TCB/readme.txt, 2726 bytes 6 tape blocks

x f-secure-ssh-2.0.13.2-dss-hpux11TCB/ssh_binary.tar, 12052480 bytes 23540 tape blocks

Tar: error! blocksize changed
#

2) this means i still have not enough space under /opt directory ??

3) and, also it means i need 12052480 bytes
free in order to install/tar this file ???

4) therefore, i checked again dir spaces using # bdf
and the result is:
Filesystem kb used avail mount on
/dev/vg00/lvo13 86016 86016 0 /
/dev/vg00/lvo18 450560 61040 365218 /var
/dev/vg00/lvo17 385024 322293 58845 /usr
/dev/vg00/lvo14 32768 1253 29549 /tmp
/dev/vg00/lvo11 67733 12553 48406 /stand
/dev/vg00/lvo16 245760 154444 85644 /opt
/dev/vg00/lvo15 20480 1130 18142 /home

[Tracey]

Sam,

During your ftp, did you transfer your tar file withthe binary option set on? If you transferred it with the ascii option set on instead, unix will not be able to read it properly since the ascii translates carriage returns. You may want to try to transfer it with binary set on (just type binary at the ftp prompt) and try it again, but remember to delete your old tar file on the unix system first.

[sam kim_1]

when i was using ftp i did:

ftp 128.xxx.xxx.10
name: root
password: summer

ftp> binary
ftp> put c:tempssh2132.tar
ftp>

[Anthony deRito]

sam, the archive was created using a relative path. This means that it will unpack in whatever directory your sitting in. Move it to a filesystem with lots of room and untar it there.

Tony

[sam kim_1]

i think previous-output is not good:

i did,
ftp> binary
ftp> put c:/temp/ssh2132.tar

[ps: actually i typed back-slash instead of
/. this forum does not allow to type back-slash. that is why i put the / slah instead of back-slash above here.]

[Anthony deRito]

sam, lets assume you transferred the file OK from NT to UNIX. What I would do now is move the file to a UNIX filesystem with more room and try to untar it there. Then repost with issues.

Tony

[sam kim_1]

1) i just tried:

# mv /opt/ssh2132.tar /tmp
# pwd
/tmp
# ls
[ssh2132.tar is there]
# tar xvf ssh2132.tar

2) samr output as before

3) i think i need 12052480bytes to untar
ssh_binary.tar ?????

[Anthony deRito]

sam, are you sure you moved the file to a different filesystem other than root (/). Run bdf and check what filesystems are available with enough space.

Tony

[Shannon Petry · Accepted solution]

I think what happened is painfully obvious. If the extraction failed because of no file space, and still fails after moving then the transfer did not complete.
Re-run the ftp, but before you put the file, cd to the directory with enough space. Someone mentioned on UNIX running bdf to see where space is Okay. Then from ftp
ftp HOST
user USERNAME
passwd
ftp> bin
ftp> cd /directory/with/enough/space
ftp> put "the_file"
ftp> by
then back on the unix box, tar xvf tarfile

[Anthony deRito]

Actually, based on Sam's history of dialogue in this forum, one cannot assume she moved the file to a DIFFERENT filesystem other than /. She must use bdf to find a DIFFERENT filesystem other than root to extract the tar file. If this is no success, then the transfer can be the blame.

She says she moved the file and recevied the same message. That message was "nospace - /dev/root file system full". This does not convince me that the file was moved across filesystems.

Get my point?

Tony

[sam kim_1]

good morning!

1) i just did (from hp box)
# bdf
[result : /var has most avavilable-space]
# cd /
# cd /var
# mkdir fsecure

2) then (from nt),
ftp 128.xxx.xxx.10
user : root
password : summer
ftp> bin
ftp> cd /var/fsecure
ftp> put c:tempusassh2132.tar
ftp> by

3) then (from hp box),
# pwd
/var/fsecure
# ls
ssh2132.tar
# tar xvf ssh2132.tar
[result is :
x f-secure ..../postinstall.sh ... 1 blocks
x f-secure ..../readme.txt ... 6 blocks
x f-secure ..../ssh_binary.tar..23540 blocks
x f-secure ..../ssh_config.tar ... 20 blocks
x f-secure ..../uninstall.sh ... 2 blocks
#

4) wow, it looks working fine w/o error,
arent they??

5) however, do i still need to untar
ssh_binary.tar and ssh_config.tar in order to install this product ??

6) (i have no manual and have not much experience installing s/w on unix box)

[Anthony deRito]

sam, now that you have worked so hard at identifying some space in /var and have untared the package, I must tell you that /var is not a good place for this product. /var is probably sitting on the root volume group right? /var is one of those filesystems that fill up quickly. I would recommend moving the product to /opt and making it its own filesystem.

But thats another subject.

After you have untared the file you noticed 2 more tar files. You ned to untar these as well but keep in mind they will consume yet even more space. Use bdf for space information.

Tony

[sam kim_1]

i am able to install it now.
thanks, all!

[however, i think i have to install -next time- different place, not /var.]