VMware KB: The Hardware Status tab displays the error: Hardware monitoring service on this host is not responding or not available – Solved

One of the alerts that often pops up in OpsMgr 2012 is that it cannot retrieve health data from the VMware hosts and falls back to using Vcenter. To fix this enable SSH on your VMware hosts and login to run the following command from the article below:

/etc/init.d/sfcbd-watchdog restart

I have not seen any interruption so far running this command.

Source: VMware KB: The Hardware Status tab displays the error: Hardware monitoring service on this host is not responding or not available

Delayed Write Failed – Event ID 50 – Solved

Saw this issue though OpsMgr 2012 R2 console, telling me that all Windows Server 2012 and 2012 R2 servers where reporting this issue every evening when the backup kicked in.

There are a lot of blog posts on the web telling you to disabling the cache on the disks and so on, but this is a default setting i did not want to change. And in my opinion that is a workaround, not a fix.

So working with this issue led me to an known error from VMware: KB2006849

Telling me that this has been solved in a patch from the 27th of january 2015 and later versions.

Version: ESXi 5.5 Patch 4
Release: 2015-01-27
Build: 2403361

To verify which version you are running, then look in the vSphere Client under one of your hosts:

VMware version

Then compare that number with this website:Build number history

If you have a build version before 2403361 (like the above example) – then you need to update your ESX hosts and the VMware tools on the virtual machines.

This solves the issue.

Event id numbers which leads to this issue:

Event ID 50, 57, 137, 140, 157 and 12289

Best regards.


How to remove vmkdump files from VMware ESX 5.x

So how can a datastore be deleted if there is an active file in a vmkdump folder that resides in the datastore running Vsphere Client and ESX 5.x?

When browsing the datastore, a vmkdump folder shows up with a file in it, this file is in use and prevents the datastore to be deleted, it is a log dump file and in my case could be remove and re-added safely to another store.

The files cannot be migrated by the Vsphere Client and trying to do so or delete dem gives an error: “Device or resource busy”

One .dumpfile is created by each host in a random datastore, and to delete and recreate them, you have to find the owner of the file, to do so, take the ID of the file and log in to your hosts by this adress to find their ID which have to match the filename:


then logon to the ESX host with putty, and run this command: “esxcli system coredump file remove –F”

Then recreate the file at a new destination with: “esxcli system coredump file add -f SERVERNAME -d DATASTORENAME”

Make the file active: “esxcli system coredump file set -p /vmfs/volumes/DATASTORE_UUID/vmkdump/FILENAME”

Run this command to see if the file is active: “esxcli system coredump file list”

So to solve this puzzle, these to blogs did the math.