starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #2619] [BUG] SteamCMD Download Unnecessary Files #1900

New issue

Closed

opened 2026-02-27 02:59:41 +03:00 by kerem · 22 comments

kerem commented

2026-02-27 02:59:41 +03:00

Owner

Originally created by @BlackYuzia on GitHub (Nov 27, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2619

User Story

As a user, I want get update server, but I desired what LGSM (steamcmd) was download only updated files so that will require less space than now.

Basic info

Distro: [Debian 9]
Game: [CS:GO]
Command: [Update]

Further Information

Sometimes (50/50), when (CSGO) server was start update.
SteamCMD download unneeded files (what didn't get updates)
For example: This is a full list of maps.

Also, since it (SteamCMD) downloads these unnecessary files, if there is not enough space,
the servers may not update at all. This is bad.

To Reproduce

Steps to reproduce the behaviour:

Download and setup server
Wait update for server
Start update for server
Check steamapps > downloading > 740 > csgo > maps folder // Sometimes, u will get unnecessary files what didn't update but downloaded.

Expected behaviour

I expected was on start update of server, LGSM (maybe this is trouble in SteamCMD, I don't sure) was download ONLY updated files. I didn't use validate option for download all files (example: maps or etc)

If u need more info - call me.
Maybe other users have the same troubles.

Originally created by @BlackYuzia on GitHub (Nov 27, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2619 ## User Story As a **user**, I want **get update server, but I desired what LGSM (steamcmd) was download only updated files** so that **will require less space than now**. ## Basic info * Distro: [**Debian 9**] * Game: [**CS:GO**] * Command: [**Update**] ## Further Information Sometimes (50/50), when (CSGO) server was start update. SteamCMD download **unneeded file**s (what didn't get updates) For example: This is a full list of maps. ![https://cdn.discordapp.com/attachments/442265055220858880/649157871073886218/unknown.png](https://cdn.discordapp.com/attachments/442265055220858880/649157871073886218/unknown.png) Also, since it (SteamCMD) downloads these unnecessary files, if there is not enough space, the servers may not update at all. This is bad. ## To Reproduce Steps to reproduce the behaviour: 1. Download and setup server 2. Wait update for server 3. Start update for server 4. Check `steamapps > downloading > 740 > csgo > maps` folder // Sometimes, u will get **unnecessary files** what didn't update but downloaded. ## Expected behaviour I expected was on start update of server, LGSM (maybe this is trouble in SteamCMD, I don't sure) was download ONLY updated files. I didn't use `validate` option for download all files (example: maps or etc) If u need more info - call me. Maybe other users have the same troubles.

kerem

2026-02-27 02:59:41 +03:00

closed this issue
added the
type: bug

info: steamcmd

game: Counter-Strike: Global Offensive

command: update
labels

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Nov 27, 2019):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.84. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Nov 27, 2019): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.84. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@Septembers commented on GitHub (Nov 27, 2019):

I acknowledge this issue.
On my dedicated server, 5-7 gigabytes are free. I can’t update the server through ./csgoserver update because absolutely all the maps are downloaded to the folder csgoserver/serverfiles/steamapps/downloading/740

@Septembers commented on GitHub (Nov 27, 2019): I acknowledge this issue. On my dedicated server, 5-7 gigabytes are free. I can’t update the server through ./csgoserver update because absolutely all the maps are downloaded to the folder csgoserver/serverfiles/steamapps/downloading/740

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Nov 27, 2019):

This looks like the sort of issue that Valve need to address

@dgibbs64 commented on GitHub (Nov 27, 2019): This looks like the sort of issue that Valve need to address

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@BlackYuzia commented on GitHub (Nov 27, 2019):

This looks like the sort of issue that Valve need to address

I hope it's not true.
Volvo and fixes... no, pls no...

@BlackYuzia commented on GitHub (Nov 27, 2019): > This looks like the sort of issue that Valve need to address I hope it's not true. Volvo and fixes... no, pls no...

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Nov 27, 2019):

Looking at the build history of CS:GO the size of the server has recently increased 2.19GB 9 days ago ( #7226006)
https://steamdb.info/app/740/history/

I would suggest that this might be the cause of the issue. My understanding is that SteamCMD will first download the files it needs into the steamcmd directory then copies them across to the serverfiles directory. This would cause the size of the game server to temporarily increase. Normaly this would be fine if the change is relatively small. However, if a big change happens (say 2GB) all at once this could cause an issue with servers that have limited storage.

Steam Database
Counter-Strike Global Offensive - Dedicated Server · AppID: 740
Steam Database record for Counter-Strike Global Offensive - Dedicated Server

@dgibbs64 commented on GitHub (Nov 27, 2019): Looking at the build history of CS:GO the size of the server has recently increased 2.19GB 9 days ago ( #7226006) https://steamdb.info/app/740/history/ I would suggest that this might be the cause of the issue. My understanding is that SteamCMD will first download the files it needs into the steamcmd directory then copies them across to the serverfiles directory. This would cause the size of the game server to temporarily increase. Normaly this would be fine if the change is relatively small. However, if a big change happens (say 2GB) all at once this could cause an issue with servers that have limited storage. <blockquote><img src="https://steamdb.info/static/logos/512px.png" width="48" align="right"><div><img src="/static/logos/vector_prefers_schema.svg" height="14"> Steam Database</div><div><strong><a href="https://steamdb.info/app/740/history/">Counter-Strike Global Offensive - Dedicated Server · AppID: 740</a></strong></div><div>Steam Database record for Counter-Strike Global Offensive - Dedicated Server</div></blockquote>

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Nov 29, 2019):

There are now three issues that appear to be the same. Please, can you post the output of ./csgoserver post-details

@dgibbs64 commented on GitHub (Nov 29, 2019): There are now three issues that appear to be the same. Please, can you post the output of `./csgoserver post-details`

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Nov 29, 2019):

#2624 #2623 #2619

@dgibbs64 commented on GitHub (Nov 29, 2019): #2624 #2623 #2619

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@BlackYuzia commented on GitHub (Nov 29, 2019):

@dgibbs64

./csgoserver post-details

https://hastebin.com/owesececuf

hastebin

@BlackYuzia commented on GitHub (Nov 29, 2019): @dgibbs64 > ./csgoserver post-details https://hastebin.com/owesececuf <blockquote><div><strong><a href="https://hastebin.com/owesececuf">hastebin</a></strong></div></blockquote>

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Nov 29, 2019):

@BlackYuzia Looking at your output it appears you only have 2.7GB free space which would not be enough to handle any large update (as happened a few days ago). So basically there is not enough breathing room on your server to handle updates. I will wait the output of others and if there is a simular issue it may confirm that is the problem.

The problem only occurring on CSGO servers.

There are plans to record game server size to give recommendations on disk requirements in the future.

@dgibbs64 commented on GitHub (Nov 29, 2019): @BlackYuzia Looking at your output it appears you only have 2.7GB free space which would not be enough to handle any large update (as happened a few days ago). So basically there is not enough breathing room on your server to handle updates. I will wait the output of others and if there is a simular issue it may confirm that is the problem. The problem only occurring on CSGO servers. There are plans to record game server size to give recommendations on disk requirements in the future.

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@Septembers commented on GitHub (Nov 29, 2019):

@BlackYuzia Looking at your output it appears you only have 2.7GB free space which would not be enough to handle any large update (as happened a few days ago). So basically there is not enough breathing room on your server to handle updates. I will wait the output of others and if there is a simular issue it may confirm that is the problem.

The problem only occurring on CSGO servers.

There are plans to record game server size to give recommendations on disk requirements in the future.

Hi. I had 6GB of free disk space, but I could not install the update, which took up 250 megabytes. Because with ./csgoserver update - absolutely all default maps were downloaded (which I do not need). because of this there is not enough disk space.
Is it possible to make a setting in which default (standart) maps will not load during the update?

There is simply a problem, sometimes the server updates normally, and sometimes it wants to download all the standard maps.

if the problem recurs, I will write to you.

sorry for my eng

@Septembers commented on GitHub (Nov 29, 2019): > @BlackYuzia Looking at your output it appears you only have 2.7GB free space which would not be enough to handle any large update (as happened a few days ago). So basically there is not enough breathing room on your server to handle updates. I will wait the output of others and if there is a simular issue it may confirm that is the problem. > > The problem only occurring on CSGO servers. > > There are plans to record game server size to give recommendations on disk requirements in the future. Hi. I had 6GB of free disk space, but I could not install the update, which took up 250 megabytes. Because with ./csgoserver update - absolutely all default maps were downloaded (which I do not need). because of this there is not enough disk space. Is it possible to make a setting in which default (standart) maps will not load during the update? There is simply a problem, sometimes the server updates normally, and sometimes it wants to download all the standard maps. if the problem recurs, I will write to you. sorry for my eng

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Nov 29, 2019):

@Septembers the update may have only taken up 250MB more in serverfiles but depending upon the files that have changed it may have meant SteamCMD needs to download several GB worth of files to replace existing files.

For example, if a map that's 300MB file has increased by 20MB SteamCMD will still have to download the whole 320MB updated file and then replace it. If an update changes a whole bunch of files that are large SteamCMD may have to download several GB worth of files to replace the existing files. It appears that SteamCMD downloads the whole update into a cache before applying it to serverfiles. This would balloon the disk space required drastically while the update is being downloaded.

Looking at the recent update history of CS:GO it appears that most of the maps have been updated so I think the extra files you are seeing are actually required in this instance.

This is my understanding of how it works but I may be wrong about this. When we do start releasing recommendations or disk space I will be taking this sort of issue into account and add a % extra.

@dgibbs64 commented on GitHub (Nov 29, 2019): @Septembers the update may have only taken up 250MB more in serverfiles but depending upon the files that have changed it may have meant SteamCMD needs to download several GB worth of files to replace existing files. For example, if a map that's 300MB file has increased by 20MB SteamCMD will still have to download the whole 320MB updated file and **_then_** replace it. If an update changes a whole bunch of files that are large SteamCMD may have to download several GB worth of files to replace the existing files. It appears that SteamCMD downloads the whole update into a cache before applying it to serverfiles. This would balloon the disk space required drastically while the update is being downloaded. Looking at the recent update history of CS:GO it appears that most of the maps have been updated so I think the extra files you are seeing are actually required in this instance. This is my understanding of how it works but I may be wrong about this. When we do start releasing recommendations or disk space I will be taking this sort of issue into account and add a % extra.

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@CatRuby commented on GitHub (Nov 29, 2019):

Обновление: фатально: update_steamcmd.sh выход с кодом: 1 #2623

./csgoserver postdetails

https://hastebin.com/utulazodaf

hastebin

@CatRuby commented on GitHub (Nov 29, 2019): Обновление: фатально: update_steamcmd.sh выход с кодом: 1 #2623 ./csgoserver postdetails https://hastebin.com/utulazodaf <blockquote><div><strong><a href="https://hastebin.com/utulazodaf">hastebin</a></strong></div></blockquote>

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@CatRuby commented on GitHub (Nov 29, 2019):

I also decided to provide
./csgoserver postdetails
from a server that is updated without problems, it is on the same hard drive, on the same PC, but under a different user. There were no problems with automatic updating on this server, on all others there were
https://hastebin.com/xefitesada

hastebin

@CatRuby commented on GitHub (Nov 29, 2019): I also decided to provide ./csgoserver postdetails from a server that is updated without problems, it is on the same hard drive, on the same PC, but under a different user. There were no problems with automatic updating on this server, on all others there were https://hastebin.com/xefitesada <blockquote><div><strong><a href="https://hastebin.com/xefitesada">hastebin</a></strong></div></blockquote>

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@Septembers commented on GitHub (Nov 30, 2019):

@Septembers the update may have only taken up 250MB more in serverfiles but depending upon the files that have changed it may have meant SteamCMD needs to download several GB worth of files to replace existing files.

For example, if a map that's 300MB file has increased by 20MB SteamCMD will still have to download the whole 320MB updated file and then replace it. If an update changes a whole bunch of files that are large SteamCMD may have to download several GB worth of files to replace the existing files. It appears that SteamCMD downloads the whole update into a cache before applying it to serverfiles. This would balloon the disk space required drastically while the update is being downloaded.

Looking at the recent update history of CS:GO it appears that most of the maps have been updated so I think the extra files you are seeing are actually required in this instance.

This is my understanding of how it works but I may be wrong about this. When we do start releasing recommendations or disk space I will be taking this sort of issue into account and add a % extra.

I have 8 CS: GO servers. Somewhere normally updated, but somewhere not. Therefore, I am confused.

@Septembers commented on GitHub (Nov 30, 2019): > @Septembers the update may have only taken up 250MB more in serverfiles but depending upon the files that have changed it may have meant SteamCMD needs to download several GB worth of files to replace existing files. > > For example, if a map that's 300MB file has increased by 20MB SteamCMD will still have to download the whole 320MB updated file and **_then_** replace it. If an update changes a whole bunch of files that are large SteamCMD may have to download several GB worth of files to replace the existing files. It appears that SteamCMD downloads the whole update into a cache before applying it to serverfiles. This would balloon the disk space required drastically while the update is being downloaded. > > Looking at the recent update history of CS:GO it appears that most of the maps have been updated so I think the extra files you are seeing are actually required in this instance. > > This is my understanding of how it works but I may be wrong about this. When we do start releasing recommendations or disk space I will be taking this sort of issue into account and add a % extra. I have 8 CS: GO servers. Somewhere normally updated, but somewhere not. Therefore, I am confused.

kerem commented

2026-02-27 02:59:41 +03:00

Author

Owner

@CatRuby commented on GitHub (Dec 4, 2019):

Today the error repeated, 1 out of 7 servers were updated (
On everyone else, here's a mistake
05: 03: 06.160 csgoserver: UPDATE: FATAL: Checking remote build
05: 03: 06.164 csgoserver: UPDATE: FATAL: update_steamcmd.sh exiting with code: 1

@CatRuby commented on GitHub (Dec 4, 2019): Today the error repeated, 1 out of 7 servers were updated ( On everyone else, here's a mistake 05: 03: 06.160 csgoserver: UPDATE: FATAL: Checking remote build 05: 03: 06.164 csgoserver: UPDATE: FATAL: update_steamcmd.sh exiting with code: 1

kerem commented

2026-02-27 02:59:42 +03:00

Author

Owner

@CatRuby commented on GitHub (Dec 4, 2019):

I ran the ./csgoserver ul command now and saw that many functions had been updated over the past few days, including Monitor and update, maybe the problem has already been solved, but I'm not sure if I can somehow check without waiting for the valve to update?

@CatRuby commented on GitHub (Dec 4, 2019): I ran the ./csgoserver ul command now and saw that many functions had been updated over the past few days, including Monitor and update, maybe the problem has already been solved, but I'm not sure if I can somehow check without waiting for the valve to update?

kerem commented

2026-02-27 02:59:42 +03:00

Author

Owner

@CatRuby commented on GitHub (Dec 5, 2019):

another update in cs go and again 1 out of 7 was updated, I ran the command ./csgoserver postdetails for both servers. Which is updated itself and for one that is not

A server that updates without problems
https://hastebin.com/peroyequqa

A server that is having problems updating
https://hastebin.com/keqequkebe
Hope this helps

hastebin

@CatRuby commented on GitHub (Dec 5, 2019): another update in cs go and again 1 out of 7 was updated, I ran the command ./csgoserver postdetails for both servers. Which is updated itself and for one that is not A server that updates without problems https://hastebin.com/peroyequqa A server that is having problems updating https://hastebin.com/keqequkebe Hope this helps <blockquote><div><strong><a href="https://hastebin.com/peroyequqa">hastebin</a></strong></div></blockquote> <blockquote><div><strong><a href="https://hastebin.com/keqequkebe">hastebin</a></strong></div></blockquote>

kerem commented

2026-02-27 02:59:42 +03:00

Author

Owner

@CatRuby commented on GitHub (Dec 6, 2019):

I decided to attach the csgoserver-script logs of two servers, 1vs1 which is updated without problems, Pub which is experiencing problems. Maybe someone will see a solution to the problem
logs 1vs1.log
logs pub.txt

@CatRuby commented on GitHub (Dec 6, 2019): I decided to attach the csgoserver-script logs of two servers, 1vs1 which is updated without problems, Pub which is experiencing problems. Maybe someone will see a solution to the problem [logs 1vs1.log](https://github.com/GameServerManagers/LinuxGSM/files/3933664/logs.1vs1.log) [logs pub.txt](https://github.com/GameServerManagers/LinuxGSM/files/3933665/logs.pub.txt)

kerem commented

2026-02-27 02:59:42 +03:00

Author

Owner

@Septembers commented on GitHub (Dec 10, 2019):

Again, with csgoserver update, all maps are loaded

@Septembers commented on GitHub (Dec 10, 2019): ![image](https://user-images.githubusercontent.com/30748067/70526069-91833580-1b6a-11ea-8278-43682494c112.png) Again, with csgoserver update, all maps are loaded

kerem commented

2026-02-27 02:59:42 +03:00

Author

Owner

@Septembers commented on GitHub (Jan 7, 2020):

each update is the same. All default maps are uploaded to the server during the server update. on my other servers this is not what is wrong?

@Septembers commented on GitHub (Jan 7, 2020): ![Screenshot_1](https://user-images.githubusercontent.com/30748067/71882241-e6a86c00-3155-11ea-98a9-f60831b67afa.png) each update is the same. All default maps are uploaded to the server during the server update. on my other servers this is not what is wrong?

kerem commented

2026-02-27 02:59:42 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Mar 10, 2020):

I am currently unsure on the solution apart from ensuring you have a large enough hard disk to handle this. There is nothing I can directly do as it is a bug with SteamCMD which is maintained by Valve

@dgibbs64 commented on GitHub (Mar 10, 2020): I am currently unsure on the solution apart from ensuring you have a large enough hard disk to handle this. There is nothing I can directly do as it is a bug with SteamCMD which is maintained by Valve

kerem commented

2026-02-27 02:59:42 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 11, 2021):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Mar 11, 2021): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.