Your message dated Sun, 02 Jan 2011 14:32:11 +0000
with message-id <[email protected]>
and subject line Bug#608269: fixed in corosync 1.2.1-4
has caused the Debian Bug report #608269,
regarding corosync: does not start correctly on boot
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.)
--
608269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608269
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: corosync
Version: 1.2.1-3
Severity: important
After booting the machine, corosync is not started correctly:
crm_mon -r1
Connection to cluster failed: connection failed
ps fax | grep corosync
806 ? Ssl 0:01 /usr/sbin/corosync
818 ? S 0:00 \_ /usr/sbin/corosync
819 ? S 0:00 \_ /usr/sbin/corosync
820 ? S 0:00 \_ /usr/sbin/corosync
821 ? S 0:00 \_ /usr/sbin/corosync
822 ? S 0:00 \_ /usr/sbin/corosync
823 ? S 0:00 \_ /usr/sbin/corosync
Stopping is not possible with /etc/init.d/corosync stop
A normal kill is ingnored.
Kiilling with -9, and then starting corosync works though:
killall -9 corosync
/etc/init.d/corosync start
Starting corosync daemon: corosync.
1530 ? Ssl 0:00 /usr/sbin/corosync
1540 ? SLs 0:00 \_ /usr/lib/heartbeat/stonithd
1541 ? S 0:00 \_ /usr/lib/heartbeat/cib
1542 ? S 0:00 \_ /usr/lib/heartbeat/lrmd
1543 ? S 0:00 \_ /usr/lib/heartbeat/attrd
1544 ? S 0:00 \_ /usr/lib/heartbeat/pengine
1545 ? S 0:00 \_ /usr/lib/heartbeat/crmd
# crm_mon -1
============
Last updated: Sun Dec 26 14:13:37 2010
Stack: openais
Current DC: NONE
2 Nodes configured, 2 expected votes
4 Resources configured.
============
OFFLINE: [ sonic futro ]
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages corosync depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii libcorosync4 1.2.1-3 Standards-based cluster framework
ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip
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: 10.0.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
--
Never reveal your best argument.
--- End Message ---
--- Begin Message ---
Source: corosync
Source-Version: 1.2.1-4
We believe that the bug you reported is fixed in the latest version of
corosync, which is due to be installed in the Debian FTP archive:
corosync-dbg_1.2.1-4_i386.deb
to main/c/corosync/corosync-dbg_1.2.1-4_i386.deb
corosync_1.2.1-4.diff.gz
to main/c/corosync/corosync_1.2.1-4.diff.gz
corosync_1.2.1-4.dsc
to main/c/corosync/corosync_1.2.1-4.dsc
corosync_1.2.1-4_i386.deb
to main/c/corosync/corosync_1.2.1-4_i386.deb
libcorosync-dev_1.2.1-4_i386.deb
to main/c/corosync/libcorosync-dev_1.2.1-4_i386.deb
libcorosync4_1.2.1-4_i386.deb
to main/c/corosync/libcorosync4_1.2.1-4_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guido Günther <[email protected]> (supplier of updated corosync package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sun, 02 Jan 2011 12:41:52 +0100
Source: corosync
Binary: corosync corosync-dbg libcorosync4 libcorosync-dev
Architecture: source i386
Version: 1.2.1-4
Distribution: unstable
Urgency: low
Maintainer: Debian HA Maintainers
<[email protected]>
Changed-By: Guido Günther <[email protected]>
Description:
corosync - Standards-based cluster framework (daemon and modules)
corosync-dbg - Standards-based cluster framework (debugging symbols)
libcorosync-dev - Standards-based cluster framework (developer files)
libcorosync4 - Standards-based cluster framework (libraries)
Closes: 608269
Changes:
corosync (1.2.1-4) unstable; urgency=low
.
* [2ebaf59] Move corosync start out of rcS since we want to be able to log
to syslog and rsyslog isn't started in rcS. (Closes: #608269)
Checksums-Sha1:
3fb9366cc41c0c0914ec427374d2c3b7029b2785 1289 corosync_1.2.1-4.dsc
9f8e91b3809a8ced7e666f7cc51f33c6157deaa0 11155 corosync_1.2.1-4.diff.gz
84121595381b15ee25451ce4f0cf719f41c82dba 343426 corosync_1.2.1-4_i386.deb
851db5d1f37895045ba432a5275222f1a83dd190 2018828 corosync-dbg_1.2.1-4_i386.deb
0d0a05445c3ba9ce77c18d3de6aa6da6bd094dbf 268188 libcorosync4_1.2.1-4_i386.deb
5c35f65965b68a8dca2661e7c22411dd5e697c34 403632
libcorosync-dev_1.2.1-4_i386.deb
Checksums-Sha256:
352a93259e85dc54a02bd377d5032af292d58412763689e4b96dc92796afc463 1289
corosync_1.2.1-4.dsc
a912f6efd41ff19f5b67f897d9893d485404b721bdd45950ffb9274835e79cb1 11155
corosync_1.2.1-4.diff.gz
4b89237cfc194b7c0a94eb257af81fd1f3a7f40518b52c9e952978c2405c3b41 343426
corosync_1.2.1-4_i386.deb
591fe3e644bfcb7c41c003abccd0e50da426c0daaea70735b1c2b81f9bfe4b43 2018828
corosync-dbg_1.2.1-4_i386.deb
3567d808e47f6db021ba5b21b5877c92a30dbfb3d1874da9acf762fdbd5146b5 268188
libcorosync4_1.2.1-4_i386.deb
078a4ec26c18fb67923fc0c1db0b26bfc21b5d2f4406b8c772cb9a9eaf289714 403632
libcorosync-dev_1.2.1-4_i386.deb
Files:
3d64fd6dd977e35548dfd23f10128d70 1289 admin optional corosync_1.2.1-4.dsc
b6f9ac8402b0ff4269cad0dd434720e8 11155 admin optional corosync_1.2.1-4.diff.gz
a29c338a746810adc53f892ff72579e2 343426 admin optional
corosync_1.2.1-4_i386.deb
a2c61a623075195606d150987e39b43c 2018828 debug extra
corosync-dbg_1.2.1-4_i386.deb
b12830cbc032d0dd07a1c40aa65c292f 268188 libs optional
libcorosync4_1.2.1-4_i386.deb
0522e729ed70561faef49e9e23aa8974 403632 libdevel optional
libcorosync-dev_1.2.1-4_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFNIGXQn88szT8+ZCYRAnfXAJ9jEqXxUWRiTncRoRFMysTGaq7ONwCfXJ1F
WylTNVuOotcIl9a94T6i4+0=
=eqgc
-----END PGP SIGNATURE-----
--- End Message ---
