Re: libssl.so.1.1 / OPENSSL_1_1_1 not found after upgrade (ubuntu server 18.04 / apache / mod_wsgi)
Luke! That did the trick! Many thanks.
Am Mo., 24. Juni 2019 um 01:19 Uhr schrieb Luke :
> Hah! Found it!
>
> The psycopg2-binary module needed to be reinstalled (now version 2.8.3)
>
> I believe the old one must have been compiled against libssl1.1.0, which
> was replaced by 1.1.1 in the upgrade which broke things.
>
> On Monday, June 24, 2019 at 11:11:11 AM UTC+12, Luke wrote:
>>
>> I'm having the same problem, totally unable to find a resolution so far.
>>
>> I get no error messages of any use, even with all logging set to DEBUG.
>> The only thing i'm seeing is "Truncated or oversized response headers
>> received from daemon process" in the apache error log.
>>
>> Works fine when using the Django development server. Broke last week
>> after updating the system python and openssl packages.
>>
>> Anyone else having this problem?
>>
>> On Friday, June 14, 2019 at 1:31:29 PM UTC+12, Volker wrote:
>>>
>>> Two days ago my django app which runs on an Ubuntu 18.04.2 LTS server
>>> with apache 2.4 (from repo9 and mod_wsgi in an venv with Python 3.6 throws
>>> an exception after https login - as it seems - after a package upgrade.
>>> To my understanding libssl/openssl is causing the error. The error
>>> message below states that openssl_1_1_1 is not found. Though it seems to be
>>> installed.
>>>
>>> Could you guys give me a pointer? Please let me know if I need to
>>> provide additional information.
>>>
>>> Thanks and cheers!
>>>
>>>
>>>
>>> Two days ago following packages where upgraded:
>>> =
>>> libelf1:amd64 0.170-0.4 => 0.170-0.4ubuntu0.1
>>> libglib2.0-0:amd64 2.56.4-0ubuntu0.18.04.2 => 2.56.4-0ubuntu0.18.04.3
>>> libglib2.0-data:all 2.56.4-0ubuntu0.18.04.2 =>
>>> 2.56.4-0ubuntu0.18.04.3
>>> libnss-systemd:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>>> libpam-systemd:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>>> libpython3.6-minimal:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>>> libpython3.6-stdlib:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>>> libpython3.6:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>>> libssl1.1:amd64 1.1.0g-2ubuntu4.3 => 1.1.1-1ubuntu2.1~18.04.1
>>> libsystemd0:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>>> libudev1:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>>> openssl:amd64 1.1.0g-2ubuntu4.3 => 1.1.1-1ubuntu2.1~18.04.1
>>> python3-cryptography:amd64 2.1.4-1ubuntu1.2 => 2.1.4-1ubuntu1.3
>>> python3-distutils:all 3.6.7-1~18.04 => 3.6.8-1~18.04
>>> python3-gdbm:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04
>>> python3-lib2to3:all 3.6.7-1~18.04 => 3.6.8-1~18.04
>>> python3.6-minimal:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>>> python3.6-venv:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>>> python3.6:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>>> systemd-sysv:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>>> systemd:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>>> udev:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>>>
>>> Login Implementation
>>>
>>> Im using djangos login views:
>>> settings.py:
>>> LOGIN_URL = '/accounts/login/'
>>> urls.py:
>>> path('accounts/', include('django.contrib.auth.urls')),
>>>
>>> Error after Login Page of application / and django admin:
>>>
>>> "Internal Server Error
>>> The server encountered an internal error or misconfiguration and was
>>> unable to complete your request."
>>>
>>> Error in Apache Log
>>> ==
>>> [Thu Jun 13 18:58:10.555937 2019] [wsgi:error] [pid 1274:tid
>>> 140451378087680] [client 77.8.21.189:48212] mod_wsgi (pid=1274):
>>> Request data read error when proxying data to daemon process: Connection
>>> reset by peer.
>>> [Thu Jun 13 20:46:51.186545 2019] [wsgi:error] [pid 1274:tid
>>> 140451252197120] [client 217.18.178.226:61510] Truncated or oversized
>>> response headers received from daemon process 'fotobau.ourdomain.de':
>>> /srv/fotobau/djangoprojekt/wsgi.py, referer:
>>> https://www.fotobau.ourdomain/accounts/login/
>>>
>>> Unfortunately I failed to obtain a core dump till now.
>>>
>>> Though right now I suspect the problem occurs when django tries to
>>> receive the https/encrypted user and password. I suspect this because I got
>>> another error message!
>>>
>>> Another Error in Django Log
>>>
>>> Here I got a new error message: The first one ('Exception' is not JSON
>>> serializable) is fairly common - though I didn´t manage to fix it till now,
>>> it never really bothered.
>>> Though after the package upgrade it raises a new error message (which
>>> will raise itself again for 3 times) below - the one with "ImportError:
>>> /usr/lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1":
>>>
>>> ERROR 2019-06-12 19:57:17,638 log 505 Internal Server Error:
>>> /restservice/v1/fotos/
>>> Traceback (most recent call last):
>>> File
>>> "/home/eidle/.virtualenvs/fotobau/lib/python3.6/site-packages/django/core/handlers/exception.py",
>>> line 34, in
Re: libssl.so.1.1 / OPENSSL_1_1_1 not found after upgrade (ubuntu server 18.04 / apache / mod_wsgi)
Hah! Found it!
The psycopg2-binary module needed to be reinstalled (now version 2.8.3)
I believe the old one must have been compiled against libssl1.1.0, which
was replaced by 1.1.1 in the upgrade which broke things.
On Monday, June 24, 2019 at 11:11:11 AM UTC+12, Luke wrote:
>
> I'm having the same problem, totally unable to find a resolution so far.
>
> I get no error messages of any use, even with all logging set to DEBUG.
> The only thing i'm seeing is "Truncated or oversized response headers
> received from daemon process" in the apache error log.
>
> Works fine when using the Django development server. Broke last week after
> updating the system python and openssl packages.
>
> Anyone else having this problem?
>
> On Friday, June 14, 2019 at 1:31:29 PM UTC+12, Volker wrote:
>>
>> Two days ago my django app which runs on an Ubuntu 18.04.2 LTS server
>> with apache 2.4 (from repo9 and mod_wsgi in an venv with Python 3.6 throws
>> an exception after https login - as it seems - after a package upgrade.
>> To my understanding libssl/openssl is causing the error. The error
>> message below states that openssl_1_1_1 is not found. Though it seems to be
>> installed.
>>
>> Could you guys give me a pointer? Please let me know if I need to provide
>> additional information.
>>
>> Thanks and cheers!
>>
>>
>>
>> Two days ago following packages where upgraded:
>> =
>> libelf1:amd64 0.170-0.4 => 0.170-0.4ubuntu0.1
>> libglib2.0-0:amd64 2.56.4-0ubuntu0.18.04.2 => 2.56.4-0ubuntu0.18.04.3
>> libglib2.0-data:all 2.56.4-0ubuntu0.18.04.2 => 2.56.4-0ubuntu0.18.04.3
>> libnss-systemd:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>> libpam-systemd:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>> libpython3.6-minimal:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>> libpython3.6-stdlib:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>> libpython3.6:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>> libssl1.1:amd64 1.1.0g-2ubuntu4.3 => 1.1.1-1ubuntu2.1~18.04.1
>> libsystemd0:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>> libudev1:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>> openssl:amd64 1.1.0g-2ubuntu4.3 => 1.1.1-1ubuntu2.1~18.04.1
>> python3-cryptography:amd64 2.1.4-1ubuntu1.2 => 2.1.4-1ubuntu1.3
>> python3-distutils:all 3.6.7-1~18.04 => 3.6.8-1~18.04
>> python3-gdbm:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04
>> python3-lib2to3:all 3.6.7-1~18.04 => 3.6.8-1~18.04
>> python3.6-minimal:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>> python3.6-venv:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>> python3.6:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
>> systemd-sysv:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>> systemd:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>> udev:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>>
>> Login Implementation
>>
>> Im using djangos login views:
>> settings.py:
>> LOGIN_URL = '/accounts/login/'
>> urls.py:
>> path('accounts/', include('django.contrib.auth.urls')),
>>
>> Error after Login Page of application / and django admin:
>>
>> "Internal Server Error
>> The server encountered an internal error or misconfiguration and was
>> unable to complete your request."
>>
>> Error in Apache Log
>> ==
>> [Thu Jun 13 18:58:10.555937 2019] [wsgi:error] [pid 1274:tid
>> 140451378087680] [client 77.8.21.189:48212] mod_wsgi (pid=1274): Request
>> data read error when proxying data to daemon process: Connection reset by
>> peer.
>> [Thu Jun 13 20:46:51.186545 2019] [wsgi:error] [pid 1274:tid
>> 140451252197120] [client 217.18.178.226:61510] Truncated or oversized
>> response headers received from daemon process 'fotobau.ourdomain.de':
>> /srv/fotobau/djangoprojekt/wsgi.py, referer:
>> https://www.fotobau.ourdomain/accounts/login/
>>
>> Unfortunately I failed to obtain a core dump till now.
>>
>> Though right now I suspect the problem occurs when django tries to
>> receive the https/encrypted user and password. I suspect this because I got
>> another error message!
>>
>> Another Error in Django Log
>>
>> Here I got a new error message: The first one ('Exception' is not JSON
>> serializable) is fairly common - though I didn´t manage to fix it till now,
>> it never really bothered.
>> Though after the package upgrade it raises a new error message (which
>> will raise itself again for 3 times) below - the one with "ImportError:
>> /usr/lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1":
>>
>> ERROR 2019-06-12 19:57:17,638 log 505 Internal Server Error:
>> /restservice/v1/fotos/
>> Traceback (most recent call last):
>> File
>> "/home/eidle/.virtualenvs/fotobau/lib/python3.6/site-packages/django/core/handlers/exception.py",
>>
>> line 34, in inner
>> response = get_response(request)
>> File
>> "/home/eidle/.virtualenvs/fotobau/lib/python3.6/site-packages/django/core/handlers/base.py",
>>
>> line 156, in
Re: libssl.so.1.1 / OPENSSL_1_1_1 not found after upgrade (ubuntu server 18.04 / apache / mod_wsgi)
I'm having the same problem, totally unable to find a resolution so far.
I get no error messages of any use, even with all logging set to DEBUG. The
only thing i'm seeing is "Truncated or oversized response headers received
from daemon process" in the apache error log.
Works fine when using the Django development server. Broke last week after
updating the system python and openssl packages.
Anyone else having this problem?
On Friday, June 14, 2019 at 1:31:29 PM UTC+12, Volker wrote:
>
> Two days ago my django app which runs on an Ubuntu 18.04.2 LTS server with
> apache 2.4 (from repo9 and mod_wsgi in an venv with Python 3.6 throws an
> exception after https login - as it seems - after a package upgrade.
> To my understanding libssl/openssl is causing the error. The error message
> below states that openssl_1_1_1 is not found. Though it seems to be
> installed.
>
> Could you guys give me a pointer? Please let me know if I need to provide
> additional information.
>
> Thanks and cheers!
>
>
>
> Two days ago following packages where upgraded:
> =
> libelf1:amd64 0.170-0.4 => 0.170-0.4ubuntu0.1
> libglib2.0-0:amd64 2.56.4-0ubuntu0.18.04.2 => 2.56.4-0ubuntu0.18.04.3
> libglib2.0-data:all 2.56.4-0ubuntu0.18.04.2 => 2.56.4-0ubuntu0.18.04.3
> libnss-systemd:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
> libpam-systemd:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
> libpython3.6-minimal:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
> libpython3.6-stdlib:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
> libpython3.6:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
> libssl1.1:amd64 1.1.0g-2ubuntu4.3 => 1.1.1-1ubuntu2.1~18.04.1
> libsystemd0:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
> libudev1:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
> openssl:amd64 1.1.0g-2ubuntu4.3 => 1.1.1-1ubuntu2.1~18.04.1
> python3-cryptography:amd64 2.1.4-1ubuntu1.2 => 2.1.4-1ubuntu1.3
> python3-distutils:all 3.6.7-1~18.04 => 3.6.8-1~18.04
> python3-gdbm:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04
> python3-lib2to3:all 3.6.7-1~18.04 => 3.6.8-1~18.04
> python3.6-minimal:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
> python3.6-venv:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
> python3.6:amd64 3.6.7-1~18.04 => 3.6.8-1~18.04.1
> systemd-sysv:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
> systemd:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
> udev:amd64 237-3ubuntu10.21 => 237-3ubuntu10.22
>
> Login Implementation
>
> Im using djangos login views:
> settings.py:
> LOGIN_URL = '/accounts/login/'
> urls.py:
> path('accounts/', include('django.contrib.auth.urls')),
>
> Error after Login Page of application / and django admin:
>
> "Internal Server Error
> The server encountered an internal error or misconfiguration and was
> unable to complete your request."
>
> Error in Apache Log
> ==
> [Thu Jun 13 18:58:10.555937 2019] [wsgi:error] [pid 1274:tid
> 140451378087680] [client 77.8.21.189:48212] mod_wsgi (pid=1274): Request
> data read error when proxying data to daemon process: Connection reset by
> peer.
> [Thu Jun 13 20:46:51.186545 2019] [wsgi:error] [pid 1274:tid
> 140451252197120] [client 217.18.178.226:61510] Truncated or oversized
> response headers received from daemon process 'fotobau.ourdomain.de':
> /srv/fotobau/djangoprojekt/wsgi.py, referer:
> https://www.fotobau.ourdomain/accounts/login/
>
> Unfortunately I failed to obtain a core dump till now.
>
> Though right now I suspect the problem occurs when django tries to receive
> the https/encrypted user and password. I suspect this because I got another
> error message!
>
> Another Error in Django Log
>
> Here I got a new error message: The first one ('Exception' is not JSON
> serializable) is fairly common - though I didn´t manage to fix it till now,
> it never really bothered.
> Though after the package upgrade it raises a new error message (which will
> raise itself again for 3 times) below - the one with "ImportError:
> /usr/lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1":
>
> ERROR 2019-06-12 19:57:17,638 log 505 Internal Server Error:
> /restservice/v1/fotos/
> Traceback (most recent call last):
> File
> "/home/eidle/.virtualenvs/fotobau/lib/python3.6/site-packages/django/core/handlers/exception.py",
>
> line 34, in inner
> response = get_response(request)
> File
> "/home/eidle/.virtualenvs/fotobau/lib/python3.6/site-packages/django/core/handlers/base.py",
>
> line 156, in _get_response
> response = self.process_exception_by_middleware(e, request)
> File
> "/home/eidle/.virtualenvs/fotobau/lib/python3.6/site-packages/django/core/handlers/base.py",
>
> line 154, in _get_response
> response = response.render()
> File
> "/home/eidle/.virtualenvs/fotobau/lib/python3.6/site-packages/django/template/response.py",
>
> line 106, in render
>
