Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon5.gif   v3.1.3 does not work with logbooks from v2.9.2?, posted by Yves on Thu Feb 1 03:12:03 2018 test1.pngtest2.png
    icon2.gif   Re: v3.1.3 does not work with logbooks from v2.9.2?, posted by Andreas Luedeke on Thu Feb 1 10:14:55 2018 
       icon2.gif   Re: v3.1.3 does not work with logbooks from v2.9.2? - solved, posted by Yves on Fri Feb 2 00:02:54 2018 
Message ID: 68730     Entry time: Thu Feb 1 10:14:55 2018     In reply to: 68729     Reply to this: 68733
Icon: Reply  Author: Andreas Luedeke  Author Email: andreas.luedeke@psi.ch 
Category: Question  OS: Windows  ELOG Version: 2.9.2->3.1.3  
Subject: Re: v3.1.3 does not work with logbooks from v2.9.2? 
Hi Yves,
just my two pence, maybe they help you to figure out what's going on:
versions 2.* had all entries of one logbook in one directory. Version 3.* create a subdirectory for each year. This had been added for me: if you use AFS for logbook storage, then you have a limit on how many files you can put into a single directory.
So the first time you start elogd 3.* with data from an elogd 2.* it should move all your logbook entries into sub-directories for each year. If that would have happened, you would not be able to use these logbook directories with the 2.9.2 version.
Maybe your logbook client is not allowed to create sub-directories? Although I would guess that it then would just throw an error message and stop.
Cheers, Andreas
Yves wrote:

I have just upgraded elog from 2.9.2 -> 3.1.3.

3.1.3 runs fine with new logbooks. However, when trying to run 3.1.3 with my logbooks created with 2.9.2 things stop working.

Here is the command I run for testing [attachment 1]: first of all it takes a very long time (~ 10 minutes) for it to index the logbooks. When finished indexing I try it out in a web browser - it takes infinite time to load: no error message appears but also no logbook. After an hour or so elogd crashes without an error message.

When running 2.9.2 on the same machine, all runs wel (attachment 2)

 

cfd file: (I only left in one logbook - they are all configured the same)

[global]
port = 18080
Logging level = 3
Max content length = 500000000
Date format = %A, %d %B %Y


[Logrun - Amptek]
Theme = default
Comment = Logrun Amptec
Reverse sort = 0
Quick filter = Date, Type

 

Any ideas on how to solve this?

 

ELOG V3.1.5-fe60aaf