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

(Bug) Nothing is being indexed #41

Closed
banteg opened this issue Mar 6, 2018 · 6 comments
Closed

(Bug) Nothing is being indexed #41

banteg opened this issue Mar 6, 2018 · 6 comments
Labels
bug 🐛 Something isn't working

Comments

@banteg
Copy link

banteg commented Mar 6, 2018

the project compiles fine, the database is created, the server is running smoothly, frontend works fine.

i'm using local parity with this config:

[parity]
chain = "spec.json"

[footprint]
pruning = "archive"
tracing = "on"

i tried both master and production branches.

the problem: the database is not populated, nothing is being indexed.

screen shot 2018-03-06 at 3 50 32 pm

@igorbarinov igorbarinov added the bug 🐛 Something isn't working label Mar 6, 2018
@igorbarinov igorbarinov changed the title Nothing is being indexed (Bug) Nothing is being indexed Mar 6, 2018
@rstormsf
Copy link
Contributor

@banteg run heroku local
make sure you have redis also installed

@acravenho
Copy link
Contributor

@banteg The database is populated with a series of workers that need to be scheduled. Easiest way is to dedicate a dyno to each worker in heroku.

Here is a list of workers that need to be scheduled to start indexing blocks:

web = bin/start-pgbouncer-stunnel mix phx.server
balances = bin/start-pgbouncer-stunnel mix scrape.balances 1000000
blocks = bin/start-pgbouncer-stunnel mix scrape.blocks 1000000
internal_transactions = bin/start-pgbouncer-stunnel mix scrape.internal_transactions 10000
receipts = bin/start-pgbouncer-stunnel mix scrape.receipts 10000
scheduler = bin/start-pgbouncer-stunnel mix exq.start scheduler
worker = bin/start-pgbouncer-stunnel mix exq.start

@banteg
Copy link
Author

banteg commented Mar 16, 2018

Thanks for your answers. I think that readme should be updated accordingly.

@rstormsf
Copy link
Contributor

@acravenho can you provide a good documentation on how to run an explorer?

@acravenho
Copy link
Contributor

@banteg @rstormsf I'm in the process of updating readme. I will have it done by Monday.

acravenho added a commit to acravenho/poa-explorer that referenced this issue Mar 19, 2018
Concerns: Should we add in the correct procedure to start a Heroku instance?

Fixes blockscout#41
acravenho added a commit to acravenho/poa-explorer that referenced this issue Mar 19, 2018
Concerns: Should we update Readme with a Heroku instance as well?

Fixes blockscout#41
@KronicDeth
Copy link
Contributor

Indexer has been rewritten in #162. This bug and setup instructions to fix it are obsolete. Open an new issue you have problems using new indexer on master.

jcortejoso pushed a commit to jcortejoso/blockscout that referenced this issue Jan 16, 2020
Added a tab to the addresses to show Celo related information
shellteo pushed a commit to shellteo/blockscout that referenced this issue Jul 26, 2023
rabyyuson referenced this issue in HorizenLabs/eon-explorer Aug 3, 2023
* Added horizen specific frontend styling components (#37)

* Added horizen specifc frontend styling components

* added new line

* new logos and rpc omission support (#41)

* new favicons and footer description (#47)

* resized logo (#50)

* logo footer update (#54)

* updated title,description,removed metamask footer (#55)

Co-authored-by: Alex Hill <zanderbest16@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants