similar to: 'error in rsync protocol data stream' - Tim Conway

Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: >Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: [...] >>+ >>+ err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, >>+ failover_dev); >>+ if (err) { >>+ netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n",

Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: >Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: [...] >>+ >>+ err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, >>+ failover_dev); >>+ if (err) { >>+ netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n",

We have been running into problems here, we have 2 PRI's when they fillup, All channels in use, and we dial more calls asterisk becomes unstable and crashes alot. We are currently on: Asterisk CVS-v1-0-10/26/04-09:35:31 built by root@localhost on a i686 running Linux I know I need to upgrade. Is this a know issue?? Kyle

On Wed, May 02, 2018 at 10:51:12AM -0700, Samudrala, Sridhar wrote: > > > On 5/2/2018 9:15 AM, Jiri Pirko wrote: > > Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: > > > Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: > > [...] > > > > > > > > + > > > > + err =

Attached is a spec file for OpenSSH on SuSE 6.4 and 7.0 systems. It differs from the current spec file in the following details: - Only one rpm file is created containing client and server files. - PreReq `openssl-devel' is changed to `openssl'. - Path '/usr/libexec/ssh' is changed to '/usr/lib/ssh' for ssh-askpass and gnome-ssh-askpass. The resulting

https://bugzilla.mindrot.org/show_bug.cgi?id=2563 Bug ID: 2563 Summary: ssh bash -c drops arguments of the first command send to the remote. Product: Portable OpenSSH Version: 6.9p1 Hardware: ix86 OS: Linux Status: NEW Severity: major Priority: P5 Component: ssh

Hi, Got a strange problem with rsync ! Here is the story ... I got a linux rsync server running for 8 months without any problem (rsync 2.6.6 18) I got about a dozen of rsync clients (linux and windows, generally using a 2.6.5 rsync version) that synchronize their datas without any problem. Some of them only synchronize a few datas (10 GB) and some others synchronize large amount of data

Hello, While doing a local "rsync" with: rsync -v -auxHS --force / /backup/ (on /backup is mounted another disk), I get these errors: rsync: error writing 4 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) rsync: error writing 69 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data

Hi, I'm trying to figure out why when I do an rsync (Solaris, version 2.6.4 on both sides) from a site on the West Coast of the US to a site on the East coast, I keep getting directories updated when I use the command like this: # rsync -ar -v -v -i -O --force --delete --exclude=.snapshot --stats \ src:/sysic/lib/freedomlib_V100/ /sysic/lib/freedomlib_V100/ And I get output like this,

Hi, First post to the list, so please feel free to set me straight if I'm not following some protocol or other :o) We need to use rsync to send files to a client, being a Windows user, we decided to try both the cwrsync implementation and also a straight cygwin/rsync install. I'm experiencing the following errors: using cygwin implementation: $ sh clientupload.sh

I've just released rsync 3.0.0pre5, the latest pre-release version of the upcoming 3.0.0 release. Things are progressing well in our efforts to stamp out bugs for the final release. Please keep up the good work in testing this and sending email to the rsync mailing list with your questions, comments, bug reports, etc. Thanks! You can download the tar file and its signature from here:

I've just released rsync 3.0.0pre5, the latest pre-release version of the upcoming 3.0.0 release. Things are progressing well in our efforts to stamp out bugs for the final release. Please keep up the good work in testing this and sending email to the rsync mailing list with your questions, comments, bug reports, etc. Thanks! You can download the tar file and its signature from here:

Hi * I'm using rsync to mirror software from one Sun Workstation (mecc27) to the other (mecc29). (solaris 5.7) worked perfect... 'til 1 week ago !! Everybody claims nothing has been changed in the configs of the machines (couldn't find anything, though), but rsync is doing nothing at all. just after being called it exits without any error message, warning, whatever.. here the log

Moin, I wrote a small backup script that use rsync: r5backup (http://sourceforge.net/projects/r5backup/). It backup dozen of unix machines for many people. But when I try to backup /var/lib/zope2.9 I get an error 11. It does not matter if zope is running or not. I can't see an error meassge in the (verbose) logfile: [client] parse_filter_file(/etc/r5backup/profiles/boulder.exclude,0,3)

https://bugzilla.samba.org/show_bug.cgi?id=2645 ------- Additional Comments From dalgoda@ix.netcom.com 2005-04-24 11:36 ------- It looks like the culprit is the change for receiver.c 1.130. It pulled the call to send_file_list(-1,...), which is what handled the one_file_system code. It's not like we can easily go back either, since flist.c 1.267 removed support for f=-1. Bummer. --

I had this working on an older version, since 2.6.9 that when I set --delete and --dry-run, I get no "Deleting ******" lines. Also, the --delete-before never worked for me. Working on a space constrained mirror, this has proven very handy, when it works. What's up with the new versions? I haven't changed a thing. Best regards, Tiago Marques

Hi list! I'm trying to use rsync to do a regular remote backup of a 450GB sized container file located on my squeeze server onto a colocated QNap NAS device. Both use rsync 3.0.7. While this setup works for most files, it fails on this large file (see log below). I'm already trying to help rsync using "-P" to indicate that rsync should reuse the current copy and not trying

I have this failing every times I want to "update" the "destination". I've tried through SSH (from my box -/home is a NFS mount point here- to the backup one) or directly through "local transport" (because /home/ is a local RAID-5 mount point on the backup box). $ rsync -v -e /usr/bin/ssh -ax --delete \ /home/beta /home/worx \

I'm experiencing some unexpected behavior with rsync v2.5.6. After looking around it seems like several people have experienced similar problems in the past, but those appear to be old bugs that are solved now. Also doesn't appear to be any direct bugfixes made for this issue since 2.5.6. The strange thing is that things seem to work when I use ssh for transport. However now I need to

Hi, I've been attempting to use rsync 3.1.2 to copy files from a macOS 10.12.2 system to an AFP mounted share. The command I'm using is: rsync -avAX -M--fake-super ./testDir ./mnt/testDir/ This works fine and all the extended attributes are copied and readable. I then try to use rsync to copy these files back with: rsync -avAX --fake-super -M--super ./mnt/testDir/ ./testDir2/ This