Ignite-UX - Add new client for recovery...

[Jonathan Rowbury_1]

After installing ignite-ux for the first time I'm trying to add a new client for recovery.

I pick one of my servers and add it as a fully qualified hostname, I'm then prompted for the root password as remsh command access was denied, I enter the root password fine but I then receive the following error message;

In: /var/opt/ignite/client.mnt//0x001083FAB551 exists
ERROR: Failed to install symbolic link to /var/opt/ignite/client.mnt/
ERROR: Failed to initialize client directory in /var/opt/ignite/client.mnt

I then get a subsequent error message informing me that the client directory for the system I choose wasn't able to be set up...

Thank you in advanced for any replies.

[Eileen Millen]

If the file exists, you could rename it with the mv command and then try again.

[Jonathan Rowbury_1]

Thank you Eileen for your idea, unfortunately I've tried this already but still get the same error. The adding of a new client goes through the process of copying the client tools over and creating the necessary directory structure but then falls over at the last minute with the error message I stated. Does anyone else have anymore ideas I might try?

[Printaporn_1]

Please make sure that youi can rlogin from ignite server to client without supply password.
remove client or rename file and try add client again.

[Jonathan Rowbury_1]

Thanks for the suggestion printaporn, I do not have rlogin enabld on any of my servers for security reasons so I am unable to do this. Does ignite rely on rlogin at all to enable access between servers? As the client tools and necessary directory structures get created on the new client being added I did not feel the error message related to a connection issue, I'm very puzzled as to what is going on, does anyone else have more thoughts or ideas.

[RikTytgat · Accepted solution]

Hi,

I had the same problem just this morning.

The error occured when I supplied a fully qualified domain name for the client I wanted to add for recovery.

When using the hostname alone, it worked fine, but I don't know whether you can try that in your setup.

In my setup, both Ignite Server and the host are in the same domain.

Hope this helps,
Rik

[Bill McNAMARA_1]

You need to add the client to the .rhosts
Then make sure that the nfs exports are setup correctly with anon rw rights.
What ignite revision are you using?
After doing the above, remove the client via the GUI and try again.

Later,
Bill

[Jonathan Rowbury_1]

A big thank you Rik for your prompt response, just like you I entered my host without fully qualifying it's domain and I added a client fine. Is it supposed to work like this?

I'd also like to thank everyone else who replied, your time is much appreciated.