Logs / Garry's Mod
Share a GMod log and find Lua errors
Paste the console or console.log from your Garry's Mod server. The analysis assigns every Lua error to the addon, Workshop addon or gamemode it comes from – so you see right away which of your 80 addons is the problem. It also detects missing files, Workshop downloads, network overflows, the entity limit and crashes.
Where do I find the log?
Console in the panel- Easiest: copy the output straight from the server console. At Nexthosting, “Share log” does this in one click.
garrysmod/console.log- Only exists if the server runs with the launch parameter -condebug. The complete console then ends up in this file.
garrysmod/logs/- With log on in server.cfg, the server writes log files per map change (L1114000.log …). They contain connections and chat, but Lua errors only partly.
garrysmod/data/- Some addons (for example admin mods) write their own logs to the data folder. You can paste those too.
What the analysis detects for Garry's Mod
- Lua errors with stack trace, assigned to the addon, Workshop addon or gamemode – with a link to the Workshop page
- “attempt to index a nil value”, “attempt to call a nil value” and syntax errors with a plain explanation
- Missing files (“Couldn't include file”) and unregistered network messages
- Workshop downloads that fail, plus missing models and materials
- Network overflows, entity limit (no free edicts), Lua memory, lag and crashes
- Invalid login token (GSLT) and outdated server version
- Map, gamemode, tickrate, slots, admin mod (ULX, SAM, FAdmin) as well as kicks and bans
Common Garry's Mod errors and how to fix them
attempt to index a nil valueattempt to call a nil valueCouldn't include file … (File not found)Calling net.Start with unpooled message nameReliable channel overflow / Disconnect: overflowED_Alloc: no free edictsunexpected symbol near … (syntax error)Lua Panic / not enough memoryInvalid server login token (GSLT)Workshop: Failed to download addonMissing models (ERROR) and purple-black texturesFAILED TO BIND TO PORT / Address already in useSegmentation fault (core dumped)Exit code 137 / OOMKilled
Questions about Garry's Mod logs
- How do I share a GMod log?
- Copy the console output or open console.log, paste it in above and click “Save”. You can pass on the link from the address bar directly – for example to the developer of the addon that throws the error.
- How can I tell which addon causes the error?
- Every Lua error names a file path like addons/vehicle_shop/lua/…. The folder name after addons/ is the addon. For Workshop addons, the name is in square brackets in front. The analysis does this for you and groups identical errors.
- Are Steam IDs and IPs shared?
- No. Steam IDs, IP addresses, the login token (sv_setsteamaccount), RCON passwords and webhooks are masked before saving.
- Can I share errors from the client too?
- Yes. Client-side Lua errors appear in your game's console (the ~ key) and, with -condebug, in garrysmod/console.log on your PC. The analysis treats them the same way.