topic ignite problem in Operating System - HP-UX

ignite problem

emily_3 — Fri, 04 Jun 2004 00:00:05 GMT

hello,

I would like to ignite two servers with exactly the same software, and the two servers also have the same hardware configuration.
One of the server can ignite successfully, but the other always encountered problem, which indicate some of the specified filesystem size is not enough for the s/w will be installed.
The size of the filesystem, which is defined in the ignite config file, is correct. But I don't understand why the ignite estimate the s/w will be loaded is so big that the size of the filesystem is not enough?

Re: ignite problem

Steven E. Protter — Fri, 04 Jun 2004 00:32:25 GMT

You might want to say which filesystem.

You may have inadvertantly included the golden image tar file or other large file in one or the other configuration/images.

You may have a hardware problem that leaves disk unavailable. Check the ignite hardware inventory image.

Something may be missing.

SEP

Re: ignite problem

emily_3 — Fri, 04 Jun 2004 00:53:51 GMT

Hi,

I suspect it's hardware issue, since the other unit can be successfully loaded. But it could display the two harddisks and size correctly. I don't what else need to check?

Re: ignite problem

Bharat Katkar — Fri, 04 Jun 2004 01:04:58 GMT

Emily,

1. Check the /var/opt/ignite/clients/clientname/install.log files for both the client where you can pinpoint the problem accurately.
2. Check the hardware of the second server if it is Okay.
3. Check whether you are using same cfg files for both the servers in /var/opt/ignite/INDEX files.
4. Also check whether you have same /opt/ignite/data/Rel_B.11.23/hw_patches_cfg for both the servers.

Hope that helps.
Regards,

Re: ignite problem

emily_3 — Mon, 07 Jun 2004 01:24:25 GMT

Thanks for your reply.

i found the problem is that the size of the root_swap, which is two times size of the physical memory, occupied too much of the harddisk. It causes the other software doesn't have enough space to be loaded.
i solve this problem by decreasing the size of the root_swap. But I am not sure whether this will have any potential problem, since root_swap<2*hd?