Troubleshooting Common Garry's Mod Server Errors

Overview

Running a heavily modded Garry's Mod server requires effective troubleshooting skills. From Lua runtime exceptions to segmentation faults, missing content textures, and Steam authentication errors, this guide outlines standard diagnostic workflows in DustBowl Warden.

Common Error Signatures and Solutions

1. Black and Purple Checkerboard Textures / Red ERROR Models

• Symptom: Structures, roads, or props appear as checkered textures or giant red ERROR models.
• Cause: Missing Counter-Strike: Source or Valve game content.
• Resolution:
  1. On the server: Verify /home/container/garrysmod/cfg/mount.cfg has valid paths pointing to mounted content in /home/container/content/cstrike.
  2. On client: Remind connecting players to install CS:S or install an authorized CS:S content addon pack.

2. Segmentation Fault (Crash to Desktop)

• Symptom: The server terminates abruptly and the Warden console prints Segmentation fault (core dumped) or exits with code 139.
• Cause: Outdated C++ binary modules (.dll or .so files in garrysmod/lua/bin/) or corrupt map geometry.
• Resolution:
  1. Check garrysmod/lua/bin/ for third-party modules (like old MySQL connectors) and update them.
  2. Test booting with a vanilla map (e.g., gm_construct) to rule out map corruption.

3. Out of Memory (Container Exit Code 137)

• Symptom: The container stops suddenly and Warden reports Exit Code 137.
• Cause: Memory leaks in custom Lua scripts or exceeding container RAM limits.
• Resolution:
  1. Check RAM usage on the DustBowl Warden dashboard.
  2. Clear /home/container/garrysmod/cache/ to remove temporary download caches.
  3. Remove unoptimized weapon or vehicle packs with massive uncompressed textures.

4. "No Steam Web API Key" Console Warning

• Symptom: The console warns No Steam Web API Key provided! Workshop items will fail to download.
• Resolution:
  1. Open Warden Startup Parameters.
  2. Paste your 32-character key into the STEAM_WEB_API_KEY field.
  3. Restart the server.

5. Excessive Something is creating script errors! Notifications

• Symptom: Client screens are spammed with script error notifications.
• Resolution:
  1. Open the Warden Console to view the full Lua stack trace.
  2. Identify the addon name, filename, and line number listed in the stack trace.
  3. Update or remove the offending addon from garrysmod/addons/.

Useful Interactive Tools

• Draft MOTD and rules with the GMod DarkRP Rules & MOTD Generator.
• Generate ban appeal templates with the GMod Ban Appeal Template Generator.
• Manage admin commands with the GMod ULX Admin Command Reference.