topic Re: Ignite gzip error in Operating System - HP-UX

Ignite gzip error

Pradep — Sat, 13 Jun 2009 13:37:41 GMT

Hi,
Make_net_recovery is failing with below gzip error. I had it working earlier with more than 3 GB image size. so disk size is not a problem.

# Ignite-UX C.6.1.44 HP-UX System Installation Services
# gzip -V
gzip 1.3.5 (HP-UX fixlevel 1)
(2002-09-30)
same version of gzip is working fine in other similar image servers.

* Archiving contents of sngux028 via tar to
/var/opt/ignite/recovery/arch_mnt/2009-06-13,22:00.

gzip: stdout: Unknown error
ERROR: The gzip command failed (exit status 1).
ERROR: The gzip command failed (exit status 1).

ERROR: The make_sys_image command failed. The system recovery archive will
not be created.

======= 06/13/09 22:17:56 SST make_net_recovery completed unsuccessfully

Re: Ignite gzip error

Dennis Handly — Sat, 13 Jun 2009 14:40:12 GMT

>so disk size is not a problem.

Do you have enough free space?
bdf /var/opt/ignite/recovery/arch_mnt/

>gzip: stdout: Unknown error

(This message isn't helpful at all. What kind of broken software doesn't try to print out errno?)

Since gzip doesn't support large files yet, it has to read/write from/to a pipe and have cat(1) actually read/write from/to the files.

Re: Ignite gzip error

Pradep — Sat, 13 Jun 2009 15:53:05 GMT

yes..it has eniguht free space.

for unknown error: how can i debug it? can ignite be run in debug mode ?

Re: Ignite gzip error

sujit kumar singh — Sat, 13 Jun 2009 17:05:57 GMT

Hi Pradep,

1) try normally if gzip is working, try by zipping a test file on the system.

2) Try using the make_net_recovery command using the option -m pax

3) are you having some file on the system geater than 2 GB in size?

4) bdf on /var/opt/ignite/recovery/arch_mnt to see if you have enough free space, at the time of running make_net_recovery are you able to note the estimated size of the archive and compare that with the free space on the destination?

regards
sujit

Re: Ignite gzip error

Dennis Handly — Sat, 13 Jun 2009 17:59:32 GMT

>for unknown error: how can I debug it? can ignite be run in debug mode?

If ignite doesn't use a demon, you can use tusc:
tusc -fp -ea -o tusc.out make_net_recovery ...

Then look down to execv for gzip and see if you also see cat.