similar to: Rsync error on client end: unexpected tag 3 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(843) [sender]

Hello, I am new to this list. ?I am trying to compile the current svn version of kdeedu on an amd64 linux machine ?which uses R and I get the following compiler output. ------------------------------------------- ?79%] Building CXX object cantor/src/backends/R/rserver/CMakeFiles/cantor_rserver.dir/rserver.o $SOURCES/kdeedu/cantor/src/backends/R/rserver/rserver.cpp: In member function

Ok I updated both systems to rsync-2.6.8 and found the info on setting strace on the server. Here are the trace logs, there are two calls the first is just the module list which finishes normally the second is the file list in the test module which fails after the list. By the way I have no idea what any of this means (sorry if I'm not supposed to post traces to the list)

Hi, I'm rather new to this project, having stumbled across it earlier this afternoon, so forgive me if I'm still trying to find my way around. I was in the need of an alternative to NFS that would let me spread the task of sharing my downloaded source code files across a couple of boxes, and GlusterFS looked like a great candidate, having had no luck with Coda or OpenAFS. I also want

hello, running an rsyncd server I get the following into the error log when trying to sync on a module : (...) Mar 15 15:32:44 xxxxxx rsyncd[5202]: building file list Mar 15 15:34:55 xxxxxxxxx rsyncd[5202]: rsync: writefd_unbuffered failed to write 4092 bytes to socket [sender]: Connection reset by peer (104) Mar 15 15:34:55 xxxxxxxxxx rsyncd[5202]: rsync error: error in rsync protocol data

hello, I get some error messages when using BackupPC with rsyncd-style backup: - on the backup server : BackupPC 2.1.2, using its own rsync perl module - on the box being backed up : rsync 2.6.6 , runing as a daemon (rsyncd) the area to be backed up is rather big : ~120 Gb the rsyncd daemon is configured with a big timeout = 7200 a) this is what I get on the backup server

Hello, > upsmon doesn't work on amd64. > On i686 everything is OK. Configs are the same. > I'm attaching strace - could You help? this might be linked to that: https://alioth.debian.org/tracker/index.php?func=detail&aid=301880&group_id=30602&atid=411544 when you say work", can you give a bit of detail (ie doesn't receive events, crash (seems not as per

Hi. While debugging some encfs errors in the logs, I realized they are being generated because rsync (chrooted inside a encfs file system, --reverse) is trying to access files like: /root/.popt, /etc/localtime etc. This doesn't seem to be related to ID-name mapping as I already have numeric ids enabled in config. Here is the relevant strace output: [pid 25549] chroot("/chroot")

I'm testing an upgrade of an i686 production machine running 1.4.24.1 to 1.6.0.9. I've installed dahdi-linux-2.1.0.4. But: asterisk -cvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv Asterisk 1.6.0.9, Copyright (C) 1999 - 2008 Digium, Inc. and others. Created by Mark Spencer <markster at digium.com> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.

Hi all, When setting auth mechanisms: plain login cram-md5 and only having pam passdb and passwd userdb. dovecot nevers starts and crashes reporting: Feb 29 10:19:41 pitux-clust-op1 dovecot: Dovecot v1.0.10 starting up Feb 29 10:19:41 pitux-clust-op1 dovecot: auth(default): CRAM-MD5 mechanism can't be supported with given passdbs Feb 29 10:19:41 pitux-clust-op1 dovecot: Auth process died

Dear All, I have attempted to install the R-Excel Interface with poor results. The version of R is 1.6.1, the version of R-Excel is 1.0, the version of COM is 0.99. All of these were downloaded Monday, 6 January 2003. R (version 1.6.1) is installed on the machine and appears to run correctly on its own. The computer is a Compaq Pentium 4 machine with 128 meg of RAM running Windows 2000 and

Hi, here is an example of tftpd-hpa running in daemon mode failing to reopen /dev/log. No wonder, as it tries after chrooting. Cheers, Feri. $ sudo strace -f -p 2356 Process 2356 attached - interrupt to quit select(5, [4], NULL, NULL, NULL) = 1 (in [4]) setsockopt(4, SOL_IP, IP_PKTINFO, [1], 4) = 0 recvmsg(4, {msg_name(16)={sa_family=AF_INET, sin_port=htons(57109),

summary: e.g., how to replace '<query R for package=package_name>' in the following: for RSERVER in 'foo' 'bar' 'baz' ; do ssh ${RSERVER} '<query R for package=package_name>' done or is there a better way to script checking for an R package? details: For my work I need a few non-standard R packages. I do that work on 2 clusters. One uses

I have a problem with rsync hanging when transferring multiple files over a VPN to a separate server. Local server is RHEL4 and remote server is FC6. It ends up failing with the following error message: rsync: connection unexpectedly closed (3193 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(600) [receiver=3.0.0pre8] rsync: connection

https://bugzilla.samba.org/show_bug.cgi?id=4633 Summary: rsync mirror fails when using -a/-o/-g options Product: rsync Version: 2.6.3 Platform: x86 OS/Version: Windows XP Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

I started to have problems similar to ones described in the past on this list but could not find any kind of resolution. I did an lsmod, a mount command, and for fun, did an strace on shutdown to see where it is hanging, and an ltrace as well. Any thoughts? Module Size Used by parport_pc 28033 0 lp 15661 0 parport 38153 2

Hi all, I am using Match directive and internal-sftp to chroot sftp users into their directory. Connection and login works. I can change directories and put/get files. Also logging of the internal sftp-process works (created a /dev/log socket inside the chroot). As soon as I use the 'ls' command, nothing happens and the the process gets stuck. Listing files does work as soon as I remove

Hi! I am a new user of Debian and am having an issue loading RStudio Server, which may or may not be related to a previous 'Release file expiration error' when trying to perform apt-get update prior to installing r-base into my remote Debian system. E: Release file for http://mirror.optus.net/debian/dists/jessie-updates/InRelease is expired (invalid since 13d 17h 49min 2s). Updates for

Perhaps I can ask a slightly different question? Is there some kind of test I can do on a hung process so I can determine whether it's active or not, in a script? The output of strace is below but it doesn't mean much to me I'm afraid. Is there a straight forward difference between strace for a "real" connection and one of my hung ones that I can use to manually kill them?

I just did a bit of testing on OpenBSD and there the above setup seems to work and I can remove the files just fine over sftp. So this thing should work but there's still something causing it to fail on CentOS's side. One difference between our CentOS and OpenBSD is that OpenBSD uses newer openssh server. I looked through the release notes and didn't see any changes related to

I am running rsync over a VPN. The connection has been stable for some time, but recently it has started failing. I am including the strace of the failure below. Basically, the client disconnects typically with an error 12. I have 3 other clients using the same openvpn/rsync configuration, and those are stable, so I am fairly confident this is something on this particular link. The