Just upgraded from ESX4.0 to 4.0 update 2 (build 261974). everything looks like it went OK but when i try to power on the VMs after the update i get an "insufficient resources" error displayed on screen in vSphere.
anyone any ideas? the HDD is fine with 295GB free capacity according to vSphere. I've also rebooted the server but that hasn't helped.
Sounds good. Please let us know how this turns out!
If you found this at all helpful please award points by using the correct or helpful buttons! Thanks!
Sounds like an HA configuration issue.
How did you configure HA (failover capacity)? Did you already try to run a "Reconfigure for HA" on the hosts?
André
Is this an individual host or part of a cluster?
If you found this at all helpful please award points by using the correct or helpful buttons! Thanks!
i didn't.
our set up is one ESX host with a 1TB local disk. I have a similiar set up in a different site and i ran the update weeks ago no problem. Today I ran the same update but have come up with this issue. The only difference is that in the first case i ran the update from a CD and booted from that CD to apply the update, in this case i SCPd the update.zip file out to the remote esx and ran esxupdate --bundle /path/update.zip update
that worked from what i could see and it asked me to reboot,. I rebooted the ESX and it came up fine, I can connect using vSphere, but when i try power up a VM i get this error.
@jamesbowling is an individual host
Just out of curiosity, can you login to the console and see if you see anything that may say COS Swap not configured? Or possibly login to the cli and run: free -m and show us the output? If you receive the message above or show 0 for swap space, check out: http://kb.vmware.com/kb/1016297
If you found this at all helpful please award points by using the correct or helpful buttons! Thanks!
logged in using putty and ran free -m with the results attached:
when i log into vSphere i dont get any errors. if i go to the events tab for any of my VMs that i have tried to power up i can see an error that states
cannot power on testvm on bpmvm1 in ha-datacenter. a general system error occured
... in this case i SCPd the update.zip file out to the remote esx
Just in case you copied the bundle to the OS disk instead of a VMFS datastore, make sure the filesystem does not run out of space.
Run a "df -h" to check the free space and delete the update bundle and/or any other unneeded files.
... cannot power on testvm on bpmvm1 in ha-datacenter
Do you or did you manage the hosts in vCenter at any time?
André
@james bowling using putty the output of free -m is:
free -m
total used free shared buffers cached
Mem: 783 719 63 0 22 579
-/+ buffers/cache: 117 665
Swap: 0 0 0
don't get any error when i log onto the vSphere clinet. if i go to events tab for any VM that i have tried to power up i see and error
can not power on testvm in bpmvm1 in ha-datacenter. a general system error occured
@andre
vspher is showing the server the host as having 295 GB free. i copied the bundle to /vmfs/volumes/Storage1/update/
results of df -h:
Filesystem Size Used Avail Use% Mounted on
/dev/sdb5 4.9G 1.7G 3.0G 36% /
/dev/sda1 1.1G 93M 936M 10% /boot
/dev/sdb2 2.0G 88M 1.8G 5% /var/log
we dont use vCentre at all.
See how your Swap shows 0's? You need to follow the KB article I posted in my earlier response.
If you found this at all helpful please award points by using the correct or helpful buttons! Thanks!
@james
yeah sorry only re-read your post again and am going through the steps now
results of fdisk -l
Disk /dev/sda: 999.6 GB, 999653638144 bytes
64 heads, 32 sectors/track, 953344 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1100 1126384 83 Linux
/dev/sda2 1101 1210 112640 fc VMware VMKCORE
/dev/sda3 1211 953344 974985216 5 Extended
/dev/sda5 1211 953344 974985200 fb VMware VMFS
Disk /dev/sdb: 8183 MB, 8183087104 bytes
255 heads, 63 sectors/track, 994 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 102 819283+ 82 Linux swap / Solaris
/dev/sdb2 103 357 2048287+ 83 Linux
/dev/sdb3 358 994 5116702+ 5 Extended
/dev/sdb5 358 994 5116671 83 Linux
tried to run swapon /dev/sdb1
getting swapon command not found
just for teh sake of it the contents of /etc/fstab are below
UUID=f7f89f4f-1d84-4c0c-ad1f-3bf4629c04a3 / ext3 defaults 1 1
UUID=58970182-5e09-4d1f-8b6a-e1464a36bc67 /boot ext3 defaults 1 2
None /dev/pts devpts defaults 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
None /proc proc defaults 0 0
None /sys sysfs defaults 0 0
UUID=6a681357-e477-4645-94a4-c4717650d44a /var/log ext3 defaults,errors=panic 1 2
UUID=7ddc6cfc-104b-4b19-add2-e2851580cf87 swap swap defaults 0 0
~
/sbin/swapon /dev/sdb1
If you found this at all helpful please award points by using the correct or helpful buttons! Thanks!
if browse to /sbin and try run swapon /dev/sdb1 and i get the same error or even if i run /sbin/swapon /dev/sdb1
I am assuming you are logging in as root? Or are you logging in as yourself and then su to root? If you are su to root, try su - instead of just su.
If you found this at all helpful please award points by using the correct or helpful buttons! Thanks!
used putty from a windows 7 machine but logged in to the ssh session as root. could that be teh problem? isn;t there something in ESX that stops root logging in via a SSh session and you have to change it. maybe this is the case too, maybe something is stopping root from runnig the command
If you are able to login as root then you should be fine. Do me a favor and run find / -name "swapon" -print and see if it finds the command anywhere.
If you found this at all helpful please award points by using the correct or helpful buttons! Thanks!
after a few seconds it just returns me to the prompt. also tried the swapon from a different user name same result
Very odd that the command is not there.
James Bowling