Le Tuesday 25 October 2011 23:20:34 Joey L, vous avez écrit :
[...]
Hi !
> and my config is this :
> root@debby1:~# cat /etc/corosync/corosync.conf
> ## generated by drbd-gui 0.9.9
>
> aisexec {
> user: root
> group: root
> }
>
> corosync {
> user: root
> group: root
> }
>
> amf {
> mode: disabled
> }
>
> logging {
> to_stderr: yes
> debug: off
> timestamp: on
> to_file: no
> to_syslog: yes
> syslog_facility: daemon
> }
>
> totem {
> version: 2
> token: 3000
> token_retransmits_before_loss_const: 10
> join: 60
> consensus: 4000
> vsftype: none
> max_messages: 20
> clear_node_high_bit: yes
> secauth: on
> threads: 0
> # nodeid: 1234
> rrp_mode: active
>
> interface {
> ringnumber: 0
> bindnetaddr: 192.168.2.0
> mcastaddr: 226.94.1.1
> mcastport: 5405
> }
>
> interface {
> ringnumber: 1
> bindnetaddr: 192.168.2.0
> mcastaddr: 226.94.1.2
> mcastport: 5405
> }
> }
>
> service {
> ver: 0
> name: pacemaker
> use_mgmtd: no
> }
Here is mine :
aisexec {
user: root
group: root
}
corosync {
user: root
group: root
}
amf {
mode: disabled
}
logging {
to_stderr: yes
debug: off
timestamp: on
to_logfile: no
to_syslog: yes
syslog_facility: daemon
}
totem {
version: 2
token: 3000
token_retransmits_before_loss_const: 10
join: 60
consensus: 4000
vsftype: none
max_messages: 20
clear_node_high_bit: yes
secauth: on
threads: 0
# nodeid: 1234
rrp_mode: active
interface {
ringnumber: 0
bindnetaddr: 10.100.0.0
mcastaddr: 225.0.0.4
mcastport: 5405
}
}
service {
ver: 0
name: pacemaker
use_mgmtd: no
}
I've just created one interface.
I think two rings is usefull when you have multiple networks interfaces
(public/private...)
[...]
>
> root@debby1:~#
>
>
> 3. both nodes are in a wait... status.
> I get this error when i log at the log of my node:
>
> Oct 25 13:58:27 debby1 openhpid: ERROR: (init.c, 76, OpenHPI is not
> configured. See openhpi.conf file.)
> Oct 25 13:58:27 debby1 openhpid: ERROR: (openhpid.cpp, 270, There was
> an error initializing OpenHPI)
This is not about the cluster.
> Oct 25 14:15:38 debby1 crmd: [21949]: ERROR: crm_timer_popped:
> Election Timeout (I_ELECTION_DC) just popped!
> Oct 25 14:18:38 debby1 crmd: [21949]: ERROR: crm_timer_popped:
> Integration Timer (I_INTEGRATED) just popped!
> Oct 25 14:21:38 debby1 crmd: [21949]: ERROR: crm_timer_popped:
> Integration Timer (I_INTEGRATED) just popped!
> Oct 25 14:24:38 debby1 crmd: [21949]: ERROR: crm_timer_popped:
> Integration Timer (I_INTEGRATED) just popped!
> Oct 25 14:27:38 debby1 crmd: [21949]: ERROR: crm_timer_popped:
> Integration Timer (I_INTEGRATED) just popped!
> Oct 25 14:30:38 debby1 crmd: [21949]: ERROR: crm_timer_popped:
> Integration Timer (I_INTEGRATED) just popped!
> Oct 25 14:33:38 debby1 crmd: [21949]: ERROR: crm_timer_popped:
> Integration Timer (I_INTEGRATED) just popped!
[...]
> Timeout (I_ELECTION_DC) just popped!
This is not good...
It seems that your nodes don't see each over, via the multicast canal.
[...]
> 4. i can not get the nodes out of "wait.." status and in the folder
> options - the service folder - i can not create a service or group.
>
> I am so close - but yet so far - I rebuilt new boxes and configured
> different ip address.
> debby1 - 192.168.2.121 and debby2 - 192.168.2.122
>
> thanks
> mjh
You're near, be persistant !
Attachment:
signature.asc
Description: This is a digitally signed message part.