very long subject cause buffer overflow, posted by Stefano Lacaprara on Tue Apr 14 13:26:50 2020
|
Hi,
I'm using elog 313 on an ubuntu server.
|
Re: very long subject cause buffer overflow, posted by Stefano Lacaprara on Thu Apr 16 10:07:18 2020
|
Additional information: I tried to recompile with -g (debug) and run it in gdb but the crash is not reproduced that way (w/ or w/o gdb). I guess that the
memory handling in debug mode is different so the corruption is not
there anymore.
|
|
Re: very long subject cause buffer overflow, posted by Stefan Ritt on Thu Apr 16 10:11:13 2020
|
Can you try to reproduce it on this (!) server? I cannot reproduce it on my home copy server, so I guess that might be fixed in meantime. Can you update
to the current version of elog?
|
|
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate v
|
| My try on this server ->> see the subject |
|
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate v
|
indeed, I'll try to move to ELOG V3.1.4-80633ba
> My try on this server ->> see the subject |
|
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate v
|
> indeed, I'll try to move to ELOG V3.1.4-80633ba
>
> > My try on this server ->> see the subject
|
|
... subject erased ..., posted by Stefan Ritt on Thu Apr 16 11:03:03 2020
|
I found two potential memory leaks which I fixed in the git version, so you can try again.
Another possibility, which is actually preferred, is to limit the size of the subject filed to a reasonable number. You can do that with following option
|
|
... subject erased ..., posted by Stefano Lacaprara on Thu Apr 16 11:12:32 2020
|
> I found two potential memory leaks which I fixed in the git version, so you can try again.
Just tested, and it works! Many thanks for very quick patch!
|
Mirroring function for a full both-sides synchronization, posted by Sergei Gavrilov on Mon Feb 24 15:58:55 2020
|
Hello, dear ELOG's gurus.
Please help me to understand a problem with mirroring function.
It appears in ELOG V3.1.4-a04faf9f - the last official Windows release, as well as previous 3.1.3 Windows release, which I have checked for |
Re: Mirroring function for a full both-sides synchronization, posted by Stefan Ritt on Thu Apr 2 13:37:21 2020 
|
The entry ID #0 was a bug in logging routine only, so in the elog logbook the ID is certainly not zero. But the logging bug has been fixed now, so please
update your version of elog.
Then I tried to reproduce your problem. I set up two servers, the master listening at port 8080 and the slave listening at port 8081. I created |
How to add bulk client list at once, posted by Sunilkumar on Sun Mar 29 13:30:09 2020
|
Please let me know how to add Button for adding client next to Client Mnemonics.
I need to add bulk client lists in the Elog page there are 1000+ clients . |
|
Re: How to add bulk client list at once, posted by Stefan Ritt on Wed Apr 1 15:16:43 2020
|
Options are limited to 200. To add options dynamically, use
Extendable options = <name>
as desribed in the manual. |
|
Re: How to add bulk client list at once, posted by Sunilkumar on Wed Apr 1 19:27:53 2020
|
Hi Stefan
Thanks for Response , It helped me lot .
is it possible to give refence to include 1000 clients in one file and adding that referece file to Roptions ? |
|
Re: How to add bulk client list at once, posted by Stefan Ritt on Wed Apr 1 20:01:26 2020
|
No, that's not possible with elog.
Sunilkumar
wrote:
Hi Stefan |
|
email notification fail to retrieve images in the text , posted by MATT TERRON on Wed Apr 1 12:29:47 2020
|
When I use the email notification for an entry with images in the text, it seems the email server cannot retrieve the image. When I inspected the URL
of the image it went to the login page.
Is that because the logbook has a password config that the access from the URL of the image needs authentication? Or |
|
Re: email notification fail to retrieve images in the text , posted by Stefan Ritt on Wed Apr 1 13:01:39 2020
|
First thing you want to try is to upgrade elog to the last version. Older versions have problems in including images.
Then you want to check the "Email Format" in your elogd.cfg configuration file. Only if "16" is included there, then attachments
are sent as email attachments and images will be included in yoru email. If not, only a link of the image is included in your email, and you correctly |
|
How does attributes substitution work?, posted by Gianluca Rigoletti on Fri Mar 20 14:07:59 2020
|
Hello,
Let's say I have a logboook where I define two attributes:
[TOTEM] |
|
Re: How does attributes substitution work?, posted by Stefan Ritt on Fri Mar 20 14:24:28 2020
|
There could be a bug which is triggered by the fact that $M is a substring of $min. Try to rename $M to $Month or so.
Stefan
Gianluca |
|
How to update date fields so 'alarms' work correctly., posted by John on Sat Feb 29 06:04:57 2020
|
Hi Stefan!
In the user manual under misc it says this: "The elog program makes it possible to submit logbook
entries automatically by the system or from scripts. In some shift logbooks this feature is used to enter alarm messages automatically into the logbook. |
|
Re: How to update date fields so 'alarms' work correctly., posted by Sebastian Schenk on Fri Mar 13 16:38:53 2020
|
Dear John,
I am a user of the elog system and no developer, so no complete answer guaranteed.
The quote of the manual describes the case, if e.g. an hardware component discovers a failure and the connected PC makes an automatic (new) entry |
|
Re: How to update date fields so 'alarms' work correctly., posted by John on Fri Mar 13 18:34:30 2020
|
Hi Sebastian!
Thank you soo much for your kind response. You are correct in all of your assumptions as to what I want to do (or not do!). Everything should
be on clients side, and I want the date to be updated in each record, daily, or hourly, in order to allow the 'alarm' system I created to be able |
|
ELOG reverts to demo configuration, posted by VUIIS SysAdmin on Thu Feb 20 16:54:32 2020
|
I have been using elog for over 10 years. Suddenly my elog installation has changed (probably from a recent update. My /etc/elogd.cfg has changed to
the original demo configuration. Even after changing it to my configuration from backup none of the entries for the logbooks apper even though the tabs
for the logboos are ther all logbooks are empty. I have looced at the logbook files and the entries seem to be there but are not showing on the web interface. |
|
Re: ELOG reverts to demo configuration, posted by Andreas Luedeke on Fri Feb 21 19:11:12 2020
|
If you've upgraded from an elog 2.x version to an 3.x version, then all entries of a logbook will be moved into subfolder, one for each year.
If you then switch back to the 2.x version of elog, it'll not find any entries.
You can move them back to the folder for the logbook (one directory up) and they'll be found again after the next restart of elog. |
|
Elogd crashes on search, posted by Laurent Jean-Rigaud on Fri Jan 31 15:17:04 2020
|
OS: CentOS 7 x86_64 up2date with RPM 3.14 x86_64
Connexion to ELOG
open one logbook and click search,
input "test" and click "Search" : BOOM
Firefox
can not connect anymore on ELOG.
The crash is met with several words now ("test", "post", "4.5", are the |
|
Re: Elogd crashes on search, posted by Stefan Ritt on Fri Jan 31 15:27:21 2020
|
Do you see the same problem on this server here?
If not, then it must be related to your specific configuration. You have to teach me how to reporduce the error in order to fix it. Best would
be a minimal elogd.cfg which causes the error. |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Fri Jan 31 15:34:56 2020
|
Hi Stefan,
The problem seems to be specific with our logbooks. Maybe one of the file is corrupted or bad string encoding ?! But how to find the source of
the problem ? |
|
Re: Elogd crashes on search, posted by Stefan Ritt on Fri Jan 31 15:46:09 2020
|
The only way for me is to reproduce it. Could be corrupted data file, or config file. Try with a new logbook with the same configuration, then add logbook
files one by one until it happens.
Stefan |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Mon Feb 3 13:31:15 2020
|
Hi Stefan.
I installed debuginfo and ran elogd with gdb attached.
(gdb) backtrace |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Tue Feb 4 13:56:51 2020
|
Hi Stefan,
My previous dump is useless as your elog-debuginfo rpm is stripped.
So i rebuild elog w/ -g , reinstall it and activate core generation. I restst a search of "test" and get this in gdb corefile . |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Tue Feb 4 17:07:02 2020
|
At #5, there is message_id=426 . You think it's this elog entries # 426 that is the source of crash ?
Laurent
Jean-Rigaud wrote:
Hi Stefan, |
|
Re: Elogd crashes on search, posted by Stefan Ritt on Tue Feb 4 17:19:49 2020
|
Looks like. Can you dig into the database file and have a look at that entry? Or send me the file containing that entry (together with your elogd.cfg)
Stefan
Laurent |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Tue Feb 4 18:33:56 2020
|
Stefan,
I cut the log in two parts w/o modifying the content and the search runs. It seems that the size of this entrie 426 is closed to a limit (as
during testing, i met a message after clicking save to recompile elog to increase a size of something), so it could be the problem. |
|
Re: Elogd crashes on search, posted by Stefan Ritt on Tue Feb 11 12:12:49 2020
|
Thanks for the detailed investiations and report. Finally I could reproduce the problem by having messages with a text body size close to 250000 bytes
(some internal limit). Never thought that someone really has the patience to write 250'000 chars in a single message, but I guess you did some copy/paste
from a large file. Thought in such cases people use attachments. Nevertheless, I fixed an internal memory allocation problem, now it shoudl be fine to |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Fri Feb 21 14:42:25 2020
|
Thanks to you, Stefan !
You software is very usefull for us and it's nice to have support.
Have a nice day ! |