Auto Tournament

Troubleshooting

Fixes for common csm problems.

For problems between Auto Tournament and the servers, see the main Troubleshooting page. For plugin problems, see the Ready Up FAQ.

Start with doctor

csm doctor

doctor checks the most common problems and offers a fix for each one it finds:

  • SteamCMD available, and the SteamCMD wrapper in /usr/bin/steamcmd.
  • Ownership in your home folder: files owned by root instead of your account. sudo csm setup-host --skip-deps fixes it.
  • Steam Runtime installed (SteamRT3), on systems that need it.
  • CS2 shared libs (libv8.so) present on each server.

Add --yes to apply all fixes without questions, or --server 2 to check one server. Without a terminal (for example from a script), doctor only applies fixes with --yes.

Logs

  • Server console log: csm logs 1 200, or the file in ~/logs/server-1.log.
  • csm's own log: ~/logs/csm.log. Each command also writes its own log file next to it.
  • csm logdir shows the log folder and the 10 latest command logs.
  • In the menu: Tools > View recent command logs.

To follow the log live:

tail -f ~/logs/csm.log

A server does not start

  1. Run it in the foreground to see the error:

    csm debug 1
  2. Try the other launcher. It prefers the libraries that come with CS2:

    csm start --alternate 1
  3. Run csm doctor.

To see how a server was really started, show the tmux start command and the running process:

tmux list-panes -a -F "#{session_name}: #{pane_start_command}" | grep cs2-1
ps auxww | grep '~/server-1/game/' | grep -v grep

libv8.so is missing

The server fails because libv8.so is not found. Check the game files and copy them to the server again:

csm fix-libv8 1

Use 0 for all servers. doctor offers the same fix.

Debian 13 and Ubuntu 25.04

On Debian 13 and newer, and Ubuntu 25.04 and newer, csm installs Steam Runtime (SteamRT3, Steam app 1628350) into ~/steamrt and starts the servers through it.

If it is missing, doctor offers to install it. To force Steam Runtime on or off on any system:

CSM_STEAMRT=1 csm restart    # always use Steam Runtime
CSM_STEAMRT=0 csm restart    # never use Steam Runtime

Set the same variable in the update monitor cron job, or it goes back to the default on the next update.

steamclient.so is missing

The server fails with a Steamworks or steamclient.so error. csm normally links this file during the install. To link it by hand:

mkdir -p ~/.steam/sdk64
ln -sf ~/.local/share/Steam/steamcmd/linux64/steamclient.so ~/.steam/sdk64/steamclient.so
csm restart

Game files are broken

Rebuild one server from master-install:

csm reinstall 2

Unable to locate package steamcmd

Run sudo csm install-deps. It turns on the apt source that has SteamCMD and tries again. See Install to do it by hand.

Other problems during install

  • Unsupported architecture: run uname -m. csm runs on x86_64 and arm64 only.
  • Downloads fail: check that the machine can reach GitHub and Steam over HTTPS. Check the proxy and the firewall.
  • Don't run csm as root or with sudo: run csm as the account that owns the servers, without sudo. Run sudo csm setup-host once first. Only setup-host, install-deps, self-update and cleanup-all take sudo.

On this page