After updating to 7.0 U1, I noticed these messages spamming the logs and while they are related VSAN, I don't use it or have it configured so I can't figure out why they are even showing. 2021...
See more...
After updating to 7.0 U1, I noticed these messages spamming the logs and while they are related VSAN, I don't use it or have it configured so I can't figure out why they are even showing. 2021-01-24T21:53:24.087Z error vsand[530325] [opID=MainThread cliutils::GetVSANClusterInfo] Failed to query cluster info: Failure 2021-01-24T21:53:29.089Z error vsand[530325] [opID=MainThread cliutils::GetVSANClusterInfo] Failed to query cluster info: Failure 2021-01-24T21:53:33.133Z info vsand[530352] [opID=Thread-2 VsanSystemImpl::_ConfigInfoPrintLog] configInfo: skipped 2021-01-24T21:53:33.133Z info vsand[530352] [opID=Thread-2 VsanSystemImpl::_ConfigInfoPrintLog] configInfo: skipped Any ideas?
I noticed that recently these errors started filling my logs but I can't find any information while searching. error hostd[526498] [Originator@6876 sub=StatsvcHostServiceTokenHandler] Asyn...
See more...
I noticed that recently these errors started filling my logs but I can't find any information while searching. error hostd[526498] [Originator@6876 sub=StatsvcHostServiceTokenHandler] AsyncAuthenticate: Token invalid Any ideas? Running ESXi 7.0. Thank you.
@ashilkrishnan Thanks! I got it working. I followed the KB and created a simple .XML file with the required port without having to edit the original. Is it default behavior for it not to persist afte...
See more...
@ashilkrishnan Thanks! I got it working. I followed the KB and created a simple .XML file with the required port without having to edit the original. Is it default behavior for it not to persist after reboot? I noticed that my custom .XML file is deleted after restarting the host.
@ashilkrishnan Sorry for the late reply. I configured Syslog.global.logHost as needed but need to create a custom rule for port 8514 but that link you posted is not working. I found this article but ...
See more...
@ashilkrishnan Sorry for the late reply. I configured Syslog.global.logHost as needed but need to create a custom rule for port 8514 but that link you posted is not working. I found this article but not sure if it's the correct way.
I am trying to send my Esxi hosts logs to a Graylog server listening on port 8514 and while I can configure the host to send it on this port, I am having a tough time configuring the firewall to allo...
See more...
I am trying to send my Esxi hosts logs to a Graylog server listening on port 8514 and while I can configure the host to send it on this port, I am having a tough time configuring the firewall to allow the outgoing traffic. By simply enabling the firewall required in the host only allows outgoing on 514. How do I change it to 8514 in my case? Thanks!
I recently noticed that both of my ESXi 6.7 U2 hosts are currently showing status "unknown" for their storage adapters but everything seems to be working fine. Should I be concerned? Thank...
See more...
I recently noticed that both of my ESXi 6.7 U2 hosts are currently showing status "unknown" for their storage adapters but everything seems to be working fine. Should I be concerned? Thank you.
I recently installed PowerChute Network Shutdown Appliance to monitor my cluster and noticed that now my hosts will show a "Find by IP" task every two minutes under recent tasks. I contacted APC ...
See more...
I recently installed PowerChute Network Shutdown Appliance to monitor my cluster and noticed that now my hosts will show a "Find by IP" task every two minutes under recent tasks. I contacted APC but have yet to hear back. Here's a screenshot: Anyone seem this behavior before and if so, is there any action that I need to take or is this expected since the appliance is now constantly monitoring everything?
I tried using a different name for the machine when prompted in the wizard and now it works. Could anyone explain what happened here and if any further action on my part is necessary? It seem...
See more...
I tried using a different name for the machine when prompted in the wizard and now it works. Could anyone explain what happened here and if any further action on my part is necessary? It seems that remnants of the old machine still exist somewhere?
Hello! Yesterday I tried creating a VM using a Linux Server ISO and was successful but later decided to delete the VM and start over in order to tweak the settings but now receive the followin...
See more...
Hello! Yesterday I tried creating a VM using a Linux Server ISO and was successful but later decided to delete the VM and start over in order to tweak the settings but now receive the following error: Create VM Key haTask-ha-folder-vm-vim.Folder.createVm-136981211 Description Create a new virtual machine Folder: State Failed - File [Dell_DISK] Ubuntu/Ubuntu_0.vmdk was not found Errors File system specific implementation of Lookup[file] failed File system specific implementation of Lookup[file] failed File system specific implementation of Lookup[file] failed File system specific implementation of Lookup[file] failed File system specific implementation of Lookup[file] failed File system specific implementation of Lookup[file] failed File system specific implementation of LookupAndOpen[file] failed File system specific implementation of Lookup[file] failed File system specific implementation of Lookup[file] failed File system specific implementation of Lookup[file] failed File system specific implementation of Lookup[file] failed File system specific implementation of Lookup[file] failed I have recently deleted my Windows VM and tried to re create in order to try and replicate the issue but the Windows VM can be created just fine. Thanks in advance.
