On Tue, May 22, 2007 at 01:47:59PM -0400, Robert Gil wrote: > Nevermind. This was all due to incorrect time on a couple of the nodes. > One node was in the past, and one was in the future. > > It may be beneficial to fix this as it DOES cause a kernel panic. Maybe > add some kind of time sync check to disallow a node from joining when > its time isn't within X of the cluster. That sounds reasonable, but incorrect timings shouldn't affect ccsd or rgmanager *shrug* I'll see if I can spot anything in rgmanager which would explain it, but I don't expect anything to jump out at me. -- Lon -- Lon Hohberger - Software Engineer - Red Hat, Inc. -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
