[ClusterLabs] wireshark cannot recognize corosync packets

[cys]

corosync.conf and debug logs are in attachment.

And two messages from kernel:

2017-03-14 11:37:20.097233 - info  e1000: eth0 NIC Link is Down

2017-03-14 11:44:41.032121 - info  e1000: eth0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX


Thanks.


On 2017/3/15 16:29, Jan Friesse wrote:
>> Yesterday I found corosync took almost one hour to form a cluster(a
>> failed node came back online).
>
> This for sure shouldn't happen (at least with default timeout settings).
>
>>
>> So I captured some corosync packets, and opened the pcap file in 
>> wireshark.
>>
>> But wireshark only displayed raw udp, no totem.
>>
>> Wireshark version is 2.2.5. I'm sure it supports corosync totem.
>>
>> corosync is 2.4.0.
>
> Wireshark has corosync dissector, but only for version 1.x. 2.x is not 
> supported yet.
>
>>
>> And if corosync takes too long to form a cluster, how to diagnose it?
>>
>> I read the logs, but could not figure it out.
>
> Logs, specially when debug is enabled, has usually enough info. Can 
> paste your config + logs?
>
> Regards,
>   Honza
>
>>
>> Thanks.
>>
>>
>>
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org
>> http://lists.clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
compatibility: whitetank
quorum {
	provider: corosync_votequorum
	two_node: 0
}

totem {
	version: 2
	token: 10000
	vsftype: none
	clear_node_high_bit: yes
	rrp_mode: none
	secauth: off
	transport: udpu
	interface {
		ringnumber: 0
		bindnetaddr: 200.201.162.53
		mcastport: 5405
	}

}

logging {
	fileline: off
	to_stderr: no
	to_logfile: yes
	logfile: /var/log/cluster/corosync.log
	to_syslog: yes
	syslog_facility: daemon
	syslog_priority: info
	debug: on
	function_name: on
	timestamp: on
	logger_subsys {
		subsys: AMF
		debug: off
		tags: enter|leave|trace1|trace2|trace3|trace4|trace6
	}

}

amf {
	mode: disabled
}

aisexec {
	user: root
	group: root
}

nodelist {
	node {
		ring0_addr: 200.201.162.52
		nodeid: 1
	}

	node {
		ring0_addr: 200.201.162.53
		nodeid: 2
	}

	node {
		ring0_addr: 200.201.162.54
		nodeid: 3
	}

}

-------------- next part --------------
A non-text attachment was scrubbed...
Name: corosync.log.gz
Type: application/gzip
Size: 970856 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20170316/5d10f698/attachment-0001.gz>