search for: sigusr1s

hi guys We use rsync extensively in keeping the site resources in synch across redundant infrastructure. While attempting rsync for one of the boxes we find that the rsync process simply sleeps. The situation remains the same even if we have sync very small contents of the order of 4 KB. The same run with the -an flag runs without any issues. We run rsync over ssh on solaris boxes. To debug the

Here is patch 1 of 2. Roger diff -rup nut-2.7.4.orig/clients/upsmon.c nut-2.7.4.dev/clients/upsmon.c --- nut-2.7.4.orig/clients/upsmon.c 2015-12-29 13:08:34.000000000 +0100 +++ nut-2.7.4.dev/clients/upsmon.c 2016-07-01 09:46:21.567766415 +0200 @@ -525,6 +525,18 @@ static int get_var(utype_t *ups, const c numq = 2; } + /* Subcommands for polling SIGUSR1, SIGUSR2 RP */ + if (strcmp(var,

https://bugzilla.samba.org/show_bug.cgi?id=4327 Summary: Sudden rsync errors Product: rsync Version: 2.6.8 Platform: All URL: http://www.ercbroadband.org OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

Here is patch 2 of 2. Roger diff -rup -x '*.html' -x '*.8' -x '*.5' nut-2.7.4.orig/docs/man/upsd.txt nut-2.7.4.dev/docs/man/upsd.txt --- nut-2.7.4.orig/docs/man/upsd.txt 2015-12-29 09:42:34.000000000 +0100 +++ nut-2.7.4.dev/docs/man/upsd.txt 2016-07-07 10:08:51.939354892 +0200 @@ -119,6 +119,16 @@ administrative functions like SET and IN controlled in

First off: Our clusters are LVS balanced Apache 2.2.3 + mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a pgcluster backend. On 2 of our deployed clusters, we are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it

Hi Rsync Support, Recently we encountered issue on our prod environment because the rsync seems hanging, it took time building the list.Previously the rsync process was working before 10:24am not until 10:25am. See sample log below. We have one source server and the data files will be rsync to 2 webservers. Please advise what could be the cause of the issue. Please let me know if you need

hi.. i want to know how is defined signal "SIGUSR1" for dovecot. i want to know what dovecot do when the comand kill was executed in "Rotating logs" in http://wiki.dovecot.org/Logging.. thanks in advance!! -- Salu2 ;)

I can. I've removed every other compilation flags from clang and even used GCC, with the exact same behaviour. cheers, --renato On 29 July 2014 15:15, Evgeniy Stepanov <eugeni.stepanov at gmail.com> wrote: > OK, we can switch to SIGHUP. Could you please verify that this SIGUSR1 > behavior is not caused by MSan? > > On Tue, Jul 29, 2014 at 6:09 PM, Renato Golin

On 29 July 2014 15:02, Evgeniy Stepanov <eugeni.stepanov at gmail.com> wrote: > You mean replacing SIGUSR1 with SIGHUP in the test case? Weird, I > don't see how they are different. So, AFAIK, they should be identical. But I put some printfs and sleeps around and it wasn't a synchronization issue. My man page says that SIGUSR1 should terminate if there isn't a handler for

Howdy, We occassionally get the following error when running our nightly backups: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) This happens more on one or two machines than on any of the others. We've looked high and low to see if we're mistakenly sending these signals, but nothing is that we can find. Does anyone know what this might be from? Is it the server

Trying to rsync between win2k machines. rsync version is 2.5.3pre (downloaded today) This is the message after 368100 files have been checked: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) My cmdline is : c:\sbin\rsync\rsync -az /cygdrive/d/Home xxx@xxx.skelleftea.se::dropZone/GY/ba-disk01 --stats -v -P --timeout=84600 I have tried with both with and without -z (-az or -a)

The latest version of dispatch.fcgi in the trunk has the following code snippet: trap("USR1") do # Go to exit as soon as possible. end One of the issues I encountered while debugging fcgi under windows is that SIGUSR1 is not supported in the native Windows version of Ruby (though it is in cygwin). Currently, I have it commented out to allow dispatch.fcgi to run without blowing up.

It is necessary to kick the state machine any time another thread blocks due to write() encountering a full buffer, to get the reader thread to learn that it must now poll on POLLOUT rather than just POLLIN. POSIX only provides two ways to do this: either poll() on a second fd (our pipe-to-self trick), or interrupt the polling with EINTR due to delivery of a signal. So, I played with the latter

Hi, I have a problem with rsyncing large data sets (consisting bunch of small files) over ssh. rsync 2.6.6 on both sides. Linux 2.6.10 on receiving side, 2.6.12.6 on sending side. This strace is from rsyncing over 2Mbit link but I can repeat it over 100Mbps lan, too (while testing on lan 2.6.11.3 was on sending and 2.6.12.6 on receiving side). I wonder what can be problem here? Some

I just ran this again and got this error: leelab/NCBI_Data_old/GenBank/htg write failed on leelab/NCBI_Data_old/GenBank/htg : Error 0 rsync error: error in file IO (code 11) at receiver.c(243) Received signal 16. (no core) rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) The command I am running is: /usr/local/bin/rsync -auv --delete --rsh=/usr/bin/ssh lpgfs104:/share/group/*

Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? Using the same config that I've had for the past 10 or so point releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, but with 2.2.33 (and .1 and .2) no new logfiles are created, file descriptors still have the original files open and keep writings to those logs. On an idling test instance, I get: master:

I'm trying to transfer thousands of file from a remote machine to my server.Every-time I do this, I'm getting error saying "received SIGUSR1 or SIGINT (code 20) at rsync.c(231)".Pl. suggest me what could be wrong and how can I rectify this. The command i'm using is rsync -avz --copy-links --delete childes.psy.cmu.edu::CHILDES /var/www/localhost/htdocs/childes

Hi, I am encountering a error saying-rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229). This error was encountered after 2.5hrs of rsync. What does this exactly mean? I am pretty new the whole concept so not able to figure it out. Regards, Madhavan Chari -------------- next part -------------- HTML attachment scrubbed and removed

Hello, I found a new issue with glusterfs 3.2.1 - im getting a glusterfs process for each mountpoint and they are consuming all of the CPU time. strace won't show a thing - so no system calls are made Mounting the same volumes on another server works fine. Has anyone seen such a thing? Oder any idea, what causes this and how to fix it? The logfiles don't show any information about

https://bugzilla.samba.org/show_bug.cgi?id=5695 Summary: rsync local timeout Product: rsync Version: 3.0.3 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: gabriele.tozzi@gmail.com QAContact: