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 Stuck #2837

Closed
adamkrellenstein opened this issue Dec 12, 2024 · 5 comments
Closed

Node Stuck #2837

adamkrellenstein opened this issue Dec 12, 2024 · 5 comments

Comments

@adamkrellenstein
Copy link
Member Author

and here too

Screenshot 2024-12-12 at 4 18 42 PM

@adamkrellenstein
Copy link
Member Author

image

@adamkrellenstein
Copy link
Member Author

Looks like this is due to mempool parsing after catch up. We need to improve the logging here dramatically.

Make sure we're clearly reporting (DEBUG) how much of the mempool has been parsed, if there are any slow / failing Bitcoin Core calls, when the parsing is done, etc.

@adamkrellenstein
Copy link
Member Author

We'll get more logs with: c5fe4c5

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

No branches or pull requests

1 participant