NAV 5.1.2
I had to upgrade the OS on my NAV-box, and hence all the software depending on libraries.
After this I have wsgi throwing errors on me. Not all the time. Users local to NAV can log in just fine, but users who authenticate via ldap gets the error.
I have tried to reinstall psycopg2. I have also switched from installing mod_wsgi from an OS-package to using pip
Apache/2.4.51 (FreeBSD) OpenSSL/1.1.1l mod_wsgi/4.9.0 Python/3.7
The error is not connected to communication with the ldap-server (AD)
Output with debug=true in webfront.conf
ldap_create ldap_url_parse_ext(ldaps://XXXX.ad.uit.no:636) ldap_sasl_bind ldap_send_initial_request ldap_new_connection 1 1 0 ldap_int_open_connection ldap_connect_to_host: TCP XXXX.ad.uit.no:636 ldap_new_socket: 18 ldap_prepare_socket: 18 ldap_connect_to_host: Trying 129.242.xx.zzz:636 ldap_pvt_connect: fd: 18 tm: -1 async: 0 attempting to connect: connect success [Tue Nov 02 08:53:35.941429 2021] [wsgi:error] [pid 34769] [client 129.242.14.106:49209] Truncated or oversized response headers received from daemon process 'NAV': /usr/local/lib/python3.7/site-packages/nav/wsgi.py, referer: https://nav.uit.no/index/login/?origin=/&noaccess [Tue Nov 02 08:53:35.977367 2021] [core:notice] [pid 34758] AH00052: child pid 34760 exit signal Segmentation fault (11)
Any ideas?
--Ingeborg
NAV 5.1.2
I had to upgrade the OS on my NAV-box, and hence all the software depending on libraries.
After this I have wsgi throwing errors on me. Not all the time. Users local to NAV can log in just fine, but users who authenticate via ldap gets the error.
Problem resolved. Turned out that openldap was linked towards an older version of openssl.
--Ingeborg