Your message dated Wed, 21 Dec 2016 21:46:29 +0100
with message-id <20161221204629.i6jdfymfymiqs...@gavran.carpriv.carnet.hr>
and subject line heartbeat: v1 config style not compatible with systemd
has caused the Debian Bug report #818961,
regarding heartbeat: v1 config style not compatible with systemd
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 ow...@bugs.debian.org
immediately.)
--
818961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: heartbeat
Version: 1:3.0.5+hg12629-1.2
Severity: grave
Tags: upstream
Justification: causes non-serious data loss
Hello,
as previous reported on IRC the v1 config style does not work with systemd as
init system. Failovers are broken, because of the event based systemd, instead
of LSB ordering for services. I also tried out the 1:3.0.6-2 version, without
any luck.
Upstream also states (have not got the link now) that it is unsupported, since
v1 style does not get new features.
IMO the package should warn (debconf dialog prio high?) the user if he upgrades
heartbeat and systemd+v1 config is in use.
Why severity grave?
On setting up some test VMs I noticed that it looks like the cluster is working,
but on intensive testing (just some failovers or using /usr/share/heartbeat/
scripts) everything broke again and again. For productive setups this will fail
in a bigger downtime and the user could not identify the real problem (missing
support) from the logs, except of some coredumps and never taking over clients.
-- System Information:
Debian Release: 8.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Closing this bug as the problem could not be reproduced with
heartbeat 1:3.0.6-3 from unstable with the following haresources:
node1 IPaddr2::192.168.122.101/24/ens3 drbddisk::drbd0 LVM::cluster
Filesystem::/dev/cluster/srv::/srv::ext4 mysql apache::/etc/apache2/apache2.conf
When fully configured both heartbeat service and all cluster resources
start properly on cluster boot. Stopping a cluster node moves the
resources to the remaining node as expected.
If there are still problems in using heartbeat on systemd based
machines please reopen providing cluster logs and configuration
for the issue.
--
Valentin
--- End Message ---
