Fatal error on ssl transport asyncio

Fatal error on SSL transport #3393

Comments

yjqiang commented Nov 17, 2018

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File «/var/containers/Bundle/Application/84DF3BDF-B442-41B6-93B3-AB45EDA9E5FC/Pythonista3.app/Frameworks/Py3Kit.framework/pylib/asyncio/sslproto.py», line 640, in _process_write_backlog
ssldata = self._sslpipe.shutdown(self._finalize)
File «/var/containers/Bundle/Application/84DF3BDF-B442-41B6-93B3-AB45EDA9E5FC/Pythonista3.app/Frameworks/Py3Kit.framework/pylib/asyncio/sslproto.py», line 156, in shutdown
ssldata, appdata = self.feed_ssldata(b»)
File «/var/containers/Bundle/Application/84DF3BDF-B442-41B6-93B3-AB45EDA9E5FC/Pythonista3.app/Frameworks/Py3Kit.framework/pylib/asyncio/sslproto.py», line 220, in feed_ssldata
self._sslobj.unwrap()
File «/var/containers/Bundle/Application/84DF3BDF-B442-41B6-93B3-AB45EDA9E5FC/Pythonista3.app/Frameworks/Py3Kit.framework/pylib/ssl.py», line 692, in unwrap
return self._sslobj.shutdown()
ssl.SSLError: [SSL] called a function you should not call (_ssl.c:2299)

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

yjqiang commented Nov 17, 2018

I used “try” and tried handle this exception, but I can’ catch it.

aio-libs-bot commented Nov 17, 2018

GitMate.io thinks the contributor most likely able to help you is @asvetlov.

Possibly related issues are #3242 (Error), #3117 (Fatal read error on socket transport), #3141 (Fatal read error on socket transport ), #2822 (Unexpected SSL error (CERTIFICATE_VERIFY_FAILED)), and #272 (SSL documentation).

asvetlov commented Nov 17, 2018

What Python and aiohttp versions do yo use?

yjqiang commented Nov 17, 2018

python 3.6.1 and aiohttp 3.4.4 by using pip

asvetlov commented Nov 17, 2018

The problem not in aiohttp itself but in Python asyncio.
Try to upgrade to Python 3.7.1 — it has several asyncio SSL fixes.
I don’t know if these fixes are enough for your case though.

yjqiang commented Nov 17, 2018

I’m using Pythonista on ios, so I can’t upgrade to 3.7.1 by myself. But if the author made it, I would try and give you the feedback.

yjqiang commented Nov 17, 2018

Should I close it now or let it open until …?

yjqiang commented Nov 17, 2018 •

By the way, I think I find the reason of #3117 and #3141 and #3202. Can I reopen #3202 , since I made that issue? And I left a message for you there, several days ago.

asvetlov commented Nov 17, 2018

Yes, better to report on upstream.
Regarding #3202 — let’s briefly discuss your findings with closed issue status and decide what to do after that.

yjqiang commented Nov 17, 2018 •

@asvetlov I wrote something in #3202 few minutes ago.

yjqiang commented Nov 17, 2018

Yes, better to report on upstream.
Regarding #3202 — let’s briefly discuss your findings with closed issue status and decide what to do after that.

Did you read that? I think that’s important.

Источник

«Fatal error on SSL transport» when exiting python script #20482

Comments

rjohnsonrxr commented Aug 31, 2021

Package Name: azure-eventhub-checkpointstoreblob-aio
Package Version: 1.1.4
Operating System: MacOs 10.15.7
Python Version: 3.9.1

Describe the bug
Error is occurring after exiting python program :

To Reproduce
Steps to reproduce the behavior:
Minimal repro :

Expected behavior
Error should not occur

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

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

xiangyan99 commented Sep 2, 2021

Thanks for the feedback, we’ll investigate asap.

yunhaoling commented Sep 13, 2021

hey @rjohnsonrxr, I am able to reproduce the issue on windows which gave me more information on the error:

according to the doc of asyncio.run :

This function always creates a new event loop and closes it at the end. It should be used as a main entry point for asyncio programs, and should ideally only be called once.

So I think it’s because the underlying ssl obj is hooked with one asyncio loop in the first asyncio.run , and the loop get closed after the running which leads to the second call find that the previous loop hooked with the ssl obj is already closed.

To bypass it, you could use the same loop to run those two method, so your code could be like:

Please let me whether it works for you or you need any other help.

Источник

Fatal error on SSL transport #67

Comments

Memurame commented Jan 28, 2017 •

I have cloned the New Monocle.
Now the Scanner has Errors in the Logs Like This.

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

Noctem commented Feb 2, 2017

I’m not quite sure what the problem is here. Does it happen in the middle of sessions or while exiting? On every request, many, or just a few? Is your internet connection stable?

Memurame commented Feb 5, 2017

Yes my internet connection is stable.

Here a littlebit more.

MonkeyTedBaker commented Sep 28, 2017

I figured out what this is.
asyncio.sslproto.SSLProtocol and other TCP related errors tend to happen when the server can’t process TCP in a timely manner. While there could be various reasons for this (mostly infra related), one common reason is the maximum CPU usage of server.

Usually, Monocle is very conservative in terms of CPU usage but when doing certain operations like bootstrap, MORE_POINTS, etc, it maxes out CPU and when that happens, server fails to properly process TCP connections and you get those errors.

jeffpeiyt commented Mar 25, 2018

@MonkeyTedBaker great findings. We find similar issuing on SSLProtocol with the Fatal error on SSL transport . Do you have suggestions to mitigate the issue other than to lower cpu usage? Seems when that happens, many IO/TCP requests are failing

Footer

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.

Источник

fatal error on ssl transport #571

Comments

yjqiang commented Nov 1, 2018

During handling of the above exception, another exception occurred:

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

yjqiang commented Nov 1, 2018

pythonista 320000 python 3.6.1 aiohttp 3.4.4

cclauss commented Nov 1, 2018 •

Please also provide a minimal code snippet that generates this error message.

Источник

AttributeError: ‘NoneType’ object has no attribute ‘feed_appdata’ #2546

Comments

binrush commented Nov 22, 2017

Long story short

We have small aiohttp-based running on many customers servers. All errors from these servers are reported to Sentry. There are many errors whitch looks like aiohttp bugs, here’s details:

Steps to reproduce

Unfortunately, we can not reproduce this issue on our environment and do not have access to affected servers.

Your environment

aiohttp server 2.3.2
Centos 6/7

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

asvetlov commented Nov 22, 2017

Thanks for report.
The problem is actually in asyncio itself.
I’m trying to write a complex fix for SSL transport but it takes a while.
You can simply ignore this noisy error message.

P.S.
Let’s keep the issue open for the reference for a while.

bigbagboom commented Dec 20, 2017 •

same error I got:

waiting for the fix. Thanks a lot.

agronholm commented Feb 1, 2018

I hit this one too but not with aiohttp. Is there a relevant issue on CPython’s bug tracker?

asvetlov commented Feb 2, 2018

There are several issues related to asyncio ssl support, I’ll address them before new Python release.

thehesiod commented Feb 6, 2018

just hit this too

daniel-kukiela commented Feb 16, 2018

I have the same issue, just to let you know 🙂

vladiscripts commented Feb 16, 2018

thomaszdxsn commented Feb 23, 2018

I too. have something temp way fix it? pls

asvetlov commented Feb 23, 2018

The error is harmless, you could just ignore it.
asyncio tries to write into closed SSL connection and fails — but nothing is corrupted, the socket is closed successfully etc. Bug fix should just ignore such write tries.
I’ll apply the fix to Python 3.6.5

daniel-kukiela commented Feb 23, 2018 •

It depends.
It harms our voice channel steram using discordpy. I’m not sure if that’s because discordpy doesn’t handle that error from aiohttp, or aiohttp doesn’t handle error from asyncio.
End result — i can’t handle that in my code, no indicators that something happend, stream «looks» as usual, like nothing happend, but no data is streamed (i don’t even have a way to check and restart stream).
(i’m waiting for a next occurence of that issue to grab full stack and see)

asvetlov commented Feb 23, 2018

I pretty sure discord problem is not related.

daniel-kukiela commented Feb 23, 2018 •

The relation is stream breaks and i see that error in console. Or in other words — if that error occurs, stream breaks, but discordpy «doesn’t know» about that and is still streaming (no further error of any type, it just «streams» like nothing happend, but of course no data is transferred).
I’ll try to find out what and where doesn’t handle that properly and update here if necessary.

asvetlov commented Feb 23, 2018

Socket is closed before displaying the message, writing into closed socket is an error anyway.

Insoleet commented Mar 2, 2018

Probably related, additionnaly to the error reported in this issue, I also get such errors :

Insoleet commented Mar 9, 2018

Does this error means we need to reinit the Client Session before trying to send new requests ?

asvetlov commented Mar 9, 2018

I guess no. Just ignore all errors that happen on connection closing.

asvetlov commented Mar 10, 2018 •

Fixed in upstream, please test on Python 3.6.5

lock bot commented Oct 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs.
If you feel like there’s important points made in this discussion, please include those exceprts into that [new issue].
[new issue]: https://github.com/aio-libs/aiohttp/issues/new

Footer

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.

Источник