Package: corosync
Version: 1.4.2-3
Severity: normal
Dear Maintainer,
in some circumtances, when '/etc/init.d/corosync stop' is called, the script
hangs forever.
In /var/log/syslog, there are many messages like these:
[...]
Jun 4 10:14:12 rasca corosync[2179]: [pcmk ] notice: pcmk_shutdown: Still
waiting for crmd (pid=2210, seq=6) to terminate...
Jun 4 10:14:42 rasca corosync[2179]: [pcmk ] notice: pcmk_shutdown: Still
waiting for crmd (pid=2210, seq=6) to terminate...
Jun 4 10:15:12 rasca corosync[2179]: [pcmk ] notice: pcmk_shutdown: Still
waiting for crmd (pid=2210, seq=6) to terminate...
Jun 4 10:15:42 rasca corosync[2179]: [pcmk ] notice: pcmk_shutdown: Still
waiting for crmd (pid=2210, seq=6) to terminate...
Jun 4 10:16:12 rasca corosync[2179]: [pcmk ] notice: pcmk_shutdown: Still
waiting for crmd (pid=2210, seq=6) to terminate...
[...]
I have some resources configured in Pacemaker, and some are misconfigured.
So, this bug is just to ask for killing the daemon harder (maybe -9 ?) after a
timeout.
Please, let me know if you would like me to write a patch for the init.d script
that implements a timeout in the stop operation.
Also, please let me know if you think this is not an important issue.
Regards.
-- System Information:
Debian Release: 7.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages corosync depends on:
ii adduser 3.113+nmu3
ii libc6 2.13-38
ii libcfg4 1.4.2-3
ii libconfdb4 1.4.2-3
ii libcoroipcc4 1.4.2-3
ii libcoroipcs4 1.4.2-3
ii libcpg4 1.4.2-3
ii libevs4 1.4.2-3
ii liblogsys4 1.4.2-3
ii libpload4 1.4.2-3
ii libquorum4 1.4.2-3
ii libsam4 1.4.2-3
ii libtotem-pg4 1.4.2-3
ii libvotequorum4 1.4.2-3
ii lsb-base 4.1+Debian8
corosync recommends no packages.
corosync suggests no packages.
-- Configuration Files:
/etc/corosync/corosync.conf changed:
totem {
version: 2
# How long before declaring a token lost (ms)
token: 3000
# How many token retransmits before forming a new configuration
token_retransmits_before_loss_const: 10
# How long to wait for join messages in the membership protocol (ms)
join: 60
# How long to wait for consensus to be achieved before starting a new
round of membership configuration (ms)
consensus: 3600
# Turn off the virtual synchrony filter
vsftype: none
# Number of messages that may be sent by one processor on receipt of
the token
max_messages: 20
# Limit generated nodeids to 31-bits (positive signed integers)
clear_node_high_bit: yes
# Disable encryption
secauth: off
# How many threads to use for encryption/decryption
threads: 0
# Optionally assign a fixed node id (integer)
# nodeid: 1234
# This specifies the mode of redundant ring, which may be none, active,
or passive.
rrp_mode: none
interface {
# The following values need to be set based on your environment
ringnumber: 0
bindnetaddr: 172.22.0.0 & 255.255.0.0
mcastaddr: 226.94.1.1
mcastport: 5405
}
}
amf {
mode: disabled
}
service {
# Load the Pacemaker Cluster Resource Manager
ver: 0
name: pacemaker
}
aisexec {
user: root
group: root
}
logging {
fileline: off
to_stderr: yes
to_logfile: no
to_syslog: yes
syslog_facility: daemon
debug: off
timestamp: on
logger_subsys {
subsys: AMF
debug: off
tags: enter|leave|trace1|trace2|trace3|trace4|trace6
}
}
/etc/default/corosync changed:
START=yes
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
