Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon5.gif   2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Mon Nov 2 21:23:38 2009 
    icon2.gif   Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by Stefan Ritt on Tue Nov 3 09:04:34 2009 
       icon2.gif   Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Wed Nov 11 19:45:19 2009 
          icon2.gif   Re: Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by Heinzmann on Tue Nov 17 19:31:46 2009 
          icon2.gif   Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Fri Nov 20 19:32:22 2009 
             icon2.gif   Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Mon Dec 7 21:25:23 2009 
                icon2.gif   Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Thu Dec 10 18:12:19 2009 
                   icon2.gif   Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by Stefan Ritt on Thu Dec 10 19:06:18 2009 
Message ID: 66621     Entry time: Tue Nov 17 19:31:46 2009     In reply to: 66596
Icon: Reply  Author: Heinzmann  Author Email: catman333@web.de 
Category: Bug report  OS: Windows  ELOG Version: 2.7.7 2246 
Subject: Re: Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.

 

I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.

 

This is running under Win2K with SP4 as an automatic service on port 80.

 

I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.

 

If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.

I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash. 

 In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:

 

 Hi,

I´m using 2.7.7 rev 2246 and tested it with my logbooks without any problems. But today I had no chance to reach them anymore. Strange.

Regards,

 

Michael

 

ELOG V3.1.5-3fb85fa6