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

The relayer '*' could not be found #1

Closed
gaia opened this issue Feb 21, 2023 · 2 comments
Closed

The relayer '*' could not be found #1

gaia opened this issue Feb 21, 2023 · 2 comments

Comments

@gaia
Copy link

gaia commented Feb 21, 2023

Saw the presentation on the Lido call. Looking forward to testing this out!

  File "/home/ubuntu/eth-block-proposal-monitor/src/main.py", line 836, in <module>
    insert_new_slot(data['slot'], data['proposer'], data['relay'], data['missed'], data['empty'], reward)
  File "/home/ubuntu/eth-block-proposal-monitor/src/db_ops.py", line 146, in insert_new_slot
    raise Exception("The relayer '"+relayer+"' could not be found. Please update your relay config and try again.")
Exception: The relayer 'Blocknative' could not be found. Please update your relay config and try again.```

Next time I run it, it will give an error about a different relayer (`The relayer 'ultra sound' could not be found`).

`pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)`
`commit 34d34cfab7611442696dbef0cbda8d7040815a6a (HEAD -> main, origin/main, origin/HEAD)`

Not running under a dedicated user, but it is an unprivileged user (standard `ubuntu` user). it's already isolated inside it's own LXD/LXC container.


@frangrech
Copy link
Contributor

Hi, could you try deleting the slot_data.db file located in /eth-block-proposal-monitor/data/ and running the script again? On the first run, and on the creation of the database, it should populate the relayers table using the relay_config.json that should be located in /eth-block-proposal-monitor/config/.

@gaia
Copy link
Author

gaia commented Feb 22, 2023

thanks, fran! that did it.

small suggestion: if /etc/systemd/system/eth2_block_monitoring.service already exists, do not overwrite it when running the script again. ppl customize it, it's best to not overwrite. if the user needs it rebuild, they can simply delete it.

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

No branches or pull requests

2 participants