> > Here are the messages in the logs on cluster2 around the time of the > > shutdown. Any help on how to prevent this lockup from happening (or > > pointers on what I'm doing wrong) would be appreciated! > > > > actually, this looks similar to a bug that I'm fixing right now. > (Rebooting the Master lock server when also having gfs mounts on the > same node is causing sockets to get mixed up. > https://bugzilla.redhat.com/beta/show_bug.cgi?id=148029 ) > > Just looking at the code, it seems to be present in 6.0 as well. > bummer. I'll get that fixed. Thanks Michael! So in the meantime, I could probably avoid this problem by electing one of the non-mounters as the master lock server? -- ---------------------------------- Marc Swanson, Software Engineer Sonitrol Communications Corp. Hartford, CT Email: mswanson@xxxxxxxxxxxx Phone: (860) 616-7036 Pager: (860) 948-6713 Cell: (603) 512-1267 Fax: (860) 616-7589 ----------------------------------
