In newly deployed host, there is this configuration issue "no coredump target has been configured" and I have created a coredump file manually in my shared datastore. I have checked the status and the file is both active and configured. But I have the issue displaying in host summary. Do i need to reboot the host for effect?? Or Is there any other solution possible to resolve coredump configuration issue??? (Note: I have tried coredump partition. Still no progress.)
What are the coredump settings?
You can check with
$esx = Get-VMHost -Name MyEsx
$esxcli = Get-EsxCli -VMHost $esx -V2
$esxcli.system.coredump.partition.list.Invoke()
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
thank you but even after configuring coredump partition and file settings, configuration issue is not resolved
Can I resolve this issue without rebooting host?
Those lines do not configure the coredump settings, they just list the current settings.
Normally setting the coredump settings does not require a reboot afaik.
See also KB2004299
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Ya. I have used the following commands to create coredump file in my shared datastore.
$esxcli.system.coredump.file.add($null, "datastore1", $true, "coredumpfile", 100)
file is also created in datastore and its active.
still configuration issue is not resolved
Did you list the settings with the lines I sent earlier?
Can you share what it displays?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
I don't have a screenshot. Will share it tomorrow. Currently I'm in my home. but the output for coredump file creation is like this
Path Active Configured
------------------------------------------------------------------------ ------ ----------
/vmfs/volumes/52b021c3-f6b3da50-4c76-001d0904c5a5/vmkdump/coredumpfile1.dumpfile true true
That looks ok.
You did check that the path is correct?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
yes. I did. Coredump files are both active and configured in my shared datastore. But still " no coredump target" configuration issue is not resolved. After rebooting my host the issue is resolved. I'm confused.:smileyconfused: