• If you have a problem you cannot solve by yourself, here's what to do:

  Please be sure that you read all documentation and searched mail list archives. If you still can't find a solution you can post questions to the mailing list. Try and start off your email with a simple, clear explanation of what you think is wrong, surprising or unexpected. We know that many of you don't have good English skills. That's OK. Just try and be logically organized, and as clear as you can be, and try and avoid really long sentences or really long paragraphs. Those just make it harder to understand. Logical organization of the information and clarity really helps everyone - including you. It's also good to send your email as plain text and not as HTML. HTML email causes problems for some people, and annoys others. Plain text works great for mailing lists. Please include the following:

  • What OS are you running.
  • What version (distro/kernel).

  • How did you install Heartbeat (tar.gz, rpm, src.rpm or manual installation).

  • What version of Heartbeat did you install?

  • Include your configuration files from both machines. You can omit authkeys. Send them as text/plain attachments.

  • Log files from any machines that were active at the time. If they are small enough, send them as text/plain attachments. If your mail program doesn't let you control the MIME type, then rename them with a .txt suffix so that your mail program gets the hint. Otherwise, if they are really big, zip them up first (and give them a sensible suffix) so the list does not reject them.

  Please don't send "cleaned up" logs. The real logs have more information in them than cleaned up versions. Always include at least a little irrelevant data before and after the events in question so that we know nothing was missed. Please narrate what you did when, preferably with timestamps taken from the logs. Don't edit the logs unless you really have some super-secret high-security reason for doing so. This means you need to attach 5-8 files.

  For heartbeat versions >= 2.1.3, the easiest way to get together all files is to use hb_report. If you still want to go the manual way:

  Include 5 for an R1 cluster with debug output goes into the same file as your normal output and 6 if you're an R1 cluster with debug output going to the same file, 7 if you're running an R2 cluster with debug output going into a single file, and 8 otherwise. For each machine you need to send:

  • ha.cf

  • The output from cibadmin -Ql or haresources (for R1 clusters)

  • normal logs
  • debug logs (perhaps)

  If you want to file a bug report, then you can see the bugzilla information in the ContactUs page for more details.

Linux-HA site built by the Linux-HA crowd. HTML4 / CSS2