I would like to know, if the command "Admin restrict edit time = " does really work as intended.

In my case I have the following global configuration:

Admin user = <me>
Restrict edit = 1
Restrict edit time = 1
Admin restrict edit time = 10000

And every time, when I want to edit an entry (as admin), that is older than 1 hour, i get the following error message:

"Entry can only be edited 1 hours after creation"

The command "Append on edit = " is getting executed everytime, when a dropdown menu is changed. This happens even at the first creation of an entry, so the append text stucks up multiple times in the text body.

Hi guys,

we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:

Authentication = Kerberos, File
Kerberos Realm = TEST.COM
Password file = ./pwd.xml

Even if the kinit comand is retrieving correctly a ticket for the user tsearch@TEST.COM(we see it using klist and tcpdump on lo interface), elogd kerberos authentication is not working.

We tried using tcpdump for troubleshooting but no traffic is generated on the loopback interface.

Did someone solve this problem or do you have an idea on how to make the kerberos authentication working?

Thanks

I have "Summary lines = 1" in the config file. The first line visualized in the summary list, in the Text column, is truncated. I'm using the default style.

Which is the way to set the number of character displayed?

I have already tested your patch backporting the change to 2.7.7.1. It works like a charm.

Thank you very much!

We recently installed ELOG and it works pretty well, but the load times are rather inconsistent. Most of the time 
it is very fast, but it also often hangs for around 5-10 seconds while loading. It seems to affect all parts of 
the page that are returned at random, so sometimes the main html file will hang, sometimes the css file and 
sometimes the images.

The hardware it is running on is nothing special, an older 3 GHz Celeron, but it should be fast enough. It is 
running on Debian 7. 

Any ideas what the problem could be, or how I could investigate it further to find the bottleneck?

> I'm not an expert in debugging web applications. Here are my two cent:
> We once had a problem when we hosted very large logbooks (several 10 thousands of entries) that the server would run
> out of real memory and was slowed down by swapping. Therefore my first idea would be to monitor the server: Is
> the CPU load peaking? What happens with the memory consumption? Any other suspicious process running on the server?
> But it could be as well a network or browser problem. Did you try different browsers?
> Did you check the elogd log file?

The logbook only has a few hundred entries, elogd is using only around 20-30 MB and there is enough free RAM. The load 
average for the server is around 0.2, elogd only uses 5% CPU at most when it is accessed and the CPU is idle most of the 
time. 

Strangely it happens mostly when using Chrome, and almost never with Firefox. I captured the network traffic, but I can't 
see anything unusual. It just takes very long until the answer is returned by the elogd server.

Hi,

I have been trying to get the display mode into threaded by default, it does not work on any of my logbooks. I saw related threads in this forum but none gave me a solution (unless the 2.7.8-2282 is available for download).

Here is a simple example which i can not get working.

thanks for your help

FX