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?

The instructions for securing elogd using an SSL proxy are incomplete.
http://midas.psi.ch/elog/adminguide.html#secure
http://midas.psi.ch/elogs/contributions/11

If you follow these instructions, elogd will still listen for and accept non-SSL connections on it's own TCP port bypassing the SSL proxy.

(True, the elogd TCP port number is somewhat secret, so there is some security-by-obscurity here).

To secure the elogd TCP port against connections that bypass the SSL proxy, elogd has to be started
with the "-n localhost" command line options.

To add this option, one has to edit /etc/init.d/elogd. I do not know if this change will be lost when the elog rpm package is updated.

It would be better if this option could have been specified through elogd.conf.

The "-n" command line option is not documented here
http://midas.psi.ch/elog/adminguide.html#config
but is visible if you run "elogd -h".

P.S. Even with "-n localhost", users of the local machine can bypass the SSL proxy.

K.O.

Is there any way to include the text of a log message in the CSV export? 
Anyway to include a pointer to the attachment?

In version 2.6 the themes do not work right on Windows. 
The URL is fixed at whichever logbook that is selected (e.g. ELOG 2.5.9-4 is <link rel="stylesheet" type="text/css" href="default.css"> & ELOG 2.6.0-1 is <link rel="stylesheet" type="text/css" href="http://localhost:8080/demo/default.css">).

Version 2.0.5 of elog has been released today. Among various bugfixes, the 
display speed for threaded lists has been improved significantly. Display 
all messages of this forum and press the reload button to see the 
difference.

Hi Stefan,

I'm experiencing problems importing XML (.csv is not working at all for me).

My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"

- During "preview" I see that all entries are listed.

- During the import I get the "wrong date format" error.

- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.

- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.

- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.

Any suggestion what could be wrong? Is it the missing date-value?

I was wondering if anyone out there has had any success with importing XML data into ELOG. Using the XML schema which I derive from the EXPORT data from ELOG into XML format or creating the file from scratch, I either blowup the system and have to restart elogd or it doesn't work and says, XML file doesn't contain ELOG_LIST element (which I create and it still doesn't work).

Basically, I am trying to take spreadsheet data, convert it into XML and upload it as a logbook so I don't have to perform lots of data entry. I also tried .CSV but have had no luck. 

Any thoughts or ideas? 

Dear ELOG users,

this is to announce an important security update. As proposed by Lukasz Olejnik (CERN/PSNC), ELOG has now switched to strong encryption of password. So everybody concerned in security is advised to update to the new version 2.8.0. Existing password files for Windows users and Linux users not using HAVE_CRYPT are automatically converted. Those installations which used HAVE_CRYPT in the past under Linux have to ask their users to re-enter their password (via the link "Forgot password") after the upgrade to version 2.8.0.

Best regards,

  Stefan Ritt