Skip to content
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

Open
DerMoki opened this issue Nov 15, 2019 · 22 comments
Open

SteamCMD timed out waiting for user info #6692

DerMoki opened this issue Nov 15, 2019 · 22 comments
Labels

Comments

@DerMoki
Copy link

DerMoki commented Nov 15, 2019

Your system information

  • up to date SteamCMD
  • Debian 9
  • Opted into Steam client beta?: [Yes]
  • Have you checked for system updates?: [Yes]

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

@kisak-valve kisak-valve changed the title 7 Days to Die - Serverinstall Debian 9 SteamCMD timed out waiting for user info Nov 15, 2019
@Claiyc
Copy link

Claiyc commented Dec 1, 2019

Same issue here, using anonymous login.

connection_log.txt:
IPv6 HTTP connectivity test (ipv6check-http.steamcontent.com / (...) - FAILURE (Invalid)
IPv6 UDP connectivity test (ipv6check-udp.steamcontent.com / (...) - TIMEOUT

(Not using ipv6 at all / no plans on using ipv6)

appinfo_log.txt:
[2019-12-01 18:01:02] RequestAppInfoUpdate: nNumAppIDs 1
[2019-12-01 18:01:02] Change number 0->7299591, apps: 0/0, packages: 0/0
[2019-12-01 18:01:02] Requesting 1 apps, 1 packages (meta data, 1024 prev attempts)
[2019-12-01 18:01:03] Requesting 1 apps, 1 packages (full data, 1024 prev attempts)
[2019-12-01 18:01:03] UpdatesJob: finished OK, nAppsUpdated 1 (3 KB), nPackagesUpdated 1 (60 KB)
[2019-12-01 18:01:03] Requesting 1034 apps, 0 packages (meta data, 1024 prev attempts)
[2019-12-01 18:01:04] Requested 551 access tokens, 38 received, 513 denied
[2019-12-01 18:01:05] Updated SHAs with 38 new access tokens
[2019-12-01 18:01:05] Downloaded 46 apps via HTTP, 1049 KB (243 KB compressed)
[2019-12-01 18:01:05] Requesting 988 apps, 0 packages (full data, 1024 prev attempts)
[2019-12-01 18:01:18] Starting async write /appcache/appinfo.vdf (791011 bytes)
[2019-12-01 18:01:32] RequestAppInfoUpdate: nNumAppIDs 1
[2019-12-01 18:02:02] UpdatesJob: finished Failure, nAppsUpdated 46 (1049 KB), nPackagesUpdated 0 (0 KB)
[2019-12-01 18:02:03] Starting async write /appcache/appinfo.vdf (791011 bytes)

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.

@Alth3r
Copy link

Alth3r commented Dec 4, 2019

Got the same issue for a CS:GO server:

[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...FAILED. Timed out.
OK
CWorkThreadPool::~CWorkThreadPool: work processing queue not empty: 1 items discarded.

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.

@struppinet
Copy link

struppinet commented Dec 5, 2019

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...

Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.
@sSteamCmdForcePlatformType linux
"@sSteamCmdForcePlatformType" = "linux"

Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...OK
force_install_dir /steamcmd/7dtd
app_update 294420 public validate
ERROR! Timed out waiting for AppInfo update.
quit
CWorkThreadPool::~CWorkThreadPool: work processing queue not empty: 2 items discarded.

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.

@struppinet
Copy link

struppinet commented Dec 5, 2019

Tried the official steamcmd docker container: same result ...
docker run -it --name=steamcmd cm2network/steamcmd bash

Just update/upgrad/dist-upgrade my system and still the same.
But after a reboot it is now working again!

@Claiyc
Copy link

Claiyc commented Dec 8, 2019

An update to Debian 10 (from Debian 9) fixed the issue for me.

@Alth3r
Copy link

Alth3r commented Dec 9, 2019

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.

@brysondev
Copy link

brysondev commented Dec 11, 2019

Using: CentOS Linux release 8.0.1905 (Core).
After updating/upgrading still cannot login anonymous.


[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...FAILED. Timed out.
OK

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.

This used to be my solution also but now it doesn't seem to work.

@bviktor
Copy link

bviktor commented Dec 11, 2019

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.

@bviktor
Copy link

bviktor commented Dec 11, 2019

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.

@bviktor
Copy link

bviktor commented Dec 11, 2019

#6326 (comment)

So the dudes apparently think those are the only kernels in existence. C8 runs on

$ uname -a
Linux c8test 4.18.0-80.11.2.el8_0.x86_64 #1 SMP Tue Sep 24 11:32:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

And yes, those counters do increase:

$ sudo nstat -az | grep -i wqueue
TcpExtTCPWqueueTooBig           43                 0.0

So maybe #6326 isn't fixed after all.

@bviktor
Copy link

bviktor commented Dec 11, 2019

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:

sudo dnf install -y centos-release-stream
sudo dnf -y update
sudo reboot

Then it's quite a bump:

$ uname -a
Linux c8test 4.18.0-147.6.el8.x86_64 #1 SMP Tue Oct 15 15:19:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Aaand that's it, steamcmd immediately starts to work.

@vega0
Copy link

vega0 commented Dec 12, 2019

Thank you brotha

@ravenx99
Copy link

Can confirm, on Debian 9, an update last night and a reboot this morning did not fix.
Upgrading kernel to linux-image-4.9.0-11-amd64, which doesn't seem to have been available last night, did fix.

@Alth3r
Copy link

Alth3r commented Dec 13, 2019

Is there a similar solution for Debian systems?

@ravenx99
Copy link

I just did an apt-get update && apt-get dist-upgrade to upgrade the kernel to the latest on Debian 9.

@Alth3r
Copy link

Alth3r commented Feb 5, 2020

On my Buster installation the problem still exists:
uname -a
Linux hostname 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux

@DerMoki
Copy link
Author

DerMoki commented Feb 12, 2020

Update to Debian 10, but the problem still exists too

@ertug2
Copy link

ertug2 commented Feb 24, 2020

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.

>
Steam>login anonymous

Connecting anonymously to Steam Public...Loaded client id: 18389946503649214524
Listening for IPv4 broadcast on: 27036
Logged in OK
Waiting for user info...FAILED. Timed out.
OK

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.

@VergilPrime
Copy link

This is in fact not OK.

@ertug2
Copy link

ertug2 commented Mar 3, 2020

Agreed.

@danielgran
Copy link

Same here

@nvtkaszpir
Copy link

nvtkaszpir commented Oct 31, 2022

got the same issue with two different accounts on the same linux host:

  • mine works, but always asks for password and steamguard code, I never managed to save my password on the host:
Logging in user 'nvt_k...' to Steam Public...FAILED (invalid cached credentials)

password: OK
Waiting for client config...OK
Waiting for user info...OK
app_update 223250  validate
 Update state (0x0) unknown, progress: 0.00 (0 / 0)
Error! App '223250' state is 0x204 after update job.
app_update 1290 verify
Success! App '1290' already up to date.
  • account of my friend at first logs (asks for steamguard) and after login it never prompts for password, but it responds very slowly and then shows timeouts when retreiving user data:

Logging in user 'bart..' to Steam Public...OK
Waiting for client config...ERROR! Timed out waiting for AppInfo update.
OK
Waiting for user info...FAILED (Timed out)
OK
app_update 223250  validate
ERROR! Timed out waiting for AppInfo update.

Nothing interesting in the logs, maybe I should enable debug/trace logs (how?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests