[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [Libevent-users] SSL problems after update to libeven 2.1.8
- To: libevent-users@xxxxxxxxxxxxx
- Subject: Re: [Libevent-users] SSL problems after update to libeven 2.1.8
- From: Azat Khuzhin <a3at.mail@xxxxxxxxx>
- Date: Wed, 14 Feb 2018 18:52:28 +0300
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: libevent-users-outgoing@xxxxxxxx
- Delivered-to: libevent-users@xxxxxxxx
- Delivery-date: Wed, 14 Feb 2018 10:52:48 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=NRb+BhiJFBZmu01GzLQy4NiphjDRpajTxRdkYhbfKbI=; b=qcJSs7M31bjHeNjAXPHvQL5atgrKpfr+jXs8dNN+FRn135kDMsiSxjcpGkTDTDszwT WlV6c1XcCO4ORIOL0N5uY2yvZ1UWEemQvpekCtxAPSrx2tfvLRZThYMAM+21WOmuvCDj KAMiqbtbZv6Q0Zu7k+6UtIOF3FhpZqVsOLrUWH+LJkf2oSUTaU/FzxeGhKy/wU9S1zhE 4nDZuJAV++r/v0DoZWV8VHq2rCVby7c3tr9mZdipMQ1cRsFB/mDDmavcVjjbStJ4osjk jy1UkQG02agv2D5AZH+NtLtdBN6iDsmUzvinYCcLwTQJ2IjR528MEcu/Fhdwx6eoPP/s TR5A==
- In-reply-to: <217F0ED1-142B-436E-BDB1-CA4066833D2D@mesosphere.io>
- References: <631C57CE-6BA7-472A-B964-0F3C46BF9E49@mesosphere.io> <20180122202742.GN8106@azat> <CAL2dqyOXMCWcTC+oHrgLy95vOi3aZpnYSzaFMxP6yjn4Tr+uJw@mail.gmail.com> <20180124155336.GO8106@azat> <CAL2dqyP=a2V87zqZhMayrjMg--pf9L-riOxOAfpq6pT2ZB1o7g@mail.gmail.com> <20180204194905.GP8106@azat> <217F0ED1-142B-436E-BDB1-CA4066833D2D@mesosphere.io>
- Reply-to: libevent-users@xxxxxxxxxxxxx
- Sender: owner-libevent-users@xxxxxxxxxxxxx
- User-agent: Mutt/1.9.3 (2018-01-21)
On Wed, Feb 14, 2018 at 04:33:07PM +0100, Alexander Rojas wrote:
> Really hard to achieve, I was playing around and failed to get a minimal reproducer.
Maybe you have a container with all this stuff (+debug symbols) ?
So that I can play in it.
> [debug] ../event.c: asked to terminate loop.
H, who asked this?
> [debug] timeout_next: event: 0x7f70d0000df0, in 0 seconds, 71990 useconds
> Error was 2
> Error was 5
So:
- 2 is SSL_ERROR_WANT_READ
- 5 is SSL_ERROR_SYSCALL
(according to openssl/ssl.h)
So can you add printing of errno along with SSL_get_error() in print_err()?
It looks like it got SSL_ERROR_WANT_READ and then tried to read() but
failed, and hence SSL_ERROR_SYSCALL.
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users in the body.