Heartbeat error: Cannot write to media pipe 0

Today I tested a heartbeat setup. Everything went fine until…

I performed a reboot of one of the hosts. The host came back and started to communicate with the other heartbeat. At that moment heartbeat started to generate ERROR messages. The load of heartbeat and the load of syslog increased because of the amount of error messages and my /var/log/messages file grew quite a bit.

When the problem started heartbeat was printing lots of information in the log files, but after some time only this messages appeared in the logs.


Jul 17 16:27:33 heartbeat: [2893]: ERROR: Cannot write to media pipe 0: Resource temporarily unavailable
Jul 17 16:27:33 heartbeat: [2893]: ERROR: Shutting down.
Jul 17 16:27:33 heartbeat: [2893]: ERROR: Message hist queue is filling up (200 messages in queue)

20 minutes after the first occurrence of this message the master heartbeat process killed itself. During this time it generated over 30000 times the above error.

The guys of #linux-ha helped me with this error and explained that it is caused by the serial link. The messages sent over the cable didn’t arrive in time.
The fix for it is easy, increase the baud in your ha config file.

My baud was first configured at 9600 and increasing it to 19200 fixed this error.

This entry was posted on Tuesday, July 17th, 2007 at 19:23 and is filed under Linux SysAdmin. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply