We run elog on a server to provide a logbook for our laboratory. We noticed that elog is very slow on loading pages: browser pages spend a lot of time in charging (actually one can speed the procedure refreshing the page but it is quite annoying).

I checked the server load with top and it doesn't show any abnormal CPU or memory usage. Then I ran lsof and I noticed that there are more than 200 entries related to the same elog PID and labelled with CLOSE_WAIT.

My questions are: can the slowness of my logbook be due to the presence of all these CLOSE_WAIT entries (which seems if I understood well wait for a response)? If it's the case, how can I solve this issue?

Thanks

We obtained a certificate from let's encrypt in order to replace the self signed certificate provided with elog. We copied the new certificates replacing the older server.crt

The problem is that when restarted elog raises an error related to the fact it is looking for server.crt and it doesn't find it anymore.

I searched in elog config file in order to find a way to indicate the new certificate but I didn't find how to manage this issue.

Any suggestion?

Hi Laurent,

thanks very much! Probably I've copied the certificate in the wrong directory. I'll try ASAP

Hi I'm here again,

According to my conf file I run elog under a specified user and group different from root. So I copied the .pem file I obtained from certbot in /etc/ssl as well as /urs/local/elog/ssl and ssl folder in the user directory (I will call it <user-dir>) but when I launch elog I receive the error that cannot initialize SSL because the old self signed certificate server.crt in <user-dir>/ssl is not found.

I wonder where in elog.cfg or elsewhere is written that <user-dir>/ssl/server.crt must be usedand how to fix it

Thanks

Hi,
I just installed v.2.6.1 coming from the previous 2.6.0 (on Win2000)
When I access the "configuration" function from a logbook, in the cfg page I only see two buttons in the header
(save or cancel); in the previous version I saw more buttons there ("global config", "create new logbook" and so
on), so here I'm unable to access global configuration or logbook management (except for current logbook options).
I am logged in as admin (actually I have a single-user configuration, thus no particular users defined).
I hope this report may be helpful, and not just being caused by a misunderstanding on my side ;)
Thanks
GiorgioCC

 
> I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
> (save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
> this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution?

Yes, I tried that. Maybe I'll have some other try on other PCs and investigate further, I'll surely let you know. Thanks
for the prompt response and compliments for your very good work! ELog is really a great piece of software.

> > I just installed v.2.6.1 coming from the previous 2.6.0 (on Win2000)
> > When I access the "configuration" function from a logbook, in the cfg page I only see two buttons in the header
> > (save or cancel); in the previous version I saw more buttons there ("global config", "create new logbook" and so
> > on), so here I'm unable to access global configuration or logbook management (except for current logbook options).
> 
> I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
> (save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
> this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution?

Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both with the
existing cfg file and with the new cfg.
Choosing "configuration", I still only see the current logbook configuration file section with "Save" and "cancel"
buttons, no access to global config whatsoever; the same as I saw on windows version. I tried version 2.6.1-1622.
Regards
Giorgio

> I tried again, using the configuration file from the distribution (elog:1627/1). Hitting "config", I see the picture
> attached (elog:1627/2). So it's a mystery why it is different in your case...

Indeed... I peeked into the code, and I got the feeling it could be a matter of incorrect user setup (though I have no
users/authorizations defined at all) or maybe browser cookies. A thin trail, but I'll try some debug directly on the
code and, should I come up with something, I'll surely notice you.
Thanks for your support!