Need to understand the 'corosync' debug logs in RHEL6 cluster with pacemaker.

Solution Unverified - Updated -

Issue

  • Need to understand the 'corosync' debug logs in RHEL6 cluster with pacemaker.
  • What does below logs tell us? Why are they generated in the first place? Could these logs be removed?
2014-03-04T15:01:00+01:00 hostname [CONFDB] lib_init_fn: conn=0x96ae640
2014-03-04T15:01:00+01:00 hostname [CONFDB] exit_fn for conn=0x96ae640
2014-03-04T15:01:50+01:00 hostname [CONFDB] lib_init_fn: conn=0x96ae640
2014-03-04T15:01:50+01:00 hostname [CONFDB] exit_fn for conn=0x96ae640
2014-03-04T15:02:40+01:00 hostname [CONFDB] lib_init_fn: conn=0x96ae640

Environment

  • Red Hat Enterprise Linux Server 6 (with the High Availability Add on).

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.