Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Fix OpenClaw Gateway "spawn EBADF" / "RPC probe failed" / "EMFILE too many open files" errors caused by file descriptor exhaustion from too many files in wor...
Fix OpenClaw Gateway "spawn EBADF" / "RPC probe failed" / "EMFILE too many open files" errors caused by file descriptor exhaustion from too many files in wor...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
OpenClaw Gateway crashes or hangs with these errors: spawn EBADF when running exec commands RPC probe failed / gateway timeout Logs show EMFILE: too many open files, watch Gateway process is running but unresponsive
The Gateway automatically watches all files under ~/.openclaw/workspace/ for changes. If you place virtual environments (.venv), node_modules, large datasets, or tens of thousands of small files inside workspace, the file watcher will exceed macOS's default file descriptor limit (256), causing the process to hang.
Run the one-click repair script: bash fix.sh What it does: Detects workspace file count Finds and removes unnecessary dependency directories (.venv, node_modules) inside workspace Backs up your existing LaunchAgent plist Updates LaunchAgent to set file descriptor limit to 524,288 Restarts the Gateway service Verifies service health
If you prefer to fix manually: Remove large directories from workspace: # Never put these inside ~/.openclaw/workspace/: rm -rf ~/.openclaw/workspace/*/.venv rm -rf ~/.openclaw/workspace/*/node_modules # Move datasets/models/venvs to ~/Downloads/ or /tmp/ Update LaunchAgent resource limits: Edit ~/Library/LaunchAgents/ai.openclaw.gateway.plist and add inside the root <dict>: <key>HardResourceLimits</key> <dict> <key>NumberOfFiles</key> <integer>524288</integer> </dict> <key>SoftResourceLimits</key> <dict> <key>NumberOfFiles</key> <integer>524288</integer> </dict> Restart Gateway: launchctl bootout gui/$(id -u) ~/Library/LaunchAgents/ai.openclaw.gateway.plist launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/ai.openclaw.gateway.plist sleep 10 && openclaw gateway status
✅ Do NOT put these inside ~/.openclaw/workspace/: Python virtual environments (.venv, venv) Node.js node_modules directories Large datasets (>1000 files) AI model weights (.pt, .bin, .pth files) Cache directories with thousands of small files ✅ Put these outside workspace: /tmp/, ~/Downloads/, or any directory outside ~/.openclaw/workspace/
After fix, run: openclaw gateway status You should see RPC probe: ok in the output.
If fix fails: Check logs: tail -50 ~/.openclaw/logs/gateway.err.log Verify no large directories remain in workspace: find ~/.openclaw/workspace -type f | wc -l (should be < 1000) Manually restart Gateway: openclaw gateway stop && openclaw gateway install
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.