Password File Config Issue, posted by Mark Delaney on Fri Feb 4 23:35:27 2022
|
I expanded an elog server from 1 to 3 logbooks. For each logbook there is a separate password file defined.
When I try to add a new user in one of the 2 new logbooks using config => new user, it adds the user to the password file for the original
logbook. |
Re: Password File Config Issue, posted by Stefan Ritt on Thu Feb 10 14:02:15 2022
|
Can you try the "top groups" option, which means putting each logbook into a separate top group as described in the documentation. For us this
works well, new users are only added to the right password file. There is however the problem that as admin you might be logged in to several logbooks
(as remembered in your browser via cookies), so you might want to log out from all logbooks first (or clear all cookies of elog), then log in to one logbook |
Default "Author" when replying to a log entry, posted by Jan Just Keijser on Tue Feb 1 15:39:38 2022
|
what is the default value for "Author" when replying to a log entry ? I now see that for each reply to a log entry, the value of "Author"
is set to the value of the author of the original entry - this makes it very hard to see which user has replied to a particular log entry, especially when
users start replying to replies etc. |
|
Re: Default "Author" when replying to a log entry, posted by Stefan Ritt on Tue Feb 1 15:43:00 2022
|
As you can see, on this forum the author for replies is correct. This is done via the config option:
Preset on reply Author = $long_name
Jan |
|
Re: Default "Author" when replying to a log entry, posted by Jan Just Keijser on Tue Feb 1 16:43:34 2022
|
Excellent, exactly what I was looking for, many thanks!
Stefan |
|
elog@Ubuntu 18.04, posted by Carsten Winkler on Sat Jan 29 09:05:47 2022
|
Hello,
I try to start elog at Ubuntu 18.04. When I run sudo /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg I
get following error: |
|
Re: elog@Ubuntu 18.04, posted by Stefan Ritt on Mon Jan 31 09:10:41 2022
|
Looks like you don't have shared libraries correctly configured on your system. Try "ldconfig" on your system or link elogd statically
(google how to do that).
Stefan |
|
Re: elog@Ubuntu 18.04, posted by Carsten Winkler on Tue Feb 1 09:13:40 2022
|
sudo ldconfig didn't solve the problem
Is there any other solution than elog static linking? |
|
Re: elog@Ubuntu 18.04, posted by Carsten Winkler on Tue Feb 1 16:16:34 2022
|
downloading the sources and building them on the target system solved the problem
Carsten
Winkler wrote:
sudo ldconfig |
|
Text formatting panel inside entries, posted by Mariia Fedkevych on Fri Jan 28 17:49:35 2022
|
Hello!
How can I make appear the text formatting panel (above the main text body field) inside entries? |
|
Adjustment of summary columns, posted by Mariia Fedkevych on Fri Dec 17 11:54:38 2021
|
Hi!
Is it possible to manage the column widths on a logbook's summary page one by one? |
|
Re: Adjustment of summary columns, posted by Stefan Ritt on Fri Dec 17 12:11:22 2021
|
You can manually modify the CSS style to adjust column widths. Locate elog.css which resides under elog/themes/default/elog.css, then find the class
“.listtitle”, and modify the line
width: 0%; |
|
Re: Adjustment of summary columns, posted by Mariia Fedkevych on Fri Jan 28 17:37:55 2022
|
Thank you!
Stefan
Ritt wrote:
You can manually modify the CSS style to adjust column widths. Locate |
Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 08:13:10 2011 
|
Hi,
We have a problem with the search command: Since our last upgrade to v2.9.0-2418 the searched string is pre- and postfixed with ASCII character
expressed in % format, see the attached image. The searched string is prefied with %255E and postfxed by %2524 in the URL. And teh search fails. This affects |
|
Re: Spurious characters in the searched string, posted by Stefan Ritt on Mon Sep 26 10:38:59 2011
|
Olivier Callot wrote:
Hi, |
|
Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 11:16:19 2011
|
Stefan Ritt wrote:
|
|
Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 14:49:48 2011
|
Olivier Callot wrote:
|
|
Re: Spurious characters in the searched string, posted by Phil Rubin on Mon Jan 3 19:11:08 2022
|
Hi,
Ten years later...this problem shows up in my installation behind Apache, affecting only drop-down menu searches. Test installations with
elog serving itself do not show the problem, so I presume it has something to do with Apache configuration, re-routing, etc. Unfortunately, this |
|
Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Wed Dec 1 12:37:57 2021
|
Hello,
I am trying first time to use the tool /usr/bin/elog. From the documentation is not clear to if everything must be in quotes or not, if every |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 1 13:05:14 2021
|
Please issue the elog command with an added "-v" flag and post the output here.
Stefan
Jose |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 08:28:19 2021
|
Hi Stefan,
Here is the, I believe, relevant part of the output:
------------------------------------------------- |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Tue Dec 7 11:56:37 2021
|
If you need HTTPS then you must specify the "-s" option.
You could have looked into the help of the elog command:
> elog -h |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 14:25:37 2021
|
This is what I get with -s:
---------------------------------
Successfully connected to host elog-1.matrix.com, port 80 |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Tue Dec 7 14:46:16 2021
|
If you use HTTPS, you have to connect to port 443 of your server, using the "-p" option.
Furthermore, you run under an Apache server, right? How do you do the redirecting to elogd? I guess you specified a subdir in the URL named /LogBook
to redirect to elogd. The you use another part of the URL to select the logbook, which again might be "LogBook". Is that correct? So your full |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 15:09:36 2021
|
Not really. The full URL in the browser is https://elog-1.matrix.com/LogBook. That's why I am trying with "-h elog-1.matrix.com -l LogBook"
I have just tried with -p, here is the full output:
[root@elog-1 ~]# /usr/bin/elog -h elog-1.matrix.com -p 443 -v -x -l LogBook |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Tue Dec 7 17:50:37 2021
|
The reply from the server
Response received:
HTTP/1.1 404 Not Found |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Wed Dec 8 10:49:20 2021
|
I don't see anything in httpd logs.
I am just reusing an entry I created via web, so the attributes are correct. Nothing is missing, correct spelling, etc. I keep trying.
BTW, I have just realized that the output of "elog -h" does not "man log", which is the one I have been using so far. |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Tue Dec 7 18:24:42 2021
|
But this is real progress! Now elog successfully connected, and all your data was transmitted, but elogd refused your content.
A possible explanation is that one required attribute of this logbook was not provided in your elog command, or that one value of an
attribute does not match any allowed value for that attribute. |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 8 10:59:58 2021
|
Ok, you Apache listes on two ports. On port 80 with HTTP and on port 443 with HTTPS. If you connect to port 80, there is no fowarding to elogd, that's
why Apach complains
The requested URL /LogBook/ was not found on this server. |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Wed Dec 8 11:23:48 2021
|
Thanks for the comments. I will pass them to the admins.
Stefan |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Wed Dec 8 12:05:43 2021
|
With curl, I get this as part of the output:
<table class="dlgframe" width="50%" cellpadding="1"
cellspacing="0"<tr><td class="errormsg">Error: Command "<b>Submit</b>" not allowed</td></tr>
Hopefully |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 8 13:19:55 2021
|
That reply indicates that the login was not successful. So something went wrong with the authentication. You can try to switch off passwords to see if
that makes a difference.
Jose |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Thu Dec 9 10:33:09 2021
|
Have you tried to connect directly to elogd and not going through Apache?
Jose
Caballero wrote:
Thanks for the comments. I will pass them to the admins. |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Thu Dec 9 21:58:08 2021
|
Nope. How? Is it documented?
Stefan
Ritt wrote:
Have you tried to connect directly to elogd and not going through Apache? |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Fri Dec 10 21:41:05 2021
|
It is the default. If you install ELOG on your PC and run it, then every access will be directly to the ELOG web service. If you want to have Apache
inbetween, it is some extra effort.
Jose |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 14 21:42:45 2021
|
Hi Andreas,
I realize from your response that my question was not clear. I was not asking how to get it. Note that I am just a regular user, I am not the
administrator of the service. |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Thu Dec 16 18:24:41 2021
|
Now you've totally lost me.
elogd is a web service. You connect to it with a web browser. You don't pass arguments at startup of the service that refers to specific
atrributes. I have no idea what you intend to do, you need to explain a lot more. |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Thu Dec 16 21:34:05 2021
|
Hi Andreas.
It seems I didn't fully understand the comment by Stefan when he said "Have you tried to connect directly to elogd and not going through
Apache?". My bad. |
|
Logfile not registering entry numbers?, posted by Sergio Navarrete on Fri Oct 19 08:38:06 2018
|
I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes
Date Time [User@IP] {Logbook} NEW entry #0
How can I make the #0 be the real entry number for the reply? |
|
Re: Logfile not registering entry numbers?, posted by Andreas Luedeke on Fri Oct 19 13:08:30 2018
|
It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For
new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving |
|
Re: Logfile not registering entry numbers?, posted by David Pilgram on Mon Oct 29 14:26:28 2018
|
As a regular elog (ab)user, I have seen this behaviour from time to time. So far as I recall, the cause actually is that a normal entry is looking
for the entry in the "Reply to" field of the normal entry in the yymmdda.log file. When that entry does not exist, then I see a duplicate
line of an entry with entry "#0", in emboldened black type. I did have a screenshot, but cannot find it for now. |
|
Re: Logfile not registering entry numbers?, posted by Stefan Ritt on Wed Apr 1 15:57:27 2020
|
I finally found some time to fix that bug. Was just that the log file hat #0, the bug should not have had any ohter side effects. Now the logfile is
fine.
David |
|
Re: Logfile not registering entry numbers?, posted by Sergio Navarrete on Thu Dec 16 08:23:22 2021
|
It seems that the latest Windows binary still predates this fix. Will there be a new installer soon? Thanks for your support.
Stefan
Ritt wrote:
I finally found some time to fix that bug. Was just that the log file |