Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Trent, Thanks for the help. I really appreciate the response. I've brought both nodes offline then tried the following scenarios: Bring HA1 online, keep HA2 offline Bring HA1 & HA2 online Upon bringing HA2 back online while keeping HA1 online I get the following in syslog(nothing else catches my eye as a problem): Dec 6 09:43:16 ha1 pengine: [16124]: WARN: unpack_rsc_op: Processing failed op fs_mysql_start_0 on ha1: unknown error (1) Dec 6 09:43:16 ha1 pengine: [16124]: WARN: common_apply_stickiness: Forcing fs_mysql away from ha1 after 1000000 failures (max=1000000) Dec 6 09:43:16 ha1 pengine: [16124]: notice: RecurringOp: Start recurring monitor (5s) for ip1 on ha1 Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Leave resource fs_mysql#011(Stopped) Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Leave resource mysql#011(Stopped) Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Start ip1#011(ha1) Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Start ip1arp#011(ha1) Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Start fs_webfs#011(ha1) Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Start apache2#011(ha1) Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Leave resource drbd_mysql:0#011(Master ha1) Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Leave resource drbd_mysql:1#011(Stopped) Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Leave resource drbd_webfs:0#011(Master ha1) Dec 6 09:43:16 ha1 pengine: [16124]: notice: LogActions: Leave resource drbd_webfs:1#011(Stopped) The rest is posted here: http://173.255.238.111/log I'm seeing that there is clearly a problem but I don't know where to go from here. I am seriously considering wiping my filesystem and continuing from that point. Would that be more effecient? Thanks again for the help. On Mon, Dec 6, 2010 at 4:14 AM, Trent Lloyd <lathiat at bur.st> wrote: > Hi Jeffrey, > > > On 06/12/2010, at 12:43 AM, Jeffrey Taylor wrote: > > Here is the output from crm_mon upon boot: > > Failed actions: > > fs_mysql_start_0 (node=ha2, call=26, rc=1, status=complete): unknown > error > fs_mysql_start_0 (node=ha1, call=10, rc=1, status=complete): unknown > error > > There are some blatant errors, but I'm at a loss after trying several > techniques covered online. Any help would be greatly appreciated. Thank you. > > > What you really need to do is analyze the logs to see exactly what the > "unknown" error is - and is this error still happening? Should be in the > heartbeat logs and/or syslog > > > If you can't find the MySQL start error there - if neither of the nods are > online now, bring 1 online manually (dont forget filesystems etc) and see if > MySQL starts - you can check the MySQL error log which is called > 'hostname.err' and found in the data directory. > > Regards, > Trent > > > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20101206/68d84e92/attachment.htm>