| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68900
|
Wed Feb 27 02:34:46 2019 |
 | Xuan Wu | wux@ihep.ac.cn | Question | Linux | 3.1.3 | elog hanged when uploading photo failed |
Hi all,
We came across a problem recently when clicking "Upload" button, then elog hanged and never being accessed. I have checked the elog logs and find that it seems that elog didn't get the path of the picture for some reason. So is it a bug or our operation isn't correct? |
| Attachment 1: log.png
|
|
|
68899
|
Tue Feb 26 14:31:00 2019 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.2 | Re: Migration from 3.1.2 version to 3.1.4 |
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
| Vladimir Travalja wrote: |
|
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.
The migration should be done from one server version (CentOS 6.10 to CentOS 7.6). Also we are talking about migration from one subdomain to another. Example subdomain1.example.com to subdomain2.example.com. Old elog application version is 3.1.2 and I would like to migrate to the latest version 3.1.4
Is the migration from one system to another possible? What are the prerequisites for migration?
Are there any instructions how to do it?
Thank you in advance and have yourself a lovely day,
Warmest regards
|
|
|
68898
|
Tue Feb 26 14:26:13 2019 |
 | Vladimir Travalja | vlt@hll.mpg.de | Question | Linux | 3.1.2 | Migration from 3.1.2 version to 3.1.4 |
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.
The migration should be done from one server version (CentOS 6.10 to CentOS 7.6). Also we are talking about migration from one subdomain to another. Example subdomain1.example.com to subdomain2.example.com. Old elog application version is 3.1.2 and I would like to migrate to the latest version 3.1.4
Is the migration from one system to another possible? What are the prerequisites for migration?
Are there any instructions how to do it?
Thank you in advance and have yourself a lovely day,
Warmest regards
|
|
68897
|
Mon Feb 25 17:03:50 2019 |
 | Kester Habermann | kester.habermann@gmail.com | Bug report | Linux | 3.1.4-1 | elogd hangs on self referencing log entry |
Hello,
Somehow when replying to a log entry, a log entry was created that was referring to itself. How this happened, I have no idea. The effect was that each time this enty was loaded, the elogd started to hang, going to 100% load and not responding to any http requests anymore. This problem can be reproduced by manually creating such a self-referencing log entry (see attachment). The problem entry that leads to the crash can be made by editing any elog entry and adding a line "Reply to: X" and a line "In reply to: X" where X is the MID of this entry.
1) Maybe it is possible to add a check when writing files that ensure, that is a log entry does not reference itself.
2) Maybe when loading files are preparing the thread view, elogd can detect cycles and abort.
|
| Attachment 1: 011108a.log
|
$@MID@$: 1
Date: Thu Nov 08 18:37:57 2001
Reply to: 1
In reply to: 1
Author: Stefan Ritt
Type: Routine
Category: General
Subject: Welcome
Attachment:
Encoding: ELCode
========================================
[B]Congratulations for installing ELOG sucessfully!
[/B]
This is a demo entry to ensure the elogd server is working correctly.
Click [I]"New"[/I] to add new pages and [I]"Delete"[/I] to delete this page.
|
|
68896
|
Thu Feb 21 08:51:21 2019 |
| Finn Junker | fj@tvis.net | Question | Windows | 3.14 | Re: Unwanted double entries eg. double clicking submit button |
Thank your very much for your work on this - as i mentioned this is a minor issue.
Kind Regards Finn
| Stefan Ritt wrote: |
|
"I committed" means that the change is sent to the GIT repository. People who compile from the source code can pull and compile immediately. Windows users have to wait until I do the next release. I'm developing on a Mac and have to boot a special (old) Windows machine to compile the .exe which each time takes me about one hour including documenation updates, changelog updates, upload of zip files etc. Since my main job is heading a research group, I only can devote this hour once in a while, depending on my work load. Sometime even the weekends are too short.
| Alan Grant wrote: |
|
I'm also happy to see this change implemented as we've had to deal with the same issue at times as well. Will this change be incorporated into the latest version (314-2, aka elog-latest.exe), or will there be a new version release (that is not in Changelog yet)? If so, can you give any ETA on this new code availability?
Also I noticed that the Elog Home page still says "Current version is: 3.1.2". I assume that only means it hasn't been updated, not that it means it's the current STABLE version and subsequent releases are beta -- please correct me if I'm wrong. I just want to make sure I understand how the versions and releases work.
Endless thanks for this product and all your work Stefan.
| Stefan Ritt wrote: |
|
I just committed some code which disables the "Submit" button after the first click and replaces the text with "Please wait...". So double submits should not be possible any more.
| David Pilgram wrote: |
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
| Finn Junker wrote: |
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting i a double or triple entry containing the same text and a almost identical timestamp.
Is there a way to aviod this?, my "solution" so far has been to select the entries and manually delete them. I'm using Elog version 3.14
Kind Regards Finn
|
|
|
|
|
|
|
68895
|
Wed Feb 20 22:45:39 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 3.1.2 | Re: New feature request for Options list |
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 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.
|
|
|
68894
|
Wed Feb 20 22:41:23 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.14 | Re: Unwanted double entries eg. double clicking submit button |
"I committed" means that the change is sent to the GIT repository. People who compile from the source code can pull and compile immediately. Windows users have to wait until I do the next release. I'm developing on a Mac and have to boot a special (old) Windows machine to compile the .exe which each time takes me about one hour including documenation updates, changelog updates, upload of zip files etc. Since my main job is heading a research group, I only can devote this hour once in a while, depending on my work load. Sometime even the weekends are too short.
| Alan Grant wrote: |
|
I'm also happy to see this change implemented as we've had to deal with the same issue at times as well. Will this change be incorporated into the latest version (314-2, aka elog-latest.exe), or will there be a new version release (that is not in Changelog yet)? If so, can you give any ETA on this new code availability?
Also I noticed that the Elog Home page still says "Current version is: 3.1.2". I assume that only means it hasn't been updated, not that it means it's the current STABLE version and subsequent releases are beta -- please correct me if I'm wrong. I just want to make sure I understand how the versions and releases work.
Endless thanks for this product and all your work Stefan.
| Stefan Ritt wrote: |
|
I just committed some code which disables the "Submit" button after the first click and replaces the text with "Please wait...". So double submits should not be possible any more.
| David Pilgram wrote: |
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
| Finn Junker wrote: |
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting i a double or triple entry containing the same text and a almost identical timestamp.
Is there a way to aviod this?, my "solution" so far has been to select the entries and manually delete them. I'm using Elog version 3.14
Kind Regards Finn
|
|
|
|
|
|
68893
|
Wed Feb 20 22:24:05 2019 |
 | Alan Grant | agrant@winnipeg.ca | Request | Windows | 3.1.2 | New feature request for Options list |
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. |