1833159 Members
3006 Online
110051 Solutions
New Discussion

Ignite Client Issue

 
SOLVED
Go to solution
UVA
Regular Advisor

Ignite Client Issue

Hello Gurus,

I created a ignite server, i exported a client
image using the make_net_recovery command.

Howevre when i try to boot the client for reinstallion from the ignite servere, it gives following error,


The command "/opt/ignite/bin/bootsys -wv -S -R B.11.31 nakbqas1 2>/var/tmp/baa014010" will be used to reboot nakbqas1. Would you
like to proceed?

ERROR: Secure mode was specified, but no RSA or DSA public key files
could be found. You may need to use ssh-keygen(1) to create
a public/private key pair

Any hints are there?
4 REPLIES 4
Steven E. Protter
Exalted Contributor
Solution

Re: Ignite Client Issue

Shalom,

YAY!

Ignite is finally using ssh instead of insecure transport services.

ssh-keygen -t dsa


This will generate public key files which must be exchanged on both servers as authorized_keys files

More on this:

http://www.hpux.ws/?p=19

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
UVA
Regular Advisor

Re: Ignite Client Issue

Hi

Thanks steve, when using GUI for this it asks

for copying the the key.

So it is ok.
UVA
Regular Advisor

Re: Ignite Client Issue

Hi,

I created a recovery image of vg00 by using following command

make_net_recovery -s nakgdev1 -a nakgdev1:/ignite -x inc_entire=vg00


after completion, this recovery image size shows only 3 gb, but my vg00 actual size is 130 gb

can any one clear my doubt
Bill Hassell
Honored Contributor

Re: Ignite Client Issue

You can be sure that everything was copied by counting the number of files and directories on the source and the destination. Use the find command:

find / -type f | wc -l
find / -type d | wc -l

Be sure you count the same set of files. For instance, if you used the option -x inc_entire=vg00, then other filesystems on vg01, etc will not be included.


Bill Hassell, sysadmin