SteamCMD and Download Timeouts

[Jodian]

Good day!

Does anyone know of a way to supress SteamCMD from timing out when it's actually working and downloading an item? I've written a very extensive script to keep my Ark server (and it's mods) updated, and it works beautifully with one exception.

One of the mods (Ark Advanced) is about 1.3GB in size. My dedicated server has an extremely fast internet connection but even it is unable to complete this download before the SteamCMD service times out. I also can't seem to find any way to "resume" mod downloads like you can with games.

I know a workaround would be to download the mod in the client and then copy it over to the server, but that kind of defeats the purpose of only installing the dedicated server in the first place.

Anyone have any ideas?

[Jodian]

Actually I think I figured it out... I was able to add "validate" to the end of the mod update and it seems to have resumed the mod download. Just have to repeat that process in my script a few times, like so;

workshop_download_item 346110 572277026
workshop_download_item 346110 572277026 validate
workshop_download_item 346110 572277026 validate

It's a messy way to do it, as you might end up validating the mod a few times after it's fully downloaded, but it's better than NOT having the full mod downloaded.

P.S. My first line doesn't include "validate" because my script wipes the mods from both the temp download folder and the Ark server before updating. Ensures the mods are installed cleanly and there are never any orphaned files.

[Darwin G.]

hh

[Mach2Infinity]

@ViperZeroOne, thank you for sharing the workaround using validae twice.

I use the below format:

"steamcmd.exe" +login ****** ****** +set_steam_guard_code #### +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 450814997" validate +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 450814997" validate +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 497661914" validate +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 497661914" validate

Repeating it twice is enough to save the download so when it invariably times out, you can resume from where you left off rather than always starting from scratch and getting no where.

Apparently the time ouits are due to TTL (Time-To-Live) packets expiring around the 1GB mark.:

Ark Server Manager thread[arkservermanager.freeforums.net]

[Jack the Smack]

Originally posted by Mach2Infinity:

@ViperZeroOne, thank you for sharing the workaround using validae twice.

I use the below format:

"steamcmd.exe" +login ****** ****** +set_steam_guard_code #### +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 450814997" validate +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 450814997" validate +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 497661914" validate +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 497661914" validate

Repeating it twice is enough to save the download so when it invariably times out, you can resume from where you left off rather than always starting from scratch and getting no where.

Apparently the time ouits are due to TTL (Time-To-Live) packets expiring around the 1GB mark.:

Ark Server Manager thread[arkservermanager.freeforums.net]

You only need to put validate and force_install_dir once.

[BurgerFanMan]

For some reason I'm having this problem in much smaller files, less than a megabyte each.

[Raka_suci]

Originally posted by BurgerFanMan:

For some reason I'm having this problem in much smaller files, less than a megabyte each.

just like you, i tried to download this addon Disguise SWEP and yeah.....timeout

[Xentor]

I'm pretty sure this happens when you do log into an anonymous account instead of your main account. All my addons started downloading successfully after logging into my actual steam account.

[Pill]

Originally posted by Mach2Infinity:

@ViperZeroOne, thank you for sharing the workaround using validae twice.

I use the below format:

"steamcmd.exe" +login ****** ****** +set_steam_guard_code #### +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 450814997" validate +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 450814997" validate +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 497661914" validate +force_install_dir E:\Apps\Steam +"workshop_download_item 107410 497661914" validate

Repeating it twice is enough to save the download so when it invariably times out, you can resume from where you left off rather than always starting from scratch and getting no where.

Apparently the time ouits are due to TTL (Time-To-Live) packets expiring around the 1GB mark.:

Ark Server Manager thread[arkservermanager.freeforums.net]

Definitely saved me after an hour or so of searching. All i did was
open the Steam CMD
force_install_dir
copy the address from the cmd<steamapps<workshop<downloads<(press your game code folder I.E.311210) right click the number from the line copy address
so it looked like
force_install_dir C:\Users\John Smith\Downloads\cmd\steamapps\workshop\downloads\311210
press enter
then workshop_download_item 311210 2112576356
enter and then if that timeouts
workshop_download_item 311210 2112576356 validate
then just
workshop_download_item 311210 2112576356 if it times out keep pasting until it says success
then you got what you wanted to download

[Jodian]

Originally posted by Pill:

Definitely saved me after an hour or so of searching. All i did was
open the Steam CMD
force_install_dir
copy the address from the cmd<steamapps<workshop<downloads<(press your game code folder I.E.311210) right click the number from the line copy address
so it looked like
force_install_dir C:\Users\John Smith\Downloads\cmd\steamapps\workshop\downloads\311210
press enter
then workshop_download_item 311210 2112576356
enter and then if that timeouts
workshop_download_item 311210 2112576356 validate
then just
workshop_download_item 311210 2112576356 if it times out keep pasting until it says success
then you got what you wanted to download

Please check dates, this is an EXTREMELY old message thread from back when Ark Server Manager still had some issues. Today it's an extremely efficient way to manage your Ark server and does everything you need, including mod update and validation.

[WalkerFamily]

Originally posted by Jodian:

Please check dates, this is an EXTREMELY old message thread from back when Ark Server Manager still had some issues. Today it's an extremely efficient way to manage your Ark server and does everything you need, including mod update and validation.

Steam CMD *still* has the timeout issue on any mod larger than 1GB all these years later. This thread's workaround is still required for very large mods, such as Primal Fear, etc. Ark Server Manager will indeed timeout on large mod installs or updates today, as it still uses Steam CMD behind the scenes.

[Jodian]

Originally posted by WalkerFamily:

Steam CMD *still* has the timeout issue on any mod larger than 1GB all these years later. This thread's workaround is still required for very large mods, such as Primal Fear, etc. Ark Server Manager will indeed timeout on large mod installs or updates today, as it still uses Steam CMD behind the scenes.

Pretty sure it depends on your internet speed... I run 3 servers with about 35-40 mods on each, total size of the mods per server is about 7-9GB, and ASM has absolutely no issues keeping them updated every morning at 4am.

[RPG Gamer Man]

Originally posted by Jodian:

Originally posted by WalkerFamily:

Steam CMD *still* has the timeout issue on any mod larger than 1GB all these years later. This thread's workaround is still required for very large mods, such as Primal Fear, etc. Ark Server Manager will indeed timeout on large mod installs or updates today, as it still uses Steam CMD behind the scenes.

Pretty sure it depends on your internet speed... I run 3 servers with about 35-40 mods on each, total size of the mods per server is about 7-9GB, and ASM has absolutely no issues keeping them updated every morning at 4am.

Be also aware that ISP's also put limits on how much data you can use before "slowing" down your internet. It depends on which isp you use, but most have this in their TOS . You can read about it more here:

https://www.avast.com/c-how-to-stop-isp-throttling

[WalkerFamily]

Originally posted by Jodian:

Pretty sure it depends on your internet speed... I run 3 servers with about 35-40 mods on each, total size of the mods per server is about 7-9GB, and ASM has absolutely no issues keeping them updated every morning at 4am.

Originally posted by RPG Gamer Man:

Be also aware that ISP's also put limits on how much data you can use before "slowing" down your internet. It depends on which isp you use, but most have this in their TOS . You can read about it more here:

https://www.avast.com/c-how-to-stop-isp-throttling

It's not an internet speed issue, its a very well known and still unfixed steamcmd.exe issue where any *single* mod larger than 1GB will timeout during download (Valve set steamcmd.exe's TTL too low and haven't fixed it all these years later). You *have* to use "validate" on each successive timeout to continue the download until correct completion. This isn't about the total size of all your mods either, its an issue with any ONE mod that is larger than 1GB in size... such as Primal Fear, Extinction Core, etc.

I have Telus PureFiber 1Gbps service (both up and down) and steamcmd.exe timeouts on 1GB+ mod updates on this service as it will on a 20Mbps or any other service.

If you run servers with 1GB+ sized single mods, you absolutely must run your own update script for these large mods as ASM won't handle them either (as I said earlier it also uses steamcmd.exe in the background).

[Jodian]

Originally posted by WalkerFamily:

It's not an internet speed issue, its a very well known and still unfixed steamcmd.exe issue where any *single* mod larger than 1GB will timeout during download (Valve set steamcmd.exe's TTL too low and haven't fixed it all these years later). You *have* to use "validate" on each successive timeout to continue the download until correct completion. This isn't about the total size of all your mods either, its an issue with any ONE mod that is larger than 1GB in size... such as Primal Fear, Extinction Core, etc.

I have Telus PureFiber 1Gbps service (both up and down) and steamcmd.exe timeouts on 1GB+ mod updates on this service as it will on a 20Mbps or any other service.

If you run servers with 1GB+ sized single mods, you absolutely must run your own update script for these large mods as ASM won't handle them either (as I said earlier it also uses steamcmd.exe in the background).

Well, as someone who (as stated) downloads single mods in excess of 1GB all the time using ASM, thus SteamCMD, I can clearly tell you that the issue doesn't happen (to me) anymore. Yes, I'm talking single mods that are over 1GB in size. The fact it's still happening to you could mean there's something beyond the simple explanation that "Oh, it's a SteamCMD problem". That said, I can only tell you that. I don't have enough invested in this conversation to provide you with actual evidence. So believe it or not, makes no difference to me.

[Raka_suci]

So, Any fixes? i tired reading all this thread