Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 801 of 808  Not logged in ELOG logo
    icon2.gif   Re: TEXTSIZE too big message, posted by Illam Pakkirisamy on Wed May 17 17:43:46 2023 

Hi Xuan,

Sorry for the delayed response.  I just got back from my travel.  I tried your solution, but in my system I don't see elogd.h in the src folder.  Here is what I see and also I don't see any "make" binary in the folders.  I'm running the Windows version.

Thanks.
Illam

Xuan Wu wrote:

Hi Illam,

You can find it in src/elogd.h, #define TEXT_SIZE  250000, the original value 250000, you can change it to a larger one like #define TEXT_SIZE    1000000. Then recompile it again, just need typing "make". Elog Version is 3.1.3 in my site. HTH.

Cheers,

Xuan Wu

Illam Pakkirisamy wrote:

Hi,  any help will be appreciated on this.  I have not still figured this out.

Thanks.
Illam

Illam Pakkirisamy wrote:

Hi,

I'm getting the TEXTSIZE TOO BIG message every time I have more text in my entry.  I understand there is a way to increase the TEXTSIZE and re-compile.  Where can I find the TEXTSIZE parameter that I can increase and also how do I re-compile.

Appreciate your help.

Thanks.
Illam

 

 

 

    icon2.gif   Re: New elog version 3.1.5, posted by Finn Junker on Tue Apr 11 12:51:12 2023 

Hi Stefan

Is there anything the community or forum can help you with or supply for creating a windows version?

Kind Regards Finn

Stefan Ritt wrote:

A new version 3.1.5 of elog has been released with all accumulated fixes over the past actually few years. I made a tar file, a RPM, but I could not compile yet a windows version.

https://elog.psi.ch/elog/download.html

Best,
Stefan

 

    icon2.gif   Re: broken http response when deployed on OpenShift, posted by Enrico Gamberini on Mon Jul 15 09:45:56 2024 

Hi Laurent,

Thanks, good point! I'm building a vanilla version (no extra options enabled as I'm using Webserver authentication).

3.15 RPM:

-rwxr-xr-x. 1 elog elog 1574768 Feb 26 17:29 elogd

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

 

 

 

    icon2.gif   Re: HTML Editor not working after enabling SSL, posted by Daniel Sajdyk on Tue Mar 21 14:25:25 2023 elog.png

Hello,

I found that someone else had the same issue - https://dev.ckeditor.com/ticket/10874#no1

In Firefox I do not have problems, but in Chrome and Edge i have. 

His solution was:

My problem is solved. The .htaccess file sents any request to the login page. Therefore CKEditor could not reach the CSS file. Thanks for helping!

Sinse I don't use apache webserver, I don't know what should I do. 

It looks that also in my case problem is with file progressjs.min.css (please look at attached screenshot)

Anyone have solution for this?

Best Regards

Daniel

Daniel Sajdyk wrote:

Hello,

After enabling SSL=1 in /usr/loca/elog/elogd.cfg file, HTML editor loading very long. 

After changing SSL to 0, everything work flawlessly.

Does anyone know what can cause this behaviour?

Best Regards
Daniel

 

    icon2.gif   Re: HTML Editor not working after enabling SSL, posted by Daniel Sajdyk on Tue Mar 21 14:25:25 2023 

Hello,

I found that someon

Daniel Sajdyk wrote:

Hello,

After enabling SSL=1 in /usr/loca/elog/elogd.cfg file, HTML editor loading very long. 

After changing SSL to 0, everything work flawlessly.

Does anyone know what can cause this behaviour?

Best Regards
Daniel

 

    icon2.gif   Re: HTML Editor not working after enabling SSL, posted by Daniel Sajdyk on Tue Mar 21 14:25:26 2023 

Hello,

I found that someone else had the same issue - https://dev.ckeditor.com/ticket/10874#no1

But I don't know why

Daniel Sajdyk wrote:

Hello,

After enabling SSL=1 in /usr/loca/elog/elogd.cfg file, HTML editor loading very long. 

After changing SSL to 0, everything work flawlessly.

Does anyone know what can cause this behaviour?

Best Regards
Daniel

 

    icon2.gif   Re: Record date isn't set to current date when replying to elogs, posted by Stefan Ritt on Mon Apr 15 17:50:20 2024 

Have you tried the config option "Preset on reply <attribute> = $date". On a reply, the <attribute> will be preset with the current date.

Stefan

Celeste Torkzaban wrote:

Hello,

I started using the record date feature in one logbook, since we plan to copy over old entries Joplin/Onenote. When starting a new entry, I see that the record date is automatically set to the current date, but when I reply to an elog, the record date is automatically set to the record date of the elog I'm replying to. Is there a way to fix this?

 

 

    icon2.gif   Re: Exporting the entries from ELOG, posted by Stefan Ritt on Tue Feb 28 19:22:50 2023 

Find -> Export to...

Illam Pakkirisamy wrote:

Hi,

Is there a way to export the ELOG entries into a file like an Excel sheet or something.  I see import but not export.

Appreciate your help.

Thanks.

Illam

 

ELOG V3.1.5-3fb85fa6