**SOLVED!!** Hi Paul,
On Fri, Mar 4, 2016 at 8:44 PM, Paul Slootman <[email protected]> wrote: > On Fri 04 Mar 2016, John Lewis wrote: > > > > If running from server (backup machine), it's hang and need to be > > terminated using ^C > > > > root@server:/backup/dirvish/client1# ssh -p 11111 -i > > /root/.ssh/id_rsa_dirvish_client1 client1 "/etc/dirvish_mysql_dump.sh" > > > > ^Croot@server:/backup/dirvish/client1# > > This is the problem, you can forget alle the dirvish stuff until you get > this to work. > > Yes, thank you for point this so I can look at the right place. > Use 'ps aux' > Noted with thanks. > Long story short: just remove the semicolon! > Noted with thanks. > > (I was talking about colons earlier with no space behind them, entirely > a different issue...) > > And I just noticed something: your 'ps' output shows "ssh -p 9731", not > "ssh -p 11111"... What's going on there?! > Forgot to edit :P > > As I said, concentrate on getting the ssh working. > Start it on the dirvish server, then check the client1 whether there is > a connection: "netstat -tnp | grep :11111", the last column is process > ID of the process using that connection. Use ps -fp XX to check what > that process is. You can use "ps faux" to see a process tree, which may > be useful. > So this is what happen and how to solve this: On the client1 machine, on the /etc/ssh/sshd_config PermitRootLogin forced-commands-only So every command that want to be runned remotely need to be "registered" before. I generate the ssh key for /etc/dirvish_mysql_dump.sh using ssh-keygen from server, copy it to client1 and at the client machine, add the content to authorized_keys2. I cant to this without you guys. Thanks a lot: Paul, Andi, Olivér, Patrick and the others. > Paul > > Thanks again, John.
_______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
