Your message dated Tue, 14 Sep 2010 11:32:10 +0000
with message-id <[email protected]>
and subject line Bug#596694: fixed in corosync 1.2.1-2
has caused the Debian Bug report #596694,
regarding corosync fails to start corretly
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.)


-- 
596694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596694
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: corosync
Version: 1.2.1-1
Severity: important


Hi,

after a clean install of debian squeeze and increasing the consensus timeout to 
3600 (to solve 
#573030) corosync does not start correctly after boot. crm_mon is unable to 
connect to the cluster.

The processlist (ps auxf) shows the following:

root       773  0.3  1.3 128960  5136 ?        Ssl  13:11   0:00 
/usr/sbin/corosync
root       808  0.0  0.8 114484  3308 ?        S    13:11   0:00  \_ 
/usr/sbin/corosync
root       809  0.0  0.8 114480  3308 ?        S    13:11   0:00  \_ 
/usr/sbin/corosync
root       810  0.0  0.8 114480  3308 ?        S    13:11   0:00  \_ 
/usr/sbin/corosync
root       811  0.0  0.8 114480  3308 ?        S    13:11   0:00  \_ 
/usr/sbin/corosync
root       812  0.0  0.8 114480  3308 ?        S    13:11   0:00  \_ 
/usr/sbin/corosync
root       813  0.0  0.8 114480  3308 ?        S    13:11   0:00  \_ 
/usr/sbin/corosync
root       925  0.1  0.4  52416  1888 ?        Sl   13:11   0:00 
/usr/sbin/rsyslogd -c4
root       958  0.0  0.3  44568  1336 ?        Ss   13:11   0:00 ha_logd: read 
process
root       959  0.0  0.2  44568   932 ?        S    13:11   0:00  \_ ha_logd: 
write process

Killing the corosync processes and doing a

> /etc/init.d/corosync start

the processlist now shows

root      1422  0.0  1.3 146160  5268 ?        Ssl  15:15   0:00 
/usr/sbin/corosync
root      1433  0.0  3.1  79524 12036 ?        SLs  15:15   0:00  \_ 
/usr/lib/heartbeat/stonithd
103       1434  0.0  1.2  82444  4892 ?        S    15:15   0:00  \_ 
/usr/lib/heartbeat/cib
root      1435  0.0  0.6  83428  2372 ?        S    15:15   0:00  \_ 
/usr/lib/heartbeat/lrmd
103       1436  0.0  0.8  83504  3112 ?        S    15:15   0:00  \_ 
/usr/lib/heartbeat/attrd
103       1437  0.0  0.7  83876  2972 ?        S    15:15   0:00  \_ 
/usr/lib/heartbeat/pengine
103       1438  0.0  0.9  89732  3612 ?        S    15:15   0:00  \_ 
/usr/lib/heartbeat/crmd

and crm_mon works as expected.

The bug seems to be caused by corosync being started earlier than the syslog 
daemon during boot:

/etc/init.d/corosync:

#! /bin/sh
#
### BEGIN INIT INFO
# Provides:          corosync
# Required-Start:    $network $remote_fs
# Required-Stop:     $network $remote_fs
# Default-Start:     S
# Default-Stop:      0 1 6
# Short-Description: corosync cluster framework
### END INIT INFO
[...]


/etc/init.d/rsyslog:

#! /bin/sh
### BEGIN INIT INFO
# Provides:          rsyslog
# Required-Start:    $remote_fs $time
# Required-Stop:     umountnfs $time
# X-Stop-After:      sendsigs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: enhanced syslogd
# Description:       Rsyslog is an enhanced multi-threaded syslogd.
#                    It is quite compatible to stock sysklogd and can be
#                    used as a drop-in replacement.
### END INIT INFO
[...]


It seems that corosync must be started after the syslogd and perhaps even after 
ha_logd 
(part of the package cluster-glue):

/etc/init.d/logd:

[...]
### BEGIN INIT INFO
# Description: ha_logd is a non-blocking logging daemon.
#       It can log messages either to a file or through syslog
#       daemon.
# Short-Description: ha_logd logging daemon
# Provides: ha_logd
# Required-Start: $network $syslog $remote_fs
# Required-Stop: $network $syslog $remote_fs
# X-Start-Before: heartbeat openais
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
### END INIT INFO

Here corosync seems to be missing in the line 'X-Start-Before'.

Greetings,

Frank


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages corosync depends on:
ii  adduser                       3.112      add and remove users and groups
ii  libc6                         2.11.2-2   Embedded GNU C Library: Shared lib
ii  libcorosync4                  1.2.1-1    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: 127.0.0.1 
                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



--- End Message ---
--- Begin Message ---
Source: corosync
Source-Version: 1.2.1-2

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-2_i386.deb
  to main/c/corosync/corosync-dbg_1.2.1-2_i386.deb
corosync_1.2.1-2.diff.gz
  to main/c/corosync/corosync_1.2.1-2.diff.gz
corosync_1.2.1-2.dsc
  to main/c/corosync/corosync_1.2.1-2.dsc
corosync_1.2.1-2_i386.deb
  to main/c/corosync/corosync_1.2.1-2_i386.deb
libcorosync-dev_1.2.1-2_i386.deb
  to main/c/corosync/libcorosync-dev_1.2.1-2_i386.deb
libcorosync4_1.2.1-2_i386.deb
  to main/c/corosync/libcorosync4_1.2.1-2_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: Tue, 14 Sep 2010 13:05:21 +0200
Source: corosync
Binary: corosync corosync-dbg libcorosync4 libcorosync-dev
Architecture: source i386
Version: 1.2.1-2
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: 582104 596694
Changes: 
 corosync (1.2.1-2) unstable; urgency=low
 .
   * [a2453fb] Add status to corosync init script (Closes: #582104) - thanks to
     Raoul Bhatia for the patch
   * [986d8ed] Make sure we start before and stop after $syslog (Closes:
     #596694) - thanks to Frank Schmidt for tracking down the start issues
Checksums-Sha1: 
 a18550a58954967309d49389f5e9185fe4a3604e 1289 corosync_1.2.1-2.dsc
 339f8cf6510dafc660b04577b4482195a095c05d 10735 corosync_1.2.1-2.diff.gz
 6cfa08e1e303132020e009093e025d29ab98b463 343028 corosync_1.2.1-2_i386.deb
 b9e37f54ed8de6ad5694c9a5367d6e582ff1ec56 2019848 corosync-dbg_1.2.1-2_i386.deb
 79ed3802cd111aa0f5c7fb858b656b606b760569 267944 libcorosync4_1.2.1-2_i386.deb
 a8b019541b94555714f041a4b2701ed59c18eb53 403486 
libcorosync-dev_1.2.1-2_i386.deb
Checksums-Sha256: 
 25a29bd1e8f3dbe1f4f59e81fb6112b57fe660e8fa7a516a55cc98bc0c08c314 1289 
corosync_1.2.1-2.dsc
 1352d7f33b3ca62bbde6739d4460788f3d67b3bb41f120c2e2fb602aa4adc809 10735 
corosync_1.2.1-2.diff.gz
 ea9a332639cb8b3b8e200c0788a3ae340aa5dca361ada3dd8c981959a9d074ee 343028 
corosync_1.2.1-2_i386.deb
 970e50d6c0519f8627dd20c54f2b09726465bf9a300c93fb0c40343c26ddebbd 2019848 
corosync-dbg_1.2.1-2_i386.deb
 5d44dd5030cc3798b1a08a9b36490c2e19408a8ecc4f1a21d0f21c92422d4f22 267944 
libcorosync4_1.2.1-2_i386.deb
 abfd06314936682ad6f70a730e1dba5b868824da8315a4c0d130be45c8556cae 403486 
libcorosync-dev_1.2.1-2_i386.deb
Files: 
 f3d35b7c8b433855c7890b0a1bece298 1289 admin optional corosync_1.2.1-2.dsc
 5fa7b0ab1f347658471e7b9b25e0c626 10735 admin optional corosync_1.2.1-2.diff.gz
 d60bf47658611b48228165bf761d58ba 343028 admin optional 
corosync_1.2.1-2_i386.deb
 699286a63076826021889d54ff54d90c 2019848 debug extra 
corosync-dbg_1.2.1-2_i386.deb
 a1dd17eaa498f9090d69734bdbdc3c0d 267944 libs optional 
libcorosync4_1.2.1-2_i386.deb
 f4d34cfb4c149869852ae8d2642e157f 403486 libdevel optional 
libcorosync-dev_1.2.1-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFMj1o/n88szT8+ZCYRAvBMAJwIalDSyXiMDa2R26xFJokpCdOb5wCcDjnz
bL1PyrqUc/Xw11ZCIfppkbg=
=kDDE
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to