similar to: SIGCHLD SIG_IGN, then wait - warning messages

I'm trying to understand how to properly setup the /etc/rsyncd.conf file to run an rsync daemon with a secrets file specified in a module - the rsync.conf manpage does not spell it out clearly enough. Rsync server is rsync-2.5.6. If this is my /etc/rsyncd.conf file: ------------------------------------ log file = /var/log/rsync uid = root gid = root [test] uid = rsync1 gid =

Peter Dimitrov and myself were debugging a very peculiar bug when libguestfs is run as a plugin from collectd: https://www.redhat.com/archives/libguestfs/2018-November/thread.html#00023 The long story short is that collectd leaks SIGCHLD == SIG_IGN setting into plugins: https://www.redhat.com/archives/libguestfs/2018-November/msg00095.html This means that any plugin that does the usual

On Tue, Nov 13, 2018 at 10:04:33AM +0000, Daniel P. Berrangé wrote: > On Fri, Nov 09, 2018 at 12:19:30PM +0000, Richard W.M. Jones wrote: > > Peter Dimitrov and myself were debugging a very peculiar bug when > > libguestfs is run as a plugin from collectd: > > > > https://www.redhat.com/archives/libguestfs/2018-November/thread.html#00023 > > > > The long

Hi Rich, On Fri, Nov 9, 2018 at 1:19 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > Peter Dimitrov and myself were debugging a very peculiar bug when > libguestfs is run as a plugin from collectd: > > https://www.redhat.com/archives/libguestfs/2018-November/thread.html#00023 > > The long story short is that collectd leaks SIGCHLD == SIG_IGN setting > into

On Fri, Nov 09, 2018 at 12:19:30PM +0000, Richard W.M. Jones wrote: > Peter Dimitrov and myself were debugging a very peculiar bug when > libguestfs is run as a plugin from collectd: > > https://www.redhat.com/archives/libguestfs/2018-November/thread.html#00023 > > The long story short is that collectd leaks SIGCHLD == SIG_IGN setting > into plugins: > >

Hi, thank you very much for reporting this! Sounds like a bug in the exec plugin – it never ceases to amaze me how many issues a single plugin can have ;) > > > This means that any plugin that does the usual pattern of: > > > > > > pid = fork (); Note that the exec plugin is the *only* plugin that does this. All other plugins are forbidden to fork(), popen() or

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:

Some background information. I have used Debian with Asterisk for several years. Have encountered zero problems. I am now trying to setup an Asterisk on a CentOS7 box using VMWare Workstation. I am brand new to CentOS and RHEL so I may be missing something obvious. I am installing CentOS Minimal Install and Asterisk from Source. (I have installed Asterisk from Source on Debian hundreds of

Thank you Tzafrir. I had been using different users in earlier attempts to make this work. Decided to try everything where root is the only user, simply to verify it's working. For problem 2, where asterisk is writing to the log but doesn't seem to receive the SIP packets even though tcpdump indicates they are making it to the box on 5060, I am starting asterisk while logged in as root.

Hi, I don''t know whether this is a ruby, puppet, or facter bug. The whole issue is one of the "really weird" ones. I first noticed the problem when working with puppet on a train, without any internet connection. In such situation, two problems appear: 1) Mildly annoying, frequent 2-second pauses followed by: Timed out seeking value for ipaddress I think this is

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

Yes, this is a patch against an older version of OpenSSH with other stuff anyways, BUT, it's so TRIVIAL(*), that you can see how it would apply to newer versions (which I've not tried). Here's the gist: server_loop2() has a race condition with respect to reception of SIGCHLD and checking/setting child_terminated. This patch does two things: wait_until_can_do_something() adds a 1

Hi What if you have sysv signals (i.e. signal is restored when handler is called) and child process exits here? Zombie will be left, because SIGCHLD is ignored at that point. Shouldn't signal be before waitpid? Mikulas static void main_sigchld_handler(int sig) { int save_errno = errno; pid_t pid; int status; while ((pid = waitpid(-1, &status, WNOHANG))

A quick glance shows that the exec plugin actually is clearing the signal mask: https://github.com/collectd/collectd/blob/master/src/exec.c#L526 Can you give some more context when this problem comes up? Ideally in a Github issue (hint, hint ;). -- Florian octo Forster Hacker in training GnuPG: 0x0C705A15 http://octo.it/

On Tue, Nov 13, 2018 at 12:00:19PM +0100, Florian Forster wrote: > Hi, > > thank you very much for reporting this! Sounds like a bug in the exec plugin – > it never ceases to amaze me how many issues a single plugin can have ;) > > > > > This means that any plugin that does the usual pattern of: > > > > > > > > pid = fork (); > > Note

On Tue, Nov 13, 2018 at 03:17:33PM +0200, Peter Dimitrov wrote: > I was extending the virt plugin. > It already collects similar data (about VMs) using Libvirt's API, but lacks > disk usage information. > > I went through some hoops to link libguestfs correctly to collectd. > Is it okay to just include fork(), waitpid() example? It does reproduce the > issue. Yes, I

Hi list, I have 3 Citrix Xenserver 5.6  and currently building a a VM backup server. I took the xe client on one of the server and installed it on the backup server (gentoo based) installed the stunnel package to make XE work. now when running, I get this error message : [server ­~ #] ./xe help -debug -s 192.168.111.17 -u user -pw pass Connecting via stunnel to [192.168.111.17] port [443]

on systems that has separate IPv4/v6 socket layer (i.e. IPv4 packet does not get routed to AF_INET6 socket) rsync --daemon would accept IPv6 sessions only. open_socket_in() tries to deal with the situation, but it was not enough. here's the patch. (it is required on all *BSDs to accept both IPv4 and IPv6 connections with --daemon mode) itojun --- ? configure.lineno ? lib/dummy

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, we have two UPSes - one Galaxy and one from Socomec, both monitored by the NUT server. The NUT server runs the version 2.7.2. We have roughly 3500 clients running upsmon, reading the status of both UPSes. They run mainly the version 2.6.4 and some 2.7.2. We observed the following on both client versions, regardless whether we run upsmon in the daemon or debug mode: Running upsc socomec