On Fri, Apr 25, 2008 at 6:14 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hello list, > > I have an ordered and collocated group that consists of the following > elements that startup in order: > Resource Group: GROUPS_KNWORKS_mail > drbddisk_knworks_mail (heartbeat:drbddisk): Started asknmapr01 > drbddisk_axigenbin (heartbeat:drbddisk): Started asknmapr01 > ip_knworks_mail (heartbeat::ocf:IPaddr2): Started asknmapr01 > fs_knworks_mail (heartbeat::ocf:Filesystem): Started asknmapr01 > fs_axigen_bin (heartbeat::ocf:Filesystem): Started asknmapr01 > ip_knworks_mail_external (heartbeat::ocf:IPaddr2): Started > asknmapr01 > axigen_initscript (lsb:axigen): Started asknmapr01 > axigenfilters_initscript (lsb:axigenfilters): Started asknmapr01 > > whenever I failover/migrate the group between nodes, everything works just > as expected, however the 2 bottom LSB scripts never start. they just stay > in "stopped" mode until I run the following commands: > > for x in asknmapr01 asknmapr02; do crm_resource -C -r > axigenfilters_initscript -H $x; done > for x in asknmapr01 asknmapr02; do crm_resource -C -r axigen_initscript -H > $x; done > > These 2 command run cleanup for both scripts, on both nodes. after I run > them the scripts start fine without any action from me. upon migration > again, the same thing occurs. I have to "cleanup" the scripts once again to > get them to run. > > Any ideas would be very appreciated.
At a guess, one of the earlier scripts is saying "i've started" before it really has (which is 100% broken) and the failing script(s) need the service which isn't 100% started. But without logs or anything its hard to say _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
