Hello,
how can I debug corosync to find the reason for the following continuous
syslog entries?
May 5 15:08:53 gw-palast1 corosync[520]: [TOTEM ] ring 0 active with
no faults
May 5 15:09:46 gw-palast1 corosync[520]: [TOTEM ] Incrementing
problem counter for seqid 51007 iface 192.168.12.1 to [1 of 10]
May 5 15:09:48 gw-palast1 corosync[520]: [TOTEM ] Incrementing
problem counter for seqid 51011 iface 192.168.12.1 to [2 of 10]
May 5 15:09:48 gw-palast1 corosync[520]: [TOTEM ] Decrementing
problem counter for iface 192.168.12.1 to [1 of 10]
May 5 15:09:50 gw-palast1 corosync[520]: [TOTEM ] ring 0 active with
no faults
May 5 15:10:02 gw-palast1 corosync[520]: [TOTEM ] Incrementing
problem counter for seqid 51079 iface 192.168.12.1 to [1 of 10]
May 5 15:10:05 gw-palast1 corosync[520]: [TOTEM ] ring 0 active with
no faults
May 5 15:10:22 gw-palast1 corosync[520]: [TOTEM ] Incrementing
problem counter for seqid 51171 iface 192.168.12.1 to [1 of 10]
May 5 15:10:24 gw-palast1 corosync[520]: [TOTEM ] ring 0 active with
no faults
May 5 15:10:50 gw-palast1 corosync[520]: [TOTEM ] Incrementing
problem counter for seqid 51303 iface 192.168.12.1 to [1 of 10]
May 5 15:10:52 gw-palast1 corosync[520]: [TOTEM ] ring 0 active with
no faults
May 5 15:11:05 gw-palast1 corosync[520]: [TOTEM ] Incrementing
problem counter for seqid 51371 iface 192.168.12.1 to [1 of 10]
May 5 15:11:07 gw-palast1 corosync[520]: [TOTEM ] ring 0 active with
no faults
This logging appears only in the syslog of the active Node of the
cluster (two nodes). There are two rings configured.
eth0 (192.168.12.1) is the interface for all services of the cluster and
it is connected to the switch.
eth1 (192.168.176.1) is a private connection for corosync where the two
interfaces are connected by a cable.
The workload of eth0 should be not very high.
It makes no difference if corosync is configured with multi- or unicast
udp and rrp_token_expired_timeout: 100 doesn't help too.
I appreciate any help you can provide.
Matthias
corosync.conf:
# Please read the openais.conf.5 manual page
totem {
version: 2
# How long before declaring a token lost (ms)
token: 5000
# 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: 5000
# 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: on
# 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: active
# rrp_token_expired_timeout: 100
interface {
ringnumber: 1
bindnetaddr: 192.168.176.0
mcastaddr: 239.95.2.1
mcastport: 6455
}
interface {
# The following values need to be set based on your environment
ringnumber: 0
bindnetaddr: 192.168.12.0
mcastaddr: 226.95.1.1
mcastport: 6458
}
# transport: udpu
}
nodelist {
node {
ring0_addr: 192.168.12.1
ring1_addr: 192.168.176.1
nodeid: 1
}
node {
ring0_addr: 192.168.12.2
ring1_addr: 192.168.176.2
nodeid: 2
}
}
quorum {
provider: corosync_votequorum
two_node: 1
}
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
}
}
--
Dipl.-Ing.(FH) Matthias Hellinghausen
EDV-Abteilung
BZD Gesellschaft f. Transfusionsmedizin Duisburg mbH
Königstrasse 63 - 47051 Duisburg
Tel.: +49 (0) 203 - 300 95 8557
Fax: +49 (0) 203 - 300 95 8564
Email: mh@xxxxxx
Sitz der Gesellschaft: Duisburg
Amtsgericht Duisburg HRB 4273
Geschäftsführung: Sybille Trobisch, Olaf Frahm
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
