I am one who received an email every time there is a new entry in this forum.

I have just noticed that since May 20, every email contains the message "An old ELOG entry has been updated: "

whereas before that date, the vast majority say "A new ELOG entry has been submitted: "

Is this something to do with the saving of draft messages?

Talking of which, I see my draft of this message shows up in the forum before I have submitted it.

Hej,

I discovered a problem uploading images taken with the cameras of mobile devices to new elog entries directly from said devices. When selecting the image and choosing "Upload", either the blue page loading indicator gets stuck at around 10% (mobile Safari, iOS 8.3, iPhone 4 and iPad mini) or the error message "failed secure connection; connection reset while page was being loaded" ("Fehler: gesicherte Verbindung fehlgeschlagen. Verbindung zum Server wurde zurueckgesetzt waehrend die Seite geladen wurde") appears shortly after (Android 5.02, Firefox 37.0.2, Motorola G).

From the desktop browser (Firefox 38.0.5, OSX 10.10) there is no problem uploading images at all.

So far, this problem is very reproducible, but only when using ELOG with SSL enabled. Without SSL, the problem disappears on all platforms.

The ELOG daemon runs under Linux (Fedora 18) and I have also tried using the latest development version of ELOG.

Running ELOG with debug messages the only output after the page has been loaded is:

TCP connection #0 on socket 4 closed
TCP connection #0 on socket 4 closed

After these, there is no further output and the mobile devices do not indicate any progress either even after many mi.

The minimal config file I have been using is:

[global]
; network
port = 443
SSL = 1
URL = https://my.server.somewhere/
; paths
Logbook dir = /usr/local/elog/logbooks
Resource dir = /usr/local/elog
Logfile = /tmp/elog.log

[demo]
Attributes = Author, Type, Category, Subject
Required Attributes = Author, Type
Options Type = Status, Modification, Problem Report, Problem Details, Problem Fixed, Other
Options Category = Facility, Experiment, IT, Other
List Page Title = $logbook - $subject

As mentioned before, removing the first three lines fixes the problem (the URL line points to my actual server of course).

I would appreciate any pointers on how to debug this further! The functionality of posting images directly from mobile devices is quite important for the planed deployment of ELOG and I would very much prefer to have SSL enabled when doing so.

Thanks and cheers,

Hanno

I have multiple elogs running on a server.  Is it possible to set one elog to a different timezone?  For example, I run an elog for a group in Washington state, and another elog for a collaboration group in Germany.  I would like to set each elog to their respective timezone. 

thanks,

Gary

Hej,

I just noted that when having an unknown (or presumably misspelled) user name in the "Admin user" line in the
config file, that the other users are no longer treated as admins and do not see the corresponding link to the
admin page e.g. on the list page. In my specific situation, I in fact have only one user registered (new
password file) but two users still on the admin list (old config file). The one user is only treated as admin
after removing the offending name from the list of admins.

I understand that this might be the intended behavior -- but I wonder if this could lead to a situation where
one locks oneself out, e.g. when adding a misspelled user name to the list.


Thanks and cheers,

Hanno

In the emails generated by anyone making an entry in this log book, every apostrophe is followed by a semi-colon.  So the text "I don't think..."  appears in the email as "I don';t think...", and possibly that comment will appear in the email as "I don';;t think...." - not sure on the last bit.  It has been around in the past few versions of elog, but don't recall precisely when this started occurring.  It was fine back in February, with v2.9.2 (presumably) running.

Older versions of elogd have a problem with sending long attachements - the send() syscall is not protected against interrupt by SIGALARM. This seems to be fixed in non-SSL builds of current elog (version 3+), 
but for SSL builds, the error handling for the SSL_write() function looks incorrect. In addition, from OpenSSL documentation it is not clear if SSL_write() can handle signal interrupts at all.
K.O.

URL causes elogd to crash when a global password file name doesn't match any group's password file name. 

The offending URL is copied from the address field of the browser after sorting a logbook by on of the fileds.

After login out and using the copied URL, elogd shows the authentication dialog and then crashes after the credentials are submited.

Some debugging point me to a NULL pointer on the following instruction in line   25502  of elogd.c :

  if (lbs->pwd_xml_tree) {

The work around was to name the global password file as the password file of one of the groups.