Aside from the previous SNAPDUMP suggestion, what about issuing "CP VMDUMP" from the comatose Linux server? And investigating use of the public-domain/free TRACK utility currently available at: http://vm.marist.edu/track/code.html
Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Rempel, Horst" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <[email protected]> 08/07/2008 05:49 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Linux sles9 felt in coma Hello, one of our Linux sles9 SP4 DB2 databaseservers running under z/VM 5.3.0 RSU0801 felt yesterday afternoon in a kind of coma. The linux stopped running. The putty-session got an timeout. I was no longer able to ping. The processor for this lpar was only 20% busy for other linux guests at this time. After that I tried to logon directly to the green screen. But I only got a black screen with LOGON LX004 at the top. The ind user lx004 shows no I/Os, no cpu consumtion. The performance toolkit displayed only zeros for this LX004. After force/xautolog LX004 everything worked fine again. Looking in the linux logs gave no hint what lead to the coma situation. There is enough space free in the filesystems. I have no idea what happened yesterday. Has anybody an idea ? What can I do if the situation come back again ? This mail is crossposted to [EMAIL PROTECTED] and [email protected] kind regards Horst Rempel The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
