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

Log full of ERROR: Unable to get spend information #6539

Open
screw opened this issue Jan 25, 2025 · 4 comments
Open

Log full of ERROR: Unable to get spend information #6539

screw opened this issue Jan 25, 2025 · 4 comments
Assignees

Comments

@screw
Copy link

screw commented Jan 25, 2025

I have Dash Core:22.0.0, and my log is full of messages:

ERROR: Unable to get spend information

I have this in my config:

txindex=1
addressindex=1
spentindex=1

I have tried reindexing without any change.

@kxcd
Copy link

kxcd commented Jan 26, 2025

Hi @screw how is this error affecting you? Is there some functionality that is missing or not working?

@screw
Copy link
Author

screw commented Jan 26, 2025

Hi kxcd, no, I am not aware of any missing functionality, but it is worrying to see a log full of ERROR messages.

@knst
Copy link
Collaborator

knst commented Jan 26, 2025

ERROR: Unable to get spend information

This issue is being fixed in a coming Dash Core v22.1: #6450

every call of RPC getrawtransaction causes this error logs on high level if spent index is disabled, but actually it just means that no couple extra fields are hidden in output which is expected if no index.

@screw could you try RC1 to check it https://github.com/dashpay/dash/releases/tag/v22.1.0-rc.1 to ensure that no more spamming messages for you?

@screw
Copy link
Author

screw commented Jan 26, 2025

Thanks, guys, for the prompt replies.

I will try to test it during the week.

I've read #6450, and as far as I understand it, it mainly affects the error messages when the particular index is not enabled, but I do have the spent index enabled (spentindex=1).

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

3 participants