I hate to ask, but the initial SteamCMD setup doesn't have to be run as "root" or anything insecure like that - does it? HLDSUpdateTool never cared, and was perfectly happy running in it's own isolated little world (i.e. sub-dir's of the home directory for the user context is runs under is fine).

Couldn't set up the Steam Runtime. Are you running low on disk space?
Are you running out of diskspace?

Thanks for following-up.
178.97 GB available on a 500-GB drive.

On Thu, 2013/02/14 05:14 AM, John Drinkwater <[email protected]> wrote:

Couldn't set up the Steam Runtime. Are you running low on disk space?
Are you running out of diskspace?

---

Reply to this email directly or view it on GitHub:
https://github.com/ValveSoftware/steam-for-linux/issues/1701#issuecomment-13546831

You should run steamcmd.sh
steam.sh is there for backwards compatibility with server operators running the old method: STEAMEXE=steamcmd ./steam.sh

I'm trying to install Serious Sam 3 dedicated server. I have tried the Linux Game Server Managers method but that failed, so I tried to do things manually but that didn't work as well. I've searched like crazy but I can't find a solution.

I followed the SteamCMD instructions exactly, and I tried multiple times but when I try to launch the SS3 dedicated server, I just get the following error:

ldd: ./Sam3: No such file or directory
ldd: ./Sam3: No such file or directory
cat: /etc/debian_version: No such file or directory
LOG:  Loaded "/home/steam/steamcmd/ss_bfe/Bin/GameEnv_Steam.so".
INF:  GameEnv API: Steam
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
dlopen failed trying to load:
steamclient.so
with error:
libXrandr.so.2: cannot open shared object file: No such file or directory
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.

I tried following this step. No ~/.steam/ folder was created by default so I created the directory myself and then created the symlink:

mkdir -p ~/.steam/sdk32/
ln -s /home/steam/steamcmd/linux32/steamclient.so /home/steam/.steam/sdk32/steamclient.so

As expected, this didn't work either. There is a steamclient.so in the Serious Sam 3 install directory but that doesn't seem to matter. I ran steamclient.sh just to see what would happen and I received the same error messages as in the first post.

My setup is CentOS 7 64-bit, completely up to date.

It just seems like I can't run Steam headless. I don't understand what I'm doing wrong but I've tried both methods multiple times and I just can't launch the dedicated server. Same for Serious Sam HD: The Second Encounter. I was actually able to run CSS completely headless using Linux Game Server Managers although I couldn't connect to the server or see it in the server list when I launched the game locally. I don't think my provider is blocking any ports but even if they are, I don't think that should stop be from at least launching the SS3 dedicated server.

Can close this old case I suppose - since it surrounded getting things to work under CentOS, and given the new official stance/emphasis on Ubuntu: Reference

I know this is old, but I ran into a similar problem. Steam requires the 32 bit library.

sudo apt-get install lib32gcc1 fixed my diskspace issue on debian.

Its similar on CentOS according to the wiki:
https://developer.valvesoftware.com/wiki/SteamCMD#Linux.2FOS_X