Loose of Data, posted by Lahreche Abdelmadjid on Sun Sep 27 16:03:48 2020
|
Hi,
Since few days I Notice that I've some data who disappear from ELOG (software).
I find them on ELog/Logbooks, but can't view them in the application ELOG ! |
Re: Loose of Data, posted by Lahreche Abdelmadjid on Sun Sep 27 16:10:06 2020
|
Oh! I can view all data but only from the PC where ELOG is Installed !
From the other PC data missed.
Lahreche |
|
Re: Loose of Data, posted by Lahreche Abdelmadjid on Sun Sep 27 16:40:16 2020
|
The solution is in the reindex
Lahreche
Abdelmadjid wrote:
Oh! I can view all data but only from the PC where ELOG is Installed |
Bug report. "Submit" button misbehave, posted by Andrey on Tue Sep 22 18:54:04 2020
|
Hi.
I am an IT guy of the AMS collaboration at CERN. We have been using your wonderful elog software for about 10 years now. Thanks! It served us
so well that I guess we never got in touch with you. |
|
SOLVED, posted by Andrey on Wed Sep 23 11:51:57 2020
|
Hi again. We have solved our problem!
It was caused by a non-defined mod_auth_openidc configuration parameter:
# Interval in seconds after which the session will be invalidated when no interaction has occurred. |
|
Query to get values for Attributes, posted by Florian Feldbauer on Mon Sep 21 09:17:52 2020
|
Hey,
I'm trying to integrate the Elog into our SlowControl System (Phoebus/EPICS). As a first step I translated the python library to Java. So
writing new Entries and viewing them works. |
Re: Query to get values for Attributes, posted by Andreas Luedeke on Mon Sep 21 20:03:49 2020
|
That would be a nice feature...
If you are good in parsing HTML you can achieve this feature: when you create a new entry "<elog-URL>?cmd=new", you'll get
HTML source code that provides you with all possible attribute choices. |
|
Re: Query to get values for Attributes, posted by Florian Feldbauer on Tue Sep 22 09:27:45 2020
|
Thanks for the tipp. I managed to use XPATH to get the values for my Type and Category attributes!
The API, I'm developing for Phoebus is quiet simple. It currently just supports Author, Subject, Type and Category as attributes and the
latter two are just lists of values. |
|
view connecting account, posted by Lahreche Abdelmadjid on Sun Sep 13 09:13:31 2020
|
Hi All,
Can I view who is connected to ELOG (I'm the Admin) ?
thank you. |
|
Re: view connecting account, posted by Andreas Luedeke on Mon Sep 14 17:25:08 2020
|
Yes, you can see that in the logging file, if you turn on logging. You might want to read the manual https://elog.psi.ch/elog/config.html. Here's
the relevant excerpt:
|
|
Re: view connecting account, posted by Lahreche Abdelmadjid on Tue Sep 15 12:31:09 2020
|
Thank you, I found it.
Andreas
Luedeke wrote:
Yes, you can see that in the logging file, if you turn on logging. |
|
testing the client: unclear it worked, posted by Jose Caballero on Thu Jul 30 17:03:12 2020
|
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
|
|
Re: testing the client: unclear it worked, posted by Stefan Ritt on Fri Jul 31 08:34:35 2020
|
The <hostname> you have to actually replace with your real host name. Same for logbook, username and password.
On my local test system I get (actual password hidden here with "...")
~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test |
|
Re: testing the client: unclear it worked, posted by Jose Caballero on Mon Sep 14 15:40:02 2020
|
Sorry for the late reply. I didn't get email notification about an answer to my question :)
Actually, I just wrote <hostname> and so on for privacy. In my attempt, they have real values.
And yet, I got as result: "Message successfully |
|
Insert images slow downs the ELOG, posted by Zbigniew Reszela on Wed Sep 9 11:41:23 2020
|
Dear all,
First, many thanks for creating and sharing this great tool which is ELOG! Our users are very happy with it!
I have few questions about inserting images into the entries. |
|
Re: Insert images slow downs the ELOG, posted by Andreas Luedeke on Sat Sep 12 19:19:02 2020
|
I found the most limiting factor of ELOG to be the file access. ELOG stores all entries in files and therefore has a lot of disk access.
We found that an AFS directory for ELOG is unusable. We tried to store our logbooks on NFS, and it was barely usable but slow. Now we use a local
disk on the server, that works fine. |
|
field selections persist across new log entries?, posted by Anthony Krishock on Tue Sep 8 14:22:11 2020
|
All,
I am using elog as an observation log for amateur astronomy. I have a form configured, but I would like to know if it is possible to |
|
Re: field selections persist across new log entries?, posted by Sebastian Schenk on Tue Sep 8 16:35:14 2020
|
As far as I know, it is not possible, if you make a "new" entry.
You could configure the elog, to always PRESET an atribute, but then it is always the same, not the last.
I think the "duplicate" entry function could provide you partly with the functionality you want, as it copies all old values into a |
|
Re: field selections persist across new log entries?, posted by Andreas Luedeke on Wed Sep 9 10:33:58 2020
|
It is probably possible, but requires a big of a hack.
Whenever you save a new entry or edit an old one, you run a little shell script
to write the value of this field into a file.
Whenever you create a new entry you read the PRESET value with a shell script from that file.
Here
are the relevant excepts from the documentation: |
|
Using curl to post new entries, posted by Florian Feldbauer on Wed Sep 2 10:24:58 2020
|
Hey,
i'm trying to use curl to post new entries to our logbook as described here: https://elog.psi.ch/elogs/Forum/68597.
The Elog is installed via the Deban package on Buster. |
|
Re: Using curl to post new entries, posted by Florian Feldbauer on Wed Sep 2 11:56:04 2020
|
After going through the code of the Python API (https://github.com/paulscherrerinstitute/py_elog/blob/master/elog/logbook.py) I tried the following:
$ python3
>>> from passlib.hash import sha256_crypt |
|
Re: Using curl to post new entries, posted by Stefan Ritt on Wed Sep 2 15:42:40 2020
|
This is correct. The elogd daemon needs username and password in parameters "unm" and "upwd". The password must be SHA256 encoded,
so best is to grab it from the password file. This way one does not have to send clear text passwords over the network.
Florian |