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?