Reverse proxy setting of Elog for Apache httpd 2.4 so that changing password windows works ?, posted by Takashi Ichihara on Tue Mar 19 06:13:03 2019
|
In CentOS 7.6 + Apache httpd-2.4.6 + ELOG V3.1.4 environment with Reverse Proxy setting of
/etc/httpd/conf/httpd.conf
: |
Re: Reverse proxy setting of Elog for Apache httpd 2.4 so that changing password windows works ?, posted by Takashi Ichihara on Tue Mar 26 06:41:21 2019
|
The problem was resolved. I forgot to do this statement...
https://elog.psi.ch/elog/adminguide.html
Because elogd uses links to itself (for example in the email notification and the redirection after a submit), it has to know under which URL it |
|
Interfaced with SSO, posted by Patricia Mendez Lorenzo on Fri Mar 22 09:53:39 2019
|
Dear Supporters,
I am evaluating the elog software as lobgook for high energy pgysics and I was just wondering the interface with SSO from the login point of |
Re: Interfaced with SSO, posted by Andreas Luedeke on Fri Mar 22 11:52:46 2019
|
ELOG understands kerberos authentication (See https://elog.psi.ch/elog/config.html#access).
If your SSO works with kerberos, then your SSO user name and password can be used to sign in to ELOG. But I'm not sure if that is what you
are asking for... |
|
HTML editor not working after updating to V3.1.4, posted by Ross Gibson on Tue Mar 19 23:24:48 2019
|
Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type
in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify? |
|
Re: HTML editor not working after updating to V3.1.4, posted by Stefan Ritt on Wed Mar 20 01:12:36 2019
|
Have you cleared your browser cache? There might be some old JavaScript stored there. If that does not help, remove elog and reinstall it to make sure to
have the correct libraries on the server (first back up you logbooks, then restore them afterwards).
|
|
Re: HTML editor not working after updating to V3.1.4, posted by Ross Gibson on Wed Mar 20 06:50:57 2019
|
Thanks Stefan. Tried these without success. I tried opening in another browser and it works fine in Firefox or Internet Explorer - the problem only appears
in Microsoft Edge. Perhaps its an issue with a Microsoft update (corporate rollout) to Edge and just a coincidence that I noticed it after updating Elog.
|
Very long URLs in message list corrupt layout, posted by Ederag on Sun Mar 10 01:07:53 2019
|
First, thank you so much for elog;
after using it for about 3 years, it has proven really handy and reliable.
When there is a very long URL in a message in "plain" encoding, |
|
Chain certificate, posted by Michal Falowski on Mon Mar 4 18:55:09 2019
|
I tried to run elog with SSL so I created key and crt files. In crt file I added client certificate and intermediate certifacte. Unfortunately, when
I try to run openssl s_client -showcerts -connect myexample.com:443 I got only the first certificate from the chain. Anyone has idea
why this happens? |
|
Mirror synchronization and file servers, posted by Frank Baptista on Fri Mar 1 19:18:53 2019
|
We have a number of temperature chambers – each has its own laptop running a local ELOG server, with unique logbook for each. Using the mirror
feature, these individual logbooks periodically synchronize to a single remote desktop server, which has a copy of each of the logbooks. All of that
works great, as long as each of the ELOG servers are storing the logbook(s) to their respective local hard drive. |
|
Re: Mirror synchronization and file servers, posted by Stefan Ritt on Mon Mar 4 13:35:13 2019
|
Sounds really strange to me. The remote server does not "know" that "S:\" is a network drive, so the syncing process should work
exactly as before. The only idea I have is that the access to the network files take pretty long, and you run into a timeout during syncing. We had this
in the past (for AFS netwhor shares, not Windows shares), where sometimes we have a blocking behaviour where the file access lasted 10-20 seconds, and |
New feature request for Options list, posted by Alan Grant on Wed Feb 20 22:24:05 2019
|
Is it possible to include an option in the next release to have the Options list reference a text file of attributes rather than explicity listing the
attributes in the Config file directly?
This would make it much easier to maintain a particular list that is referenced in several log books. |
|
Re: New feature request for Options list, posted by Stefan Ritt on Wed Feb 20 22:45:39 2019
|
I can put it on the wish list.
Alan
Grant wrote:
Is it possible to include an option in the next release to have the |
|
Re: New feature request for Options list, posted by Andreas Luedeke on Thu Feb 28 14:56:50 2019
|
Just my two cent - I would have many very good applications for that feature:
Keep option lists identical over different logbooks.
Keep option lists identical over different applications.
Create
option lists from a database - that allows to use the options in many applications and in the database; e.g. a list of systems with a failure database, |
|
Re: New feature request for Options list, posted by David Pilgram on Thu Feb 28 16:03:36 2019
|
May I slip my vote in for this, especially if it would allow more than 100 attributes (the default, and I do know how to increase it).
I even considered cutting that into two groups,. the first being words like "New", "Re-" and the second being actions.
Clunkey and binned. |
Migration from 3.1.2 version to 3.1.4, posted by Vladimir Travalja on Tue Feb 26 14:26:13 2019
|
Hi,
sorry for bugging you with this, but I could not find any information for making migration of elog system from one server to another. |
|
Re: Migration from 3.1.2 version to 3.1.4, posted by Stefan Ritt on Tue Feb 26 14:31:00 2019
|
To move an elog instance, just stop the old server, move the configuration file elogd.cfg and the logbook directory to the new server, and start the
new server. If the URL of the server changes, you have to adjust it in elogd.cfg.
Stefan |