[5928] in Release_7.7_team
Why would Athena networking die when its virtual image is suspended a while?
daemon@ATHENA.MIT.EDU (William Cattey)
Thu Mar 13 16:11:08 2008
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3FC1C597-9E85-4B58-8D84-E0B11A1647D7@mit.edu>
Cc: vmware-release@mit.edu, "Michael R. Gettes" <gettes@mit.edu>
Content-Transfer-Encoding: 7bit
From: William Cattey <wdc@MIT.EDU>
Date: Thu, 13 Mar 2008 16:09:51 -0400
To: release-team@mit.edu
X-Spam-Flag: NO
X-Spam-Score: 0.00
I'm gonna start off asking this question to Release Team, and then
over time converge on the best place to ask such questions.
Alex Prengel and I are experimenting with Athena in a VMware image.
Yesterday he brought a problem to me that I have reproduced myself:
Repeat by:
Start Athena VMware image.
Log in.
Suspend image.
Let sit over night.
Resume image.
Actual behavior:
The network is down.
AFS is dead.
A little while later the panel disappears with the helpful message,
"Killed"
in the console window.
Expected behavior:
Suspend and resume a few minutes later gives a fully functioning
Athena machine,
picking up where I left off.
I was able to recover by:
su
/etc/sysconfig/network-scripts/ifdown eth0
/etc/sysconfig/network-scripts/ifup eth0
/etc/init.d/openafs stop
/etc/init.d/openafs start
But since panel had died I also had to log out and log back in.
----
Might this be an interaction with if-plugd?
I'm going to test to see if this is an RHEL 4 issue by doing an RHEL
4 install and repeating the test (first without AFS, then with AFS.)
I'd be grateful for conjectures as to what might be happening.
-Bill
----
William Cattey
Linux Platform Coordinator
MIT Information Services & Technology
N42-040M, 617-253-0140, wdc@mit.edu
http://web.mit.edu/wdc/www/
