Hi, in order to test the cluster setup, I've setup a cloned environment in vmware simulating the two cluster nodes.
When firing up heartbeat, the following (among others) lines are logged: Sep 29 13:20:28 storage1 heartbeat: [22635]: WARN: glib: TTY write timeout on [/dev/ttyS0] (no connection or bad cable? [see documentation]) Sep 29 13:20:28 storage1 heartbeat: [22635]: info: glib: See http://linux-ha.org/FAQ#TTYtimeout for details Sep 29 13:20:28 storage1 heartbeat: base64_to_binary: invalid input [>]! Sep 29 13:20:28 storage1 heartbeat: [22631]: WARN: string2msg_ll: node [storage2] failed authentication Sep 29 13:20:29 storage2 heartbeat: [16739]: WARN: string2msg_ll: node [storage1] failed authentication Sep 29 13:20:30 storage2 heartbeat: [16739]: WARN: string2msg_ll: node [storage1] failed authentication I assume there's something wrong with the setup of the virtualized serial port interfaces. One box has a serial port using a named pipe as server end, the other box uses the same named pipe as client end in vmware setup. Serial communication seems to work. I verified this by using "cat < /dev/ttyS0" on one node and "echo 'test' > /dev/ttyS0" on the other. Is there a more verbose test to check serial connectivity? Anyone running heartbeat without these messages in a vmware environment? Guest and Host OS: Ubuntu 04.08.1 Heartbeat: 2.1.3 (using the original Ubuntu packages) VMware: 6.0.3 Regards, Stefan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
