On Wed, Dec 29, 2010 at 02:38:21PM +0100, Stefan Voelkel wrote:
Package: corosync
Version: 1.2.1-3
Severity: important
After booting the machine, corosync is not started correctly:
There's just not enough information in this report. What does the
process do? Does this happen with standalone corosync or only with
heartbeat? What's in the logs?
-- Guido
crm_mon -r1
Connection to cluster failed: connection failed
ps fax | grep corosync
806 ?Ssl0: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 ?Ssl0:00 /usr/sbin/corosync
1540 ?SLs0: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-3Standards-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.
___
Debian-ha-maintainers mailing list
debian-ha-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/debian-ha-maintainers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
