Chinaunix首页 | 论坛 | 博客
  • 博客访问: 4697033
  • 博文数量: 1647
  • 博客积分: 16831
  • 博客等级: 上将
  • 技术积分: 12479
  • 用 户 组: 普通用户
  • 注册时间: 2011-02-25 07:23
个人简介

柔中带刚,刚中带柔,淫荡中富含柔和,刚猛中荡漾风骚,无坚不摧,无孔不入!

文章分类

全部博文(1647)

文章存档

2019年(1)

2018年(20)

2017年(68)

2016年(61)

2015年(52)

2014年(204)

2013年(224)

2012年(644)

2011年(373)

分类: 虚拟化

2018-10-22 17:20:23

No coredump target has been configured

此问题未回答

WebOpsNovice
WebOps 2014-11-12 上午4:04

Hi


I'm seeing the "No coredump target has been configured" message on one of my hosts after installation and it has local storage. I should have fixed this before it has VM's on it but I didn't..


So I check to see what it is currently set at...


C:\Program Files (x86)\VMware\VMware vSphere CLI>esxcli -s X.X.X.X  -h Y.Y.Y.Y system coredump partition get

Enter username: XXXXXXX

Enter password:

Not a known device: naa.6d4ae520a0be19001b76325c0ec1d22a


Then I list available partitions


C:\Program Files (x86)\VMware\VMware vSphere CLI>esxcli -s X.X.X.X  -h Y.Y.Y.Y system coredump partition list

Enter username: XXXXXXX

Enter password:

no configured dump partition found; skipping


My concern is accidentally initialising an active partition, how can I set the coredump partition and can it be done via the web client?

我有同样的问题 显示 0 喜欢(0)
  • 1. Re: No coredump target has been configured
    bspagna89Hot Shot 
    vExpert
    bspagna89 2014-11-12 上午7:38 (回复 WebOps

    Hi,


    Please check out this KB :


    VMware KB: Configuring a diagnostic coredump partition on an ESXi 5.x host 


    1. Validate that something shows up in this list -  esxcli system coredump partition list

    2. Set the coredump partition by :

      esxcli system coredump partition set --partition="mpx.vmhba2:C0:T0:L0:7"

      esxcli system coredump partition set --enable true


    You can also try using :

    esxcli system coredump partition set --enable true --smart

    This will automatically set a partition.


    Hope this helps.

  • 2. Re: No coredump target has been configured
    tyepezLurker
    tyepez 2015-9-10 上午8:43 (回复 WebOps

    Solución al problema "no coredump target has been configured. host core dumps cannot be saved"


    Mediante SSH, consultamos el estado de la partición de diagnostico (coredump).

    # esxcli system coredump partition get

    Not a known device *mi-anterior-identificador-de-disco*

    # esxcli system coredump partition list

    no configured dump partition found; skipping


    El resultado muestra que esto no está funcionando, si es el caso, se necesita re-configurar la partición de diagnóstico.

    # esxcli system coredump partition set --unconfigure


    Listamos las particiones existentes

    # esxcli system coredump partition list

    Name Path Active Configured

    -------------------------------------- ---------------------------------------------------------- ------ ----------

    naa.6005076040ab4c101d8314b335edd7a0:7 /vmfs/devices/disks/naa.6005076040ab4c101d8314b335edd7a0:7 false false

    naa.6005076040ab4c101d8314b335edd7a0:9 /vmfs/devices/disks/naa.6005076040ab4c101d8314b335edd7a0:9 false false

    Para seleccionar y activar automáticamente una partición de diagnóstico accesible, ejecutamos el siguiente comando:

    # esxcli system coredump partition set --enable true --smart


    Nuevamente consultamos el estado de la partición de diagnóstico y listo, problema resuelto.

    # esxcli system coredump partition get

    Active: naa.6005076040ab4c101d8314b335edd7a0:9

    Configured: naa.6005076040ab4c101d8314b335edd7a0:9


    Saludos,

  • 3. Re: No coredump target has been configured
    DanyDemersNovice
    DanyDemers 2016-3-31 下午2:01 (回复 tyepez

    Even if I don't understand spanish, I understood the command in Tyepez post and this was the solution for us after migration the boot into a new SAN we had these error on all our esxi host. Thank you for this information.

  • 4. Re: No coredump target has been configured
    acartyLurker
    acarty 2017-9-26 下午3:22 (回复 DanyDemers

    I don't speak Spanish either but this fix worked for me too. Thanks.

  • 5. Re: No coredump target has been configured
    singhrajNovice
    singhraj 2018-2-13 上午5:54 (回复 acarty

    i am having issue because new ESXi hosts is storing its coredump file on different data stroe on SAN and some ESXi stroing on local disk.

    i am trying to find out how ESXi pick to SAN (VNX)datastroe or local datastore to store its coredump file.

  • 6. Re: No coredump target has been configured
    singhrajNovice
    singhraj 2018-2-13 上午5:56 回复 singhraj

    we did not configured coredump target when we setup new ESXi6.5 hosts

  • After some disk changes on one VMware ESXi host i met this error:

    "No coredump target has been configured. Host core dumps cannot be saved".

    My changes were to remove every local disk on the ESXi host. ESXi installation was made on a SD memory card, therefore there's no room to place core dumps. And this is why ESXi host gives you this warning.

    Apparently you must have a local disk in which have a partition to reserve for core dumps, but searching on the web i found a solution for my needs.

    With this solution i can continue to have core dumps (even if i can live without they ;-) ) without having local disks.

     

    Here the steps:

    What you need before continue:

    ESXi SSH shell enabled and knowledge on hot to connect via SSH (if you don't know how to do that, please follow te white rabbit)

    - vCSA AKA vCenter Server Appliance . If you dont' have vCenter at all or have a vCenter installed on Windows platform i'm sorry, you can stop here, or you can try to adapt some part of this tutorial to match the Windows platform.

    - connect to the ESXi host with an SSH shell

    - type this commend to take note of the vmknic you use to communicate with vCenter server:
    esxcfg-vmknic -l
    normally you have vmk0 as management nic, but maybe you have an other one

    - set remote core dumps with this command:
    esxcli system coredump network set --interface-name vmk0 --server-ipv4 192.168.15.8 --server-port 6500

    where vmk0 is you management interface that communicate with vCenter Server Appliance, 192.168.15.8 is the ip of your vCSA and 6500 is the standard remote core dumps collector of your vCSA.

    - enable remote core dumps with this command:
    esxcli system coredump network set --enable true

    - verify that all went good:
    esxcli system coredump network get
    esxcli system coredump network check

    - now we can disable local core dumps:

    esxcli system coredump file list (if you want to show where and which are this core dumps)
    esxcli system coredump file set --enable false
    esxcli system coredump file remove --force
    esxcli system coredump file list (to show that there's no more core dumps)

    - save this strenuous work for next reboots
    /sbin/auto-backup.sh

    - disable VMkernel.Boot.autoCreateDumpFile
    This is an Advanced Setting on the ESXi Host (Configuration > Software > Advanced Settings)
    Use the vSphere client to do this.
    vmkernel-boot-autocreatedumpfile

     

    - reboot the ESXi host to verify that everything you have written is working. If you cannot reboot the host no problem, i live well also without this ;-)


阅读(500) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~
评论热议
请登录后评论。

登录 注册