Here is what I put in my Root User's SSH Public Key
I figured out how to add the other key to the authorized_keys file. Had to use 'ee' to edit it.
The SSH CLI test goes through now without asking me for a PW but the replication task still fails.
auth.log on PULL shows this so I think it is authenticating ok.
Dec 31 00:17:02 R2D2 sshd[28480]: Accepted publickey for root from 192.168.2.10 port 53511 ssh2: RSA 70:06:b6:26:a9:6a:b8:f9:8c:5a:18:87:84:e6:54:9c
Dec 31 00:17:02 R2D2 sshd[28480]: Received disconnect from 192.168.2.10: 11: disconnected by user
No idea if this is causing problems.
Code:
ec 30 01:08:09 C3PO nmbd[3413]: [2015/12/30 01:08:09.818850, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Dec 30 01:08:09 C3PO nmbd[3413]: *****
Dec 30 01:08:09 C3PO nmbd[3413]:
Dec 30 01:08:09 C3PO nmbd[3413]: Samba name server C3PO is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.10
Dec 30 01:08:09 C3PO nmbd[3413]:
Dec 30 01:08:09 C3PO nmbd[3413]: *****
Dec 30 01:08:09 C3PO nmbd[3413]: [2015/12/30 01:08:09.819009, 0] ../source3/nmbd/nmbd_incomingdgrams.c:311(process_local_master_announce)
Dec 30 01:08:09 C3PO nmbd[3413]: process_local_master_announce: Server R2D2 at IP 192.168.2.11 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcin
Dec 30 01:08:09 C3PO nmbd[3413]: [2015/12/30 01:08:09.819096, 0] ../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
Dec 30 01:08:09 C3PO nmbd[3413]: *****
Dec 30 01:08:09 C3PO nmbd[3413]:
Dec 30 01:08:09 C3PO nmbd[3413]: Samba name server C3PO has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.2.10
Dec 30 01:08:09 C3PO nmbd[3413]:
Dec 30 01:08:09 C3PO nmbd[3413]: *****
Dec 30 01:08:25 C3PO nmbd[3413]: [2015/12/30 01:08:25.836985, 0] ../source3/nmbd/nmbd_become_lmb.c:418(become_local_master_fail2)
Dec 30 01:08:25 C3PO nmbd[3413]: become_local_master_fail2: failed to register name WORKGROUP<1d> on subnet 192.168.2.10. Failed to become a local master browser.
I looked in the messages log on PUSH and I don't see any errors authenticating persay.