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 thread did not provide any details of the solution.
The problem looks like this:
Type: %255ERoutine%2524
or, in the url:
https://servername/?Type=%25255ERoutine%252524
Removing 2525 from front and back of the url makes everything work.
The only rewrite entries in the configuration file(s) are:
## Rewrite rules
RewriteEngine On
#redirect non-SSL traffic to SSL site
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
Perhaps there's a rewrite rule that could be added to block the 2525? Something like:
RewriteCond %{QUERY_STRING} 2525
RewriteRule .* - [F,L]
I don't have a lot of experience configuring Apache, so any suggestions would be welcome.
Thanks.
Phil
| Olivier Callot wrote: |
|
| Olivier Callot wrote: |
|
| Stefan Ritt wrote: |
|
| Olivier Callot wrote: |
|
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 searches from drop-down menus.
Thanks in advance.
|
Strange. In this forum it works without extra characters. Just try it yourself. Do you have any strange configuration? Can you send me a minimal elogd.cfg which produces that error, maybe derived from the example elogd.cfg from the distribution.
- Stefan
|
Well, It may be our implementation of re-routing web requests: The requested string in elog is prefixed by %5E (^) and postfixed by %24 ($). But in my case, the '%' is again escaped as %25 so the prefix becomes %255E that is not understood by elog as being '^' ...
I will see with my experts in routing if this is something that can be fixed in our configuration. But when elog processes the input string, it should un-escape these characters and find back the '^', no?
|
It turned out to be a setting of our re-routing of requests that re-escaped the '%'. Sorry for the noise. Cheers
|
|
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 elog.css which resides under elog/themes/default/elog.css, then find the class “.listtitle”, and modify the line
width: 0%;
to something like
width: 10%;
you can play with the width until it suits your needs. After each change, you have to reload the page in the browser to see the effect.
If you only want to change the width of a specific column, add following lines to your elog.css:
.listtitle:nth-child(4) {
width:30%;
}
where ‘4” is for example the 4th column. You can have several of these statements for different columns.
To hide the text, use the option 'summary lines' as described in the manual.
| Mariia Fedkevych wrote: |
|
Hi!
Is it possible to manage the column widths on a logbook's summary page one by one?
Also, is it possible to hide the Text column without actually hiding the text body in entries (as Show Text = 0 in elog.cfg does)?
Kind regards,
Mariia
|
|
|
|
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?
In my logbook I do not have it (also in minimized form) and I do not find a way to enable it via elogd.cfg.
Thank you!
- Mariia |
|
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:
/usr/lib/libssl.so.10: version `libssl.so.10' not found (required by /usr/local/sbin/elogd)
I checked following:
ls -l /usr/lib/libssl.so.10
lrwxrwxrwx 1 root root 41 Jan 29 08:24 /usr/lib/libssl.so.10 -> /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
ls -l /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
-rw-r--r-- 1 root root 424664 Aug 24 18:16 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
What's going wrong? And how to solve the problem?
Best,
Carsten |
|
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
| Carsten Winkler wrote: |
|
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:
/usr/lib/libssl.so.10: version `libssl.so.10' not found (required by /usr/local/sbin/elogd)
I checked following:
ls -l /usr/lib/libssl.so.10
lrwxrwxrwx 1 root root 41 Jan 29 08:24 /usr/lib/libssl.so.10 -> /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
ls -l /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
-rw-r--r-- 1 root root 424664 Aug 24 18:16 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
What's going wrong? And how to solve the problem?
Best,
Carsten
|
|
|
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?
| Stefan Ritt wrote: |
|
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
| Carsten Winkler wrote: |
|
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:
/usr/lib/libssl.so.10: version `libssl.so.10' not found (required by /usr/local/sbin/elogd)
I checked following:
ls -l /usr/lib/libssl.so.10
lrwxrwxrwx 1 root root 41 Jan 29 08:24 /usr/lib/libssl.so.10 -> /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
ls -l /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
-rw-r--r-- 1 root root 424664 Aug 24 18:16 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
What's going wrong? And how to solve the problem?
Best,
Carsten
|
|
|
|
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 didn't solve the problem
Is there any other solution than elog static linking?
| Stefan Ritt wrote: |
|
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
| Carsten Winkler wrote: |
|
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:
/usr/lib/libssl.so.10: version `libssl.so.10' not found (required by /usr/local/sbin/elogd)
I checked following:
ls -l /usr/lib/libssl.so.10
lrwxrwxrwx 1 root root 41 Jan 29 08:24 /usr/lib/libssl.so.10 -> /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
ls -l /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
-rw-r--r-- 1 root root 424664 Aug 24 18:16 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
What's going wrong? And how to solve the problem?
Best,
Carsten
|
|
|
|
|
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.
Have verified that access to the logbooks is controlled via the separate password files. If it would help to provide an example of the elogd.cfg or if I need to clarify further, let me know.
Any suggestions welcome.
Thanks. Mark. |