Re: [rdiff-backup-users] SSH time out, how to remedy? [Scanned]

[Pieter Donche]

I now have, EITHER on the server and on the client
TCPKeepAlive yes
ClientAliveInterval 15

and still no luck, after 3 to 4 minutes:
Read from remote host macos.cmi.ua.ac.be: Connection reset by peer
Fatal Error: Lost connection to the remote system

(in FreeBSD 7.2, the SSH (part of the OS) the /etc/ssh/sshd_config
has no option ServerAliveInterval, so I can't test that)

On Wed, 3 Jun 2009, Jason Spalding wrote:

> Make sure at least TCPKeepAlive is uncommented (remove the #). I've had too
> many issues with so-called "defaults" on any system to trust if they're not
> explicitly defined.
>
> Yes, they would have to be changed on the target machine - the machine that
> has the SSH *server* on it.
>
> Having said that, and in partial answer to your next question - according to
> my copy of Pro OpenSSH (a valuable resource if you start using ssh more) you
> can set these settings on the local SSH client as well, thus preventing the
> need for you to change anything on the server.
>
>
> On 3/6/09 6:30 PM, "Pieter Donche" <address@hidden> wrote:
>
> > Hi,
> > both on the backup and target machine my /etc/ssh/sshd_config has:
> > #TCPKeepAlive yes
> > #ClientAliveInterval 0
> > #ClientAliveCountMax 3
> >
> > The manual says TCPKeepAlive is default yes.
> > So I don't understand  why the connection still dies ?
> >
> > If I want to use ClientAliveInterval and ClientAliveCountMax,
> > these would have to be changed on the target machine?
> > would
> > ClientAliveInterval 15
> > ClientAliveCountMax 3
> > be a reasonable choice?
> > this would send out every 15 seconds after no data has been received
> > from the client a request of a response from the client and try that
> > 3 times?
> >
> > Is that correct?
> >
> > Can these settings for the ssh connection used by rdiff-backup been set
> > somewhere on the command line that I have in targetmachine's
> > /root/.ssh/authorized_keys2 ?
> > now it has:
> > command="rdiff-backup --server --restrict-read-only
> > /",from="<mybackupmachine>",no-port-forwarding,no-X11-forwarding,no-pty
> > ssh-rsa AA   ... vQ== backup@<mybackupmachine>
> >
> > (this would leave the 'general' settings of sshd_config intact)
> >
> >
> > On Wed, 3 Jun 2009, Jason Spalding wrote:
> >
> > > Do you have TCPKeepAlive turned on in your /etc/ssh/sshd_config (or
> > > appropriate config file)? And if so, have you toyed with the
> > > ClientAliveInterval and ClientAliveCountMax intervals? See
> > > http://www.openssh.com/faq.html#2.12 for a quick reference.
> > >
> > > On 3/6/09 4:43 PM, "Pieter Donche" <address@hidden> wrote:
> > >
> > > > If I initiate a rdiff-backup at the command line from my backup server:
> > > >
> > > > address@hidden ~]$ /usr/local/bin/rdiff-backup macos-backup::/var
> > > > /home/backup/ma
> > > > cos/var
> > > > Previous backup seems to have failed, regressing destination now.
> > > > Read from remote host macos.cmi.ua.ac.be: Connection reset by peer
> > > > Fatal Error: Lost connection to the remote system
> > > >
> > > > Seems the SSH connection gets lost..
> > > >
> > > > How can one remedy to this (rdiff-backup paramters, ssh parameters ???)