Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Record ID corruption, posted by Frank Baptista on Sun May 3 15:58:24 2020 
    icon2.gif   Re: Record ID corruption, posted by David Pilgram on Sun May 3 18:05:32 2020 
       icon2.gif   Re: Record ID corruption, posted by Frank Baptista on Sun May 3 22:43:12 2020 200428a.log
          icon2.gif   Re: Record ID corruption, posted by David Pilgram on Mon May 4 14:55:53 2020 
             icon2.gif   Re: Record ID corruption, posted by Frank Baptista on Fri May 22 21:03:05 2020 
                icon2.gif   Re: Record ID corruption, posted by David Pilgram on Sat May 23 16:15:38 2020 
Message ID: 69146     Entry time: Sun May 3 18:05:32 2020     In reply to: 69145     Reply to this: 69147
Icon: Reply  Author: David Pilgram  Author Email: David.Pilgram@epost.org.uk 
Category: Question  OS: Windows  ELOG Version: V3.1.4-80633ba 
Subject: Re: Record ID corruption 

Hi,

I've had problems in the past due to a dodgy pointer creating branches despite a "No branches" in the configuration file.  It would be very interesting to see what the 200428a.log file looks like with these entries: in the screenshot they appear to be shown in time order, but do the "Reply to" and "In reply to" liknes in each entry (in the .log file) show a linear progression through the entires, a branch or indeed this same order as the screenshot.  If the duplicated entry sequential to 5657 (i.e 5658) then I would suspect something akin to my pointer's double click when I only made a single click, so fast that then second entry were created before the "No branches" checking part of the program had been reached.  Not so sure about such an event here unless entry 5658 were already open but not closed?

 

Regards,

David.

Frank Baptista wrote:

Hi all,

I've encountered an occasional problem that seems to be exacerbated by having a message with many replies.

In our use of ELOG, we run lengthy environmental tests (often several days) in multiple temperature chambers (one logbook for each chamber).  We document the start of the test with a log entry, and then periodically create replies -- first to the original log entry, and then to each successive reply (no branching allowed), in order to document how far along the test is.

What I'm seeing is an occasional "hiccup" in the order of records -- in the snapshot below, you can see that the record ID(s) go (in chronological order) ....5654, 5655, 5656, 5659, 5657, 5658, 5660, 5661....

Additionally, in this example, record ID# 5659 and record ID# 5657 are duplicates -- duplicate time stamp and duplicate text.

Has anyone else encountered this? 

Thanks,
Frank
 

 

ELOG V3.1.4-80633ba