Hi all,

I do not know if this is a common problem. I have a virtual machine hosted on Hyper-V that has Fedora 16 installed on it.

After a fresh reboot, I am able to SSH/FTP into this server. However, after about say 3 - 5 hours, the SSH consistently times out. Same goes for FTP as well. Then I would have no choice but to reboot the virtual machine. This is just inefficient.

Currently I have a scheduled reboot for the server to happen during off-hours, but it's not a permanent enough fix for if the server goes down during work hours. Is there any way for me to diagnose what is wrong, and how to fix it?

Thank you for your time and attention.

hi, something not clear here
// after about say 3 - 5 hours, the SSH consistently times out. //
is this mean
1) after 3 or 5 hours you cannot make ssh to the machine
or
2) after 3 or 5 hours your hanging ssh connection disconnect you?


if no 1 . is your machine is dead ?
if no 2 - there is a "keepalive" function in ssh config file you need to enable it

Hi routers,

After 3 to 5 hours, nobody can SSH into the machine anymore. I don't leave SSH connections running for 3 - 5 hours straight (maybe I could try?)

I can access the machine via Hyper-V console, and it works fine (ie. listing files, using vim), and seems pretty responsive. Trying to SSH into that server then however, always causes timeouts (ie. via PuTTy). Same for FTP. Websites hosted on this server become inaccessible as well.

Thanks.

ok my suggestion, once you can log in,
try update all the software and kernel, also dont forget to check grub.conf
then reboot the server, once up again the check the running kernel make sure its latest,
also can look at the log file

if happen again, i think you better consult the server support, could be hardware issue eg NIC
because normaly if company sell vm, there is more than one NIC is used, then possible
the NIC use for your vm got problem

if in doubt why can login to Hyper-V but not vm, its because its managed via host system
use diffrent NIC

possibility is there

Hi routers

Sorry was away for the weekend. What should I look for specifically in grub.conf?

How do I update the softwares and kernels? If possible I do not want to touch stuff that does not need to be touched.

Are there any other ways I can test for the hardware problems?

I'll need a little clarification, I don't quite understand what I should be doing at this point.

Thanks.

I also wonder if the problem might be because I didn't install Linux Integration Services?

It might be responsible for faulty VM connections.

updating software and kernel is compulsory , without that you will face security issue
but for me fedora is not for production in mind,.

to update the system just execute cmd below

to check invidual file for update
preproceed
or
once update you need to reboot
then login check with following command

more will come, just you need to learn it

Hi sorry for the late reply.

I rebuilt a new VM, this time installing CentOS 6.2 as it is compatible with Linux Integration Services.

So far I have no problems - no more intermittent dying every day.

Thanks