NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Error 7077010002
Can anyone throw any light on the above error code (7077010002)? I have a backup of a remote server set up to use rsync over ssh. The connection used to work but now fails with the above code. ...
***SOLVED***
Thanks to JennC for pointing me to the appropriate logs.
The issue was not with the ReadyNAS as such but with the configuration of the ssh forced commands. The root 'authorized_keys' file starts with the phase:
from="192.168.xxx.xxx", command="/usr/bin/rsync" ssh-rsa....
where 'xxx' is replaced by the ip address of the NAS. This restricts a root login to the NAS, and only to exceute the rsync command. In reorganising my network recently I had changed the static IP address of the NAS ... thus the condition failed. I hadn't noticed the failure at the time (note to self... pay more attention to your logs) and had not made the link. Correcting the IP address in the authorized_keys file solved the problem.
PM sent to @JennC as requested.
For other community members.... Downloading the logs provided much more information than can be got from the ReadyNAS web interface. Therefore a recommended debugging step.
The logs show an rsync error code 23 which, I believe, is a permissions error (not sure if this is a 'read' or 'write' permission error). I am logging in via ssh as root (forced commands only) and running rsync. I can see a successful loggin to the remote server, therfore need to double-check the 'forced commands' configuration.
Any other thoughts gratefully recieved.
***SOLVED***
Thanks to JennC for pointing me to the appropriate logs.
The issue was not with the ReadyNAS as such but with the configuration of the ssh forced commands. The root 'authorized_keys' file starts with the phase:
from="192.168.xxx.xxx", command="/usr/bin/rsync" ssh-rsa....
where 'xxx' is replaced by the ip address of the NAS. This restricts a root login to the NAS, and only to exceute the rsync command. In reorganising my network recently I had changed the static IP address of the NAS ... thus the condition failed. I hadn't noticed the failure at the time (note to self... pay more attention to your logs) and had not made the link. Correcting the IP address in the authorized_keys file solved the problem.
Hi neilb41,
I am glad you were able to resolve it. Sorry I was away when you sent all those messages.
Posting what resolved it is also very much appreciated. Thanks for contributing to the community!
Regards,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
