I've identified the problem : in fact, that was due to a process launched via the SERVICE script, but which was not stopped on clusvcadm -s SERVICE (or -d) . Then, on service cman stop, the modprobe -r dlm was successful but at the end of this modprobe -r, the lsmod indicates one user left on cman : cman 136480 1 but without user identification (such as "cman 136480 10 dlm" when cs4 is all active). So the modprobe -r cman was then impossible. Could someone explain to me the link between a process managed in the SERVICE script and the remaining 1 user on cman ? Thanks Alain Moullé >> I have a systematic problem with cman stop on my configuration : >> knowing that there is no service with autostart in >> the cluster.conf, and that I have only one main service >> to be started by : clusvcadm -e SERVICE -m <node_name> >> First test : >> launch CS4 OK >> stop CS4 OK >> no problem >> Second test : >> launch CS4 >> clusvcadm -e SERVICE -m <node_name> >> then >> clusvcadm -d SERVICE >> stop CS4 ... >> in this case, cman stop is systematically FAILED ... >> This is true if both cases where CS4 is started >> on peer node as well as where is it stopped. >> Any clue or track to identify the problem ? -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
