setting up a SteamCMD server on Linux (SteamPipe - Application ID 2403)

Turbonium

Platinum Member
Mar 15, 2003
2,157
82
91
I tried posting on the official Steam forums (original thread), but they're not used much, and I'd like a helpful response as soon as possible, so I'm posting this here as well:

I am trying to setup a new server (on Linux) for The Ship using SteamCMD (The Ship was converted to SteamPipe some time ago).

When trying to open/run srcds_run (via Terminal), I get the following error:

Code:
Auto detecting CPU
Using SSE2 Optimised binary.
Auto-restarting the server on crash
Unable to find gameinfo.txt. Solutions:

1. Read http://www.valve-erc.com/srcsdk/faq.html#NoGameDir
2. Run vconfig to specify which game you're working on.
3. Add -game <path> on the command line where <path> is the directory that gameinfo.txt is in.
Unable to find gameinfo.txt. Solutions:

1. Read http://www.valve-erc.com/srcsdk/faq.html#NoGameDir
2. Run vconfig to specify which game you're working on.
3. Add -game <path> on the command line where <path> is the directory that gameinfo.txt is in.

Add "-debug" to the /home/main/the_ship/srcds_run command line to generate a debug.log to help with solving this problem
Thu Aug 1 05:23:09 EDT 2013: Server restart in 10 seconds

The provided link in the output above is broken, which makes it even more odd.

FYI: the GameInfo.txt file is just fine, leaving me even more confused. It is in the directory:

/home/main/the_ship/ship/

Any ideas on what's wrong?
 

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Maybe *nix Software or PC Gaming would be a better fit for your question, if you want a timely answer.
 

Turbonium

Platinum Member
Mar 15, 2003
2,157
82
91
Maybe *nix Software or PC Gaming would be a better fit for your question, if you want a timely answer.
I thought of posting in *nix Software, but wasn't sure.

Can a mod move this thread over to that forum?
 

Jodell88

Diamond Member
Jan 29, 2007
8,762
30
91
Try running via terminal:

Code:
srcds_run -debug

And post the results here. I'm not sure where the debug.log will go.
 

Turbonium

Platinum Member
Mar 15, 2003
2,157
82
91
Try running via terminal:

Code:
srcds_run -debug

And post the results here. I'm not sure where the debug.log will go.
Every 10 seconds, it says the following:

Code:
----------------------------------------------
CRASH: Fri Aug  2 22:10:50 EDT 2013
Start Line: ./srcds_i686 -debug -game cstrike
End of Source crash report
----------------------------------------------

Seems it's thinking the game is CS for some reason?
 
Last edited:

Jodell88

Diamond Member
Jan 29, 2007
8,762
30
91
Ok, after doing a bit more reading I've found out that each game has a srcds_run executable. Is that correct?

If that is indeed the case, call the srcds_run executable with the -debug parameter. So far the debug logs have been worthless. :/
 

Turbonium

Platinum Member
Mar 15, 2003
2,157
82
91
Ok, after doing a bit more reading I've found out that each game has a srcds_run executable. Is that correct?

If that is indeed the case, call the srcds_run executable with the -debug parameter. So far the debug logs have been worthless. :/
Can you clarify? I'm not sure I know what you mean. Didn't I already do this above? I literally entered the following into Terminal:

Code:
./srcds_run -debug

Here are the files in the same directory as srcds_run by the way:

shipds_steamgames.vdf
srcds_amd
srcds_486
srcds_686
steam_dll
 

Turbonium

Platinum Member
Mar 15, 2003
2,157
82
91
I also just tried the following:

Code:
./srcds_run -debug -game ship

And I get the following in debug.log:

Code:
Start Line: ./srcds_i686 -debug -game ship
End of Source crash report
 
Last edited:

Turbonium

Platinum Member
Mar 15, 2003
2,157
82
91
I'm scouring the Net trying to find a solution, but info is hard to find. :/

I might just run a Windows variant of SRCDS instead if this keeps up. Thing is, my system specs are limited, so I wanted better performance. :(
 
Last edited:

Jodell88

Diamond Member
Jan 29, 2007
8,762
30
91
Are you just posting the output of the terminal? It should be generating a file called debug.info that should have more detailed information in it. If it only contains the two lines that you posted above it would not help since it does not say what is wrong.