Turns out the pm_tick delay panic string was kind of self-induced. The system had halted for an unrelated reason and when we said "go" at the OK prompt, it paniced with the panic string indicating the heartbeats were out of sync. This makes sense becuase it had been at the OK prompt. Thanks to David Foster and Robert Harris for their replies. > Hello, > > We are in the process of learning about Sun Cluster 3.0. We currently > have two E-250's clustered together, sharing an A-5000 disk array. > > For no apparent reason I can find, we are seeing the following panic: > > Aborting node because pm_tick delay of xxxxx ms exceeds yyyyy ms > > > Anyone have any ideas about how to prevent this from happening? > > Thanks in advance. > > --Joe Walker > > _______________________________________________ > sunmanagers mailing list > sunmanagers@sunmanagers.org > http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Tue Jul 31 12:28:27 2001
This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:25:00 EDT