search for: sigusr1

...y n c : c o n n e".., 63) = 63 poll(0xFFBEE0E8, 1, 60000) = 1 write(1, " ?\0\0\b r s y n c : c".., 67) Err#32 EPIPE Received signal #13, SIGPIPE [ignored] write(2, " r s y n c : w r i t e".., 81) Err#32 EPIPE Received signal #13, SIGPIPE [ignored] sigaction(SIGUSR1, 0xFFBEDAF8, 0xFFBEDB78) = 0 sigaction(SIGUSR2, 0xFFBEDAF8, 0xFFBEDB78) = 0 getpid() = 7970 [7969] Received signal #18, SIGCLD [caught] siginfo: SIGCLD CLD_EXITED pid=7971 status=0x000C waitid(P_ALL, 0, 0xFFBED6D8, WEXITED|WTRAPPED|WNOHANG) = 0 waitid(P_ALL, 0, 0xFFBED6D8, WEXITED|WTR...

...ients/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, "SIGUSR1") == 0) { + query[0] = "SIGUSR1"; + query[1] = ups->upsname; + numq = 2; + } + if (strcmp(var, "SIGUSR2") == 0) { + query[0] = "SIGUSR2"; + query[1] = ups->upsname; + numq = 2; + } + if (!strcmp(var, &...

...ite(4, "\0\0\0\0\0\0\0\0\0\0\0\0Q\332\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4092) = -1 EPIPE (Broken pipe) 31556 --- SIGPIPE (Broken pipe) @ 0 (0) --- 31556 write(2, "rsync: writefd_unbuffered failed"..., 82) = 82 31556 write(2, "\n", 1) = 1 31556 rt_sigaction(SIGUSR1, {SIG_IGN}, NULL, 8) = 0 31556 rt_sigaction(SIGUSR2, {SIG_IGN}, NULL, 8) = 0 31556 wait4(31557, 0x7fffea7a594c, WNOHANG, NULL) = 0 31556 getpid() = 31556 31556 kill(31557, SIGUSR1) = 0 31556 kill(31622, SIGUSR1) = 0 31622 <... select resumed>...

...is often `/var/state/ups`. The *STATEPATH* directive in linkman:upsd.conf[5] overrides this variable. +SIGNALS +------- + +upsd accepts the following signals: + +*SIGINT* *SIGQUIT* *SIGTERM*:: +The upsd process shuts down. + +*SIGHUP*:: +The upsd process reloads it's configuration files. + +*SIGUSR1*:: +upsd remembers the SIGUSR1 signal on behalf of each UPS. When a +client such as linkman:upsmon[8] polls upsd for UPS status chnges, the SIGUSR1 +is reported as a status change. Once reported, upsd discards it's record of +the signal. If a further SIGUSR1 is received while a previous SIG...

...are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it difficult to debug what the problem might be. From what I''ve been following on the list, the appropriate next debugging step is to send a SIGUSR1 signal to the spinning mongrel to get it to spit out what it thinks it is currently running. All we get from this is the following: /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in `join'': SIGUSR1 (SignalException) from /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib...

...se of the issue. Please let me know if you need more information. ============= Start of rsync Block @ Wed Dec 23 10:25:43 SGT 2009 ================ Wed Dec 23 10:25:43 SGT 2009 copying/updating/deleting /svcm/u02/rsync/cron_rsyncexecute_prod.sh building file list ... rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(231) Rsync failure to rsync://oMy2portalProdRsync at lnx09:9060/oMy2Lnx09Prod - Error Code: 20. Error Desc: Received SIGUSR1 or SIGINT Subject:Rsync failure to rsync://oMy2portalProdRsync at lnx09:9060/oMy2Lnx09Prod - Error Code: 20. Error Desc: Received SIGUSR1 or...

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 <renato.golin at linaro.org> wrote: >> On 29 July 2014 15:02, Evgeniy Stepanov <eugeni.stepanov at gmail.com> wrote: >>> You mean replacing SIGUSR1 with SIGHUP in the test case? W...

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 it (different t...

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 or the client t...

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) On the server im using cygwinsrv with the following parameters to rsync...

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. I could issue a patch to circumvent it if Windows is detected, but that hardly seems like Doing The Right Thing. Thoughts? Advice?...

...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 approach by running the reader thread with SIGUSR1 blocked except during the poll, where other threads change their kick action from writing into the pipe-to-self to instead calling pthread_kill() to force EINTR. Unfortunately, using only poll() for this is racy; to fix the race, we either have to resort to POSIX pselect() (which is horribly klunk...

...resumed> ) = 1 (in [5], left {59, 240000}) 28445 --- SIGCHLD (Child exited) @ 0 (0) --- 28461 read(5, "", 4) = 0 28461 write(2, "rsync: connection unexpectedly closed (579059629 bytes received so far) [receiver]\n", 83) = 8 3 28461 rt_sigaction(SIGUSR1, {SIG_IGN}, {0x80570b0, [USR1], SA_RESTART}, 8) = 0 28461 rt_sigaction(SIGUSR2, {SIG_IGN}, {0x80570e0, [USR2], SA_RESTART}, 8) = 0 28461 waitpid(28446, <unfinished ...> 28445 waitpid(-1, <unfinished ...> 28461 <... waitpid resumed> 0xbfff8fd8, WNOHANG) = -1 ECHILD (No child pro...

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/* /share/group/ > An update on this problem... I get the error below (and the error I > reported previously) when running rsync 2.5.2 compiled from...

.../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: Warning: Sent SIGKILL to 1 log processes I can see both SIGUSR1 and SIGKILL generated by the master process, but the current log process doesn't terminate - it receives SIGUSR1, but not SIGKILL. Anyone able to verify this on their own setup? Am I missing a required config change? Using epoll, which hasn't changed. -- David Zambonini

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 > childeslog & Thanks, Kavithaa -------------- next...

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

...ing? Oder any idea, what causes this and how to fix it? The logfiles don't show any information about this. Rebooting the server several times didn't help. Reinstalling the gluster rpms and cleaning out /etc/gluster* didn't help either. A dump from shooting one of the processes with SIGUSR1 can be found here: http://www.xidras.com/logfiles/core Regards, Georg

...<... select resumed> ) = 0 (Timeout) [pid 3082] time(NULL) = 1218891337 [pid 3082] write(2, "io timeout after 300 seconds -- e"..., 39io timeout after 300 seconds -- exiting) = 39 [pid 3082] write(2, "\n"..., 1 ) = 1 [pid 3082] rt_sigaction(SIGUSR1, {SIG_IGN}, NULL, 8) = 0 [pid 3082] rt_sigaction(SIGUSR2, {SIG_IGN}, NULL, 8) = 0 [pid 3082] waitpid(3083, 0xbfff4cac, WNOHANG) = 0 [pid 3082] getpid() = 3082 [pid 3082] kill(3083, SIGUSR1) = 0 [pid 3082] write(2, "rsync error: timeout in data send"..., 79r...