Главная » Криптовалюты

Warning error while handling message traceback most recent call last chia

Содержание
  1. 1.1.1 Ubuntu: Not Synced #2408
  2. Comments
  3. salamanders commented Apr 22, 2021 •
  4. Questions
  5. dorkmo commented Apr 22, 2021
  6. salamanders commented Apr 22, 2021
  7. nowickj commented Apr 22, 2021 •
  8. megablue commented Apr 22, 2021
  9. salamanders commented Apr 22, 2021 •
  10. salamanders commented Apr 22, 2021
  11. hoffmang9 commented Apr 22, 2021
  12. salamanders commented Apr 22, 2021
  13. hoffmang9 commented Apr 22, 2021
  14. salamanders commented Apr 22, 2021
  15. salamanders commented Apr 22, 2021
  16. salamanders commented Apr 22, 2021 •
  17. salamanders commented Apr 22, 2021 •
  18. dorkmo commented Apr 23, 2021
  19. salamanders commented Apr 23, 2021
  20. dorkmo commented Apr 23, 2021
  21. hoffmang9 commented Apr 24, 2021
  22. Dravenex commented Apr 27, 2021
  23. Not synced #5221
  24. Comments
  25. Commodoreuno commented May 16, 2021
  26. korobov-e commented May 16, 2021 •

1.1.1 Ubuntu: Not Synced #2408

Comments

salamanders commented Apr 22, 2021 •

  1. Woke up to the «this will stop working at height xxx» message. Ok, no worries.
  2. Noticed that I wasn’t synced since last night. Stopped around height 166101
  3. Killed my plotting.
  4. Updated to latest 1.1.1 via git.
  5. installed latest using .sh
  6. Rebooted machine
  7. Saw it go from «Not Synced» to «Synchronizing. » then back to «Not Synced»
  8. While UI was running, tried a few commands in the same . /activate terminal:
  • chia show -a node.chia.net:8444 (failed to connect)
  • chia show -a 35.80.8.179:8444 (failed to connect)
  • chia show -a 18.168.101.107:8444 (failed to connect)

I am connected to 2 nodes (1 farmer, 1 wallet)

Questions

  1. Is this broken or just «dude, wait at least 6 hours before worrying.»
  2. Is trying to connect via command line when the GUI is running a «bad thing»?
  3. If 1=Broken, Anything I should be doing to help debug?

The text was updated successfully, but these errors were encountered:

dorkmo commented Apr 22, 2021

make sure your port 8444 is forwarded to your node on your network router

salamanders commented Apr 22, 2021

make sure your port 8444 is forwarded to your node on your network router

Just confirmed, is forwarded in wifi app config.

  • Yet, https://www.yougetsignal.com/tools/open-ports/ is saying it is closed. Interesting.
  • https://www.grc.com/shieldsup says it is «stealth open» — so that is good!
Читайте также:  Майнинг ферма своими руками 2017

nowickj commented Apr 22, 2021 •

I had a similar problem. I have installed a new Ubuntu 20.04 LTS, configured everything. Status was Not Synced. After few minutes it has changed for Syncing 1120/169461, and again it has changing to Not Synced.
I have another server on Ubuntu too, but it has older version and it is Synced.
Port 8444 is open on My router.
after making
chia show -a node.chia.net:8444
chia show -a 35.80.8.179:8444

syncing moovs forward.

megablue commented Apr 22, 2021

After updating to v1.1.1 none of my windows machines are able to sync as well.

salamanders commented Apr 22, 2021 •

chia show -a node.chia.net:8444 — no error
chia show -a 35.80.8.179:8444 — error

«Status: Syncing 166101/169762»
Then a while later goes back to «Not Synced»

salamanders commented Apr 22, 2021

Oh freaky, chia version says 1.1.2.dev0

hoffmang9 commented Apr 22, 2021

The 1.1.2.dev0 is a common git related issue you can ignore.

salamanders commented Apr 22, 2021

common git related issue you can ignore — Cool, ignoring! 🙂

Any thoughts on how to debug?

hoffmang9 commented Apr 22, 2021

You need to get your router routing 8444 to your node.

salamanders commented Apr 22, 2021

Hopefully red herring:

salamanders commented Apr 22, 2021

You need to get your router routing 8444 to your node.

Is there anything that might have increased the chances of more rare issues (like this) in the last 2 days? Over in /r/chia it seems like lots of ppl are suddenly having connection or sync issues. Or did we reach some threshold where not having 8444 routed properly suddenly has more chances of causing a glitch?

salamanders commented Apr 22, 2021 •

Upped the logs to INFO:

salamanders commented Apr 22, 2021 •

Ok so I HAVE FIXED IT FOR JUST ME. (using @hoffmang9 ‘s advice because of course they were right)

  1. I had previously set up forwarding in my mesh Wifi. This was working fine.
  2. I had also checked that the firewall was behaving. This was ALSO working fine.
  3. I had hoped that UPnP in my cable modem was working. this was NOT FINE.
  4. So I tried to do port forwarding from the modem to my mesh. xfinity’s port forwarding is (AFAIK) very broken. I couldn’t forward from the modem to my Mesh Wifi. They are trying to figure out why it is so broken.
  5. In the meantime, I moved my mesh network’s router into the xFinity DMZ. This instantly fixed the issue.
Читайте также:  Trading bitcoin between markets

I am still curious why this didn’t previously hurt me, it feels like something around the same time as the 1.x release made it MUCH more important to have that port set up right.

dorkmo commented Apr 23, 2021

i believe they said it might have to do with the huge increase in new nodes coming online. if your ports were not set up correctly before, the nodes with ports open could support a good number of others, but it became too overwhelming.

salamanders commented Apr 23, 2021

Huh. If the port needs to be routed right, then the app should check for that and give you big blinky errors if it isn’t. right?

dorkmo commented Apr 23, 2021

that would be nice! but unfortunately it doesnt 🙁 node communication seemed to be pretty stable a week or two ago, but there are thousands of nodes coming online everyday now. i think they were depending on upnp to keep most people connected to the network but it seems to not be reliable enough for the current reality.

hoffmang9 commented Apr 24, 2021

The largest blockchain in the world has 85,000 nodes. We passed that a few days ago and are adding about 10,000 nodes a day. That is. ahead of expectations.

Dravenex commented Apr 27, 2021

To the moooooooon

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Not synced #5221

Comments

Commodoreuno commented May 16, 2021

I have recurring problems with synchronization. My Port 8444 is open (Fritzbox) and the Version of Chia is 1.1.5. There are some errors in the Log file, but I have no idea of the meaning. At the moment I’m totally overwhelmed.

Читайте также:  Иностранные инвестиции как источник инвестирования

2021-05-16T19:50:35.645 full_node full_node_server : ERROR Exception , exception Stack: Traceback (most recent call last):
File «chia\server\server.py», line 356, in start_client
File «aiohttp\client.py», line 763, in _ws_connect
File «aiohttp\client.py», line 521, in _request
File «aiohttp\connector.py», line 535, in connect
File «aiohttp\connector.py», line 892, in _create_connection
File «aiohttp\connector.py», line 1032, in _create_direct_connection
File «aiohttp\connector.py», line 969, in _wrap_create_connection
File «asyncio\base_events.py», line 949, in create_connection
File «asyncio\selector_events.py», line 473, in sock_connect
concurrent.futures._base.CancelledError

2021-05-16T20:02:58.243 full_node full_node_server : ERROR Exception , exception Stack: Traceback (most recent call last):
File «chia\server\server.py», line 356, in start_client
File «aiohttp\client.py», line 763, in _ws_connect
File «aiohttp\client.py», line 521, in _request
File «aiohttp\connector.py», line 535, in connect
File «aiohttp\connector.py», line 892, in _create_connection
File «aiohttp\connector.py», line 1032, in _create_direct_connection
File «aiohttp\connector.py», line 969, in _wrap_create_connection
File «asyncio\base_events.py», line 949, in create_connection
File «asyncio\selector_events.py», line 473, in sock_connect
concurrent.futures._base.CancelledError

2021-05-16T20:03:24.621 full_node full_node_server : ERROR Exception: , closing connection None. Traceback (most recent call last):
File «chia\server\server.py», line 531, in api_call
File «asyncio\tasks.py», line 435, in wait_for
concurrent.futures._base.CancelledError

2021-05-16T20:09:27.397 full_node chia.full_node.full_node: WARNING Invalid response for slot None
2021-05-16T20:10:20.436 full_node full_node_server : WARNING Banning 183.178.100.183 for 600 seconds
2021-05-16T20:10:20.439 full_node chia.full_node.full_node: ERROR Error with syncing: Traceback (most recent call last):
File «chia\full_node\full_node.py», line 628, in _sync
RuntimeError: Weight proof did not arrive in time from peer: 183.178.100.183

2021-05-16T20:13:26.651 full_node full_node_server : ERROR Exception , exception Stack: Traceback (most recent call last):
File «chia\server\server.py», line 356, in start_client
File «aiohttp\client.py», line 763, in _ws_connect
File «aiohttp\client.py», line 521, in _request
File «aiohttp\connector.py», line 535, in connect
File «aiohttp\connector.py», line 892, in _create_connection
File «aiohttp\connector.py», line 1032, in _create_direct_connection
File «aiohttp\connector.py», line 969, in _wrap_create_connection
File «asyncio\base_events.py», line 949, in create_connection
File «asyncio\selector_events.py», line 473, in sock_connect
concurrent.futures._base.CancelledError

The text was updated successfully, but these errors were encountered:

korobov-e commented May 16, 2021 •

Have a close issue — today all day have a not synced status
Current Blockchain Status: Not Synced. Peak height: 290832
Time: Sun May 16 2021 17:36:21 UTC Height: 290832

Источник

Оцените статью
© 2024 Идеи для бизнеса