Wednesday, January 2, 2019

VMKernel Core Dump - Part II: How to add & remove coredump files


In another post I explained about the VMKernel CoreDump files but today I want to show how to delete coredump files and set their location to the new path. So before any operation, let's check tge current settings via ESXCLI:
 # esxcli system coredump file list





Each line of the result consists of a path {/vmfs/volumes/5c2...(volume UUID)/vmkdump/filename.dumpfile} , Active, Configured and Size values. If there are "False" values for Active and Configured fields then the coredump file is not activated. You can remove each one of them by:
# esxcli system coredump file remove -F -f /vmfs/volumes/5c2.../vmkdump/filename.dumpfile

(-F to run command forcefully, especially if the file is active and -f for the dump file)

But before running last line, it's better to deactivate your dumpfiles with:
# esxcli system coredump file set -u 

At last if you want to configure your host's coredump to a new file, you can run:
# esxcli system coredump file add -d (DatastoreName) -f (FileName) -s (FileSize{>100MB})

But still it's not activated so run:
# esxcli system coredump file set -p /vmfs/volumes/5c2.../vmkdump/filename.dumpfile

You can see on below picture that second file is active and configured






Note this matter you can change all of this settings by editing hosts advanced settings or attaching Host Profile to them. For more information you can check KB2090057 and KB2077516
Don't forget to run /sbin/auto-backup.sh ;)
 

No comments:

Post a Comment

I will start a new journey soon ...