mirror of
https://github.com/GameServerManagers/LinuxGSM.git
synced 2026-04-25 14:15:59 +03:00
[GH-ISSUE #1572] Unable to get CS:GO running #1228
Labels
No labels
Atomic
Epic
cannot reproduce
command: backup
command: console
command: debug
command: details
command: fast-dl
command: install
command: mods
command: monitor
command: post-details
command: restart
command: send
command: start
command: stop
command: update
command: update-lgsm
command: validate
command: wipe
distro: AlmaLinux
distro: Arch Linux
distro: CentOS
distro: Debian
distro: Fedora
distro: RedHat
distro: Rocky Linux
distro: Ubuntu
distro: openSUSE
engine: goldsrc
engine: source
game: 7 Days to Die
game: ARMA 3
game: Ark: Survival Evolved
game: Assetto Corsa
game: Avorion
game: BATTALION: Legacy
game: Barotrauma
game: Battalion 1944
game: Battlefield 1942
game: Black Mesa: Deathmatch
game: Blade Symphony
game: Call of Duty 2
game: Call of Duty 4
game: Call of Duty: United Offensive
game: Counter-Strike 1.6
game: Counter-Strike 2
game: Counter-Strike: Global Offensive
game: Counter-Strike: Source
game: Day of Infamy
game: Dayz
game: Death Match Classic
game: Don't Starve Together
game: ET: Legacy
game: Eco
game: Factorio
game: Factorio
game: Garry's Mod
game: Half-Life
game: Hurtword
game: Insurgecy
game: Insurgecy
game: Insurgency: Sandstorm
game: Just Cause 3
game: Killing Floor
game: Killing Floor 2
game: Left 4 Dead 2
game: Minecraft
game: Minecraft Bedrock
game: Mordhau
game: Multi Theft Auto
game: Mumble
game: Natural Selection 2
game: No More Room in Hell
game: Pavlov VR
game: Post Scriptum
game: Project Zomboid
game: Quake 3
game: QuakeWorld
game: Red Orchestra: Ostfront 41-45
game: Return to Castle Wolfenstein
game: Rising World
game: Rust
game: San Andreas Multiplayer
game: Satisfactory
game: Soldat
game: Soldier of Fortune 2
game: Squad
game: Squad 44
game: Starbound
game: Stationeers
game: Sven Co-op
game: Team Fortress 2
game: Teamspeak 3
game: Teeworlds
game: Terraria
game: The Front
game: Unreal Tournament 2004
game: Unreal Tournament 3
game: Unreal Tournament 99
game: Unturned
game: Valheim
game: Wurm Unlimited
game: Zombie Master Reborn
game: label missing
good first issue
help wanted
info: alerts
info: dependency
info: docker
info: docs
info: email
info: query
info: steamcmd
info: systemd
info: tmux
info: website
info: website
needs more info
outcome: duplicate
outcome: issue resolved
outcome: issue resolved
outcome: issue unresolved
outcome: pr accepted
outcome: pr rejected
outcome: unconfirmed
outcome: wontfix
outcome: wrong forum
potential-duplicate
priority
pull-request
type: bug
type: feature
type: feature
type: feature request
type: game server request
type: refactor
waiting response
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/LinuxGSM#1228
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @naxIO on GitHub (Aug 13, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1572
Hi,
I tried over several days with several clean attempts (each time from scratch) to get my CS:GO Server running.
I'm always getting
also going further I can see
Is this a steam issue? I wonder why it always enters the
state 0x202To be sure I waited between the attempts and always re-installed from scratch (wiped entire folders).Any ideas?
Thanks
@cedarlug commented on GitHub (Aug 13, 2017):
Disk space would be the most common issue.
Before you respond with "OF COURSE I HAVE ENOUGH SPACE", please note that you have not posted the output from ./csgoserver postdetails.
See the REQUIREMENTS stanza in https://github.com/GameServerManagers/LinuxGSM/wiki/Support
@Traace commented on GitHub (Aug 14, 2017):
Yes, its a issue with the Steam Client. Happens even without LinuxGSM. We have enough disk space, minimum are 8gb, we got 14gb left. Way enough for such a gameserver.
Gameserver: CS:GO
Postdetails Link: https://hastebin.com/domeluxono
Output Error: "Error! App '740' state is 0x202 after update job"
Hardware:
OS: ESXi 6.5 (5969303)
CPU: 4x Six-Core AMD Opteron(tm) Processor 8431 ->4Cores on GameserverVM-OS
RAM: 128GB DDR2 ECC -> 4GB on GameserverVM-OS
Storage: Couple TB's SATA&SAS (No RAID) @ HP Smart Array P410
GameserverVM-OS: Fedora 26 Server
But also tried with a Ubuntu Server @ 100GB Storage, e.g. 85GB ~ free after install. Still the same error message.
@naxIO commented on GitHub (Aug 15, 2017):
Okay will check space, might be an issue with temp. extraction of install data. Will report back.
@naxIO commented on GitHub (Aug 18, 2017):
Gotta confirm what @Traace is saying here. I have enough disk space, the error is the same. Now after some days passed I'm not sure if this still could be a temp. Steam issue.
Is it linked to the new Tokens maybe?
My error
Error! App '740' state is 0x202 after update job.is all over the internet, the common solution is retry spam and be lucky. So it seems like generic random download error.@naxIO commented on GitHub (Aug 26, 2017):
bump. problem persists. anyone any idea? thanks
@naxIO commented on GitHub (Aug 26, 2017):
Okay it was crazy more diskspace (30gb+) to have. Maybe would be nice to add a warning and precheck to LGSM to address this before installation attempt.
@MarkTwoFive commented on GitHub (Aug 26, 2017):
I think there was an issue/PR about disk space checks but I don't know what happened to that idea...
@Traace commented on GitHub (Sep 17, 2017):
The issue is still not fixed. Why is it labeled as resolved? Thats not correct.
This Bug isn't fixable by LinuxGSM but not "resolved" here either. A correct tag would be like "Not fixable"
@dgibbs64 Please set a proper tag.
Maybe LinuxGSM should also mention that SteamCMD is not compatible with ESXi Systems on their Website in order to prevent such "bug" reports again. ESXi Thin Provisioning feature let SteamCMD run into that issue
@lock[bot] commented on GitHub (Sep 17, 2018):
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.