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

Node gets blacklisted by the ethoscope if the connection is not good enough #131

Open
ggilestro opened this issue Sep 14, 2020 · 0 comments
Assignees
Labels
data backup Problems with data backup from ethoscopes to node

Comments

@ggilestro
Copy link
Member

If the quality of the connection between the node and the ethoscope is not good enough, the ethoscope's mariadb instance will eventually blacklist the node thus forbidding any further attempt at backing up the data.

At the moment, this can be diagnosed on the node forcing a backup from the command line

cd /opt/ethoscope-node/node_src/scripts/
sudo python ethoscope_backup.py -e 113

If there is an issue, this will return

[...]
  File "/usr/lib/python3.8/site-packages/mysql/connector/connection.py", line 148, in _do_handshake
    raise errors.get_exception(packet)
mysql.connector.errors.DatabaseError: 1129: Host '192.169.123.2' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'

The only way to fix this is to restore the connection, then SSH into the ethoscope and run

sudo mysqladmin flush-hosts
@ggilestro ggilestro added the data backup Problems with data backup from ethoscopes to node label Sep 14, 2020
@ggilestro ggilestro self-assigned this Sep 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data backup Problems with data backup from ethoscopes to node
Projects
None yet
Development

No branches or pull requests

1 participant