Hi Steven,
thanks for looking into this!
> This process pause message indicates the scheduler doesn't schedule
> corosync for 11 seconds which is greater then the failure detection
> timeouts. What does your config file look like? What load are you running?
The load at that point of time around 1.2 - nothing serious.
The config file looks like this:
----- snip -----
aisexec {
group: root
user: root
}
service {
use_mgmtd: yes
ver: 0
name: pacemaker
}
totem {
rrp_mode: passive
join: 100
max_messages: 20
vsftype: none
consensus: 10000
secauth: on
token_retransmits_before_loss_const: 10
threads: 16
token: 10000
version: 2
interface {
bindnetaddr: 192.168.1.0
mcastaddr: 239.250.1.1
mcastport: 5405
ringnumber: 0
}
# 1 GBit as Backup
interface {
bindnetaddr: x.y.z.0
mcastaddr: 239.250.1.2
mcastport: 5415
ringnumber: 1
}
clear_node_high_bit: yes
}
logging {
to_logfile: no
to_syslog: yes
debug: off
timestamp: off
to_stderr: yes
fileline: off
syslog_facility: daemon
}
amf {
mode: disable
}
----- snip -----
--
Sebastian
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
