ELOG

bash-5.1$ ldd /usr/local/sbin/elogd
   linux-vdso.so.1 (0x00007fff215f7000)
   libssl.so.3 => /lib64/libssl.so.3 (0x00007feff74c6000)
   libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007feff73eb000)
   libldap.so.2 => /lib64/libldap.so.2 (0x00007feff7384000)
   liblber.so.2 => /lib64/liblber.so.2 (0x00007feff7372000)
   libpam.so.0 => /lib64/libpam.so.0 (0x00007feff7360000)
   libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007feff7139000)
   libm.so.6 => /lib64/libm.so.6 (0x00007feff705c000)
   libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007feff7041000)
   libc.so.6 => /lib64/libc.so.6 (0x00007feff6e38000)
   libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007feff6a07000)
   libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007feff69ee000)
   libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007feff69e7000)
   libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007feff69d4000)
   libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007feff69cd000)
   libresolv.so.2 => /lib64/libresolv.so.2 (0x00007feff69b9000)
   libevent-2.1.so.7 => /lib64/libevent-2.1.so.7 (0x00007feff6960000)
   libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007feff6940000)
   libaudit.so.1 => /lib64/libaudit.so.1 (0x00007feff6912000)
   libeconf.so.0 => /lib64/libeconf.so.0 (0x00007feff6905000)
   /lib64/ld-linux-x86-64.so.2 (0x00007feff7572000)
   libz.so.1 => /lib64/libz.so.1 (0x00007feff68eb000)
   libselinux.so.1 => /lib64/libselinux.so.1 (0x00007feff68be000)
   libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007feff6884000)
   libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007feff682d000)
   libcap-ng.so.0 => /lib64/libcap-ng.so.0 (0x00007feff6822000)
   libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007feff6786000)

3.15 source vanilla build:

-rwxr-xr-x. 1 root root 1503896 Jul 15 09:31 elogd

bash-5.1$ ldd elogd
   linux-vdso.so.1 (0x00007fff60bbf000)
   libssl.so.3 => /lib64/libssl.so.3 (0x00007f8f83e44000)
   libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f8f83c1b000)
   libm.so.6 => /lib64/libm.so.6 (0x00007f8f83b40000)
   libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f8f83b25000)
   libc.so.6 => /lib64/libc.so.6 (0x00007f8f8391c000)
   libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007f8f834e9000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f8f83ef0000)
   libz.so.1 => /lib64/libz.so.1 (0x00007f8f834cd000)

Best,
Enrico

Laurent Jean-Rigaud wrote:

Hey Enrico,

Do you activate also all options with your build ? (pam/ldap/kb5/ssl)

Can you compare ldd command results on elogd binaries builded by yourself and the one from RPM ?

$ ldd /path/to/elogd

Also, size of both elogd files.

Regards

Enrico Gamberini wrote:

Sorry for posting again but something else came up.

Actually, building from source (elog-3.1.5-1.tar.gz) works just fine on OpenShift too.

The problem described below only happens when installing the packaged binary elog-3.1.5-20240226.el9.x86_64.rpm.

Best,
Enrico

Enrico Gamberini wrote:

Hello!

We're setting up ELOG on OpenShift. ELOG is installed on a Alma Linux 9 image. The container and the elog demo works fine executing the docker image locally.

When deployed on OpenShift, we get a weird response, that results in a 502 Bad Gateway. The broken response looks like:

# curl -v -H 'X-Forwarded-User: enrico.gamberini@cern.ch' https://psi-elog-container2-elisa-epdtdi.app.cern.ch/demo/

<html>redir</html>
HTTP/1.1 200 Document follows
HTTP/1.1 200 Document follows
Server: ELOG HTTP 3.1.5-23df00d
Content-Type: text/html;charset=ISO-8859-1
Set-Cookie: elmode=Summary; path=/demo; expires=Friday, 07-Dec-35 06:30:26 GMT;
Pragma: no-cache
Cache-control: private, max-age=0, no-cache, no-store

Notice the HTML tag before the HTTP header, as well the duplicate HTTP header.

I understand that it might be difficult to reproduce, but any input would be very welcome!

Thanks!

Best,
Enrico

ELOG V3.1.5-3fb85fa6