Telegraf Agents Installation fails on Windows 2022 VM's
Article ID: 433088
Updated On:
Products
Issue/Introduction
- On the Aria Operations Ui page, the Telegraf agents fails to deploy with the error - Exception occurred while trying to upload the command to the VM but able to install manually.
- Checking the ESXi hosts, vCenter, and guests for a reliable time source shows accurate timing
- Adding the certificate of the ESXi host where the guest VM is running to Aria Operations still fails.
- Log snippets in the vpxd logs of the vCenter sever matches the below:
vpxd.log:YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@pid sub=vpxLro opID=ID] [VpxLRO] – BEGIN lro-pid – guestOperationsFileManager – vim.vm.guest.FileManager.initiateFileTransferToGuest – uuid(uuid)YYYY-MM-DDTHH:MM:SS warning vpxd[06851] [Originator@pid sub=vpxUtil opID=ID] getaddrinfo failed; host:fqdn, e: N7Vmacore15SystemExceptionE(Name or service not known)YYYY-MM-DDTHH:MM:SS info vpxd[06471] [Originator@pid sub=VapiEndpoint.HTTPService.HttpConnection] HTTP Connection has timed out while waiting for further requests; <io_obj p:#x#####f###c#c####, h:-1, <TCP '###.#.#.# : ####'>, <TCP '###.#.#.# : #####'>>, N7Vmacore16TimeoutExceptionE(Operation timed out: Stream: <io_obj p:#x#####f###c#c####, h:-#, <TCP ''###.#.#.# : ####'>, <TCP ''###.#.#.# : #####'>>, duration: hh:mm:ss.us (hh:mm:ss.us))
Environment
Aria Operations 8.18.x
VMware vCenter Server 8.0.x
VMware ESXi Version: 8.0.x
Cause
Socket reset exception while executing guest operations, this can happen during network issues from CP to Endpoint.
When a makeDirectoryInGuest operation fails in vCenter, the API server logs (like vpxd.log on the appliance at /var/log/vmware/vpxd/) will show SOAP errors, often indicating insufficient privileges (e.g., VirtualMachine.GuestOperations.Modify) due to the account used lacking necessary permissions on the target VM, requiring proper role assignments in vCenter.
YYYY-MM-DDTHH:MM:SS info vpxd[06471] [Originator@pid sub=VapiEndpoint.HTTPService.HttpConnection] HTTP Connection has timed out while waiting for further requests; <io_obj p:#x#####f###c#c####, h:-1, <TCP '###.#.#.# : ####'>, <TCP '###.#.#.# : #####'>>, N7Vmacore16TimeoutExceptionE(Operation timed out: Stream: <io_obj p:#x#####f###c#c####, h:-#, <TCP ''###.#.#.# : ####'>, <TCP ''###.#.#.# : #####'>>, duration: hh:mm:ss.us (hh:mm:ss.us))
This error snipets indicates a DNS resolution failure within the vCenter Server (vpxd). Specifically, the vCenter service tried to look up the IP address for the hostname but the underlying operating system returned a "Name or service not known" error.
Resolution
- Check with your internal networking team regarding firewall rules in relations to 'InitiateFileTransferToguest'.
- Should consider that the URL or URL pattern received from the 'InitiateFileTransferToguest' is expected to be for the target ESX host where the VM resides when the API is called. The file transfer URLs use port 443 (TCP) to the host. Here is some background on what the API returns:
Guest Operations overview
VMware vSphere InitiateFileTransferToGuest API behavior
- Should consider that the URL or URL pattern received from the 'InitiateFileTransferToguest' is expected to be for the target ESX host where the VM resides when the API is called. The file transfer URLs use port 443 (TCP) to the host. Here is some background on what the API returns:
Feedback
