search

ich777 / docker-steamcmd-server

Simple Dockerfile that installs steamcmd and a selected game server
127 stars 101 forks source link

TeamFortress2 branch, "Out of memory or address space. Texture quality setting may be too high. #27

Closed Sanlys closed 2 years ago

Sanlys commented 2 years ago

debug.log: ---------------------------------------------- CRASH: Sat 18 Jun 2022 03:03:56 AM PDT Start Line: ./srcds_linux -game tf -debug +sv_pure 1 +randommap +maxplayers 24 +sv_setsteamaccount -console +port 27015 End of Source crash report ---------------------------------------------- I have set the sv_setsteamaccount, just removed it from the log.

This error only occurs when mounting it to a storage, and also happens with the cm2network/tf2 image. The container only uses ~23 megabytes when this error occurs, and I have 16 gigs installed and over 13 gigabytes left, so that's not the issue.

image My configuration, the only thing not showing in the +sv_setsteamaccount variable.

Any thoughts, the share might be too slow? I've tried running it purely off cache (an ssd) and fully without cache, neither has any different effect.

Sanlys commented 2 years ago

image This might also be useful, these are the logs from the docker container. This comes every 10 seconds, when the server restarts.

ich777 commented 2 years ago

@Sanlys please use the real path to the game files for TeamFortress2 and not the FUSE path /mnt/user/appdata/…

If you have the files on the cache drive it is something like: /mnt/cache/appdata/… Also make sure that you have set the appdata share to use cache Only or Prefer in the Share Settings.

If you don‘t have the files on the Cache drive the path is something like /mnt/disk3/appdata/…

EDIT: There is a reason why I use /mnt/cache/appdata/… in my default templates. ;)

Sanlys commented 2 years ago

image Is this what you meant? I don't believe I have files on the cache drive, but I'm not sure how to see that. When I specify the path like this, I don't think it should use cache though. I still get the same error.

Sanlys commented 2 years ago

I noticed it's now using 1.7 gigs of memory, but still gives me the same error, so probably not enough.

ich777 commented 2 years ago

I noticed it's now using 1.7 gigs of memory, but still gives me the same error, so probably not enough.

Forget about those error, the server is actually running.

Just look into the Steam Server Browser and you will see that you now can connect.

The crashing happens because this specific game needs the real file path as mentioned above.

I always recommend to use the real file path because this saves CPU usage and causes less overhead. Also please notice rhat you only need to set the path to the game files to the real file path the SteamCMD path can be left at the FUSE file path.

Sanlys commented 2 years ago

It doesn't show up for me and I can't connect with the direct ip either. The logs say the server is restarting though, it doesn't look like a warning to me. Did I set the real file path wrong?

ich777 commented 2 years ago

May I ask why you are posting here and not posting on the official support thread on the forums?

I've now tried it and it works just fine: log.txt

screenshot

As you can see the server just shows up fine in the Steam Server Browser.

On what Unraid version are you? Please post your Diagnostics.

Sanlys commented 2 years ago

My bad, didn't know you had a support thread. I reset back to defaults, and it seems like it has to be stored on cache? That seems weird to me, but it does work. Thanks for your help

ich777 commented 2 years ago

@Sanlys please also make sure that you‘ve set you appdata share to use cache Only or Prefer.