[Pacemaker] errors in corosync.log
Shravan Mishra
shravan.mishra at gmail.com
Tue Jan 19 15:59:10 UTC 2010
cibadmin 1.0.5 for OpenAIS and Heartbeat (Build:
9e9faaab40f3f97e3c0d623e4a4c47ed83fa1601)
-Shravan
On Tue, Jan 19, 2010 at 8:29 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
> On Sat, Jan 16, 2010 at 9:20 PM, Shravan Mishra
> <shravan.mishra at gmail.com> wrote:
>> Hi Guys,
>>
>> I'm running the following version of pacemaker and corosync
>> corosync=1.1.1-1-2
>> pacemaker=1.0.9-2-1
>
> That pacemaker version doesn't exist.
> What does cibadmin --version say?
>
> And are you sure about the corosync version, it doesn't look right either.
>
>>
>> Every thing had been running fine for quite some time now but then I
>> started seeing following errors in the corosync logs,
>>
>>
>> =========
>> Jan 16 15:08:39 corosync [TOTEM ] Received message has invalid
>> digest... ignoring.
>> Jan 16 15:08:39 corosync [TOTEM ] Invalid packet data
>> Jan 16 15:08:39 corosync [TOTEM ] Received message has invalid
>> digest... ignoring.
>> Jan 16 15:08:39 corosync [TOTEM ] Invalid packet data
>> Jan 16 15:08:39 corosync [TOTEM ] Received message has invalid
>> digest... ignoring.
>> Jan 16 15:08:39 corosync [TOTEM ] Invalid packet data
>> ========
>>
>> I can perform all the crm shell commands and what not but it's
>> troubling that the above is happening.
>>
>> My crm_mon output looks good.
>>
>>
>> I also checked the authkey and did md5sum on both it's same.
>>
>> Then I stopped corosync and regenerated the authkey with
>> corosync-keygen and copied it to the the other machine but I still get
>> the above message in the corosync log.
>>
>> Is there anything other authkey that I should look into ?
>>
>>
>> corosync.conf
>>
>> ============
>>
>> # Please read the corosync.conf.5 manual page
>> compatibility: whitetank
>>
>> totem {
>> version: 2
>> token: 3000
>> token_retransmits_before_loss_const: 10
>> join: 60
>> consensus: 1500
>> vsftype: none
>> max_messages: 20
>> clear_node_high_bit: yes
>> secauth: on
>> threads: 0
>> rrp_mode: passive
>>
>> interface {
>> ringnumber: 0
>> bindnetaddr: 192.168.2.0
>> #mcastaddr: 226.94.1.1
>> broadcast: yes
>> mcastport: 5405
>> }
>> interface {
>> ringnumber: 1
>> bindnetaddr: 172.20.20.0
>> #mcastaddr: 226.94.1.1
>> broadcast: yes
>> mcastport: 5405
>> }
>> }
>>
>>
>> logging {
>> fileline: off
>> to_stderr: yes
>> to_logfile: yes
>> to_syslog: yes
>> logfile: /tmp/corosync.log
>> debug: off
>> timestamp: on
>> logger_subsys {
>> subsys: AMF
>> debug: off
>> }
>> }
>>
>> service {
>> name: pacemaker
>> ver: 0
>> }
>>
>> aisexec {
>> user:root
>> group: root
>> }
>>
>> amf {
>> mode: disabled
>> }
>>
>>
>> ===============
>>
>>
>> Thanks
>> Shravan
>>
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
More information about the Pacemaker
mailing list