Hello everyone, I've tried searching for an answer to this but have had no luck. I have one ESXi host that keeps crashing periodically (once or twice a week). I get a fuchsia screen and have to reboot the host. In the logs and on the fuchsia screen I see the following error:
Alarm 'Host error' on x.x.x.x triggered by event 1732405 'Issue detected on x.x.x.x Duplicate name 'vpxa.19.gz' entry in cache
When I check the Events, I see a similar entry (actually there are 10 entries one after the other)
These Show as Warnings (10 of them in a row):
DC: 783: Duplicate name 'vpxa.19.gz' entry in cache
These Show as Errors (9 of them in a row):
0/23/2019, 7:33:21 AM Alarm 'Host error' on 10.0.0.96
triggered by event 1743276 'Issue detected on 10.0.0.96 in ###### HO: DC: 783: Duplicate name 'vpxa.19.gz' entry in cache. (2019-10-23T11:33:03.815Z cpu6:2097484)'
I was running ESXi 6.7.0 release 1 and tried updating to release 3 to see if that would fix the issue but it did not.
Anyone have any ideas what might be causing this or where to look for more information?
Vijay2027 I've attached the logs
I was looking at them this morning because the system crashed again last night at 9:37pm but I don't see anything that stands out for me other than a lot of error about vmhba33 which is a USB stick on the server, I believe it is where the ESXi is installed since it is showing up in vSphere as being only 1.82GB (I have 2 sticks attached, the one running ESXi and a spare with the ESXi Setup loaded on it in case I need to do a remote reinstall). Is it possible this USB drive is corrupt or having issues that are causing the crashes? I could do a fresh install on a different USB.
could you fix this Problem? After a Poweroutage in our Datacenter we have this errors.
It is a similar Error but the log shows only ´´ instead ´vpxa.19.gz´
Alarm 'Host error' on ********* triggered by event 1387084 'Issue detected on ********** in *****: DC: 783: Duplicate name '' entry in cache.
Same error message here.
Host working fine (no crashes or misfunctionalities) but vcenter raising this error message every two hours aprox.
Vcenter with two hosts. Only one with this issue.
>> see if you have the scratch configured on the main directory of a datastore instead of a sub directory, if yes then change it an configure as per https://kb.vmware.com/s/article/1033696?lang=en_us
>> As a workaround you can try creating and deleting a test file in var/run/log directory after taking an ssh to the host
esx $ touch /var/run/log/test-file
esx $ rm /var/run/log/test-file
Technical Support Engineer
Global Support Services, VMware Inc.