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
GUI getting stuck on startup since the flexpool.io dns went out of service. #17993
Comments
When looking at the quoted line above it suggests to me the "full node" had trouble claiming port 8444 from the OS to use for itself, as if the system reserved it for something else, or something else is currently running on it? Are you able to look and see if you have other processes running on the machine? Something that wasn't stopped previously? Something that starts up automatically? Do any other processes have control of port 8444? Perhaps signed on as another user who launched something on that port and now you're on another user account trying the same? Since I am naive to linux does the user account being used have permission to utilize that port? As far as I understand the Chia services, the "farmer" can have its errors and issues without impacting the "full node" service from running, but in this case the "full node" service wasn't able to get going because of the OS port issue? I would expect the "farmer" service to fail if it was unable to resolve the domain name, not the "full node" service. (The "farmer" uses port 8447 and the "full node" uses 8444.) |
The only thing that has ever used port 8444 on that machine is the Chia full node. |
Additional info I just figured out. |
Try rebooting before running anything to remove the possibility of zombies. You can go into config.yaml and see if there are any references to flexpool. It may be best to delete config.yaml and have chia recreate it by resyncing your wallet |
I've done the reboot then run immediately before I run anything else a few times now. |
What happened?
2-3 weeks ago, my GUI started sticking at the "starting services full node" point - the other 3 services seem to start up normally.
I never used database v1 as far as I know of, my database path is already pointing at a v2 database - this was a suggested fix, but as I'm already ON a v2 database it's not my issue.
The error log seems to be pointing at an issue with not finding flexpool.io even though there is NOTHING in my config.yaml that mentions flexpool at all.
The DNS records for flexpool seem to have expired at the time this issue started, and at the time I had been running the GUI just long enough every morning to update it's sync, which was normally happening in a very few minutes and the full node was normally starting up within well under 5 minutes to do the sync.
I do NOT use flexpool, though I think I might have used it for a short while many months to a couple years ago.
I have NOT changed anything in my configuration for quite a long time - months to a couple years.
I have no plots on this machine at all.
Version
2.1.4, 2.2.1, 2.3.0
What platform are you using?
Linux
What ui mode are you using?
GUI
Relevant log output
The text was updated successfully, but these errors were encountered: