This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
vmware:troubleshooting [2019/10/11 13:31] – lunetikk | vmware:troubleshooting [2022/09/03 16:27] (current) – lunetikk | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== VMware Troubleshooting ===== | + | ====== VMware Troubleshooting |
==== Cant apply or remediate a host profile ==== | ==== Cant apply or remediate a host profile ==== | ||
Line 121: | Line 121: | ||
__Fix:__ \\ | __Fix:__ \\ | ||
- | Connect to your ESX host via ssh and restart the management agents | + | Connect to your ESX host via SSH and restart the management agents |
< | < | ||
/ | / | ||
Line 129: | Line 129: | ||
You should be able to create or remove the snapshot afterwards | You should be able to create or remove the snapshot afterwards | ||
- | [[https:// | + | [[https:// |
+ | [[https:// | ||
+ | [[https:// | ||
==== No coredump target has been configured ==== | ==== No coredump target has been configured ==== | ||
Line 168: | Line 170: | ||
__Reason:__ \\ | __Reason:__ \\ | ||
- | Your ESX lost connection to its Boot Device, maybe because of a network outage (switch reboot, cable disconnect, | + | Your ESX lost connection to its bootdevice, maybe because of a network outage (switch reboot, cable disconnect, |
__Fix:__ \\ | __Fix:__ \\ | ||
Line 183: | Line 185: | ||
[[https:// | [[https:// | ||
+ | |||
+ | ==== No space left on device (vCenter) ==== | ||
+ | |||
+ | * vCenter AD Login doesnt work | ||
+ | * “shell.set –enabled True” shows the error “Unknown command: `shell.set' | ||
+ | * creating files will show “No space left on device” | ||
+ | |||
+ | You can also check this by connecting via SSH and entering the following commands | ||
+ | < | ||
+ | com.vmware.vimtop | ||
+ | |||
+ | com.vmware.rvc | ||
+ | |||
+ | >Host to connect to (user@host): | ||
+ | >Are you sure you want to continue connecting (y/n)? y | ||
+ | |||
+ | Warning: Permanently added ' | ||
+ | Failed to connect to localhost: No space left on device @ dir_s_mkdir - /root/.rvc | ||
+ | </ | ||
+ | |||
+ | __Reason:__ \\ | ||
+ | You have no space left on your device, mostly /var/log/ and mostly because of audit.log | ||
+ | |||
+ | __Fix:__ \\ | ||
+ | |||
+ | Because you cant use PuTTY to operate the shell, you need to open the shell with a kernelparameter in the GRUB bootloader. You need to reboot your vCenter (DOWNTIME!). Before starting your VM, set the "Power On Boot Delay" to 10 seconds. | ||
+ | |||
+ | Fatclient: | ||
+ | {{: | ||
+ | |||
+ | Webclient: | ||
+ | {{: | ||
+ | |||
+ | After starting the VM, check the VMware console and wait for the bootloader. You can stop the autostart by hitting " | ||
+ | |||
+ | Select the vCenter appliance and hit " | ||
+ | Then select the right kernel and hit " | ||
+ | Add " | ||
+ | You should now be in the shell. Check the drives with "df -h"\\ | ||
+ | If audit.log is the problem, empty it with | ||
+ | < | ||
+ | echo "" | ||
+ | </ | ||
+ | |||
+ | To fix the logrotate/ | ||
+ | |||
+ | ==== Restore from different datastore ==== | ||
+ | |||
+ | A VM is broken and needs to be restored. To do so you need to copy the VM from the backup datastore to your productive one \\ | ||
+ | |||
+ | __Reason:__ \\ | ||
+ | You dont want to run VMs from your backup datastore \\ | ||
+ | |||
+ | __Fix:__ \\ | ||
+ | Connect to your esx host via ssh and copy the files with " | ||
+ | Make sure you either rename your old .vmdk + flatfile to .old or your restore to something different (rename flat in .vmdk) | ||
+ | <code bash> | ||
+ | cp -a myvm.vmdk / | ||
+ | cp -a myvm-flat.vmdk / | ||
+ | </ | ||
+ | |||
+ | With vmkfstools you dont need to edit the flat name inside .vmdk, the tool does this for you if you choose another name | ||
+ | <code bash> | ||
+ | vmkfstools -i myvm.vmdk / | ||
+ | </ | ||
+ | |||
+ | \\ |