It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
babarian34: A small summary would still be nice at the end of each verfication, but with the full logs in text format it works ok.
Depends. A summary (including also the failed filenames) is fine if there are only few errors, but if you have e.g. over 2500 games (like I do) which probably means tens of thousands of files, and you e.g. do some stupid mishap like verify the wrong directory or something, you'll get hundreds of pages of useless summary of thousands of mismatched or missing files. Or something like that.
Post edited March 24, 2024 by timppu
avatar
babarian34: A small summary would still be nice at the end of each verfication, but with the full logs in text format it works ok.
avatar
timppu: Depends. A summary (including also the failed filenames) is fine if there are only few errors, but if you have e.g. over 2500 games (like I do) which probably means tens of thousands of files, and you e.g. do some stupid mishap like verify the wrong directory or something, you'll get hundreds of pages of useless summary of thousands of mismatched or missing files. Or something like that.
Maybe a good enough summary at the end would just be a counter for the errors found.
Post edited March 25, 2024 by phaolo
I am getting a *lot* of 500 Server Errors today for some reason. Even had 1 game fail, and have had 2 or 3 retries multiple times. I wouldn't expect anything current to be causing that kind of strain, is there something I'm missing ?
avatar
Kalanyr: I am getting a *lot* of 500 Server Errors today for some reason. Even had 1 game fail, and have had 2 or 3 retries multiple times. I wouldn't expect anything current to be causing that kind of strain, is there something I'm missing ?
Maybe increased server load because of the Spring Sale? ;-)
avatar
timppu: Depends. A summary (including also the failed filenames) is fine if there are only few errors, but if you have e.g. over 2500 games (like I do) which probably means tens of thousands of files, and you e.g. do some stupid mishap like verify the wrong directory or something, you'll get hundreds of pages of useless summary of thousands of mismatched or missing files. Or something like that.
avatar
phaolo: Maybe a good enough summary at the end would just be a counter for the errors found.
I thought gogrepoc verify already does that, doesn't it? At least I recall there is a summary how many missing files or incorrect checksums...

I think what was requested here is that it would always list the incorrect/missing files at the summary.
avatar
timppu: I thought gogrepoc verify already does that, doesn't it? At least I recall there is a summary how many missing files or incorrect checksums...
I meant a simple error counter at the end of each command (if possible).
I don't recall about verify, since it's ages I don't run it.

avatar
timppu: I think what was requested here is that it would always list the incorrect/missing files at the summary.
I understood what it was requested, but I suggested another thing, since a long recap list wouldn't make sense in a searchable log.
Post edited March 25, 2024 by phaolo
avatar
Kalanyr: I am getting a *lot* of 500 Server Errors today for some reason. Even had 1 game fail, and have had 2 or 3 retries multiple times. I wouldn't expect anything current to be causing that kind of strain, is there something I'm missing ?
I get a couple every so often also. Recent occurrence. It's GOG.

As long as you have a robust retry policy, you should be fine.
avatar
Kalanyr: I am getting a *lot* of 500 Server Errors today for some reason. Even had 1 game fail, and have had 2 or 3 retries multiple times. I wouldn't expect anything current to be causing that kind of strain, is there something I'm missing ?
avatar
Geralt_of_Rivia: Maybe increased server load because of the Spring Sale? ;-)
Yeah, that's probably it. The fact there's been like 3 days total without a sale since November 2023 made me forget that this is actually one of the big ones.
It seems having only a couple of http retries is not enough? These are the settings that I am using now, just giving GOG much more breathing room with a minute long http_retry_delay (instead of hitting GOG every few seconds if it decides to not want to co-operate for a moment), but I also increased the retry count very high because it seems something like 3-5 is not necessarily enough, as I can see from the log below? (I increased the fetch delay which I guess makes the whole update process slower, but hoping it helps GOG also to co-operate.)

# HTTP request settings
HTTP_FETCH_DELAY = 3 # in seconds
HTTP_RETRY_DELAY = 60 # in seconds #If you reduce this such that the wait between the first and third try is less than 10 seconds, you're gonna have a bad time with the 503 error.
HTTP_RETRY_COUNT = 99
HTTP_TIMEOUT = 60

From the log. What is the difference between 500 Server Error and "Connection aborted"? 500 is a generic error that something went wrong (reason unknown, but not meaning the server is unreachable?), while "connection aborted" means the server actively refused the connection? Does it seem below that gogrepoc was able to get the needed data, after enough retries; ie. no title/file was missed?

07:40:33 | (2195 / 2583) fetching game details for the_humans_3...
07:40:43 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/1275264927.json (99 retries left) -- will retry in 60s...
07:41:50 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/1275264927.json (98 retries left) -- will retry in 60s...
07:42:59 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/1275264927.json (97 retries left) -- will retry in 60s...
07:44:06 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/1275264927.json (96 retries left) -- will retry in 60s...
07:45:13 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/1275264927.json (95 retries left) -- will retry in 60s...
07:46:39 | request failed: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) (99 retries left) -- will retry in 60s...
07:47:59 | request failed: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) (98 retries left) -- will retry in 60s...
07:48:59 | (2196 / 2583) fetching game details for the_i_of_the_dragon...
07:49:13 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/2000520059.json (99 retries left) -- will retry in 60s...
07:50:23 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/2000520059.json (98 retries left) -- will retry in 60s...
07:51:35 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/2000520059.json (97 retries left) -- will retry in 60s...
07:52:43 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/2000520059.json (96 retries left) -- will retry in 60s...
07:53:56 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/2000520059.json (95 retries left) -- will retry in 60s...
07:55:09 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/2000520059.json (94 retries left) -- will retry in 60s...
07:56:41 | request failed: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) (99 retries left) -- will retry in 60s...
07:58:00 | request failed: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) (98 retries left) -- will retry in 60s...
07:59:01 | (2197 / 2583) fetching game details for the_immortal...
07:59:06 | (2198 / 2583) fetching game details for the_incredible_adventures_of_van_helsing_complete_pack...
07:59:10 | (2199 / 2583) fetching game details for the_incredible_adventures_of_van_helsing_final_cut_game...
07:59:18 | request failed: 500 Server Error: Internal Server Error for url: https://www.gog.com/account/gameDetails/1448013298.json (99 retries left) -- will retry in 60s...
08:00:31 | (2200 / 2583) fetching game details for the_incredible_adventures_of_van_helsing_ii_complete_pack...
08:00:36 | saving manifest...
08:00:39 | saved manifest
08:00:39 | saving resume manifest...
08:00:40 | saved resume manifest
08:00:40 | (2201 / 2583) fetching game details for the_incredible_adventures_of_van_helsing_iii...
500 is a valid server response, it's just one that's informing you the server is having issues.
Connection aborted is an invalid response, eg the server sent something but the response is incomplete or invalid .
avatar
timppu: It seems having only a couple of http retries is not enough? These are the settings that I am using now, just giving GOG much more breathing room with a minute long http_retry_delay (instead of hitting GOG every few seconds if it decides to not want to co-operate for a moment), but I also increased the retry count very high because it seems something like 3-5 is not necessarily enough, as I can see from the log below? (I increased the fetch delay which I guess makes the whole update process slower, but hoping it helps GOG also to co-operate.)
May I ask how many games you own? Your profile is disabled.

avatar
Kalanyr: I'd only recommend bumping it to 4 though ( or 5 if somehow have more than 10000 owner games ).
Nah, once you get up to 4.2k games, you must increase the retry count to at least 20, 'cause it can easily fail to load more than 10 times. The same applies to the website with the infinite loads (which are actually errors if you look at the F12 console output, but the website had no visual method of handling these errors, so it just keeps displaying the loading wheel).

For now, 20 retries seem good enough for me. I did not bother increasing retry delays, because, based on my browser observations, this is not a slow loading issue, but a straight up failure to load.
I reported all this to Staff and they have replicated the issue. Like I said this is not isolated to GOGREPOC, this is an account issue and affects browsers too.

Until this is fixed, the more games you buy, the worse library experience you will have.
Post edited April 07, 2024 by SargonAelther
avatar
SargonAelther: May I ask how many games you own? Your profile is disabled.
The log I quoted revealed it: 2583

07:40:33 | (2195 / 2583) fetching game details for the_humans_3...

avatar
Kalanyr: I'd only recommend bumping it to 4 though ( or 5 if somehow have more than 10000 owner games ).
avatar
SargonAelther: Nah, once you get up to 4.2k games, you must increase the retry count to at least 20, 'cause it can easily fail to load more than 10 times. The same applies to the website with the infinite loads (which are actually errors if you look at the F12 console output, but the website had no visual method of handling these errors, so it just keeps displaying the loading wheel).
I am unsure why the number of games would matter to how high you should set the retry count? Couldn't you hit the issue just as well even if you had 10 or 100 games? Also, doesn't the retry count restart from the beginning anyway, each the you hit the issue? So it is not like it is some kind of "this is the maximum number of retries during your whole game update session", but number of retries per game (or file)?

Like in my log, it starts the countdown from 99 each time it encounters the problem.

avatar
SargonAelther: For now, 20 retries seem good enough for me. I did not bother increasing retry delays, because, based on my browser observations, this is not a slow loading issue, but a straight up failure to load.
Maybe I am misunderstanding the issue then, but I thought GOG has occasionally issues responding to your requests during update (e.g. the server is too busy or something, or for some reason considers you as a spammer and puts you on hold for awhile), so I figured it makes sense to increase the delay to e.g. 30 or even 60 seconds because if GOG is having the spike or problem or whatever for some time, it makes no sense to keep asking it the same thing every second or so. Give it a rest, and retry in e.g. 30 or 60 seconds.

I figure it doesn't slow down the update process that much anyway, unless you keep hitting the issue constantly. It doesn't really matter to me if the full update takes 4 hours or 4 hours 10 minutes.
Post edited April 07, 2024 by timppu
The number of games matters because even if it could happen with 1 game ( say a 1% chance)
then the chance of it not happening at last once on 100 games is 99%^100 ~ 37%, so roughly a 63% chance of failing at leRy once.

( The actual chance is much smaller in my experience but it illustrates the maths )
avatar
timppu: The log I quoted revealed it: 2583
Thanks. I need to pay more attention lol.

avatar
timppu: I am unsure why the number of games would matter to how high you should set the retry count?
It seems to have something to do with https://www.gog.com/account seemingly loading your entire library at once. The pages are largely visual, not actual data separators as a I understand it.

There is also a clear correlation between the amount of games bought, and the performance of the https://www.gog.com/account page.
I have friends with 3k games, 4k games and 5k games. I have about 4.3k myself. The more games we buy, the more loading failures we notice, aka the infini-load, which shows up in browser's console as:
XHRGET
https://www.gog.com/account/gameDetails/1096313866.json
[HTTP/2 500 11912ms]

XML Parsing Error: mismatched tag. Expected: </meta>.
Location: https://www.gog.com/account/gameDetails/1096313866.json
Line Number 9, Column 15: 1096313866.json:9:15
Error loading product data. jsGlobal-f9c0790.js:1:383545

or the usual 500 error in GOGREPOC.

In both browser's and GOGREPOC's case, you just have to retry. On a browser you retry by clicking away and clicking on the game again, since it will never tell you that the loading has failed, outside of the console.

Additionally, the actual loading time for https://www.gog.com/account increases too. Any page can load in 1-2 seconds, while https://www.gog.com/account can take over 10.

Once I have passed 4.2k games, I started seeing GOGbears on https://www.gog.com/account several times a day. The user with 5k games, cannot load https://www.gog.com/account at all, it always leads to a GOGbear.

All other pages load fine. If we try different accounts with less games, they load fine too. I tried logging in to my GF's account with less than 500 games, it loads fine and quickly. So it is absolutely a game count issue.

More over this was pretty much acknowledged on the GOG Cafe discord server. They said they are working on this.

avatar
timppu: I thought GOG has occasionally issues responding to your requests during update (e.g. the server is too busy or something, or for some reason considers you as a spammer and puts you on hold for awhile)
That may also be true, but that should obviously only occur after a large number of queries, not immediately on your first one. I get load failures on the website and GOGREPOC immediately on my first game. The longest failure streak for me so far was failing to load 15 times in a row.

At this point the question is not whether I will encounter a 500 error, but rather how many times in a row for each game lol.

If, for whatever reason, you have trouble believing me, then see these two posts from users with libraries above 4k:
One
Two

This is also not the first time that buying over 4k games has cause issues. See here. This one was fixed recently though.
Post edited April 08, 2024 by SargonAelther
avatar
SargonAelther: It seems to have something to do with https://www.gog.com/account seemingly loading your entire library at once. The pages are largely visual, not actual data separators as a I understand it.
Ok thanks for the explanation, sounds plausible.

That seems a bit similar problem as me (and many others) now being unable to load

https://www.gog.com/forum/myrecentposts

There was discussion about this earlier, and people were reasoning it might be due to high number of posts one has written to the forums, but something actually lead me to believe it was related to the number of games one has on GOG (IIRC there was someone who had posted a lot over years as well but had relatively low number of games, and he had no issues with that link, not getting the bear).

Maybe it is related to listing all the game subforums, to which you auto-subscribe when you buy a game.

Hopefully GOG fixes that issue, otherwise it becomes a clear deterrent on buying more games on GOG. :D