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

Worker is up but not rewarded #102

Open
kalabukdima opened this issue May 20, 2024 · 3 comments
Open

Worker is up but not rewarded #102

kalabukdima opened this issue May 20, 2024 · 3 comments
Assignees

Comments

@kalabukdima
Copy link
Collaborator

Worker with PeerID 12D3KooWHjRUmQVoS6555zeKqDi1nBDsVYbR3aFdezwqFZroBzy7 has stable uptime but doesn't get any rewards.
Find out why that happens, how to fix it, and how to avoid such problems in the future.

@kalabukdima kalabukdima self-assigned this May 20, 2024
@kalabukdima
Copy link
Collaborator Author

kalabukdima commented May 20, 2024

Rewards are not granted because the worker didn't have any logs collected from it since April 15.
It's the date of dropping the Panthalassa support, and a lot of workers stopped sending logs at this time.

Image

@kalabukdima
Copy link
Collaborator Author

kalabukdima commented May 20, 2024

Debugging the reason the logs were not collected gave the following:

The suggestion to manually remove the logs.db file and restart the worker helped, and now it's sending logs and receiving rewards just fine.

@kalabukdima
Copy link
Collaborator Author

kalabukdima commented May 20, 2024

I suppose that the local data was somehow corrupted during the migration to Tethys. Judging by numerous errors in the logs, it can be the case that multiple workers are sharing the same data dir.

Actions to prevent such issues in the future:

  • Monitor that all the active workers get the rewards. @Igorgro please take a look
  • Assert that the last collected log is not from the future on the worker side.
  • Check that another worker is not already using the same data dir during the start up.

Files sent by the operator:

  • 2024-05-18_logs.debug.txt
  • 2024-05-17_logs.txt
  • logs.db with the following contents:
    next_seq_no = 86434
    query_logs.seq_no = 86433
    query_logs.log_msg = 412D3KooWCwAsNpbB9umJ6vD5ApotdobCEDxsYZgibPxp93MjeHKg412D3KooWHjRUmQVoS6555zeKqDi1nBDsVYbR3aFdezwqFZroBzy7$862bb3f7-aede-4b37-ad7b-81ae62c08bc9czM6Ly9ldGhlcmV1bS1tYWlubmV0LTE{"fromBlock": 7299130, "toBlock": 7310017, "traces": [{"callTo": ["0xffdbe829d5a9afcd50482c23eb387b9050f1f825"], "subtraces": true}], "fields": {"block": {"timestamp": true}, "trace": {"type": true, "callFrom": true, "callTo": true, "callInput": true, "callResultOutput": true}}}
    

Logs extract from the logs collector filtered by peer id:

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

1 participant