On Tuesday 10 August 2010 17:19, Igor Chudov wrote: > Guys, I just sent ha-log, ha.cf, haresources from both machines.
These look like shutdown logs, not startup logs. FWIW here's what mine's like (sanitized): ** secondary ** heartbeat: [8356]: info: Configuration validated. Starting heartbeat 2.1.4 heartbeat: [8356]: info: heartbeat: version 2.1.4 heartbeat: [8356]: info: Heartbeat generation: 1280248031 heartbeat: [8356]: info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth1 heartbeat: [8356]: info: glib: UDP Broadcast heartbeat closed on port 694 interface eth1 - Status: 1 heartbeat: [8356]: info: G_main_add_TriggerHandler: Added signal manual handler heartbeat: [8356]: info: G_main_add_TriggerHandler: Added signal manual handler heartbeat: [8356]: info: G_main_add_SignalHandler: Added signal handler for signal 17 heartbeat: [8356]: info: Local status now set to: 'up' heartbeat: [8356]: info: Link secondary.node:eth1 up. heartbeat: [8356]: info: Link primary.node:eth1 up. heartbeat: [8356]: info: Status update for node primary.node: status up harc[8362]: info: Running /etc/ha.d/rc.d/status status heartbeat: [8356]: info: Comm_now_up(): updating status to active heartbeat: [8356]: info: Local status now set to: 'active' heartbeat: [8356]: info: Status update for node primary.node: status active harc[8379]: info: Running /etc/ha.d/rc.d/status status heartbeat: [8356]: info: local resource transition completed. heartbeat: [8356]: info: Initial resource acquisition complete (T_RESOURCES(us)) heartbeat: [8397]: info: No local resources [/usr/share/heartbeat/ResourceManager listkeys secondary.node] to acquire. heartbeat: [8356]: info: remote resource transition completed. ** primary ** heartbeat: [9736]: info: Configuration validated. Starting heartbeat 2.1.4 heartbeat: [9737]: info: heartbeat: version 2.1.4 heartbeat: [9737]: info: Heartbeat generation: 1280248043 heartbeat: [9737]: info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth1 heartbeat: [9737]: info: glib: UDP Broadcast heartbeat closed on port 694 interface eth1 - Status: 1 heartbeat: [9737]: info: G_main_add_TriggerHandler: Added signal manual handler heartbeat: [9737]: info: G_main_add_TriggerHandler: Added signal manual handler heartbeat: [9737]: info: G_main_add_SignalHandler: Added signal handler for signal 17 heartbeat: [9737]: info: Local status now set to: 'up' heartbeat: [9737]: info: Link secondary.node:eth1 up. heartbeat: [9737]: info: Status update for node secondary.node: status up harc[9743]: info: Running /etc/ha.d/rc.d/status status heartbeat: [9737]: info: Link primary.node:eth1 up. heartbeat: [9737]: info: Comm_now_up(): updating status to active heartbeat: [9737]: info: Local status now set to: 'active' heartbeat: [9737]: info: Status update for node secondary.node: status active harc[9762]: info: Running /etc/ha.d/rc.d/status status heartbeat: [9737]: info: remote resource transition completed. heartbeat: [9737]: info: remote resource transition completed. heartbeat: [9737]: info: Initial resource acquisition complete (T_RESOURCES(us)) heartbeat: [9778]: info: Local Resource acquisition completed. harc[9821]: info: Running /etc/ha.d/rc.d/ip-request-resp ip-request-resp ip-request-resp[9821]: received ip-request-resp drbddisk::raid OK yes ResourceManager[9842]: info: Acquiring resource group: primary.node drbddisk::raid Filesystem::/dev/drbd0::/raid::ext3 1.2.3.4 [...] ResourceManager[9842]: info: Running /etc/ha.d/resource.d/drbddisk raid start kernel: block drbd0: role( Secondary -> Primary ) Filesystem[9913]: INFO: Resource is stopped ResourceManager[9842]: info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /raid ext3 start Filesystem[9994]: INFO: Running start for /dev/drbd0 on /raid kernel: kjournald starting. Commit interval 5 seconds kernel: EXT3 FS on drbd0, internal journal kernel: EXT3-fs: mounted filesystem with ordered data mode. Filesystem[9983]: INFO: Success IPaddr[10062]: INFO: Resource is stopped ResourceManager[9842]: info: Running /etc/ha.d/resource.d/IPaddr 1.2.3.4 start IPaddr[10139]: INFO: Using calculated nic for 1.2.3.4: eth0 IPaddr[10139]: INFO: Using calculated netmask for 1.2.3.4: 255.255.255.0 IPaddr[10139]: INFO: eval ifconfig eth0:0 1.2.3.4 netmask 255.255.255.0 broadcast 1.2.3.255 IPaddr[10122]: INFO: Success Assuming your version of heartbeat does things (and logs them) the same way, that is what you should see happening. I wish I could give you a better advice, but what I'd do at this point is boot both systems with drbd and no heartbeat (I think it should come up as secondary/secondary), boot both systems with heartbeat but no drbd (e.g. with ipaddr only) and see which one works. Dima -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
