https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #8 from Michal Ruprich ---
Great, thanks Wayne.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change option
https://bugzilla.samba.org/show_bug.cgi?id=11338
Wayne Davison changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #6 from Michal Ruprich ---
This has just freshly arrived yesterday. Same bug as before and as described
here.
https://bugzilla.redhat.com/show_bug.cgi?id=1683737
--
You are receiving this mail because:
You are the QA Contact for the
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #5 from Michal Ruprich ---
Created attachment 14872
--> https://bugzilla.samba.org/attachment.cgi?id=14872&action=edit
Patch for the rwrite function
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Pl
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #4 from Michal Ruprich ---
Hi,
we have encountered similar segfault a couple of years ago. As you can see here
in comment #2, the p *in shows that the input buffer's size and len are
unreasonably huge - len = 18446744073709532799, size
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #3 from Ralph Corderoy ---
Hi Wayne,
I don't know if James's SEGV is the same root cause as Balveer's that
was two years earlier, but I'm seeing SEGV like James's. Both times, my
network connection was down when rsync was run by cron;
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #2 from James Stevenson ---
I seem to see the same crash. Here is some additional details with symbols. It
seems to happen during network timeouts.
#0 0x7fcc2e167b05 in utf8_internal_loop (step=0x560710d73f90,
step_data=0x560710d
https://bugzilla.samba.org/show_bug.cgi?id=11338
Wayne Davison changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from Wayne Davison
https://bugzilla.samba.org/show_bug.cgi?id=11338
Bug ID: 11338
Summary: Rsync Crash - Segmentation fault
Product: rsync
Version: 3.1.1
Hardware: x64
OS: Linux
Status: NEW
Severity: normal
https://bugzilla.samba.org/show_bug.cgi?id=9798
Vijay Nag changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=9798
--- Comment #6 from Vijay Nag 2013-05-27 18:41:28 UTC ---
(In reply to comment #5)
> I asked you to test the fix. Either grab the git version or the latest
> nightly
> tar file.
Tested ok.
--
Configure bugmail: https://bugzilla.samba.org/userpr
https://bugzilla.samba.org/show_bug.cgi?id=9798
--- Comment #5 from Wayne Davison 2013-05-27 18:35:56 UTC ---
I asked you to test the fix. Either grab the git version or the latest nightly
tar file.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiv
https://bugzilla.samba.org/show_bug.cgi?id=9798
--- Comment #4 from Vijay Nag 2013-05-27 01:28:35 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > I think rsync is not handling EILSEQ error returned by iconv(3).
>
> No, but it did expect an E2BIG in preference to an EILSEQ, which
https://bugzilla.samba.org/show_bug.cgi?id=9798
Wayne Davison changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from Wayne Davison
https://bugzilla.samba.org/show_bug.cgi?id=9798
--- Comment #2 from Vijay Nag 2013-04-22 15:26:41 UTC ---
(In reply to comment #1)
> Please retry with a current version of rsync. Your 3.0.2 version is 5 years
> old.
Crash is observed in the latest rsync. I checked the diff with the latest one
an
https://bugzilla.samba.org/show_bug.cgi?id=9798
--- Comment #1 from Paul Slootman 2013-04-22 11:22:30 UTC ---
Please retry with a current version of rsync. Your 3.0.2 version is 5 years
old.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this
https://bugzilla.samba.org/show_bug.cgi?id=9798
Summary: rsync crash with SIGSEGV when read time out happens
Product: rsync
Version: 3.0.2
Platform: All
OS/Version: All
Status: NEW
Severity: critical
Priority: P5
Wayne Davison wrote:
> On Mon, Sep 5, 2011 at 8:10 AM, Voelker, Bernhard
> wrote:
>
> > but why does rsync crash _after_ issueing the error message?
>
> See the freeaddrinfo fix (git show 5fed6c07). This fix is in 3.0.9pre2, and
> 3.0.9 will be released shortl
On Mon, Sep 5, 2011 at 8:10 AM, Voelker, Bernhard <
bernhard.voel...@siemens-enterprise.com> wrote:
> but why does rsync crash _after_ issueing the error message?
>
See the freeaddrinfo fix (git show 5fed6c07). This fix is in 3.0.9pre2, and
3.0.9 will be released shortly.
..wayne.
, September 05, 2011 5:11 PM
To: rsync@lists.samba.org
Subject: rsync crash behind a firewall [cygwin]
As part of coreutils' bootstrap, rsync crashes on cygwin:
$ /usr/bin/rsync \
--delete \
--exclude '*.s1' \
-Lrtvz 'translationproject.org::tp/latest/coreutils/&#
https://bugzilla.samba.org/show_bug.cgi?id=8445
Summary: rsync crash when remote filter rule changes
Product: rsync
Version: 3.0.7
Platform: x64
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P5
-29 10:10 i686 Cygwin
I'm behind a corporate firewall which doesn't permit outgoing connections,
but why does rsync crash _after_ issueing the error message?
Or is it a Cygwin issue?
Have a nice day,
Berny
--
Please use reply-all for most replies to avoid omitting the mailing
On Mon, 2009-01-12 at 13:29 +0100, Maxence DUNNEWIND wrote:
> Anyway, after it has been working well for some time (between 2 and
> 24hours), the rsync daemon crashes.
I wouldn't call an infinite loop a crash, but whatever.
> It is still running but seems to
> retry something infinitly.
>
> The
Hello,
I'm using an rsync server on a Linux packages repository (deb packages)
to sync all mirrors.
The mirrors sync every 10 minutes. Most of the time, there is nothing to
sync, except a timestamp file, so the sync is pretty fast.
Anyway, after it has been working well for some time (between 2 a
On Mon, Dec 05, 2005 at 09:57:39AM +0400, [EMAIL PROTECTED] wrote:
> rsync: fork failed in do_recv: Cannot allocate memory (12)
That is an OS error: the fork() system call failed with ENOMEM, which
typically means that you don't have enough swap space available for the
new process. Adding mo
Dear all,
I've been using rsync since almost 1 year to
synchronise 2 RHEL 3 servers.
Everything has been running fine until a few weeks
ago.
I'm getting the following error message via
crond:
rsync: fork failed in do_recv:
Cannot allocate memory (12) rsync error:
error
Dear All,
I've been using rsync since almost 1 year to
synchronise 2 RHEL 3 servers.
Everything has been running fine until a few weeks
ago.
I'm getting the following error message via
crond:
rsync: fork failed in do_recv:
Cannot allocate memory (12) rsync error:
error
https://bugzilla.samba.org/show_bug.cgi?id=3202
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3202
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Additional Comments
https://bugzilla.samba.org/show_bug.cgi?id=3202
--- Additional Comments From [EMAIL PROTECTED] 2005-10-22 16:02 ---
i find out that it crash because it fill up stack
which is default 8MB, when i enlarge it to 32mb with ulimit, rsync work ok
--
Configure bugmail: https://bugzilla.sam
https://bugzilla.samba.org/show_bug.cgi?id=3202
Summary: rsync crash with long directory structure
Product: rsync
Version: 2.6.6
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
31 matches
Mail list logo
