In the name of Allah
Hello
I also compiled and installed corosync 1.3.4 with gcc 4.4.4 on two VMs
that are connected with bridge
on Scientific Linux 6.0 with kernel version 2.6.32-71.el6.x86_64 and
again I encountered the same problem.
I configured corosync 1.4.2 in transport udpu state and started it on
two VMs with above characteristics. They are working about 21 hours
without any problems. i will keep this vms running and will report
results.
Corosync 1.3.4 config file:
compatibility: none
totem {
version: 2
token: 5000
token_retransmits_before_loss_const: 20
join: 1000
consensus: 7500
vsftype: none
max_messages: 20
secauth: off
threads: 0
nodeid: 3
clear_node_high_bit: yes
interface {
ringnumber: 0
bindnetaddr: 192.168.100.0
mcastaddr: 226.94.1.1
mcastport: 5405
ttl: 1
}
}
logging {
fileline: off
to_stderr: no
to_logfile: yes
to_syslog: yes
logfile: /var/log/cluster/corosync.log
debug: on
timestamp: on
logger_subsys {
subsys: AMF
debug: on
}
}
amf {
mode: disabled
}
Corosync 1.3.4 log messages:
Apr 3 11:52:55 VM3 corosync[6639]: [MAIN ] Corosync Cluster Engine
('1.3.4'): started and ready to provide service.
Apr 3 11:52:55 VM3 corosync[6639]: [MAIN ] Corosync built-in features:
Apr 3 11:52:55 VM3 corosync[6639]: [MAIN ] Successfully read main
configuration file '/etc/corosync/corosync.conf'.
Apr 3 11:52:55 VM3 corosync[6639]: [TOTEM ] Initializing transport
(UDP/IP Multicast).
Apr 3 11:52:55 VM3 corosync[6639]: [TOTEM ] Initializing
transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
Apr 3 11:52:55 VM3 corosync[6639]: [TOTEM ] The network interface
[192.168.100.3] is now up.
Apr 3 11:52:55 VM3 corosync[6639]: [SERV ] Service engine loaded:
corosync extended virtual synchrony service
Apr 3 11:52:55 VM3 corosync[6639]: [SERV ] Service engine loaded:
corosync configuration service
Apr 3 11:52:55 VM3 corosync[6639]: [SERV ] Service engine loaded:
corosync cluster closed process group service v1.01
Apr 3 11:52:55 VM3 corosync[6639]: [SERV ] Service engine loaded:
corosync cluster config database access v1.01
Apr 3 11:52:55 VM3 corosync[6639]: [SERV ] Service engine loaded:
corosync profile loading service
Apr 3 11:52:55 VM3 corosync[6639]: [SERV ] Service engine loaded:
corosync cluster quorum service v0.1
Apr 3 11:52:55 VM3 corosync[6639]: [MAIN ] Compatibility mode set
to none. Using V2 of the synchronization engine.
Apr 3 11:52:55 VM3 corosync[6639]: [TOTEM ] A processor joined or
left the membership and a new membership was formed.
Apr 3 11:52:55 VM3 corosync[6639]: [CPG ] chosen downlist: sender
r(0) ip(192.168.100.3) ; members(old:0 left:0)
Apr 3 11:52:55 VM3 corosync[6639]: [MAIN ] Completed service
synchronization, ready to provide service.
Apr 3 11:53:40 VM3 corosync[6639]: [TOTEM ] A processor joined or
left the membership and a new membership was formed.
Apr 3 11:53:40 VM3 corosync[6639]: [CPG ] chosen downlist: sender
r(0) ip(192.168.100.3) ; members(old:1 left:0)
Apr 3 11:53:40 VM3 corosync[6639]: [MAIN ] Completed service
synchronization, ready to provide service.
Apr 3 15:31:06 VM3 corosync[6639]: [TOTEM ] A processor failed,
forming new configuration.
Apr 3 15:31:06 VM3 corosync[6639]: [TOTEM ] A processor joined or
left the membership and a new membership was formed.
Apr 3 15:31:07 VM3 corosync[6639]: [CPG ] chosen downlist: sender
r(0) ip(192.168.100.3) ; members(old:2 left:0)
Apr 3 15:31:07 VM3 corosync[6639]: [MAIN ] Completed service
synchronization, ready to provide service.
Apr 3 15:31:26 VM3 corosync[6639]: [TOTEM ] A processor failed,
forming new configuration.
Apr 3 15:31:34 VM3 corosync[6639]: [TOTEM ] A processor joined or
left the membership and a new membership was formed.
Apr 3 15:31:34 VM3 corosync[6639]: [CPG ] chosen downlist: sender
r(0) ip(192.168.100.3) ; members(old:2 left:0)
Apr 3 15:31:34 VM3 corosync[6639]: [MAIN ] Completed service
synchronization, ready to provide service.
Corosync 1.4.2 config File:
compatibility: none
totem {
version: 2
token: 5000
token_retransmits_before_loss_const: 20
join: 1000
consensus: 7500
vsftype: none
max_messages: 20
secauth: off
threads: 0
nodeid: 1
clear_node_high_bit: yes
transport: udpu
interface {
member {
memberaddr: 192.168.100.1
}
member {
memberaddr: 192.168.100.2
}
ringnumber: 0
bindnetaddr: 192.168.100.0
mcastaddr: 226.94.1.1
mcastport: 5405
ttl: 1
}
}
logging {
fileline: off
to_stderr: no
to_logfile: yes
to_syslog: yes
logfile: /var/log/cluster/corosync.log
debug: on
}
}
amf {
mode: disabled
}
Corosync 1.4.2 log messages:
Apr 3 11:32:41 VM1 corosync[1711]: [MAIN ] Corosync Cluster Engine
('1.4.2'): started and ready to provide service.
Apr 3 11:32:41 VM1 corosync[1711]: [MAIN ] Corosync built-in features:
Apr 3 11:32:41 VM1 corosync[1711]: [MAIN ] Successfully read main
configuration file '/etc/corosync/corosync.conf'.
Apr 3 11:32:41 VM1 corosync[1711]: [TOTEM ] Initializing transport
(UDP/IP Unicast).
Apr 3 11:32:41 VM1 corosync[1711]: [TOTEM ] Initializing
transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
Apr 3 11:32:41 VM1 corosync[1711]: [TOTEM ] The network interface
[192.168.100.1] is now up.
Apr 3 11:32:41 VM1 corosync[1711]: [SERV ] Service engine loaded:
corosync extended virtual synchrony service
Apr 3 11:32:41 VM1 corosync[1711]: [SERV ] Service engine loaded:
corosync configuration service
Apr 3 11:32:41 VM1 corosync[1711]: [SERV ] Service engine loaded:
corosync cluster closed process group service v1.01
Apr 3 11:32:41 VM1 corosync[1711]: [SERV ] Service engine loaded:
corosync cluster config database access v1.01
Apr 3 11:32:41 VM1 corosync[1711]: [SERV ] Service engine loaded:
corosync profile loading service
Apr 3 11:32:41 VM1 corosync[1711]: [SERV ] Service engine loaded:
corosync cluster quorum service v0.1
Apr 3 11:32:41 VM1 corosync[1711]: [MAIN ] Compatibility mode set
to none. Using V2 of the synchronization engine.
Apr 3 11:32:41 VM1 corosync[1711]: [TOTEM ] A processor joined or
left the membership and a new membership was formed.
Apr 3 11:32:41 VM1 corosync[1711]: [CPG ] chosen downlist: sender
r(0) ip(192.168.100.1) ; members(old:0 left:0)
Apr 3 11:32:41 VM1 corosync[1711]: [MAIN ] Completed service
synchronization, ready to provide service.
Apr 3 11:33:21 VM1 corosync[1711]: [TOTEM ] A processor joined or
left the membership and a new membership was formed.
Apr 3 11:33:21 VM1 corosync[1711]: [CPG ] chosen downlist: sender
r(0) ip(192.168.100.1) ; members(old:1 left:0)
Apr 3 11:33:21 VM1 corosync[1711]: [MAIN ] Completed service
synchronization, ready to provide service.
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
