31.10.2012 20:55, Robinson, Eric wrote:
> Okay, the two node names are ha09a and ha09b. Starting clean with all
> services turned off.
>
> This is what I get in /var/log/corosync.log on ha09a when I start corosync...
>
> Oct 31 10:22:43 corosync [MAIN ] Corosync Cluster Engine ('1.4.3'): started
> and ready to provide service.
> Oct 31 10:22:43 corosync [MAIN ] Corosync built-in features: nss
> Oct 31 10:22:43 corosync [MAIN ] Successfully read main configuration file
> '/etc/corosync/corosync.conf'.
> Oct 31 10:22:43 corosync [TOTEM ] Initializing transport (UDP/IP Multicast).
> Oct 31 10:22:43 corosync [TOTEM ] Initializing transmit/receive security:
> libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Oct 31 10:22:43 corosync [TOTEM ] Initializing transport (UDP/IP Multicast).
> Oct 31 10:22:43 corosync [TOTEM ] Initializing transmit/receive security:
> libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Set r/w permissions for uid=0, gid=0 on /var/log/corosync.log
> Oct 31 10:22:43 corosync [TOTEM ] The network interface [192.168.10.58] is
> now up.
> Oct 31 10:22:43 corosync [pcmk ] Logging: Initialized pcmk_startup
> Oct 31 10:22:43 corosync [SERV ] Service engine loaded: Pacemaker Cluster
> Manager 1.1.7
> Oct 31 10:22:43 corosync [SERV ] Service engine loaded: corosync extended
> virtual synchrony service
> Oct 31 10:22:43 corosync [SERV ] Service engine loaded: corosync
> configuration service
> Oct 31 10:22:43 corosync [SERV ] Service engine loaded: corosync cluster
> closed process group service v1.01
> Oct 31 10:22:43 corosync [SERV ] Service engine loaded: corosync cluster
> config database access v1.01
> Oct 31 10:22:43 corosync [SERV ] Service engine loaded: corosync profile
> loading service
> Oct 31 10:22:43 corosync [SERV ] Service engine loaded: corosync cluster
> quorum service v0.1
> Oct 31 10:22:43 corosync [MAIN ] Compatibility mode set to whitetank. Using
> V1 and V2 of the synchronization engine.
> Oct 31 10:22:43 corosync [TOTEM ] The network interface [198.51.100.58] is
> now up.
> Oct 31 10:22:44 corosync [TOTEM ] Incrementing problem counter for seqid 1
> iface 198.51.100.58 to [1 of 10]
> Oct 31 10:22:44 corosync [TOTEM ] A processor joined or left the membership
> and a new membership was formed.
> Oct 31 10:22:44 corosync [CPG ] chosen downlist: sender r(0)
> ip(192.168.10.58) r(1) ip(198.51.100.58) ; members(old:0 left:0)
> Oct 31 10:22:44 corosync [MAIN ] Completed service synchronization, ready to
> provide service.
> Oct 31 10:22:44 corosync [TOTEM ] A processor joined or left the membership
> and a new membership was formed.
> Oct 31 10:22:44 corosync [CPG ] chosen downlist: sender r(0)
> ip(192.168.10.58) r(1) ip(198.51.100.58) ; members(old:1 left:0)
> Oct 31 10:22:44 corosync [MAIN ] Completed service synchronization, ready to
> provide service.
> Oct 31 10:22:46 corosync [TOTEM ] ring 1 active with no faults
>
>
> Some things seem to be missing from the log. According to the ClusterLabs
> docs, I should be seeing entries similar to the following, but I am NOT. (The
> following are adapted from the ClusterLabs documentation. They are NOT
> showing up in my logs.)
>
>
> Aug 27 09:05:35 ha09a corosync[1540]: [pcmk ] info: pcmk_startup: CRM:
> Initialized
> Aug 27 09:05:35 ha09a corosync[1540]: [pcmk ] Logging: Initialized
> pcmk_startup
> Aug 27 09:05:35 ha09a corosync[1540]: [pcmk ] info: pcmk_startup: Maximum
> core file size is: 18446744073709551615
> Aug 27 09:05:35 ha09a corosync[1540]: [pcmk ] info: pcmk_startup: Service: 9
> Aug 27 09:05:35 ha09a corosync[1540]: [pcmk ] info: pcmk_startup: Local
> hostname: ha09a
>
>
> One thing that does stand out to me is that we are seeing the following line
> in the log...
>
> Oct 31 10:22:43 corosync [SERV ] Service engine loaded: Pacemaker Cluster
> Manager 1.1.7
>
> ..however we have Pacemaker 1.1.8 installed, not 1.1.7.
>
> Where is that 1.1.7 coming from?
>
> Here is what we have installed...
>
> [root@ha09a log]# rpm -qa|egrep "pacem|coros"
> pacemaker-1.1.8-0.901.eedc0cc.git.el6.x86_64
> pacemaker-cluster-libs-1.1.8-0.901.eedc0cc.git.el6.x86_64
I suspect that version you run (pre-1.1.8,
https://github.com/ClusterLabs/pacemaker/commit/eedc0cc9601d563a38ff3185414694bfbeb7ff76)
actually has problems with corosync1 (plugin-based) setups. I think that
relevant fix was
https://github.com/ClusterLabs/pacemaker/commit/89c817d795da535fca667a848d6b0503a120129a,
which was committed two days later.
Why not try official 1.1.8 which should have all these fixed?
Vladislav
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
