Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG]full_node asyncio : WARNING socket.send() raised exception

See original GitHub issue

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "websockets\protocol.py", line 827, in transfer_data
  File "websockets\protocol.py", line 895, in read_message
  File "websockets\protocol.py", line 971, in read_data_frame
  File "websockets\protocol.py", line 1047, in read_frame
  File "websockets\framing.py", line 105, in read
  File "asyncio\streams.py", line 723, in readexactly
  File "asyncio\streams.py", line 517, in _wait_for_data
  File "asyncio\proactor_events.py", line 280, in _loop_reading
  File "asyncio\windows_events.py", line 812, in _poll
  File "asyncio\windows_events.py", line 461, in finish_recv
ConnectionResetError: [WinError 64] The specified network name is no longer available

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "Lib\site-packages\chia\daemon\server.py", line 208, in safe_handle
  File "websockets\protocol.py", line 555, in send
  File "websockets\protocol.py", line 803, in ensure_open
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason

2021-11-03T21:55:10.385 full_node asyncio                 : WARNING  socket.send() raised exception.
2021-11-03T21:55:10.417 full_node asyncio                 : WARNING  socket.send() raised exception.
2021-11-03T21:55:10.591 full_node asyncio                 : WARNING  socket.send() raised exception.
2021-11-03T21:55:12.432 full_node asyncio                 : WARNING  socket.send() raised exception.
2021-11-03T21:55:13.472 full_node asyncio                 : WARNING  socket.send() raised exception.
2021-11-03T21:55:13.629 full_node asyncio                 : WARNING  socket.send() raised exception.

Been getting this error repeatedly. Running Chia 1.2.10 on Windows 10

Issue Analytics

State:
Created 2 years ago
Comments:17 (4 by maintainers)

Top GitHub Comments

1reaction

artra5253commented, Dec 7, 2021


During handling of the above exception, another exception occurred:



Traceback (most recent call last):

  File "websockets\protocol.py", line 827, in transfer_data

  File "websockets\protocol.py", line 895, in read_message

  File "websockets\protocol.py", line 971, in read_data_frame

  File "websockets\protocol.py", line 1047, in read_frame

  File "websockets\framing.py", line 105, in read

  File "asyncio\streams.py", line 723, in readexactly

  File "asyncio\streams.py", line 517, in _wait_for_data

  File "asyncio\proactor_events.py", line 280, in _loop_reading

  File "asyncio\windows_events.py", line 812, in _poll

  File "asyncio\windows_events.py", line 461, in finish_recv

ConnectionResetError: [WinError 64] The specified network name is no longer available



The above exception was the direct cause of the following exception:



Traceback (most recent call last):

  File "Lib\site-packages\chia\daemon\server.py", line 208, in safe_handle

  File "websockets\protocol.py", line 555, in send

  File "websockets\protocol.py", line 803, in ensure_open

websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason



2021-11-03T21:55:10.385 full_node asyncio                 : WARNING  socket.send() raised exception.

2021-11-03T21:55:10.417 full_node asyncio                 : WARNING  socket.send() raised exception.

2021-11-03T21:55:10.591 full_node asyncio                 : WARNING  socket.send() raised exception.

2021-11-03T21:55:12.432 full_node asyncio                 : WARNING  socket.send() raised exception.

2021-11-03T21:55:13.472 full_node asyncio                 : WARNING  socket.send() raised exception.

2021-11-03T21:55:13.629 full_node asyncio                 : WARNING  socket.send() raised exception.

Been getting this error repeatedly. Running Chia 1.2.10 on Windows 10

0reactions

github-actions[bot]commented, Jan 19, 2022

This issue was automatically closed because it has been flagged as stale, and subsequently passed 7 days with no further activity from the submitter or watchers.

Top Results From Across the Web

WARNING asyncio.write : socket.send() raised exception. #3122

Long story short ws.send_json() fails with this warning: WARNING -- asyncio.write : socket.send() raised exception. ws is from aiohttp.

python 3.x - Async socket.send() exception - Stack Overflow

transfer() . The call to gather returns the results of the coroutines, which includes raising an exception, if one occurred. The exception doesn ......

"socket.send() raised exception." Can someone please point ...

I have recently upgraded to a Raspberry Pi 4 with 4gb ram and a 32gb sd card, running Home Assistant Core 0.115.6. Log...

aio-libs/Lobby - Gitter

import asyncio import requests import time import json import random import ... 'user': 'jonas'} to user123 WARNING:asyncio:socket.send() raised exception.

Help, my bellows are broken and my socket.send raised an ...

I've Googled what seems to be the biggest errors ("NCP entered failed state" and "socket.send() raised exception.") but I can't understand ...