On 05/02/2010 18:04, Corrado Romano wrote: > Hello, > > In a Sun Cluster 3.2 I have the following behavior: > - if I enable the whole resource group sudo scswitch -Z -g<group name> > everything is correct > > > - if I enable the resources one by one (e.g. resource rs1) with the > following two commands in sequence: > > scswitch -e -j rs1 > the resource starts correctly (normal messages in /var/adm/messages and no > errors) but I get this output: > [i]scswitch: resource group failed to start on chosen node; it may end up > failing over to other node(s)[/i].No errors in the /var/adm/messages > > clrs monitor rs1 > the monitor starts correctly (normal messages in /var/adm/messages and no > errors) but I get this output: > [i]resource group failed to start on chosen node; it may end up failing over > to other node(s)[/i] > > Does somebody know what it can be the reason. I see this behavior for the > first time after working with other 5 clusters 3.2 which behaved normally > > Thx > Corrado > it might be that you don't have a proper dependencies set-up between resources and when you bring entire RG you're lucky and when you do it one-by-one you are doing it in wrong order (but lack of dependencies would be a real issue and not the order of commands you issue). Without more details it is hard to say if it is the case or if it is something else.
-- Robert Milkowski http://milek.blogspot.com
