errors in Replication tasks

[venkata]

Dear all,

I am using two FreeNAS 9.10.2 servers.
in Host-1, we created Replication Taks with below config,
Setup mode: Semi automated,
Remote Auth Token: "second host temporary Auth Token".
it worked well.

We powered off both servers for internal maintenance, when powered on both,
host-1 replication tasks status updated with failed report.
Failed report is "Failed: Could not create directory 'nonexistent/.ssh'. Permission denied (publickey,password)."
[Refer attached screenshot for reference]

We are unable to understand why its happening like this post powered on.

Kindly help regarding this..

Thank you so much for advance..

 

[nojohnny101]

Did your "routine maintenance" involve changing anything in FreeNAS?

Also please list your full hardware and software specs so we can better troubleshoot (this is standard forum rules for all new threads)

 

[venkata]

Did your "routine maintenance" involve changing anything in FreeNAS?

Also please list your full hardware and software specs so we can better troubleshoot (this is standard forum rules for all new threads)

Thank you so much or your replay. "routine maintenance" doesn't involve any changes on the FreeNAS configuration as well as hardware.
Its for changing power backup.

 

[Spearfoot]

Dear all,

I am using two FreeNAS 9.10.2 servers.
in Host-1, we created Replication Taks with below config,
Setup mode: Semi automated,
Remote Auth Token: "second host temporary Auth Token".
it worked well.

We powered off both servers for internal maintenance, when powered on both,
host-1 replication tasks status updated with failed report.
Failed report is "Failed: Could not create directory 'nonexistent/.ssh'. Permission denied (publickey,password)."
[Refer attached screenshot for reference]

We are unable to understand why its happening like this post powered on.

Kindly help regarding this..

Thank you so much for advance..

When you configured the replication tasks, did you specify a Dedicated User? The error message indicates that the user account used for the replication task doesn't have a home directory configured: 'nonexistent' is what this means. Check and make sure the replication user account has a home directory set up where the system can create the .ssh directory to contain the cryptographic setup files.