Akhilesh Mritunjai wrote: > Hi > > Couple of thoughts to proceed: > > 1. Boot with kmdb attached on system console (serial/local). When this > happens, F1-A into the debugger and do some looking around. When you're at > it, also take a crash dump/stacktrace for others to take a peek. Here's the > guide: > > http://docs.sun.com/app/docs/doc/816-5041/chp-kmdb?a=view
Thanks, so -k and F1-A. I shall try this when I next go to the datacenter. > 4. Upgrade from snv_40, the debugging has pretty good chance of turning up > something that might have been fixed many moons ago. > We already tried snv_40, 60b and 77b. They all go down. Currently trying Solaris 9, but it is not easy to get an old version to go on relatively new hardware. After that we were pondering Linux in a Solaris Zone, if there is no way for Solaris to handle a MySQL Cluster. Lund -- Jorgen Lundman | <[EMAIL PROTECTED]> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home) _______________________________________________ opensolaris-discuss mailing list [email protected]
