Your message dated Sat, 09 Jan 2021 20:49:23 +0100 with message-id <[email protected]> and subject line Re: corosync-qdevice will not daemonize/run has caused the Debian Bug report #902117, regarding corosync-qdevice will not daemonize/run to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 902117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902117 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: corosync-qdevice Version: 2.4.4-3 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages corosync-qdevice depends on: ii corosync 2.4.4-3 ii libc6 2.24-11+deb9u3 ii libcmap4 2.4.2-3+deb9u1 ii libcorosync-common4 2.4.2-3+deb9u1 ii libnspr4 2:4.12-6 ii libnss3 2:3.26.2-1.1+deb9u1 ii libnss3-tools 2:3.26.2-1.1+deb9u1 ii libqb0 1.0.3-1 ii libsystemd0 232-25+deb9u3 ii libvotequorum8 2.4.2-3+deb9u1 corosync-qdevice recommends no packages. corosync-qdevice suggests no packages. -- no debconf information corosync-qdevice is a daemon that runs on each cluster node that help provide a voting subsystem that utilizes corosync-qnet outside the cluster. After installing the packages from debian stretch, and configuring the application, it does not run. One can use -d and -f to troubleshoot issues, and even in this situation no data is logged to the console, or any syslog messages generated. The application immediately fails. Upgrading to corosync, libqb, and corosync-qdevice from testing has the same result. The cluster mailing list suggests a potential issue with compilation compatability with libqb and binutils 2.29+. Debian stretch bundles 2.28, however it's unknown how the applications are compiled/linked.
--- End Message ---
--- Begin Message ---I failed to reproduce this with the corosync 3.1.0-2 and corosync-qdevice 3.0.1-1 packages. corosync-qdevice -d -f emitted plenty of debug logs, and the position of the nodelist{} section didn't make any difference. So I'm closing this bug; please reopen with further info if appropriate. -- Thanks, Feri
--- End Message ---
