Hi Michael,
I don't think there is much you can do at this point to debug the
previous problem. To make it possible to debug in case it happens
again, you can do the following:
- Boot with -k to load kmdb. Or if you have already booted the OS,
log in as root at the console. Type "mdb -K". Once in kmdb,
type :c so you can continue normal operation with kmdb loaded.
- If/When the system hangs again, type Esc+B on the console. Once
you are in kmdb, you can force a coredump and send it to Sun for
analysis.
[1] > 0>rip
[1] > :c
- With earlier versions of ILOM sometimes the console might not
respond even though the host is up. When that happens, simply
reboot the SP and reconnect. In the previous failure you
encountered, it's quite possible that the host was up, but console
was hosed.
Sherry
On Wed, Oct 10, 2007 at 02:06:55PM -0700, Michael wrote:
> I'm a bit new to Solaris, so excuse naive question, but I have a x4500 on
> evaluation and all ssh sessions I had on it become unresponsive when I got
> into work today. NFS seemed to still work and I had some Java processes that
> were still working, but the console via the ILOM was unresponsive as well. I
> tried graceful shutdown via the ILOM and via the button on the front of the
> box. That did not work, so I forced a shutdown form the ILOM, and it came
> back OK. I looked in /var/adm/messages and there was nothing there.
>
> Where should I be looking for evidence of the cause?
>
>
> This message posted from opensolaris.org
> _______________________________________________
> opensolaris-discuss mailing list
> [email protected]
--
Sherry Moore, Solaris Kernel Development http://blogs.sun.com/sherrym
_______________________________________________
opensolaris-discuss mailing list
[email protected]
