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

How to tell a dashd daemon to reindex without updating the config file? #5485

Open
coolaj86 opened this issue Jul 7, 2023 · 1 comment
Open

Comments

@coolaj86
Copy link

coolaj86 commented Jul 7, 2023

-reindex is not a config option - putting it in the config will cause a reindex to occur every time the service is restarted, which is not desirable.

Ideally dashd should know to reindex automatically when versions change.

I'm assuming I can also just delete some files and that should cause it to reindex? What files are those?

It would also be nice if we had an RPC command that would cause a reindex.

How can I reindex without manually stopping the daemon and system launcher, running it manually, waiting for it to finish, and then manually reenabling the system launcher for the daemon?

@kxcd
Copy link

kxcd commented Jul 26, 2023

To reindex the dashd, ie the command dashd -index as a command line parameter, if using windows, you can edit the shortcut to include the parameter. If you made a copy of the shortcut before changing it, consider appending (reindex) to the edited shortcut, so you have two one to start normally and one to issue reindex as required.

As a sysadmin, I am not interested in having the wallet to automatically fall into a reindex routine willy nilly, I am quite happy to issue it as required, firstly, the process is extremely lengthy, often times when I have a corrupted dashcore folder, I will simply replace it with a known good version and restart, this gets me up and running in no time at all. Let's keep the user in the driver's seat and not add to the frustration of sysadmins whose job it is to keep this network running. 🙏

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