Hi,

Is there a way to export the ELOG entries into a file like an Excel sheet or something.  I see import but not export.

Appreciate your help.

Thanks.

Illam

Find -> Export to...

Thanks Stefan for your help.  It works but the only issue is, the screenshots that were included in the body of the entries are not usable.  Not sure if there is any workarounds for that.

...Illam

Hi,

I've just installed the news 3.1.5 version and I have 2 problems.
I don't know if it works with older versions because I started with latest.

- When using "select" menu then "edit" for multiple entries, the text is replaced with "- keep original text here -" instead of keeping the original values. Really annoying...

Another problem too, if I want to edit after, I have the error message "only author - keep original text here - can edit" although the author column is OK..
It looks like this problem is global and not only on text column.

- Version number is indicated "ELOG V3.1.4" instead of V3.1.5.

My config file :

I'm using Apache as reverse proxy with SSL and transparent Kerberos authentication (Microsoft Active Directory).
URL via Apache is https://elog.xxxxxx.xxx (no subdirectory).

Thanks for your help.

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

Thanks for your prompt help.
It looks good for text but I still have problem with "select" function (even in English).

If I use "select" menu :
- When multiple values are selected it indicates "only user - keep original values - can edit" (freshly created).




- When a single value is selected, it indicates "only user XXX can edit" where XXX is my truncated name (the first 4 letters).



After editing in with admin account the author is now my truncated name :



If I want to edit a single entry (without select menu) it works perfectly.

Thanks.
 

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.

Thanks !

Sometime I need to edit multiple values to add a new choice.
By exemple, if I add a new column "status" (open, closed...) , it's mandatory to use select menu to add the new value to existent entries.

With a lot of lines it's not possible to edit one by one.

Hello,

I  tried to install Elog 3.1.4 from rpm on Oracle Linux 9 with command:

sudo dnf localinstall elog-3.1.4-3.el7.x86_64.rpm

But I got error:

Last metadata expiration check: 0:08:06 ago on Thu 02 Feb 2023 10:35:13 CET.
Error:
 Problem: conflicting requests
  - nothing provides libssl.so.10()(64bit) needed by elog-3.1.4-3.el7.x86_64
  - nothing provides libssl.so.10(libssl.so.10)(64bit) needed by elog-3.1.4-3.el7.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Using dnf I installed libssl.so.11 (cannot find version 10) and it doesn't help. So my question is: can I use one of proposes by dnf solution as:

1. --skip-broken
2. --nobest

Does Elog will work stabilityy after that?

Best Regards

Hi Daniel,

The RPM has been build for EL7 so SSL share libs should be different with the one provided by EL9. :-)

Try to rebuild from tarball source with enclosed buildrpm script (or with elog srpms if you find any : rpm -i elog*.src.rpm && vim ~/rpmbuild/SPEC/elog.spec # update build options as SSL/LDAP/PAM... && rpmbuild -bb ~/rpmbuild/SPEC/elog.spec ).

Gûd luck

I wanted to change some CKeditor settings so tried modifying elog/scripts/ckeditor to no avail.

I wiped elog/scripts/ and dropped a fresh download of CKeditor4, with only the basic extensions. But when I open the elog it still shows the full toolbar, with elog default style and with all extensions operational.

If I leave elog/scripts empty, I get "CKeditor NOT detected" when starting elogd and the HTML option is empty and shows nothing, all as expected.

Does anyone understand this? Is there some CKeditor configuration file elog is defering to that I've overlooked? I have tried system wide seaches just in case.

elogd checks for the "scripts/ckeditor/ckeditor.js" file to detect the presence of CKeditor.

So it was just a clearing cache issue. elogd was telling the browser to use/not use CKeditor based on the aformentioned, and browser was then using the cached version. Fixed now.

And FYI for anyone who reads this when trying to modify CKeditor themselves, it seems elog needs the iFrame Editing Area plugin included.

It means that you could replace the currently distributed CKeditor with a fresh vanilla installation of CKeditor? 

Yes replacing the CKeditor folder with a vanila download works without issue, provided you clean the cache.
For what I originally wanted to do (modifiying the toolbar) I could have just run elog/scripts/ckeditor/samples/toolbarconfigurator/index.html and edited the config file, but a clean cache is needed (on Chrome, Firefox and Edge).

I downloaded the last elog-3.1.5-1.tar.gz to install elog.

All *.cxx files are missing.

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.

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

It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?

I have requested an undeletion of the article. The article was deleted  "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.

I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.

If there iy an paper on the elog, maybe it could be cited for more creditability.

It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG

I added some more references, that's about all I can do. Not sure if that is enough.

Stefan

If I understand it correctly I think it has to be submitted for review with the blue button on that page, just not sure if that should come from your side or someone else

It appears to me that this is a really stupid problem: the article provides many links to sources, but they are just links, not "references". That does not count, since links could be something else than references.

I'll try to edit it and transform the list of external links into references to verify the text. Lets hope that this will suffice.

Okay: found three articles about applications of ELOG and put them under references. I took the liberty to submit the draft: it shows that they expect some month delay for a review. I have no idea if that was what they want, but it is worth a try.

I am rather with John on this.

I deliberately stopped contributing to Wikipedia years ago after I added an observation to an entry.  That is, a piece of what could be called original research.  It was shot down in flames for being precisely that: original research.    From what I read in the Draft:Elog and the Talk section,  I think that the same issue in some guise or other will come up.  All of us use and love Elog - I think I use it for all of the listed purposes - but apart from being in the Debian distro (which I did not know about) there is very little published primary sources.  Mind you, the quality of publications as primary sources can be questioned, I can bore on with several examples.  

Has anyone ever published a paper citing their filing cabinet organisation?  Elog's obviously different, but has the same problem when it comes to citations.  It is a utility, a very useful one, but the sort of utility that might just make an aside in a paper these days.  If we were in the 1980s and (hypothetically) Elog was available and as functional, that would probably make it the subject in computer research papers and magazines. 

David.

After fiddling around I managed to get ELOG working behind the load balancer HAProxy by stacking ELOG together with an Apache reverse proxy in a Docker stack. I am currently pretty convinced that something with the HTTP communication is somehow faulty in ELOG and Apache is more forgiving than HAProxy, since the configuration is the same as without Apache. So putting ELOG behind an Apache and then Apache behind the HAProxy is working.

For the sake of completeness, here is the HAProxy configuration:

backend be_elog.km3net.de
    mode http
    server-template km3net-elog- 1 km3net-elog_apache:80 check resolvers docker init-addr libc,none

and here is the Apache httpd.conf:

Listen 80

LoadModule mpm_event_module modules/mod_mpm_event.so
LoadModule authn_core_module modules/mod_authn_core.so
LoadModule authz_core_module modules/mod_authz_core.so
LoadModule access_compat_module modules/mod_access_compat.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
LoadModule filter_module modules/mod_filter.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule env_module modules/mod_env.so
LoadModule headers_module modules/mod_headers.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule unixd_module modules/mod_unixd.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
<IfModule !mpm_prefork_module>
        #LoadModule cgid_module modules/mod_cgid.so
</IfModule>
<IfModule mpm_prefork_module>
        #LoadModule cgi_module modules/mod_cgi.so
</IfModule>
LoadModule dir_module modules/mod_dir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so

ServerAdmin email
ServerName elog.test.km3net.de

ErrorLog /proc/self/fd/2

LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog /proc/self/fd/1 common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "logs/access_log" combined
</IfModule>

<IfModule headers_module>
    #
    # Avoid passing HTTP_PROXY environment to CGI's on this or any proxied
    # backend servers which have lingering "httpoxy" defects.
    # 'Proxy' request header is undefined by the IETF, not listed by IANA
    #
    RequestHeader unset Proxy early
</IfModule>

<VirtualHost *:80>
    ServerName elog.test.km3net.de
    #ProxyPreserveHost On
    ProxyPass / http://elog:8080/
    ProxyPassReverse / http://elog:8080/

    RewriteEngine On
    RewriteCond %{HTTP:Upgrade} =websocket [NC]
    RewriteRule /(.*)           ws://elog:8080/$1 [P,L]
    RewriteCond %{HTTP:Upgrade} !=websocket [NC]
    RewriteRule /(.*)           http://elog:8080/$1 [P,L]

    ErrorLog /apache/error.log
    CustomLog /apache/access.log combined
    TransferLog /apache/transfer.log
</VirtualHost>

Long story short: I am still not able to upload anything from the command line. So something like

elog -v -h elog.test.km3net.de -p 443 -l "Individual Logbooks" -v -m elog_test.txt  -n 0 -a author="Whoever" -a Subject="Upload Test" -u USER PWD -s

gives this:

root@b9db27a421e1:/# elog -v -h elog.test.km3net.de -p 443 -l "Individual Logbooks" -v -m elog_test.txt  -n 0 -a author="Whoever" -a Subject="Upload Test" -u USER PWD -s
Successfully connected to host elog.test.km3net.de, port 443
Possibly invalid certificate, continue on your own risk!
Request sent to host:
POST /Individual+Logbooks/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------66D92EF0673838014927FA6E
Host: elog.test.km3net.de:443
User-Agent: ELOG
Content-Length: 977

Content sent to host:
---------------------------66D92EF0673838014927FA6E
Content-Disposition: form-data; name="cmd"

Submit
---------------------------66D92EF0673838014927FA6E
Content-Disposition: form-data; name="unm"

USER
---------------------------66D92EF0673838014927FA6E
Content-Disposition: form-data; name="upwd"

PWD_HASH
---------------------------66D92EF0673838014927FA6E
Content-Disposition: form-data; name="exp"

Individual Logbooks
---------------------------66D92EF0673838014927FA6E
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------66D92EF0673838014927FA6E
Content-Disposition: form-data; name="author"

Whoever
---------------------------66D92EF0673838014927FA6E
Content-Disposition: form-data; name="Subject"

Upload Test
---------------------------66D92EF0673838014927FA6E
Content-Disposition: form-data; name="Text"

foo

---------------------------66D92EF0673838014927FA6E

Response received:
HTTP/1.1 503 Service Unavailable
content-length: 107
cache-control: no-cache
content-type: text/html
connection: close

<html><body><h1>503 Service Unavailable</h1>
No server is available to handle this request.
</body></html>

Error transmitting message

Is this command line interface even able to communicate through a(n Apache) reverse proxy or does it need to communicate with elogd directly?

We were running ELOG for many many years in our experiments and the instance was operated on a Debian XEN server as a container. I am now trying to migrate it into our Docker Swarm cluster and I am using the https://hub.docker.com/r/de1lz/elog-docker Docker image, which works very well with our logbooks when I run it as a single container. However, when I put the container behind my load balancer (HAProxy) using the simple HTTP mode (which works very well for all the other HTTP-based services) with this simple configuration:

backend be_elog.km3net.de
    mode http
    server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none

I get a "too many redirects" error when I try to access one of the logbooks. The starting page works fine, but every other link leads to a pile-up of redirects.

Here is the current instance running, where you can see the behaviour: https://elog.test.km3net.de (all log entries deleted and only two logbooks activated)

My question is: what kind of redirect could go wrong here? I don't know how the internal HTTP server of ELOG works, but maybe someone faced similar issues.

My ELOG configuration is also pretty basic, and as I wrote above, everything works when I run it without the load balancer (single instance at the moment). Here is the top part of the configuration, it contains a few dozens of logbooks but they are configured the very same way. 

;User Settings
;=============
Password file = login.xml
Admin user = km3net_admin
Self register = 0
Allow password change = 0
Allow config = km3net_admin

;Group Settings:
;====
Group ELOGKM3NET = Operations IT, Operations FR

[Operations IT]
Subdir = Operations_IT
Theme = default
Default encoding = 0
Comment = KM3NeT IT Detector Operations
Attributes = Author, Type, Subject
Options Author = A, B, C
Options Type = PPM-DOM, PPM-DU, Comment, Power cut, New run
Extendable Options = Type
Required Attributes = Author, Type, Subject
Page Title = ELOG - $subject
;Sort Attributes = Author, Type
Quick filter = Date, Type, Author
Resubmit default = 2
Reverse sort = 1
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Help, Logout
Preset on first reply Subject = Re: $Subject
Preset on reply author =

Probably you need a setting

URL = https://elog.test.km3net.de

or so in your elogd.cfg file.

Stefan

Thanks for the quick reply! Sorry, I forgot to paste the "global" part of the config, I have that URL already set:

[global]
;Main Settings
;=============
Usr = elog
Grp = elog
port = 8080
SSL = 0
URL = https://elog.test.km3net.de
Title image = <img border=0 src="KM3NeT_logo.png" alt="KM3NeT logo" height="35px">
;SMTP host = smtp.fau.de
Display mode = summary
Thumbnail size = 500>
List Menu text = clock.html
Menu text = clock.html

I also tried the default configuration (example config) and it that works behind the load balancer. So I guess it's related to the password-page, which causes this redirect loop? Our logbooks are all password protected, so when a logbook URL is clicked, it should first present the login-form, and that's where it chokes.

Yeah, after you enter a password, elog redirects to what it finds in "URL". You can trace that by opening "development tools" in Google Chrome, go to "network" and watch packets going back and forth. I never worked with the load balancer, but maybe you need a different "URL" containing a '/' at the end?

My problem is that I don't even reach the page where I can enter a password. If you go to https://elog.test.km3net.de and click on a logbook, you'll see that it immediately goes into a redirect loop. I already logged the routing but there is nothing else...

Attached is the log, where you can see that `Operations+IT` redirects to `Operations+IT/` and that redirects to `Operations+IT` again, which then goes to `elog.test.km3net.de` and `Operations+IT` again etc. etc.

EDIT: I  use the very same load balancer confugration for dozens of other services incl. Apache, Nginx, GitLab, Mattermost, RocketChat etc. and all work fine. As written before, also the "example" logbook works (without password protection).

I also tried `/` at the end of the URL but it has no effect.

I am pretty clueless currently...

Yes I see the redirects. You say with the example logbook it works, right? Is it the password protection which triggers the problem or anything else? Does it work if you take out the password protection? The key is to identify which setting in your config file triggers the problem, so you can bracket the problem down between the example logbook and your logbook definition.

Yes, I used the empty `passwd` file from example. When I then click on one of the logbooks, I get to the page where I can register a user (see attached screenshot). After clickin on "Save" for the user registration, I again get the redirect error. Once there is a registered user (i.e. a non-empty password file) the redirect issue is persistent. Any idea where the problem might be? I just emptied the password file again, so you can have a one-shot, if you like.

Btw. I have SSL termination in the load balancer, so ELOG does not need to do any SSL related things (the swarm is in a locally isolated network, so all internal communication between the load balancer and the swarm machines are safe). Maybe that's the issue? On the other hand, the main page loads fine and uses SSL termination too, so I don't know, maybe there is logic behind the authentication which collides with the SSL termination.

The issue is still present and now it's quite urgent to move this last service into the Swarm. Does anyone maybe have an idea what's wrong? To sum up: if there is a non-empty password file, the login page chokes in an infinite loop of redirects. I am using the same HAProxy load balancer configuration as for all the other services (running Apache, NGINX, GitLab, XWiki, etc.):

backend be_elog.km3net.de
    mode http

    option forwardfor except 127.0.0.1
    http-request add-header X-Forwarded-Proto https if { ssl_fc }

    server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none