ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66895
|
Wed Sep 8 15:31:33 2010 |
| Devin Bougie | dab66@cornell.edu | Request | Linux | 2.7.5 | difficulty with slow connections (was Re: frequent crashes on SL4) |
Hi Stefan,
> There was a timeout of 1 sec. in the elogd daemon, which probably is too short for a satellite connection. Unfortunately I have no satellite here
> around to test it, so I "blindly" increased it to 6 seconds in the current SVN version. Please give it a try.
The latest release (2.8.0-2313) does fix this problem. Our user is now able to modify entries and upload attachments using their satellite connection.
Thank you very much for your time and help. I am sorry I didn't receive this in time to help test the old SVN version.
Sincerely,
Devin |
66894
|
Mon Sep 6 21:36:51 2010 |
| Arno Teunisse | A.teeling3@chello.nl | Bug report | Windows | V2.7.7-224 | Re: fckedit and creating tables |
Arno Teunisse wrote: |
Hello
Using windows7 and the elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246. I noticed a bug in the tables created with fckeditor. When on winxp there is no problem. So it seems windows7 related.
Don't know if I should post here or somewhere else. When i Click the table icon i get : 
When I want to continue ( Pressing Yes) i get 
So the OK button is removed, and i can only cancel. So it's impossible to create a new table in elog. ( yes , create it by hand, but that is not so nice )
Download the latest version of elog : elogd 2.8.0 built Aug 2 2010, 12:16:05 revision 2312 . Just to see if this helps. The result is the same.
Is there some solution/workaround for this ?
Thanks for elog : it's great.
|
Answer : Problem solved. It is not window7 related. When I did a fresh install ( not installing over the old directory ) everything is working as expected. So I did something wrong with installing over the old elog directory.
Thanks for you're time and the inconvenience.
|
66893
|
Mon Sep 6 21:21:25 2010 |
| Arno Teunisse | A.teeling3@chello.nl | Bug report | Windows | V2.7.7-224 | fckedit and creating tables |
Hello
Using windows7 and the elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246. I noticed a bug in the tables created with fckeditor. When on winxp there is no problem. So it seems windows7 related.
Don't know if I should post here or somewhere else. When i Click the table icon i get : 
When I want to continue ( Pressing Yes) i get 
So the OK button is removed, and i can only cancel. So it's impossible to create a new table in elog. ( yes , create it by hand, but that is not so nice )
Download the latest version of elog : elogd 2.8.0 built Aug 2 2010, 12:16:05 revision 2312 . Just to see if this helps. The result is the same.
Is there some solution/workaround for this ?
Thanks for elog : it's great.
|
66892
|
Mon Sep 6 16:18:41 2010 |
| Robert Heine | heine@kph.uni-mainz.de | Comment | Windows | All | 2.8.-2312 | Re: How to make Subst run? |
Thank you Andreas!
So I will generate the preset entry in a shell script.
And now to something completely different:
Is there a way to make the elogd options -x and -install work together?
Grüßli
Robert |
66891
|
Fri Sep 3 19:04:46 2010 |
| Renee Poutissou | renee@triumf.ca | Comment | Linux | Mac OSX | 2.8.0 | Re: Synchronizing mirror causes corruption of logbook entries with multiple logbooks defined? |
Andreas Luedeke wrote: |
Glenn Horton-Smith wrote: |
We have been experiencing corruption of logbook entries by elogd mirror synchronization. Has anyone else encountered this? Is there a known cause and/or workaround for it? [...]
I made copies of both servers' files and ran two elogd servers on my Mac on different ports, compiled from a fresh checkout of 2.8.0, and the same behavior was observed as I repeatedly made test entries and synchronized. This suggests it isn't specific to Linux architecture, 64-bit or otherwise.
|
We plan to use ELOG with mirror servers in a larger scale here, so I'm interested to know more about your problem.
Could you boil down your configuration to a minimum that still allows a reproduction of the problem and post those configurations as attachments?
Then I would try to reproduce it here. Best case I'll find a bug fix, worst case I'll reconsider the use of mirror servers ;-)
|
I have been using the mirror mechanism for one year for the online T2K /ND280 (neutrino oscillation experiment at J-PARC, Japan). It has been a savior to allow access to all collaborators to the Elog. The experiment online computers are all behind a double firewall that allow only communication through ssh and http in one direction: from the inside to the outside. The master Elog is located in Canada and accessible remotely to all collaborators. The mirror Elog is located inside the firewall on one of the online machines in Japan and synchronization is setup to run automatically every 5 minutes. There are 10 logbooks defined for each of the sub-detector groups.
At first I encountered a big problem when messages were added on both sides. It turned out that Elog mirroring does not work when the two instances are running on different time zones. After I set the machine in Canada to run on Japan time (JST), no further problems have happened. Postings are routinely entered on either of the Elogs and synchronization works well. This feature is essential to having a workable Elog for the T2K experiment.
I had reported the problem of timezones to Stefan last year. He was going to put it on his wish list.
|
66890
|
Fri Sep 3 14:43:16 2010 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Comment | Linux | Mac OSX | 2.8.0 | Re: Synchronizing mirror causes corruption of logbook entries with multiple logbooks defined? |
Glenn Horton-Smith wrote: |
We have been experiencing corruption of logbook entries by elogd mirror synchronization. Has anyone else encountered this? Is there a known cause and/or workaround for it? [...]
I made copies of both servers' files and ran two elogd servers on my Mac on different ports, compiled from a fresh checkout of 2.8.0, and the same behavior was observed as I repeatedly made test entries and synchronized. This suggests it isn't specific to Linux architecture, 64-bit or otherwise.
|
We plan to use ELOG with mirror servers in a larger scale here, so I'm interested to know more about your problem.
Could you boil down your configuration to a minimum that still allows a reproduction of the problem and post those configurations as attachments?
Then I would try to reproduce it here. Best case I'll find a bug fix, worst case I'll reconsider the use of mirror servers ;-) |
66889
|
Fri Sep 3 14:25:37 2010 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | All | 2.7.8 | Re: Elog v2.7.8 does not show substituted attributes while editing or replying |
Dennis Seitz wrote: |
Since we updated to 2.7.8 we've found a problem.
Previously, when we used
Subst on reply subject = Re: $subject
The new "Re: " text would appear in the "subject" field while the user was editing their reply, and they could edit or delete it.
Since 2.7.8, however, it does not appear while editing, but shows up only after the user submits their entry. We would prefer that this appears while the user is editing, because in some cases we want the users to have the option to modify this text. Was this intentional? Is there a way to restore the previous functionality?[...]
|
Sorry, that appears to be an undocumented bug fix :-)
The desired behaviour should be created by
Preset on reply subject = Re: $subject
The command "Subst" is supposed to overwrite the field after it is submitted.
From the documentation you will even find a nicer possibility:
Preset on first reply Subject = Re: $Subject
The prevent replies to build a long chain of "Re: Re: Re: ...."
Cheers Andreas |
66888
|
Fri Sep 3 14:14:07 2010 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Comment | All | 2.8.-2312 | Re: How to make Subst run? |
Robert Heine wrote: | Dear colleagues,
I tried to get an Subst <attrib> = $shell(<command>) to work and put this into a Preset text line, like e.g.:
Attributes = subject, ...
Options <name> = test{1}, ...
Subst myvar = $shell(dir)
{1} Preset subject = Test
{1} Preset text = $myvar
Which results in an ELOG-entry having printed "$myvar" in its body instead of the expected substitution. Changing the Subst command to: "Subst myvar = $host" or even to "Subst myvar = Test" also resulted in printing just the string "$myvar" into the submitted Elog-entry. - What am I doing wrong? |
What you want to do is done simply by:{1} Preset text = $shell(dir) You expect "Subst" to create new variables, but it cannot do this.
"Subst" can overwrite the value of an existing field in an already submitted entry, while
"Preset" allows to prefill an existing entry field and the user may overwrites it before submitting (if it is not "Locked".)
In both cases you can either call a shellscript to create the desired text, or you can use
one of the predefined variables defined in the help pages "ELOG - Syntax of elogd.cfg" for "Subst".
Cheers Andreas |