Looking for answer on debug.log ERROR on Debian Linux

[nocolife]

Hello, tried for help elsewhere without luck. Receiving a large number of SSL related errors in the log. I did some research and the same errors appear in other projects unrelated to chia, so I imagine it is a python or other issue, and I am hoping the errors can be safely ignored. The errors appear to be generated when a socket is closed while it is still receiving data, which may be fine depending what's going on exactly. Other projects have said using version 3.6 of python stops the errors.

Please advise if this is known about, and is not causing any issues to worry about. Thank you

2021-05-04T22:15:38.676 full_node asyncio                 : ERROR    SSL error in data received
protocol: <asyncio.sslproto.SSLProtocol object at 0x7f13c4be36a0>
transport: <_SelectorSocketTransport fd=105 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
    ssldata, appdata = self._sslpipe.feed_ssldata(data)
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata
    self._sslobj.unwrap()
  File "/usr/lib/python3.7/ssl.py", line 767, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

[nocolife]

still getting these constantly in new version also. 1.1.4

Unable to get answers

2021-05-05T10:57:54.212 full_node full_node_server        : INFO     -> handshake to peer 73.117.12.31 1ae5e4b224bf29814746f0d59c021eb33fdbbe603991fe4127206a266b40c91a
2021-05-05T10:57:54.213 full_node full_node_server        : INFO     Not accepting inbound connection: {'host': '73.117.12.31', 'port': 8444}.Inbound limit reached.
2021-05-05T10:57:54.287 full_node full_node_server        : INFO     Connection closed: 73.117.12.31, node id: 1ae5e4b224bf29814746f0d59c021eb33fdbbe603991fe4127206a266b40c91a
2021-05-05T10:57:54.288 full_node chia.full_node.full_node: INFO     peer disconnected {'host': '73.117.12.31', 'port': 8444}
2021-05-05T10:57:54.293 full_node asyncio                 : ERROR    SSL error in data received
protocol: <asyncio.sslproto.SSLProtocol object at 0x7f32ac526ac8>
transport: <_SelectorSocketTransport fd=114 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
    ssldata, appdata = self._sslpipe.feed_ssldata(data)
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata
    self._sslobj.unwrap()
  File "/usr/lib/python3.7/ssl.py", line 767, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)
2021-05-05T10:57:54.810 full_node full_node_server        : INFO     <- request_blocks from peer ef94b03a2c3588c06548f5400c363a16880b35cfd11d500efb4885627f5e0822 77.7.37.23
2021-05-05T10:57:54.900 full_node full_node_server        : INFO     -> respond_blocks to peer 77.7.37.23 ef94b03a2c3588c06548f5400c363a16880b35cfd11d500efb4885627f5e0822
2021-05-05T10:57:55.343 full_node full_node_server        : INFO     -> handshake to peer 45.191.222.128 56c6da50dc258c441ef51a4bc78e4821b48667bcdf060c0db559c12a2e6ab14e
2021-05-05T10:57:55.344 full_node full_node_server        : INFO     Not accepting inbound connection: {'host': '45.191.222.128', 'port': 8444}.Inbound limit reached.
2021-05-05T10:57:55.516 full_node full_node_server        : INFO     Connection closed: 45.191.222.128, node id: 56c6da50dc258c441ef51a4bc78e4821b48667bcdf060c0db559c12a2e6ab14e
2021-05-05T10:57:55.517 full_node chia.full_node.full_node: INFO     peer disconnected {'host': '45.191.222.128', 'port': 8444}
2021-05-05T10:57:55.521 full_node asyncio                 : ERROR    SSL error in data received
protocol: <asyncio.sslproto.SSLProtocol object at 0x7f32e2903710>
transport: <_SelectorSocketTransport fd=113 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
    ssldata, appdata = self._sslpipe.feed_ssldata(data)
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata
    self._sslobj.unwrap()
  File "/usr/lib/python3.7/ssl.py", line 767, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)
2021-05-05T10:57:55.650 full_node full_node_server        : INFO     <- request_signage_point_or_end_of_sub_slot from peer 2811ffdea285bf2088ee3bcd03073521feee987a0aec3e39a6cfede8f490d160 178.67.198.115

[alestanga]

I have the same issue on debian 10 and python 3.7.3
I've also installed python 3.9.5 from the source, set it as default python, I've checked with both python -V and python3 -V and they say version 3.9.5 is in use but as soon as I go in the venv python -V returns version 3.7.3
I have the same errors:
2021-05-05T21:16:59.318 full_node full_node_server : WARNING Cannot write to closing transport 24.5.132.106
2021-05-05T21:24:55.976 full_node asyncio : ERROR SSL error in data received

and also a cat | grep harvest on my debug.log returns:
2021-05-05T08:06:59.534 harvester asyncio : ERROR SSL error in data received
2021-05-05T15:21:03.622 harvester asyncio : ERROR SSL error in data received
2021-05-05T17:30:49.888 harvester asyncio : ERROR SSL error in data received
2021-05-05T18:25:44.035 harvester asyncio : ERROR SSL error in data received

what's going on?
is there a way to run chia on debian 10?

[nocolife]

did you ever get any help anywhere at all? Ive literally typed the error infront of some of the team on keybase and its never even acknowledged

[alestanga]

No, no answer. I’m thinking about farming on a raspberry at the moment… I don’t know why no one else has this problem. Inviato da iPad

…

Il giorno 9 mag 2021, alle ore 01:49, nocolife ***@***.***> ha scritto:  did you ever get any help anywhere at all? Ive literally typed the error infront of some of the team on keybase and its never even acknowledged — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[nocolife]

No, no answer. I’m thinking about farming on a raspberry at the moment… I don’t know why no one else has this problem. Inviato da iPad
…
Il giorno 9 mag 2021, alle ore 01:49, nocolife @.***> ha scritto:  did you ever get any help anywhere at all? Ive literally typed the error infront of some of the team on keybase and its never even acknowledged — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

switched everything over to Ubuntu, took all day but it runs fine without the SSL errors. They should really remove reference to Debian on the install page if its not running properly even when instructions are followed exactly. Lots of others do have the problem and are not getting any advice.

[parer55]

Same issue here on RPI4 (Debian 10, 64bit, 2Gb RAM). Don't want to migrate everything to ubuntu. It should work fine on a RPI4, I don't understand. I've looked up the specific SSL problem and it seems like there's a solution, please implement it (not sure though).

[ChesDonno]

been having a problems with 1.1.5
and I'm using Ubuntu 20.04

debug.log

[alestanga]

so now even ubuntu is not an option anymore?
is it only possible to farm on windows then?

[ChesDonno]

no idea
I wonder if dev team see this issues

[parer55]

My problem "debug.log" on a RPI4 (Debian 10, 64bit, 2Gb RAM) :
2021-05-12T11:17:16.259 full_node asyncio : ERROR SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7f2709b438> transport: <_SelectorSocketTransport fd=37 read=polling write=<idle, bufsize=0>> Traceback (most recent call last): File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received ssldata, appdata = self._sslpipe.feed_ssldata(data) File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.7/ssl.py", line 767, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

[steveleader]

I see the same issue on my RPI4 4GB running with raspios ARM64 lite (http://downloads.raspberrypi.org/raspios_lite_arm64/images/raspios_lite_arm64-2021-04-09/)

Every few minutes I get this
2021-05-13T11:23:13.930 full_node asyncio : ERROR SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7fa1a3f9b0> transport: <_SelectorSocketTransport fd=109 read=polling write=<idle, bufsize=0>> Traceback (most recent call last): File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received ssldata, appdata = self._sslpipe.feed_ssldata(data) File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.7/ssl.py", line 767, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

Do we know if it does any harm? Can we ignore it for the time being?

[kshyshkin]

Same situation on rpi4 rasbian os....

[salamanders]

I'm seeing the same, rpi4.

[sirgooey]

Seeing this as well on a Pi4 4GB, running Raspberry Pi OS 64bit. Seems fine otherwise...

2021-05-15T23:23:27.488 full_node chia.full_node.full_node: ERROR Consensus error 124, not disconnecting 2021-05-15T23:25:27.329 full_node asyncio : ERROR SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7f59430ac8> transport: <_SelectorSocketTransport fd=49 read=polling write=<idle, bufsize=0>> Traceback (most recent call last): File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received ssldata, appdata = self._sslpipe.feed_ssldata(data) File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.7/ssl.py", line 767, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609) 2021-05-15T23:25:27.450 full_node asyncio : ERROR SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7fa517bb38> transport: <_SelectorSocketTransport fd=66 read=polling write=<idle, bufsize=0>> Traceback (most recent call last): File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received ssldata, appdata = self._sslpipe.feed_ssldata(data) File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.7/ssl.py", line 767, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

[btaylor84]

I'm having this problem too. Raspberry Pi4 on Raspian 64b, chia version 1.1.6

[sirgooey]

I have a suspicion this is just effectively port-scanning on your port 8444 which Chia recommends to be open to the Internet - is that the case, is yours open?

[btaylor84]

Yes, I have my router forwarding 8444 properly. This seems to be an issue with SSL protocol data communication.

[Celt1967]

Yes Port 8444 is open. Really want to keep my RPi4 setup if possible and that is still on the Chia.net as a viable setup.

[sirgooey]

I've done a simple test here - monitoring the log while just doing a telnet on port 8444 from another machine.
This generates the same "ERROR SSL handshake failed" log message, seemingly confirming that the log entry appears simply because something that isn't actually a Chia peer/etc is connecting. This, as I've said before, could well be just a port-scan which is not uncommon for a public-Internet accessible port.

[btaylor84]

I now run my chia farm in a Ubuntu-based docker container on my RPI, and these errors have disappeared. I suspect it's due to an incorrect version of something in Raspian, that's updated in Ubuntu 20.04

[nocolife]

If it helps anyone, I switched to Ubuntu shortly after not getting any answers on this and that fixed it all for me. I also noticed they removed references to Debian on the install page so I imagine it's just not going to be supported at all. If you can't make the switch to Ubuntu I would guess you will have to poke around the install.sh and see why it installs python 3.7, and see if you can get it onto 3.8.
When I got into Chia I had absolutely no idea I'd have to completely relearn so much Linux stuff I'd forgotten from a couple decades ago, I feel like you need to be a sysadmin to be able to partake. cheers.

[btaylor84]

Thanks. I might play with configuring a Ubuntu docker container. I do enjoy the sysadmin learning part of this project, it's just part of the hobby.

[toxicroadkill]

im running debian 10, and get a huge number of ssl errors also, switching to ubuntu, is not going to happen.

i keep wondering why chia was writtin python in the first place?

python is not the greatest language by any means

how about a nice C program, and give up on the goofy python setup?

the whole "activate" thing, then do a command in the "virtual" is just "in my opinion", a pretty stupid way to write the thing

take a look at monero miners, "xmrig", and the like, it runs, it works, and it works well, and is VERY portable across diff linux versions

how many think that using python for chia was well, to put it mildly, a stupid idea?

[Namsoyo]

i have same issue on my raspi4b 8GB
👍
2021-06-28T05:47:45.005 full_node asyncio : ERROR SSL error in data received
protocol: <asyncio.sslproto.SSLProtocol object at 0x7f71977f28>
transport: <_SelectorSocketTransport fd=104 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
ssldata, appdata = self._sslpipe.feed_ssldata(data)
File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata
self._sslobj.unwrap()
File "/usr/lib/python3.7/ssl.py", line 767, in unwrap
return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

it happans moretime in one hour
so i loose my winning chances

[keliew]

I was running 1.2.1 on two different machines both running Debian Buster. 1 fell out of sync, while the other is working fine. Both have SSL errors.

Seeing how 1.2.2 has a SSL fix, I thought why not try it out. So the one falling out of sync is upgraded and is syncing OK, yet still have the following error (which I think it's 'normal'...been like this for months).

2021-07-15T10:17:05.055 full_node asyncio                 : ERROR    SSL error in data received
protocol: <asyncio.sslproto.SSLProtocol object at 0x7f77a8d3d0f0>
transport: <_SelectorSocketTransport fd=31 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
    ssldata, appdata = self._sslpipe.feed_ssldata(data)
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata
    self._sslobj.unwrap()
  File "/usr/lib/python3.7/ssl.py", line 767, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

I have other farming machines running the same on 1.7 and works fine even with these ssl errors...just this one machine was falling out of sync. Real strange...

Could it be SSL conflicts among different OS and versions on the peer network?

[keliew]

OK, so I took a stab at this on Debian Buster...

I have upgraded Debian Buster's python3-certifi and ca-certificates to (i) python3-certifi-2020.6.20 and (ii) ca-certificates-20210119, just to be sure that the system has the latest running, i.e. up-to-date. There are still SSL errors.

According to Python, it's 'normal' and should be surpressed:
python-websockets/websockets#614
https://bugs.python.org/issue34506
https://bugs.python.org/issue41596
https://bugs.python.org/issue41597
https://stackoverflow.com/questions/52012488/ssl-asyncio-traceback-even-when-error-is-handled

Python's websockets doesn't support multithreading..?

[toxicroadkill]

im all up to date also, and still get errors, it NEVER syncs the blockchain someone have a solution so chia actually works on debian?

…

On Jul 15, 2021, at 7:31 AM, keliew ***@***.*** ***@***.***>> wrote: OK, so I took a stab at this on Debian Buster... I have upgraded Debian Buster's python3-certifi and ca-certificates to (i) python3-certifi-2020.6.20 and (ii) ca-certificates-20210119, just to be sure that the system has the latest running, i.e. up-to-date. There are still SSL errors. According to Python, it's 'normal' and should be surpressed: python-websockets/websockets#614 <python-websockets/websockets#614> https://bugs.python.org/issue34506 <https://bugs.python.org/issue34506> https://bugs.python.org/issue41596 <https://bugs.python.org/issue41596> https://bugs.python.org/issue41597 <https://bugs.python.org/issue41597> https://stackoverflow.com/questions/52012488/ssl-asyncio-traceback-even-when-error-is-handled <https://stackoverflow.com/questions/52012488/ssl-asyncio-traceback-even-when-error-is-handled> Python's websockets doesn't support multithreading..? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3758 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASD5O32DNHPHL57LSHHRS2TTX3IKFANCNFSM44D5VMHQ>.

[keliew]

im all up to date also, and still get errors, it NEVER syncs the blockchain someone have a solution so chia actually works on debian?

FWIW, it works on Debian. I have a few machines all running on Debian Buster (without those updates); only one is failing to sync now. The official nodes do work.

Try increasing the number of target peers, and include all the official nodes regardless of its territory.

[toxicroadkill]

already done that

…

On Jul 15, 2021, at 10:04 AM, keliew ***@***.***> wrote: im all up to date also, and still get errors, it NEVER syncs the blockchain someone have a solution so chia actually works on debian? FWIW, it works on Debian. I have a few machines all running on Debian Buster (without those updates). The official nodes do work. Try increasing the number of target peers, and include all the official nodes regardless of its territory. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3758 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASD5O3Y25L74IWIVPA6JXFDTX32HTANCNFSM44D5VMHQ>.

[Guillaumevk]

According to the documentation (link below), I have the impression that this is not a problem.

Other normal log messages:

Source | Level | Message
full_node asyncio | ERROR | SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7f762544a8>

Source: https://github.com/Chia-Network/chia-blockchain/wiki/Logging-Messages-Reference#other-normal-log-messages

[toxicroadkill]

ok, but mine never syncs, like ever port is open, new version..never syncs... :(

…

On Jul 20, 2021, at 6:42 AM, Guillaumevk ***@***.*** ***@***.***>> wrote: According to the documentation (link below), I have the impression that this is not a problem. Other normal log messages: Source | Level | Message full_node asyncio | ERROR | SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7f762544a8> Source: https://github.com/Chia-Network/chia-blockchain/wiki/Logging-Messages-Reference#other-normal-log-messages <https://github.com/Chia-Network/chia-blockchain/wiki/Logging-Messages-Reference#other-normal-log-messages> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3758 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASD5O36INUNP3ATJCGYE6FLTYVOJ5ANCNFSM44D5VMHQ>.