similar to: Rsync between 2 datacenters not working

You could try using an automounter, like autofs, in combination with sshfs. It'll be slower, possibly a lot slower, but it should be more reliable over an unreliable connection. I've been using: remote -fstype=fuse,allow_other,nodev,noatime,reconnect,ServerAliveInterval=15,ServerAliveCountMax=40,uid=0,gid=0,ro,nodev,noatime :sshfs\#root at remote.host.com\:/ BTW, I'm not sure

Note that if you do this you are stuck with --whole-file On 03/25/2018 04:36 PM, Dan Stromberg via rsync wrote: > You could try using an automounter, like autofs, in combination with > sshfs. It'll be slower, possibly a lot slower, but it should be more > reliable over an unreliable connection. > > I've been using: > remote

If reducing the MTU is helping, you might look into turning on Path MTU Discovery. NFS can be fast for large transfers if you tune it. http://stromberg.dnsalias.org/~strombrg/nfs-test.html NFS is not terribly secure though - at least v2 and v3 weren't. Not sure about v4. On Wed, Mar 28, 2018 at 12:59 AM, Marc Roos via rsync <rsync at lists.samba.org> wrote: > > Kevin, Dan,

Hmmm, looks indeed like changing the mtu helps, strange thing is that with the bigger mtu sometimes I had no problems and often TB are copied without problems. Problem is I can't test the connection that much because the connection has been established by a third party and it is just some vlan without any hops. But thanks for the link to the nfs-test that looks interesting!

Hi. Environment: * OS: Antergos Linux (Fully updated daily) (Running as a guest on VM). * OpenSSH: 7.8p1 Description: Immediately upon creating a successful SSH tunnel login, the connection is dropped with the "packet_write_wait: Connection to X.X.X.X port 22: Broken pipe" error. I've verified the issue is due to OpenSSH 7.8p1 in the following ways: * Use a

On 02/19/2018 10:09 PM, Marcelo Ricardo Leitner wrote: > On Mon, Feb 12, 2018 at 08:05:18PM -0500, H wrote: > ... >> Not sure if I am reading your reply correctly but I should clarify >> that I have problems when running naked ssh to the server, when I >> run ssh to the same server but over the VPN connection (that goes >> via third server) everything is flawless.

I have been having broken pipe messages for a while. I think since a network architecture change. But I am not sure because I have not been monitoring the errors closely before. I added this (https://rsync.samba.org/issues.html) rsync-debug.sh script with strace of 100. But I have no idea how to interper this output. I guess between 00:55:41 and 03:06:47 nothing is happening? And then some

There is no /root/.ssh/authorized_keys on remote host, so I have to authenticate with password. On the remote host: # /usr/sbin/sshd -T | egrep permitroot permitrootlogin yes Attempting: $ ssh root@<remotehost> shows: Received disconnect from <remotehost> port 22:2: Too many authentication failures for root packet_write_wait: Connection to <remotehost> port 22: Broken

Hello, I am trying to keep my samba accounts in sync with my unix accounts. I want to login ssh. Syncing passwords works. Scenario: I create a new user: useradd -m testuser passwd testuser When I log in with the user pam_smbpass should create a corresponding samba user. I modified system-auth which is included in sshd: #### /etc/pam.d/system-auth auth requisite pam_unix.so

Hello all, I am looking to run only 1 VM on this setup, don''t need to do live migration, although that would be nice, I just want to protect against hardware and datacenter/network failure. The VM is lightly loaded, not much disk I/O or CPU load. I have two machines, each one with 2 x SATA 250GB, and 1 SSD 128GB. (There is a simple RAID-1 SATA hardware controller on board). I am

Hi Everyone, Does anyone know of any ATAs that can do proxy failover without using SRV. I don't want to rely on dns if at all possible. Basically, I have Asterisk boxes in two different data centers and I need ATAs to be able to uses the server at DC2 if DC1 goes down. The servers are already in a HA setup at each datacenter. I am looking for added protection if one of the datacenters

Hi ! Here's a patch to add remote port forwarding support (protocol 2) for openssh. I have tried to test that it works like it should but a more thorough testing is needed. This patch adds both client/server support. The patch should be applied to openssh-2.1.1p4 source tree. Also included is a PortForwarding sshd_config option, new ./configure option --disable-forwarding that should make it

On Tue, May 09, 2017 at 06:24:55PM -0500, John Griessen wrote: > I've not really dug into testing tinc yet, but if you all will humor me in an uneducated blast of questions, > I'd appreciate it. > > What can you do to keep tinc going if your high availability comes from cluster nodes being dispensable? > Can tinc run on the cluster nodes? > That seems like chicken/egg

I often change configurations in a home server environment, and have scripts to back up all config files etc. - on a fresh OS install I can quickly restore function of all the services I'm running. I'm using version 3.4.7 as a PDC on Ubuntu with 4 Windows 7 clients. I can restore smb.conf which gets the file shares and server configuration back, but I lose the trust relationship with the

Added the line as above: 'IPQoS lowdelay throughput', restarted the SSH service, tried SSH-ing and Git-ing... same error as before: 'packet_write_wait: Connection to X.X.X.X port 22: Broken pipe'. ________________________________ From: Zach Cheung <kuroro.zhang at gmail.com> Sent: 29 August 2018 07:17 To: ohadfjunkbox at outlook.com Cc: dtucker at dtucker.net;

Setup: Office A: router: Linksys WRT54GS running SVEASOFT Alchemy-pre7a v3.37.6.8sv Asterisk: v.1.2.4 static IP Office B: router: Linksys WRT54GL running Linksys firmware v4.30.2 Asterisk: v.1.2.7.1 dynamic IP (using dyndns name) Office A is set up with refresh dns and cron job for iax2 reload every 5 minutes. It rarely looses connection to Office B. Surprisingly, Office B is the one loosing

Dear OpenSSH Portable sshd developers, I'm having a problem where sshd login sessions are occasionally (as often as once a day) getting stuck indefinitely. I enabled debug messages and got a backtrace of a stuck sshd, and I think I've found the bug. I wanted to run it by the list once before filing. sshd version: OpenSSH_4.2p1 FreeBSD-20050903, OpenSSL 0.9.7e-p1 25 Oct 2004

https://bugzilla.mindrot.org/show_bug.cgi?id=2689 Bug ID: 2689 Summary: Terminal new line after packet_write_wait: Connection failure Product: Portable OpenSSH Version: 7.2p2 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh

I've not really dug into testing tinc yet, but if you all will humor me in an uneducated blast of questions, I'd appreciate it. What can you do to keep tinc going if your high availability comes from cluster nodes being dispensable? Can tinc run on the cluster nodes? That seems like chicken/egg problem though to get tinc server installed and cluster nodes brought up... If tinc needs to be

After awhile, my connections from my PC to my samba server end up with a red "X" in them (share disappeared) if I leave my explorer window open. If I click on these, they "wake up" and continue to function (and the red X's go away). If I close my explorer window (while the red X's are there) and reopen it , they are gone. An attempt to reestablish these