• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Issue with DRS Resource Settings?

R

RiDDLeRThC

2[H]4U
2FA
Joined
Jun 13, 2002
Messages
3,963
I think the cause of this issue was during a failed migration of a Virtual Machine. I can't seem to get this error to go away for the life of me. I haven't tried rebooting because of not having a downtime window, hoping it can be fixed without a reboot.

vcenter_error.jpg


Anyone else seen this before?
 
How to I access the host logs? Are you referring to the Tasks & Events tab? nothing useful in there as the error from a few days ago has already rolled off.
 
Kill DRS and then reenable will do it for sure, I'd think.

host logs will actually be on the host - in the /var/log/vmware/ directory.

edit2: Make a production2 pool, same as production, move everything to it, remove production?
 
I removed the DRS and re-enabled it, it removed all resource pools. When I re-enabled it the ESX02 box it still reporting the error.
 
esx 3.5, right?
log onto the box, do the following:
service vmware-vpxa stop
service mgmt-vmware restart

esxupdate -l query - note the name of the VPXA agent in the "new packages" section at the end.
rpm -e VPXA_PACKAGE (from above)

in VC: right click, disconnect.

Watch /var/log/vmware/hostd.log for BEGIN SERVICES
right click -> connect in VC.
 
One thing I noticed when I removed DRS is an HA error came up as well so i went ahead and disabled them both and i'm waiting for that to process. been sitting here for a about two minutes now.

Once this finishes I will do the steps outlined above.

yes its ESX 3.5
 
yeah its not a happy server right now. An error occurred while communicating with the remote host when I attempted to unconfigure HA.

It was showing not responding, disconnected the host, attempted to reconnect and its unable to contact the host now.

Attempting to SSH into the box now and its just sitting there with its prompt, no logon box yet.

VM's are still up on that host right now.
 
So I'm at the office, a wonderful purple screen has greeted me. YAY

I'm just going to reboot it but i will give anyone a chance to chime in first, not sure if anything useful is on this screen

21-18-27.nbEyeEnc_0_CAMERA.jpg


esx02_crash.jpg
 
core dump

Time to reboot that host. When it comes back up examine the logs.

/var/log/messages
/var/log/vmkernel

Should give you a good place to start.
 
I will look over the logs tomorrow.

After the reboot everything started working HA DRS enabled without a problem. VM's auto booted back up and all is working, was able to VMotion from ESX02 (problem host) to ESX01 to load balance without issue.

Odd
 
Probably could have fixed it with a restart of the management agents. I've seen similar other things when they get out of sync. Usually you can do that without affecting the VMs.
 
Wow. Now. That was unrecoverable. ESX itself had a panic there.

Need Iopoetve to look at this one. The panic appears to be in vmnix_idle thread after a heartbeat failure; that shouldn't happen.

P.S. - Nice Tails plush. ;) I used Beanie Babies for one rack installation.
 
Last edited:
NetJunkie said:
Probably could have fixed it with a restart of the management agents. I've seen similar other things when they get out of sync. Usually you can do that without affecting the VMs.
Click to expand...

mebbe - its' always fixed by rebuilding the vpxa.conf file, which is what I was having him do... That SO should not have happened. What kind of system / which update you on?
 
SpaceHonkey said:
core dump

Time to reboot that host. When it comes back up examine the logs.

/var/log/messages
/var/log/vmkernel

Should give you a good place to start.
Click to expand...

This

Also, look in /root/old_cores or /root for a vmkcore file - I need that. I'll crack it open and figure out what's up.
 
System is a Dell PowerEdge 2950 III running ESX 3.5.0 123630

I have no vmkcore file in /root i do have a vmkernel-zdump file

I have no /old_cores folder at all.
 
ok, that's it - it already zipped it. Next time you run a vm-support it'd move it to old_cores.

upload that somewhere I can get it - I'll crack it at work today :)
 
Ok, I can tell you that getting to U4 will help, as the issue is a console memory starvation.
In addition, crank the COS ram to 800 (the max)
Lastly, if you ever have the issue again, let me know, and there's a final workaround but it's a bit more one-offish.
 
Thanks, i will make that change this weekend.

I havent tried U4 yet but once I get some spare hardware i will play with it.
 
You must log in or register to reply here.
Back
Top