<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Buffer Space on Matt Allford</title><link>https://www.mattallford.com/tags/buffer-space/</link><description>Recent content in Buffer Space on Matt Allford</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 24 Mar 2017 01:04:49 +0000</lastBuildDate><atom:link href="https://www.mattallford.com/tags/buffer-space/index.xml" rel="self" type="application/rss+xml"/><item><title>ESXi - Agent can't send heartbeats: No buffer space available</title><link>https://www.mattallford.com/esxi-agent-cant-send-heartbeats-no-buffer-space-available/</link><pubDate>Fri, 24 Mar 2017 01:04:49 +0000</pubDate><guid>https://www.mattallford.com/esxi-agent-cant-send-heartbeats-no-buffer-space-available/</guid><description>&lt;p&gt;Quick post. The other day I saw an alert on an ESXi 6.0 host as follows:&lt;/p&gt;
&lt;p&gt;Agent can&amp;rsquo;t send heartbeats: No buffer space available&lt;/p&gt;
&lt;p&gt;&lt;img loading="lazy" src="https://www.mattallford.com/wp-content/uploads/2017/03/Agent_HEartbeats.png"&gt;&lt;/p&gt;
&lt;p&gt;The host was responsive and connected to vCenter Server, and the VMs were running OK on the host. I checked the vmkernel / hostd / vpxa logs, and the only mention of this was a one liner in the vmkernel log which repeated the error message above.&lt;/p&gt;</description></item></channel></rss>