Installer creates 0 byte files

[Paul Deckers_1]

We have a customer who can not install our software on an HPUX11 system and I hope someone can help.

On all of our test systems the software installs fine. Yet when the customer tries to install our software, a file which is copied to /sbin/init.d becomes a zero byte file and the rest of the installation fails.

As I said our installer works on all of our test systems and with all other customers. We have verified that the user is 'root' and that the package file etc is not corrupted. If we manualy copy the file the file ratains it's size but if we run the installer it get's overwritten and becomes 0 bytes.

The workstation is stand alone and is not connected to a network. We did verify that 'localhost' was correctly defined in the HOSTS file.

Any help will be much appreciated.

[Robert-Jan Goossens]

Full root filesystem ?

[RAC_1]

You did not give enough information in order to help you. What is the software that you are trying to install??? Is it a depot file?? Is it SD compatible?? Or is it just a tar file??? What exactly is that??

Also how you are installing it?? Are you using swinstall??

Anil

[Cheryl Griffin]

"On all of our test systems the software installs fine. Yet when the customer tries to install our software," ....

Are you saying that all other software installs correctly except your own software? If so, it sounds like something is wrong with how your software was packaged.

[Paul Deckers_1]

Ok all..let's see if I can supply the required info:

The root filesystem is not full.

The software our customer is trying to install is our GEAR for UNIX CD & DVD recording software which we develop.

The software is provided as a package file which was created on an HP system and is installed using swinstall.

We can install GEAR on all of our HP systems with no problem. Also we have many HP customers who have had no issues with installation. Only this one customer is seeing the described behaviour.

[Robert-Jan Goossens]

Paul,

Strange!

-1-You have checked reversed nslookup (IP + hostname)

-2-The file is a tar file

-3- On a stand-alone system, run swinstall to install the product:
# swinstall -s /tmp/ your_product

-4-Maybe a shot in the dark, can could you rule out a drive error ?

# dd if=/dev/rdsk/cxtydz of=/dev/null bs=1024k

Regards,
Robert-Jan

[Cheryl Griffin]

Does the swagent.log details from a working customer/site, match that of this one who gets the zero byte file? Hopefully, there may be some error message logged.

[Paul Deckers_1]

I asked for the log and we found the following error:

* Installing fileset "GEARGUI.commands,r=4.11" (1 of 1)
ERROR: Could not access remote file "sbin/init.d/GEARogm" in software item
"GEARGUI.commands,r=4.11,a=HP-UX_B.11.032/64,v=GEAR_Software:/usr"
due to an internal error on the remorte system.

Does this provide any further insite?

[Robert-Jan Goossens]

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=684293

simular to yours but no solution.

Most of the times an error
ERROR: Could not access remote file
suggest there is a network/hostname problem.

Above you said this is a stand alone system. Try the steps below.

-1-
edit your /etc/hosts file
127.0.0.1 your_name loopback

-2-
if excists
mv /etc/resolv.conf /etc/resolv.conf.old

-3-
touch /var/adm/sw/standalone

-4-
/usr/sbin/swagentd -r

Groeten,
Robert-Jan