Source: corosync Version: 2.4.2 Severity: important
-- System Information: Debian Release: 8.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) During upgrade procedure by using apt-dater (version 0.9.0) was detected that some Debian hosts (the role is loadbalacers in the system) need to upgrade corosync|2.3.6-3~bpo8+1|u=2.4.2-3~bpo8+1. Corosync has been restarted automatically and therefore we got a huge impact on whole system. Please have a look on that issue.
