topic Re: Error: Cannot access config file: in Operating System - HP-UX

Error: Cannot access config file:

Ajaysen Reddy — Mon, 01 Oct 2007 13:04:19 GMT

Hello All,

I am trying to clone 2 Identical Itanium servers. I have made a make_sys_iamge of my ignite server and trying to push it to a client. I am following the instructions from Chapter 8 of the Admin guide for my cloning. After I see the client in the ignite GUI, I see the following message:

Message From: /opt/ingite/bin/itool (tx11nfs1)

ERROR: Cannot access config file:
/opt/ignite/data/Rel_B.11.23/core_archive_cfg (referenced in
Configuration: “HP-UX B.11.23 Arvhive”).

Error: Failed to load config files from server or media.

There are no valid configuration files to select. itool must exit.

Here is some more details on my ignite server (which is also the server that I created make_sys_image from):

tx11db99{root}/var/opt/ignite/clients # ll
total 2
drwxr-xr-x 2 bin bin 1024 Oct 1 12:40 0x001A4B068D38
lrwxr-xr-x 1 root sys 14 Sep 24 16:05 sample -> 0x999999999999
lrwxr-xr-x 1 bin bin 14 Oct 1 13:02 tx11nfs1 -> 0x001A4B068D38

tx11db99{root}/var/opt/ignite/clients # ll 0x001A4B068D38
total 30
-rw-r--r-- 1 bin sys 9 Oct 1 12:39 client_name
-rw-r--r-- 1 bin sys 63 Oct 1 12:39 client_status
-rw-r--r-- 1 bin bin 858 Oct 1 12:39 config.sys
-rw-r--r-- 1 bin bin 621 Oct 1 12:39 host.info
-rw-r--r-- 1 bin bin 1344 Oct 1 12:39 hw.info
-rw-r--r-- 1 bin bin 3510 Oct 1 12:39 install.log
-rw-r--r-- 1 bin bin 3594 Oct 1 12:39 io.info
-rw-r--r-- 1 bin bin 0 Oct 1 12:40 lockfile
-rw-r--r-- 1 bin bin 36 Oct 1 12:40 server.state

tx11db99{root}/var/opt/ignite/archives/Rel_B11.23 # ll
total 7030792
-rw-r--r-- 1 root sys 675 Sep 28 14:56 make_sys_image.log
-rw-r--r-- 1 root sys 3599755369 Sep 28 14:56 tx11db99.gz

tx11db99{root}/var/opt/ignite # exportfs -v
/var/opt/ignite/clients -anon=2
/var/opt/ignite/archives/Rel_B11.23 -ro,anon=2

Appreciate all your help.

Re: Error: Cannot access config file:

Ivan Krastev — Mon, 01 Oct 2007 13:16:46 GMT

Can you post the /var/opt/ignite/INDEX file.

In this file core_archive_cfg is listed as:

"/opt/ignite/data/Rel_B.11.23/core_archive_cfg"
but it cannot be found.

Check for existense of this file in /opt/ignite/data/Rel_B.11.23/ and set permissions to bin:bin.

regards,
ivan

Re: Error: Cannot access config file:

Tim Nelson — Mon, 01 Oct 2007 13:22:32 GMT

Here is an easier way to clone.

Create network image of server1 with make_net_recovery or interactive with ignite server gui.

Then in /var/opt/ignite/clients create subdirectory with MAC address of server2. ln -s MAC server2

chown above dir to bin:bin

cd to /var/opt/ignite/clients/server1 and "find CINDEX recovery|cpio -pmdv ../server2"

add server2 to /etc/exports and /etc/hosts, exportfs -av

boot second server from ignite using lanboot

Once booted use Ignite and advanced. Change the needed IP and hostnames, etc. Then GO !

Once done edit /etc/hosts with correct addresses of server2.

You now have a clone of server1 with all the config files from server1.

Re: Error: Cannot access config file:

Ajaysen Reddy — Mon, 01 Oct 2007 14:23:42 GMT

Hello Ivan,

I have checked and corrected the /var/opt/ignite/INDEX file. Should have been /var/opt/ignite/data/Rel_B.11.23/core_archive_cfg instead of /opt/ignite/data.../core_archive_cfg. The install is now working.

Thanks for your help.

Re: Error: Cannot access config file:

Ajaysen Reddy — Tue, 02 Oct 2007 09:37:53 GMT

Tim,
You have asked to "Create network image of server1 with make_net_recovery or interactive with ignite server gui". How can I create make_net_recovery if my clone server and IgniteUX server are the same. There is no option like "-s local" as on make_sys_image.

Thanks

Re: Error: Cannot access config file:

Tim Nelson — Fri, 05 Oct 2007 10:42:13 GMT

Sorry for the late reply Ajay,

Creating a make_net_recovery of the ignite server to itself has never worked for me as it attempts to mount the client and archive dirs back to itself and fails. ( makes sense )

My process. Ignite server uses make_tape_recovery. All others do a make_net_recovery to the ignite server. I do not have any reason here to use the ignite server for the clone source.

A different option would be to create the ignite image on another server, and use that one temporarily.

Glad most things are working for you.