ERROR: The gzip command failed (exit status 161)

[Mehrens Wilhelm A.]

Im using ignite version 4.1.61 on both client and server.
On the client side is B.11.22 U ia64 installed, on the Serverside is B.11.11 U 9000/800 installed.

The error appears not permanetnt,sometime it works - sometime not.

Its just a testinstallation because new ia64
hardware. Does someone know this problem?

Thanks
whith regards
Willi

[Stanimir]

Hi!
May be your problem arise, when ignite is
trying to use old gzip-command, that not support files > 2Gb. Try to replace your
default /usr/bin/gzip /after backup,of course/
with gnu-gzip, downloaded from

www.gzip.org,

for example.

Regards,Stan

[John Palmer · Accepted solution]

The failure appears to be indicated by:-

]: 29953 Exceeded CPU time limit(coredump)


gzip appears to be exceeding your CPU time limit. What is your ulimit -t set to?

Regards,
John

[Steven E. Protter]

It amazes me that HP doesn't check gzip, though it distributes it with new systems.

Your problem could be the target filesystem of the Ignite image does not have largefiles set on it. Check /etc/fstab on the server that actaully owns the filesystem the ignite image is writing to. It should have largefiles turned on and the newfs command must have been run with the -o largefiles option, otherwise its either redo the fs or find another filesystem to store it on.

You may have BOTH problems.

When you transfer files to an fs that does not have largefiles enabled, it works great up to 2G and then stops like a truck hitting a very, very solid wall.

There are certain issues to be familiar with concerning itanium and ignite, but this is not your problem here.

Regards,

SEP

[Mehrens Wilhelm A.]

Thanks all for your comments,

the problem is fixed.
Indeed, it had something to do with ulimit. Ulimit was restricted for tcsh.I had no problem with sh as loginshell for root.