Wireshark with corosync/openais patch is quite useful for experts like you, who knows the internal of corosync. (It tells too detail so it is not useful for non-expert like me. sigh.)
Masatake YAMATO > I'm always looking for ways to make debugging/diagnosing corosync easier > since it's notoriously difficult. I've always just ignored the messages in > the subject line; they seem more or less equivalent to "something happened". > (The length of corosync messages tend to be inversely proportional to their > usefulness.) > > Is there some information we could put in those messages to make them > useful? I was recently looking at ring id's in my app, and found it would > be helpful to correlate with what appeared in /var/log/messages, but there > are no ring id's there. Would this message or another be a sensible place > to put a ring id? > > Dave > > _______________________________________________ > Openais mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/openais _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
