<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Log-Collector on ErrorVault — Developer Error Code Dictionary</title>
    <link>https://errorvault.dev/tags/log-collector/</link>
    <description>Recent content in Log-Collector on ErrorVault — Developer Error Code Dictionary</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 31 Jul 2026 00:44:04 +0800</lastBuildDate>
    <atom:link href="https://errorvault.dev/tags/log-collector/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fix clw-agent-exhausted: CloudWatch Agent Resource Pool Exhaustion</title>
      <link>https://errorvault.dev/openclaw/openclaw-clw-agent-exhausted/</link>
      <pubDate>Fri, 31 Jul 2026 00:44:04 +0800</pubDate>
      <guid>https://errorvault.dev/openclaw/openclaw-clw-agent-exhausted/</guid>
      <description>&lt;h2 id=&#34;1-symptoms&#34;&gt;1. Symptoms&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;code&gt;clw-agent-exhausted&lt;/code&gt; error manifests when the OpenClaw CloudWatch agent reaches its maximum concurrent log processing capacity. This error typically appears during high-volume log ingestion scenarios or when the agent is configured with insufficient worker threads to handle the incoming log stream volume.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Common indicators include:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Error message: &lt;code&gt;clw-agent-exhausted: Maximum concurrent requests exceeded for CloudWatch Logs agent&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;Log entries showing partial log delivery or dropped log lines&lt;/li&gt;&#xA;&lt;li&gt;CloudWatch agent process consuming excessive CPU and memory&lt;/li&gt;&#xA;&lt;li&gt;Intermittent log gaps in CloudWatch Logs console despite logs being generated&lt;/li&gt;&#xA;&lt;li&gt;API throttling responses from the CloudWatch Logs endpoint (&lt;code&gt;ThrottlingException&lt;/code&gt;)&lt;/li&gt;&#xA;&lt;li&gt;Agent status showing &amp;ldquo;running&amp;rdquo; but with degraded throughput performance&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;Shell output examples:&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
