https://errorvault.dev/tags/grpc/Recent content in Grpc on ErrorVault — Developer Error Code DictionaryHugoen-usSun, 12 Apr 2026 14:21:20 +0800https://errorvault.dev/openclaw/openclaw-clw-llm-disconnected-llm-connection-drop/Sun, 12 Apr 2026 14:21:20 +0800https://errorvault.dev/openclaw/openclaw-clw-llm-disconnected-llm-connection-drop/<h2 id="1-symptoms">1. Symptoms</h2> <p>The <code>clw-llm-disconnected</code> error in OpenClaw manifests during LLM inference or chat completion calls. Key indicators include:</p> <ul> <li>Runtime exception or return code <code>-CLW_ERR_LLM_DISCONNECTED</code> (error code <code>0xCLW_LLM_DC</code>).</li> <li>Log entries like: <code>[ERROR] clw_llm_client: Connection to LLM backend at grpc://localhost:50051 lost. Error: clw-llm-disconnected</code>.</li> <li>Failed API calls such as <code>clw_llm_generate()</code> or <code>clw_llm_chat()</code> returning <code>CLW_STATUS_DISCONNECTED</code>.</li> <li>Intermittent failures: Works initially, then drops after 30-60 seconds of idle or high load.</li> <li>Client-side stack traces pointing to <code>clw_llm_channel_state()</code> returning <code>GRPC_CHANNEL_TRANSIENT_FAILURE</code>.</li> <li>No response from server pings via <code>clw_llm_health_check()</code>.</li> </ul> <p>This error blocks all downstream LLM operations until reconnection. In production, it causes 503-like failures in web services or CLI tools using OpenClaw&rsquo;s C++ SDK.</p>