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.

Sign up for GitHub

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

Jump to bottom

Data loading produces server error #2

Open
mhuelfen opened this issue Nov 14, 2018 · 1 comment
Open

Data loading produces server error #2

mhuelfen opened this issue Nov 14, 2018 · 1 comment

Comments

@mhuelfen
Copy link

The download oft the latest data fail, since today.

Starting the script I get:

Welcome to the EOS Knights Stats Machine!
Starting up at 11:11:45 14.11.2018
Loading data from data.json...
We have data on 5247 accounts at block number 26439034 using sequence number 7789837
{ Error: {"errors":{"producer":"The request to the producer API failed"}}
    at //eosknights/node_modules/eosjs-api/lib/apigen.js:112:23
    at process.internalTickCallback (internal/process/next_tick.js:77:7) status: 500, statusText: 'Internal Server Error' }

Before that download the data was working but crashed often, with this error:

Updating: block number 26437466 at 2018-11-11T20:58:15.500 account sequence 7789103
{ Error: <html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
</html>

    at //eosknights/node_modules/eosjs-api/lib/apigen.js:112:23
    at process.internalTickCallback (internal/process/next_tick.js:77:7) status: 504, statusText: 'Gateway Time-out' }
@lukestokes
Copy link
Owner

Yeah, I've been noticing this also. Unfortunately, it seems the greymass API (which appears to be one of the few node still running the full deprecated history plugin) is crashing (the HTTP 500 series errors are server-side errors).

I may adjust my code to just query the revenue table, but that kind of defeats the purpose of externally validated data by going through each transaction. You can look up the revenue table on blocs.io right now in the mean time:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lukestokes @mhuelfen