Re: Segfault on elog-3.1.5-1 when uploading file., posted by Stefan Ritt on Tue Jan 7 20:41:13 2025
|
It is in the usual download area which is referenced at https://elog.psi.ch/elog/download.html
Stefan
| Evinrude Motor wrote: |
|
When will the new source be in the standard download area ? I'm on ubuntu .
| gary holman wrote: |
|
Thanks Stefen!
I built from source (ELOG V3.1.5-3a5f2f00) and I confirmed as fixed.
| Stefan Ritt wrote: |
|
Thanks to your stack trace, I found a case where a string might get overwritten, but only if the attachment file name is longer than 256 chars. I fixed the code and made a new RPM:
https://www.dropbox.com/scl/fi/r37qx9aka5ytt3j7vn4km/elog-3.1.5-20241213.el8.x86_64.rpm?rlkey=knct99pdltggunrbmyr2hpfe5&st=pkre24aq&dl=0
Alternatively, you can compile from sources. Give it a try.
Stefan
|
|
|
|
|
Re: Installation with amp on Rocky Linux, posted by Stefan Ritt on Fri Mar 22 07:41:56 2024
|
Is there a way to install all dependencies automatically? Like if I install a package like "emacs" I get a list of dependencies with are automatically installed:
Dependencies Resolved
====================================================================================================================================
Package Arch Version Repository Size
====================================================================================================================================
Updating:
emacs x86_64 1:24.3-23.el7_9.1 rhel7 2.9 M
Updating for dependencies:
emacs-common x86_64 1:24.3-23.el7_9.1 rhel7 20 M
Transaction Summary
====================================================================================================================================
Upgrade 1 Package (+1 Dependent package)
Total download size: 23 M
Is this ok [y/d/N]:
| Laurent Jean-Rigaud wrote: |
|
Hi Nina,
The RPM is built with Kerberos (libber*), LDAP (libldap*) and SSL (libssl*) options. These libs are missing on your system, and rpm command does not take care of dependencies.
Try to install with yum : yum install elog-latest.el7.x86_64.rpm
Normally the missing rpm files should be dlded from RL repo if your host can access to them...
.
Laurent
| Nina Bondarenko wrote: |
|
Hello all,
I am installing elog on an Rocky Linux instance. Have dependensy problem.
rpm -Uvh elog-latest.el7.x86_64.rpm
error: Failed dependencies:
liblber-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libldap-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libssl.so.10()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libssl.so.10(libssl.so.10)(64bit) is needed by elog-3.1.5-1.el7.x86_64
Any clues from developers to resolve it and keep the software working. Thank you in advance!
Bests, Nina
|
|
|
|
Re: 3.1.5 - Mass edit bug + Wrong version, posted by Stefan Ritt on Tue Feb 7 20:45:31 2023
|
If it works with a simple edit, then why don't you use that one to edit individual values. I checked and version 3.1.4 had already the same problem, so it was not newly introduced. I would have to invest a couple of hours to fix this issue correcly, which I simply don't have right now. |
|
Re: mySQL / SQL synchronisation, posted by rus on Wed Mar 28 04:05:01 2012
|
> does anybody has interest with a full synchronisation
> between elog logbook
> on mySQL and SQL database
I am interested!!!
But I don't know how to do that. |
|
Re: link to attachment within html editor, posted by Stefan Ritt on Mon Oct 9 12:30:44 2023
|
You can always insert the full link to the attachment like this one: https://elog.psi.ch/elogs/Forum/231009_104933/SCR14.PNG
But you can also use elog:69699/1 as shown here. Unfortunately you can do that only after the entry has been submitted, so you know the ID number of that entry. Once you have it, edit the entry and put it in.
Stefan
| Celeste Torkzaban wrote: |
|
Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1 (elog :/1 without the space turned into 69699/1)
|
|
|
Re: HTTP headers should be parsed case insensitive, posted by Stefan Ritt on Wed Jul 31 14:21:21 2024
|
I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?
Stefan
| André wrote: |
|
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution.
|
|
|
Re: 3.1.5 - Mass edit bug + Wrong version, posted by Stefan Ritt on Tue Feb 7 16:21:37 2023
|
I checked and found that the bug which removed the main text was there since the beginning, but it's only triggered if you switch elog to French, it doesn't happen in the English version. I changed a bit the text processing so now it should work also in the French version.
I also changed the version number which is shown at the bottom to 3.1.5.
Stefan |
|
Re: Wikipedia Article deleted, posted by Stefan Ritt on Thu Jan 19 17:00:37 2023
|
I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.
Best,
Stefan
| Sebastian Schenk wrote: |
|
Hello,
I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."
I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.
|
|