Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   Synchronizing mirror causes corruption of logbook entries with multiple logbooks defined?, posted by Glenn Horton-Smith on Fri Aug 27 23:11:45 2010 
    icon2.gif   Re: Synchronizing mirror causes corruption of logbook entries with multiple logbooks defined?, posted by Andreas Luedeke on Fri Sep 3 14:43:16 2010 
       icon2.gif   Re: Synchronizing mirror causes corruption of logbook entries with multiple logbooks defined?, posted by Renee Poutissou on Fri Sep 3 19:04:46 2010 
Message ID: 66891     Entry time: Fri Sep 3 19:04:46 2010     In reply to: 66890
Icon: Reply  Author: Renee Poutissou  Author Email: renee@triumf.ca 
Category: Comment  OS: Linux | Mac OSX  ELOG Version: 2.8.0 
Subject: 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.

 

ELOG V3.1.5-3fb85fa6