chia-blockchain-gui icon indicating copy to clipboard operation
chia-blockchain-gui copied to clipboard

Chia Takes Forever to Fully Come up

Open lsherring opened this issue 4 years ago • 4 comments

Running 1.26, Win 10 Pro fully updated. I can reproduce this every time. Upon a restart of the syste4m or Chia, the Chia program can take anywhere from 5 to ten minutes to bring up the gui. On multiple occasions, the restart of the gui fails after loading your 24 word code and you have to be patient, let it time out and click the green submit button multiple times. I have never had chia come clean the very first time. Lastly, all was running well network wise, but after a power outage and reboot, i cannot connect to any peers, I get multiple wallets being shown and I cannot synch as I only have 8 peers with 98% of them not doing any upload or download. I have a 1GB all fibre network infrastructure as well. My port forwarding is always on. I deleted it in the router and rebuilt it and still the same results.

The man issue sis Chia taking forever to come up and taking multiple tries. I have to investigate why I don't have any more peers as I once had.

To reproduce the issue, just restart the Gui.

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Screenshots

Desktop

  • OS:
  • OS Version/Flavor:
  • CPU:

Additional context

lsherring avatar Sep 16 '21 16:09 lsherring

Also, it appears as if many folks running windows are having issues getting the full compliment of peers since the 1.26 update. Myself and two others have the same issue and I never had an issue prior to the update.

lsherring avatar Sep 17 '21 02:09 lsherring

I updated to 1.27 and the same issue on both issues. But I just now checked my peers and I have 17. Very strange issue.

lsherring avatar Sep 19 '21 05:09 lsherring

I updated to 1.27 and the same issue on both issues. But I just now checked my peers and I have 17. Very strange issue.

1.27 only changed one line so it wouldn't be causing that

jack60612 avatar Sep 19 '21 17:09 jack60612

Yup I agree as I read the release notes as well, but IFM.....It can happen for no reason....IFM = Its fuckin magic.....used this term when I worked on mainframes a lot. Stuff started working again with no explanation. LOL

lsherring avatar Sep 20 '21 18:09 lsherring

This issue should be fixed now. Try to upgrade to the latest version.

seeden avatar Sep 07 '22 16:09 seeden