similar to: rsync: connection unexpectedly closed

Displaying 20 results from an estimated 1000 matches similar to: "rsync: connection unexpectedly closed"

2016 Oct 09
0
rsync: connection unexpectedly closed
Hey list, I am having problems as of late with my rsync backup. On the client side I am using the following: OPTS="-avvvrz       --compress-level=9       --itemize-changes       --delete       --delete-excluded       --human-readable       --files-from=$FILES       --include-from=$INCLUDES       --exclude-from=$EXCLUDES       --partial
2016 Oct 12
5
rsync: connection unexpectedly closed
On Wed, 2016-10-12 at 13:30 +1300, Henri Shustak wrote: > Have you tried performing a copy to a known good local device?  If a > local copy fails, then I would start checking the file system of the > source and also the hardware of that system. That's a good idea. I just tried that and it copied no problem. -- Kip Warner -- Senior Software Engineer OpenPGP encrypted/signed mail
2016 Oct 16
1
rsync: connection unexpectedly closed
On Thu, 2016-10-13 at 20:08 -0400, Kevin Korb wrote: > I don't remember whether or not you said you were running rsync over > ssh but if you are you can also debug the ssh layer.  You can even do > it at both ends.... > > On the server run a debugging sshd on an alternate port with: > /usr/sbin/sshd -dDp222 > (note that this will only accept 1 connection, debug to the
2016 Oct 13
5
rsync: connection unexpectedly closed
On Wed, 2016-10-12 at 08:36 +0200, Paul Slootman wrote: > As always it's best to first upgrade to the current version (3.1.3) > if at all possible, as there's always the chance that the cause of > your problems has already been fixed. Good call, but I believe I may have ruled this out. I didn't upgrade to 3.1.3, but both sides are running 3.1.1 protocol version 31 now. Same
2018 Feb 27
3
Established connection timing out
On Mon, Feb 26, 2018 at 5:17 PM, Kip Warner <kip at thevertigo.com> wrote: > Hey list, > > I've read the man page for both the client and server daemon, so either > I missed something or this isn't an SSH issue but something going on > with perhaps routers or MTUs. > > I am having problems with already established connections to a remote > server timing out
2010 Dec 28
1
Surround Sound
Hey folks, As I understand it, the vorbis codec had support for a channel count > 2, but that it didn't explicitly state the channel binding for channels 3, 4, ... . I'm assuming that with enough fiddling, it would theoretically be possible to use a 5.1 stream encoded into vorbis. From what I know of the CELT codec, it handles either only mono or stereo. Is that correct? -- Kip
2016 Oct 20
1
rsync: connection unexpectedly closed
On Tue, 2016-10-18 at 08:36 +0200, Paul Slootman wrote: > Try the transfer without -z. > > Paul I ended up giving up. What I did was I just removed the 30GB file (which I really didn't need anyways) and the transfer carried on without a hitch. -- Kip Warner -- Senior Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com -------------- next part
2012 Mar 30
1
failed: File name too long
Hey list, I am using rsync version 3.0.7, protocol version 30, to transfer data between amd64 and mipsel machines, tunnelled over SSH. Some file names are very long and rsync unfortunately cannot transfer them, issuing the following error message: failed: File name too long (78) I'm assuming the 78 is drawn from a system header that it was compiled against and probably not universal to the
2018 Feb 27
3
Established connection timing out
I don't believe you've said: are the disconnects happening during periods of idleness on the connection, or periods of activity? If idleness, some device or script could be actively doing a disconnect-on-idle. On Mon, 26 Feb 2018, Kip Warner wrote: > Hey list, > > I've read the man page for both the client and server daemon, so either > I missed something or this
2016 Oct 14
0
rsync: connection unexpectedly closed
I don't remember whether or not you said you were running rsync over ssh but if you are you can also debug the ssh layer. You can even do it at both ends.... On the server run a debugging sshd on an alternate port with: /usr/sbin/sshd -dDp222 (note that this will only accept 1 connection, debug to the terminal, then exit) then on the client use rsync -e "ssh -vp222" to go verbose
2010 Dec 15
9
[Bug 32406] New: nouveau fails to send hotplug event to ALSA hda hdmi audio
https://bugs.freedesktop.org/show_bug.cgi?id=32406 Summary: nouveau fails to send hotplug event to ALSA hda hdmi audio Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau
2005 Dec 31
2
Resend: setting breakpoints around hypercalls in a domU causes dom0 to lockup
Any thoughts on setting breakpoints around hypercalls? ---------- Forwarded message ---------- From: Kip Macy <kip.macy@gmail.com> Date: Dec 26, 2005 12:14 AM Subject: setting breakpoints around hypercalls in a domU causes dom0 to lockup To: xen-devel <xen-devel@lists.xensource.com>, Keir Fraser < Keir.Fraser@cl.cam.ac.uk> Stepping through hypercalls (at the source level, not
2015 Mar 16
1
Asterisk 13.1.0/PJSIP outbound calling using SIP trunk: Unable to create request with auth.No auth credentials for any realms in challenge.
On Sun, Mar 15, 2015 at 5:56 PM, Sonny Rajagopalan <sonny.rajagopalan at gmail.com> wrote: > George, > > I have the detailed log below. (Resending after trimming the email to 40KB.) > > The sequence below just repeats ad-nauseam. Is this a SIP trunk issue? > > Thanks! > I don't see anything obvious. The registration works though, right? You might want to compare
2016 Oct 13
0
rsync: connection unexpectedly closed
On 2016-10-10 17:24, Kip Warner wrote: > Note that I have temporarily disabled timeouts and added extra > verbosity. The transfer to the remote host via SSH works fine, up until > it gets to a 30+ GB file (a VM image). It gets about 90+ percent of the > way through, hangs, and then times out. I have a similar but different problem. I make a regular download from a site that always
2016 Oct 18
0
rsync: connection unexpectedly closed
On 18.10.2016 07:03, Kip Warner wrote: > From what I can tell, there are no hardware problems. I also ran fsck > on the drive. The machine seems to be fine. I can confirm the problem. Situation here: 2 identical HP Microservers (Debian 7, on site compiled rsync 3.1.2, connected via OpenVPN). SSH is used for transport. Both machines have the correct date/time set via ntpd. All files on
2016 Oct 19
1
rsync: connection unexpectedly closed
what does lsof tell? does rsync hang on a specific file? i would wonder if this is a rsync problem. as you told you killed all processes. so, on the second run rsync knows nothing from before... roland Am 18. Oktober 2016 12:08:00 MESZ, schrieb Bernd Hohmann <hohmann at harddiskcafe.de>: >On 18.10.2016 07:03, Kip Warner wrote: > >> From what I can tell, there are no
2008 Feb 20
1
regression moving from 3.1 to 3.2 (XEN) mm.c:631:d26 Bad L1 flags 18
It looks like I can no longer map a page as uncacheable. Is this intentional? -Kip _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2005 May 08
2
semantics of GETDOMAININFO
One of the things that I''ve always thought was weird, but didn''t pay too close attention to is the fact that GETDOMAININFO will return a valid result even if we give it a domid that is no longer valid. Looking at the code we get back the first valid domain after the domid we pass in. What is the reason for this design choice? When I request the attributes of a process I
2005 Nov 22
6
FreeBSD 5.3 as DomU - new kernel with sysinstall embedded
On 16/11/05, Kip Macy <kip.macy@gmail.com> wrote: > The way the initial memory space gets setup there is no way MFS could work. > It wasn''t an anticipated use. I guess somewhere either in FreeBSD GNATS or > xen''s bugzilla there should be i386-xen FreeBSD bugs filed for me to track. I intend to file a bug report sooner or later, but in the meantime I decided to
2008 Apr 30
7
rescue_from issue with AWS - uninitialized constant
The new rescue_from in edge rails seems to conflict with ActionWebService, which I need for various other purposes. When I define, for example (with AWS gem installed): <b>rescue_from ActionController::RoutingError, :with => :page_not_found</b> I get the exception: <b>uninitialized constant ActionWebService::Dispatcher::ActionController::Base</b> OK, so AWS