similar to: Having problem getting Asterisk to work on CentOS 7

On Saturday, November 2, 2019 10:40:45 PM EET Stephan Bosch <stephan at rename-it.nl> wrote: > I think we already know about this issue (tracked as DOP-942). It > apparently happens because qmail masks the SIGCHLD signal while Dovecot > doesn't unmask it before waiting for children. You're right. Isn't this a simple fix - a call to sigprocmask ? This should not be a

Hi, I got this simple test Sieve config: ############################################# # Sieve Filter # Generated by Ingo (http://www.horde.org/apps/ingo/) (11/01/2019, 10:46:06 PM) # Forwards if true { redirect "krustev at krustev.net"; } # Forward Keep Action if true { keep; stop; } ############################################# Which used to work fine with: # 2.2.27

hi, I've some issue with geo-replication (since 3.2.0) and nfs auth (since initial release). Geo-replication --------------- System : Debian 6.0 amd64 Glusterfs: 3.2.0 MASTER (volume) => SLAVE (directory) For some volume it works, but for others i can't enable geo-replication and have this error with a faulty status: 2011-05-03 09:57:40.315774] E

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.

On 7.3.2019 23.37, A. Schulze via dovecot wrote: > > Am 07.03.19 um 17:33 schrieb Aki Tuomi via dovecot: > >>> test-http-client-errors.c:2989: Assert failed: FALSE >>> connection timed out ................................................. : FAILED > Hello Aki, > >> Are you running with valgrind or on really slow system? > I'm not aware my buildsystem

Hello, I just installed BackupPC in a Debian box to use it as backup server. As you know, this software makes use, among others, of rsync. When using the rsync option, it fails. Server: Debian Jessie. BackupPC 3.3.1 built from source, executed by user "backup-user". Rsync 3.1.2 built from source with the default options. Client Debian Jessie. Rsync 3.1.2 built from source with the

Hi, As a quick workaround for geo-replication to work. Please configure the following option. gluster vol geo-replication <mastervol> <slavehost>::<slavevol> config access_mount true The above option will not do the lazy umount and as a result, all the master and slave volume mounts maintained by geo-replication can be accessed by others. It's also visible in df output.

On 02/05/2018 01:33 PM, Florian Weimer wrote: > Do you have strace output going further back, at least to the proceeding > getcwd call?? It would be interesting to see which path the kernel > reports, and if it starts with "(unreachable)". I got the strace output now, but it very difficult to read (chdir in a multi-threaded process ?). My current inclination is to blame

Hi, this is a type 3 bugreport ;) ( 3. Repeatable problems specific to your software layout.) first of all i must state, that i run openssh on a fairly old redhat based system (redhat 6.1). if you have any further questions, feel free to contact me. configure options: CFLAGS="-O2 -m486" ./configure --without-rsh --with-tcp-wrappers --prefix=/opt/openssh-2.3.0

Hi! I'm unable to write with remote rsync in daemon mode. ********* My configuration: rsync 2.6.2 Linux 2.4.20-alt16-up (ALTLinux www.altlinux.org) (There is owl-patch in ALTLinux-kernel) ========== /etc/rsyncd.conf ============= log file = /var/log/rsync [routers] comment = Our Backups path = /mnt/backup/routers uid = archiver gid = archiver use chroot = true read only = false list = true

Hi all, could someone tell me what this does mean "bad file descriptor" when trying to start asterisk. It goes till the CLI command and then die with this message. Below an strace output from asterisk -vvvvvvvvvc It's on debian Sarge kernel 2.6.7 with packages from debian VoIP team. The server was running fine till now with this version. Thanks

I have identical two hypervisors same operating system: Ubuntu 22.04.2 LTS Recently both virsh stopped talking to the libvirtd. Both stopped within a few days of each other. Currently if I run: virsh uri virsh version virsh list # virsh list ..nothing just hangs When I ran strace on these broken machines it get stuck at same spot: strace virsh list ...

Hi Angel and many thanks for your answer The application still sending & receiving data .- strace over the application: write(1, "\33[1;1H\237#SF \234", 44) = 44 <--it was sent from the application to the terminal, but ssh didn't received this string read(0, "\10", 1024) = 1 <- the client remained sending data and it

nmbd has been dying on me occasionally. I'm running mandrake 9.2 with samba3-server-3.0.0-2mdk. We've got our users in ldap but I'd seen this symptom previously when I was using an earlier version of samba that didn't support ldap. There is nothing useful in the logs and a PS shows a nmb process still running. This last time around, I had a ptrace running on both nmbd

Hello, I have several systems which I recently updated with yum -y update to all the latest packages. These systems use yum-priorities and use the CentOS (priority 1) EPEL (priority 5) and rpmforge (priority 10) repositories. After the updates, dhcpd stopped working with a SIGPIPE error which occurs shortly after it attempts to fork into the background. I worked around that problem by building

Hi there, Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the virtual guests don't get their RBD disks made available to them. On openSUSE 15.1 (which includes libvirt 5.1.0) that worked fine. The XML is as follows: <domain type='xen' id='7'>   <name>mytwotel-a</name>   <uuid>a56daa5d-c095-49d5-ae1b-00b38353614e</uuid>  

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

It's QEMU 4.2.1-lp152.9.6.1. I've tried updating it from the Open Build Service repos but there's too many version conflicts. Marcel On 26/10/20 9:02 pm, Ján Tomko wrote: > On a Friday in 2020, Marcel Juffermans wrote: >> Hi there, >> >> Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the >> virtual guests don't get their RBD disks

It should be noted that a symlink to the built llvm-config will return the paths for the system llvm instead of the built llvm; it's fine on OS X though. Some differences in realpath?

Hello every one an a pretty new year. I'm making a derivative a the Feather linux-live which can be found here: http://franboisson.homeip.net/clef/ClefAgreg.iso Everything works find except with USB key with sector size different then 512 (2048 in my case). I look at the source of syslinux and change the following: * The test in syslxmod.c * Change each time I see SECTOR_SHIFT=9 in