This isn't exactly what I'm using.. I'm using rsync over SSH.
So I set these in sshd_config
MaxSessions 30
> MaxStartups 20:60:120
>
And I wanted to know what he had set to make his rsync finish without
further errors.
Shai
On Thu, Feb 17, 2011 at 12:29 PM, Brian Hickey wrote:
> On 17/02/201
On 17/02/2011 10:04, Shai wrote:
What was the resulting configuration change (from default) that you had
made to fix this? I have reported the same issue today, and this
configuration change might be what I'm looking for.
In /etc/rsyncd.conf, try changing :
max connections =
Regards
Hello Mr. Gray,
What was the resulting configuration change (from default) that you had made
to fix this? I have reported the same issue today, and this configuration
change might be what I'm looking for.
My report: http://www.mail-archive.com/rsync@lists.samba.org/msg26787.html
Cheers,
Shai
On
Izidor, this appears to resolve my problem. Thank you for your input, I
will be sure to attribute you on serverfault.com when I add an answer to my
question post.
On Tue, Sep 21, 2010 at 2:49 AM, Izidor Jerebic wrote:
> Hi,
>
> this might be a problem with maximal number of concurrent ssh conn
Hi,
this might be a problem with maximal number of concurrent ssh connections or
connection requests. Ssh daemon has two configuration settings where you can
define what is the maximal number of clients which can connect concurrently.
This number is by default not very high, so you are probably
Greetings,
I posted this at serverfault, but in hopes that the people on this list are
different from the people there, here it is:
Update: 9/20/10: Updated the EC2 AMI on both the client and the server and
ran a 3-box test with 2 clients downloading from 1 server over 24 hours.
Upon test complet
Added --bwlimit=150 at 10:58, had a success at 10:59, failure at 11:00, and
success at 11:01.
It takes about 1.7s to execute the rsync command, for what that's worth.
That it seems to fail immediately suggests it's something
connection-related, but that it fails on rsh and ssh both suggests it's
Already tried --bwlimit. In my case it didn't change the error. It
just slowed down the identical file recognition. But when it came to a
file modified from what exist on the backup server, it dropped the
connection.
Thanks anyway for the help!
Vitorio
Le 16 sept. 10 à 15:56, Paul Slootma
On Thu 16 Sep 2010, Mac User FR wrote:
> I read somewhere that the ssh connection was stronger than rsync one
> in unstable networks. And effectively, if I run rsync via ssh ( -e
> option), the transfer happen without errors, on the same computer
> using the same networking setup.
I wouldn't be s
Hi!
Interesting subject. Since a week now I'm trying to solve the same
problem on a very precise configuration.
In my company we have some wired computers and some wireless ones. All
of them under Windows XP SP3 with all security updates. They are
backed up in a FreeNAS box under FreeNAS
> I posted this to a couple online forums already am am already doubting anyone
> will be able to directly help me solve my problems. So I am here to query
> the experts directly:
> I have a number of rsync clients trying to connect to an rsync server
> routinely, and they're intermittently fa
11 matches
Mail list logo
