did you bother fixing your permissions? if not then you still have the same problem. you have the wrong permissions on your private rsa key.

Yes, of course! Sorry I wasn't clear. I fixed the permissions, but it didn't change anything.

what do you get if you:

rsync -vvvvvvarh as parameters?

What about specifying your key?

rsync -vvvvvarh -e "ssh -i /home/user/.ssh/id_key"

Hi guys,

I really do appreciate all your help, really.
I know you all *know* for absolutely sure that this is a problem with my ssh key, but could you just imagine for a second that, maybe, this has nothing to do with my key? My key is fine, really. When I ssh directly, it works. When I rsync with -vvvvvarh, I do get a lot of text, and it says that the host is known, that it accepts the key, that all is fine. OK. Then, after that, after I'm SSHed into the remote server, it asks another time for the root password. This is the password I'm stuck at. I know the password, I just don't want to have to enter it (for cronjobs, not just out of lazyness!).

Now just imagine that this problem has nothing to do with the rsa key. What if the manufacturer of the remote server, which is a Synology NAS, has modified the system, so that rsyncing to that NAS requires a root password? For some reason rsync seems to be treated as a module that requires a root password in order to get accessed, even when you are SSHing with a user that is not root and that has a different password.

In other words, let's say I'm trying to rsync with "user", with password "pwd1". Let's also say that "root" has a password "pwdroot"
If I rsync with this user, the system will ask me for that user's password on the remote server, so I enter "pwd1". Then, it asks for a second password, where I need to enter "pwdroot".
If I setup a key for this user (I've done that), the system will skip the first password, which is basically the "SSH into remote server" step. BUT it will then still ask for the root password afterwards, and this has nothing to do with the rsa key that you seem to be very convinced is the root (a little pun intended) of my problem here! :-)

I'm not trying to be rude or anything, I do appreciate your help a lot. I'm just trying to get you guys on a different road that seems more plausible. I'm not stuck with creating a RSA key, I'm stuck *after* said key is accepted by the remote server.
Can you think of a different view on this problem that is not RSA related? Perhaps something I need to do on the remote server?

Thanks all for your precious help. Again, I'm not trying to be rude, I'm just saying that it is very unlikely that this second password has anything to do with the RSA key that I (apparently correctly) setup earlier!

:-)

No problem.

How about the contents of the rsyncd.conf file on that NAS?

Alright, here we go:

yeah. for testing reasons,.. i would totally comment out everything from [Netbackup] to the end and try again.

Including [Netbackup]? (Does it need a reboot afterwards?)

Yes, including [netbackup]. Thats what from here to here means,. inclusive.

Try without rebooting. Make sure rsyncd isnt running first. It should start up new at every connection.

Are you running an "ssh-agent?"

Just making sure! :-) - because either way, it didn't help!

@sundialsvcs: not that I'm aware of.

Bummer.

At this point, when mucking around with config and parameters doesnt pan out, i break out 'strace' and 'gdb' to see what the hell its doing and where its getting its screwy ideas from.

Good luck!

Hi,

Did you ever get this to work? I'm experiencing the exact same problem. I think it has something to do with special access limitation of Synology NetBackup folder.

Regards,
Wouter

Oh, yes, I did. But I really can't recall what the issue was... I think I had to specify the correct absolute path and not directly the ::NetBackup directory in order to get it to work.

So
had to turn into
Note the ":/" part at the beginning (not "::") and also that it is case sensitive.
Hope this helps...

That's it. Thanks a lot!