Project

General

Profile

Bug #27950

rsync execution task behaviour changed from FreeNAS 9.10 to FreeNAS11.1-U1

Added by Suresh Kumar about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
User Configuration Error
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

My rsync task setup was use to work fine using rsync over ssh with push to remote machine. After upgrade from FreeNAS 9.10 to FreeNAS 11.1, the rsync task was never executed and it does have missing alert mechanism or logging.

I created backup user on FreeNAS and remote machine and generated ssh keys the setup was just fine and it was running it for months. The rsync username is backup and when the task is executed by FreeNAS, the task is called under backup so that ssh does look for ssh keys from backup home. But with FreeNAS 11, the task are executed as root even though the username is specified clearly backup. Now the task is looking for ssh keys in /root directory but the username is backup. I believe before FreeNAS 11.1 the rysnc tasks were impersonated to backup so it can use the key from backup user and now it is directly executed by root. I am not sure if I am missing something here and I couldn't find any related post so far.

Yes if I copy the ssh keys from backup to root as authorized_keys and pub keys then it will work but I am trying to avoid any keys to root. That was my intention to have separate username for rsync.

PS : Unfortunately, overall rsync does lack for logging. This case I don't see any failure is logged.

History

#1 Updated by Dru Lavigne about 2 years ago

  • Status changed from Unscreened to Not Started
  • Assignee changed from Release Council to Vladimir Vinogradenko
  • Target version set to 11.1-U2

#2 Updated by Vladimir Vinogradenko about 2 years ago

Sorry, I was not able to repeat that. rsync is ran as proper user and his private key is used.

I think the problem may be that remote host is not in ~backup/.ssh/known_hosts or it's host key has changed or your user's ssh key permissions are invalid. What does the following command print?

su -m YOUR_FREENAS_BACKUP_USER -c 'ssh -p 22 -o "Batchmode yes" -o "StrictHostKeyChecking=yes" REMOTE_USER@REMOTE_HOST whoami'

#3 Updated by Vladimir Vinogradenko about 2 years ago

  • Status changed from Not Started to Broken
  • Reason for Blocked set to Waiting for feedback

#4 Updated by Vladimir Vinogradenko about 2 years ago

  • Status changed from Broken to Blocked

#5 Updated by Suresh Kumar about 2 years ago

Vladimir Vinogradenko wrote:

Sorry, I was not able to repeat that. rsync is ran as proper user and his private key is used.

I think the problem may be that remote host is not in ~backup/.ssh/known_hosts or it's host key has changed or your user's ssh key permissions are invalid. What does the following command print?

[...]

Vladimir Vinogradenko wrote:

Sorry, I was not able to repeat that. rsync is ran as proper user and his private key is used.

I think the problem may be that remote host is not in ~backup/.ssh/known_hosts or it's host key has changed or your user's ssh key permissions are invalid. What does the following command print?

[...]

Hello Vlad,

I ran the command and it comes back with remote username as it suppose to. The remote machine username is backup and the command returns "backup"

I think I found the issue. The remote machine disk was full and it was not allowing the incoming connections. Once after I reboot the machine and some clean up it is working now. Also some have my /root directory is wiped out after upgrade. May be it was me interrupted the upgrade. Anyway it is working now as expected and I will keep eye on it just in case anything comes out. The discussion is started from here https://forums.freenas.org/index.php?threads/rsync-execution-task-behaviour-changed-from-freenas-9-10-to-freenas-11.60981/#post-433562

My apologies to reporting this issue as a bug. Since this is end user issue and it would have been avoided to reporting this issue. Thank you so much for your time to explain this issue and thanks for all your great work.

I think we can close this issue. I am not sure whether I have permission to close or you can close it. Please let me know if I need to take any action on this issue to close it properly.

Again thanks for great product.

-Suresh

#6 Updated by Dru Lavigne about 2 years ago

  • Status changed from Blocked to Closed
  • Target version changed from 11.1-U2 to N/A
  • Reason for Closing set to User Configuration Error
  • Reason for Blocked deleted (Waiting for feedback)

Thanks for the update Suresh!

Also available in: Atom PDF