-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SteamCMD timed out waiting for user info #6692
Comments
Same issue here, using anonymous login. connection_log.txt: (Not using ipv6 at all / no plans on using ipv6) appinfo_log.txt: Thats all useful information I can get from the logs. Deleting appinfo.vdf & packageinfo.vdf from /appcache/ before every single steamcmd login helped in the past, but not anymore. |
Got the same issue for a CS:GO server:
I had the issue before, but back then I just removed the "Steam" and the ".steam" folder in the home directory before updating the game, but right now that does not seem to fix it. |
Same here. Using this docker image: didstopia/7dtd-server Last Update it helped to delete the .steam and Steam folders. Now it even fails on the waiting for user info...
Interesting. If I exec into the container with /bin/bash I always get the user info error. When starting as planned it will hang at AppInfo update. |
Tried the official steamcmd docker container: same result ... Just update/upgrad/dist-upgrade my system and still the same. |
An update to Debian 10 (from Debian 9) fixed the issue for me. |
Sadly thats not really an option for me, because my server is already running on Buster. |
Using: CentOS Linux release 8.0.1905 (Core).
This used to be my solution also but now it doesn't seem to work. |
Can confirm. Works just fine on CentOS 7 but consistently fails on CentOS 8. For a while, the install itself worked, and all consecutive updates failed. For a day or two, I haven't even been able to even install anything. |
Tried to disable SELinux, disable firewalld, run as root, install a bunch of packages, add a lot of folders to LD_LIBRARY_PATH, nope, nothing helps. |
So the dudes apparently think those are the only kernels in existence. C8 runs on
And yes, those counters do increase:
So maybe #6326 isn't fixed after all. |
OMG what a mess. I actually managed to solve it but it's ridiculous. Details here: https://wiki.centos.org/Manuals/ReleaseNotes/CentOSStream TLDR due to CentOS 8 bug kernels weren't receiving updates. That's why this bug in the kernel was left unpatched. Solution:
Then it's quite a bump:
Aaand that's it, steamcmd immediately starts to work. |
Thank you brotha |
Can confirm, on Debian 9, an update last night and a reboot this morning did not fix. |
Is there a similar solution for Debian systems? |
I just did an |
On my Buster installation the problem still exists: |
Update to Debian 10, but the problem still exists too |
Same issue has been happening at random on many of my nodes regardless of location, region, routing or kernel version for the past 2-3 months. Debian here as well. Everything is operating behind our ISP and there aren't any issues between our networks. Valve NOC confirmed that all looks fine a month ago. A temporary fix was to login to a persistent steam account, log out then log into anonymous (some games force that you are logged into anonymous to download content). On some isolated nodes, that isn't working any longer as of two to three days ago. Seems to have come right after the new debug information printed in SteamCMD a few days ago.
Anybody aware of any cache location for steamworks/steamcmd that I can try clearing? Logging into any persistent accounts has no issues at all. This usually irons itself out eventually but I would appreciate if you had some useful information to expedite it. |
This is in fact not OK. |
Agreed. |
Same here |
got the same issue with two different accounts on the same linux host:
Nothing interesting in the logs, maybe I should enable debug/trace logs (how?) |
Your system information
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Steps for reproducing this issue:
Hey Steamsupport!
I like to install 7DaystoDie to my Debian Linux Server, i have a running server since years,but after update 17 in may i cannot install the Server anymore.
I login to Steamcmd but there is a timeout:
Steam>login myAccount
Logging in user 'myAccount' to Steam Public ...
Logged in OK
Waiting for user info...FAILED. Timed out.
OK
Whats can i do, this is not a Game-Error, its from Steamcmd
The text was updated successfully, but these errors were encountered: