VMware Cloud Community
petermie
Enthusiast
Enthusiast

"File - failed to get objectId" in hostd logs

I've been looking though the logs on my ESXi 6.5 servers with vRealize Log Insight and I noticed that two of my hosts (of 16 total) show errors like the following for different VMs a few times a day. Is this something I need to be concerned about? I haven't been able to find anything by searching by any parts of any of the error messages, but since it seems to be limited to just two hosts i'm thinking there has to be something wrong somewhere, even though operationally I haven't noticed any issues or have had any reported by any of my users.

2017-03-21T20:27:47.980Z esx.mydomain.local Hostd: info hostd[12940B70] [Originator@6876 sub=Libs opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] OBJLIB-LIB: ObjLib_GetNameSpaceObjectUniqueIdFromPath : failed backend does not store object unique id in path

2017-03-21T20:27:47.980Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx': One of the parameters supplied is invalid.

2017-03-21T20:27:47.980Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmxf': Success.

2017-03-21T20:27:47.981Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.nvram': Success.

2017-03-21T20:27:47.981Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmsd': Success.

2017-03-21T20:27:47.982Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine_2-flat.vmdk': Success.

4 Replies
petermie
Enthusiast
Enthusiast

No ideas?

Reply
0 Kudos
krek
Contributor
Contributor

Same for me!

Reply
0 Kudos
vtparker
Contributor
Contributor

This is happening to me as well. I have some across this on a few VMs and the result was tat they were restarted and moved to another host...

There's an entry in Log Insight for each and every file making up the affected VMs
We're also running 6.5
be nice to know whats causing this
Reply
0 Kudos
Erik_PF
Contributor
Contributor

Did you ever get this figured out?  I'm seeing the same issue and wonder if it's related to some vmotion stalling problems I'm seeing, or just a red herring.

Reply
0 Kudos