Operating System - HP-UX
1838068 Members
3940 Online
110124 Solutions
New Discussion

make_net_recovery on trusted system ERROR

 
Andres Stickar
Frequent Advisor

make_net_recovery on trusted system ERROR

trying to make a make_net_recovery on a HP-UX 11.11 trusted system have, I have the following output error:
rp1 # make_net_recovery -A -s arbitro
* Creating NFS mount directories for configuration files.

======= 06/01/04 15:32:16 SAT Started make_net_recovery. (Tue Jun 01 15:32:16
SAT 2004)
@(#) Ignite-UX Revision B.5.1.33
@(#) net_recovery (opt) $Revision: 10.618 $

* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Recovery Tools
ERROR: Connnection to the server:arbitro failed.

Does anybody know about debug, logs or any information to help to solve the problemm.
Thanks in advance

A.
4 REPLIES 4
Mel Burslan
Honored Contributor

Re: make_net_recovery on trusted system ERROR

Is NFS server processes running fine on the ignite server arbitro ? even if they look so, I would stop and restart the nfs server from arbitro and the nfs client on the node you are trying to run the make_net_recovery command.
________________________________
UNIX because I majored in cryptology...
Mauro_25
New Member

Re: make_net_recovery on trusted system ERROR

The NFS is working fine. I can mount each nfs-directory manually without errors.
The ERROR message make my feel the problemm is in the tcp conection. I don`t know which ports use the ignite client to connect with the server.
Sridhar Bhaskarla
Honored Contributor

Re: make_net_recovery on trusted system ERROR

Hi,

You may find more information in /var/opt/ignite/recover/latest/recovery.log file.

See if you can do an

#swlist -l depot @arbitro

If that doesn't work, then you will need to check 'swagentd' process on arbitro as well on the local system.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Andres Stickar
Frequent Advisor

Re: make_net_recovery on trusted system ERROR

Finally we solve the problem
The tftp service was inactive in the client.
Thnks for the help