This Question is Answered
Bolgard schrieb:
Well, what I possibly could have done wrong with the RAM, I have done wrong now that I think of it.
The harder a machine is using it's RAM, the sooner you will see errors.Well, what I possibly could have done wrong with the RAM, I have done wrong now that I think of it.
- I added 2 GB RAM (not certified by FS since they were alot cheeper, though I get a warning in BIOS about that. Figured it wouldn't matter that much, I have had several different RAM types in workstations and have always worked fine)
* So there's totally 3 GB of RAM in 3 slots, so they're not grouper in pairs either.
Kingston says, it's not recommanded (performance deal), but should 
work. * And I'm not sure the added 2 GB is ECC (though I guess it has to be if the motherboards supports ECC?)
Quite sure, that the server should at least throw out a BIG warning, but most probably it has to be ECC.So we've found the problem there, don't you think?
I've seen so much problems with RAM, that I suppose, it is the source. But you never know.So try with 1 GB or spend lots of bucks for original RAM or some bucks for compatible. I (nearly) newer had problems with Kingston RAM and they will at least try to support you. Dunno where you live, but I found 2x2 GBytes KFJ-E50/4G for US $112.00 at the Kingston shop.
All of mine are running vmware tools. Whether I connect using VirtualCenter or directly to the machine via the VIclient it will not connect. I have tried restarting the management agents.
I was previously able to connect via the RCLI and also using VIclient or VirtualCenter, but now it has deteriorated past being able to do anything with it at all. Very impressive that the virtual machines are absolutely 100% fine still.
You should find the logs for each machine, if no other way then at least by using the datastore browser and browsing to the directory in which that machines disk files are. There you will find logs for that machine. My VMs weren't importe. A few may have been clones of others but I don't think that's relevant. The others are clearly running fine whereas this one always complains. We blame the application that runs on there but the developer gets very offended when we do. Hopefully he's not reading this right now.
I was previously able to connect via the RCLI and also using VIclient or VirtualCenter, but now it has deteriorated past being able to do anything with it at all. Very impressive that the virtual machines are absolutely 100% fine still.
You should find the logs for each machine, if no other way then at least by using the datastore browser and browsing to the directory in which that machines disk files are. There you will find logs for that machine. My VMs weren't importe. A few may have been clones of others but I don't think that's relevant. The others are clearly running fine whereas this one always complains. We blame the application that runs on there but the developer gets very offended when we do. Hopefully he's not reading this right now.
Don't blame the poor developer! 
Even if it is a memory leak in his application, ESXi should not expand that VMs RAM beyond it's maximum limit anyway. And it should most definitely not lead to this problem with the host.
All my VMs are running perfectly fine aswell. How long did it take before you completely lost connection to the ESXi? I'm guessing I've been rebooting ESXi too frequently to have reached that "state".
I'll check my VMs logs as soon as I can access a PC with VIC again (about an hour or so). If I too find events about memory that would tell us it might be a specific VM which is causing our problem...
I doubt the problem is a faulty RAM module as we both have VMs running fine... eventually a faulty RAM area would be used by a VM, and we would have seen some issues at that level aswell.
EDIT: I can not download any logs for the VMs from the server, "failed to connect to nfc server". I guess this is related to the other management issues and the current state of the ESXi. Is there no other way to view the logs? From what I can see by looking at the statistics for each VM they all seem fine, memory is not used to it's limits. Maybe it ain't the VM that is causing it after all..
Even if it is a memory leak in his application, ESXi should not expand that VMs RAM beyond it's maximum limit anyway. And it should most definitely not lead to this problem with the host.All my VMs are running perfectly fine aswell. How long did it take before you completely lost connection to the ESXi? I'm guessing I've been rebooting ESXi too frequently to have reached that "state".
I'll check my VMs logs as soon as I can access a PC with VIC again (about an hour or so). If I too find events about memory that would tell us it might be a specific VM which is causing our problem...
I doubt the problem is a faulty RAM module as we both have VMs running fine... eventually a faulty RAM area would be used by a VM, and we would have seen some issues at that level aswell.
EDIT: I can not download any logs for the VMs from the server, "failed to connect to nfc server". I guess this is related to the other management issues and the current state of the ESXi. Is there no other way to view the logs? From what I can see by looking at the statistics for each VM they all seem fine, memory is not used to it's limits. Maybe it ain't the VM that is causing it after all..