HTML editor tools grayed out, posted by Ehab Fanous on Wed Jan 22 19:35:36 2020
|
After we upgarde to eLog 3.1.4 ... The HTML editor tools are grayed out and you can't paste any images in the body of the log like I did below..
Any help will be much appreciated..
|
Re: HTML editor tools grayed out, posted by Stefan Ritt on Wed Jan 22 20:02:09 2020
|
This typically happens if you update only the executabe and not the full directory tree with the ELOG JavaScript files.
/Stefan
Ehab |
|
Re: HTML editor tools grayed out, posted by Ehab Fanous on Thu Jan 23 14:28:28 2020
|
Thank yoy for responding back to me ... I run the excutable that I downloaded from the website .. How can I do the full directory tree with the ELOG
JavaScript files??
Stefan |
|
Re: HTML editor tools grayed out, posted by Ehab Fanous on Fri Jan 24 21:50:37 2020
|
We just tested eLog and it works in Chrome but not in IE .. Is it a setting issue that we need to chnage on IE ?!
Stefan
Ritt wrote:
This typically happens if you update only the executabe and not the |
|
local usage on windows + Linux virtual machine , posted by Sara Vanini on Fri Jan 24 14:56:56 2020
|
Hello again,
I love to use elog, but I don't need any other accessing it for the moment. So, it is possible to run elog locally on my PC, and make it
not accessible from outside? |
|
Re: local usage on windows + Linux virtual machine , posted by John on Fri Jan 24 21:04:51 2020
|
Elog does not access the outside world by default. With the VM I suppose just access it via the Linux local ip address (and
port).
Sara Vanini wrote:
Hello again, |
|
Re: local usage on windows + Linux virtual machine , posted by Sara Vanini on Mon Jan 27 08:46:39 2020
|
Thanks John. I found the linux IP address with ifconfig, type it on my windows machine with the port number, but it doesn't work, the error is "website
not found"... what else could I try?
Regards |
|
PAM authentication question, posted by David Wallis on Tue Nov 5 21:42:50 2019
|
I'm testing the PAM authentication feature, and have a couple questions, a suggestion, and a comment.
First the comment... it was pretty easy to get working, and is exactly what we need here, so thanks! Our PAM stack here is designed to allow
logins with Active Directory, LDAP, or local accounts, so the PAM option preserves all of that. |
|
Re: PAM authentication question, posted by Jan Christoph Terasa on Sun Nov 17 14:55:11 2019
|
David Wallis
wrote:
I'm testing the PAM authentication feature, and have a couple questions,
a suggestion, and a comment. |
|
Re: PAM authentication question, posted by David Wallis on Thu Nov 21 18:10:28 2019
|
Hi Christoph,
Thanks for looking into this, if you can enable PAM + File, our users would be very happy!
The pam.d issue is probably related to CentOS/Red Hat, since our PAM expert warned me that it might be necessary. |
|
Re: PAM authentication question, posted by Jan Christoph Terasa on Thu Dec 19 17:46:33 2019
|
Hi David,
sorry for the delay, I currently am very busy with other important work-related business, I hope I can find some time to look into this during
christmas holiday season. |
|
Re: PAM authentication question, posted by Laurent Jean-Rigaud on Fri Jan 24 17:33:14 2020
|
Hi,
First, thanks to ELOG tool !
|
|
Re: PAM authentication question, posted by Jan Christoph Terasa on Fri Jan 24 18:13:03 2020
|
Hi Laurent,
does the ELOG server show the window immediately before even showing the login mask?
|
|
Re: PAM authentication question, posted by Laurent Jean-Rigaud on Fri Jan 24 18:22:52 2020
|
Hi,
Before le pam module link, yes.
After adding it, I wait some seconds before new login window popups with password error message. |
|
Re: PAM authentication question, posted by Laurent Jean-Rigaud on Fri Jan 31 15:39:17 2020
|
FYI i added ACL on /etc/shadow file to allow elog user for reading. Testing from elog login shell is OK.
Any suggestion ?
|
|
Running ELOG as daemon in Windows not working, posted by Duarte Alexandre Vicente Pais on Fri Jan 31 18:22:50 2020
|
Hi, I tried to set up an ELOG from a windows machine. Its functionalities work without any problem, but I cannot access at all this ELOG from any other
machine. I tried to search in this forum, but with no avail.
Could someone perhaps tell me know how to fix this problem? Or did I miss something obvious in the configuration of the ELOG? |
|
Re: Running ELOG as daemon in Windows not working, posted by Stefan Ritt on Fri Jan 31 18:50:09 2020
|
Probably a problem with your Windows Firewall. You have to convice your OS to let you in.
Stefan
Duarte |
|
Re: Running ELOG as daemon in Windows not working, posted by Duarte Alexandre Vicente Pais on Fri Jan 31 19:26:51 2020
|
Do you know which settings in the firewall panel I should change (windows 10 machine)? I went over all the access rules and could not find anything corresponding
to the ELOG.
Duarte |
|
Re: Running ELOG as daemon in Windows not working, posted by Stefan Ritt on Fri Jan 31 19:34:26 2020
|
I'm not a Windows user so I don't know details. But I believe you have to make an exception in the firwall for the elogd.exe executable. You
can certainly Google how to do that for any executable.
Stefan |
ELOG Null Pointer Dereference Denial-of-Service Vulnerability, posted by Stefan Ritt on Wed Feb 12 13:19:31 2020
|
An ELOG vulnerability has been reported, thanks to Asif Akbar of Trend Micro Security Researchworking with Trend Micro's Zero Day Initiative:
https://www.zerodayinitiative.com/advisories/ZDI-20-252/
The issue has been fixed in the current release 3.1.4-033e292 and in the RPM http://elog.psi.ch/elog/download/RPMS/elog-latest.x86_64.rpm |
Find cannot find values with brackets, posted by Sebastian Schenk on Fri Jun 14 11:29:30 2019
|
For demonstration, I created https://elog.psi.ch/elogs/Linux+Demo/8
The Find search for category aaa(bb) does not give results.
A quick filter corrects the value to aaa\(bb) and delivers results. |
|
Re: Find cannot find values with brackets, posted by Stefan Ritt on Fri Jun 14 12:43:04 2019
|
I‘m happy to merge the PR after a quick test next week.
Stefan
Sebastian |
|
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 ! |
|
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. |