Hi,
  a possible solution is to change the current SetAll() and SetNone() javascript functions to something like:


  <!--
function SetNone()
{
  for(var i=0,els=document.querySelectorAll('[name^="sub_lb"]'); i<els.length; i++)
  {
    els[i].checked = false;
  }
}
function SetAll()
{
  for(var i=0,els=document.querySelectorAll('[name^="sub_lb"]'); i<els.length; i++)
  {
    els[i].checked = true;
  }
}
//-->

It works on Chromium 58.x and Firefox 53.x, I don't know about other browsers.

The javascript snippet is generated in function elogd.c: void show_config_page(LOGBOOK * lbs) (line 13960-984 on my version of the source code).

Best,
  Stefano

Hi,

I am having trouble with uploading large (>0.5MB) files to elog. We click on upload and in a couple of seconds, the webbrowser complains that the server has dropped the connection.

Following the suggestions I found on these forums (https://midas.psi.ch/elogs/Forum/66753), I increased the timeout.tv_sec to 30 in three locations in elogd.c, but this did not help.

The problem is present in my old elog installation (from ~2 years ago), as well as the latest git snapshot from bitbucket that I cloned on June 10, 2017.

PS: Upload seems to work for non-secure configuration. It still takes a while to load, but it completes. However we prefer to use secure connections ( SSL = 1 ).
PS: Using nmap I looked at the latency to the relevant port, it can be as high as 0.5sec, but most often it is shorter.

Cheers,
e.

Hi,

Could someone at least suggest how I could debug this problem myself? If I know where to start, perhaps I can fix it myself and contribute to the software.

Best,

e.

Hi Erkcan,

I observed similar behaviours when attempting to do SSL uploads and mirroring over a WAN (see some of my recent posts).  Having not received any responses/help, and no time to try debugging the source myself, I've changed the way I use ELOG such that my attachment uploads are always local (on my Mac laptop, where I do most of my ELOGging) and I have switched off the mirroring, choosing instead to do my own rsync backup to a central linux server on which I have running a read-only ELOG executable.  This configuration is both relatively secure and stable, and it matches my use case well.  More generally, however, it is unfortunate that this SSL and mirroring functionality isn't truly there for all users, even though the documentation touts it to be so.

Best regards,

Andreas W.

One possibility is to run elog in non-SSL mode and put an Apache server in front of it. The Apache server can then do the SSL communication, and forward all requests to elog in plain text (non-SSL). This has been proven to work with large attachments, actually that's the way I use it.

I didn't find time to debug the SSL problem. If anybody is interested in doing so, the relevant code is in function server_loop() around line 30015 (SSL_read()).

Stefan

Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) .  Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this.  Can you see what it is?  Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?

[global]

.

Suppress Email to users = 1
.

[Notebook]

.

Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...

.

{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...

{3} Email Category TDAQ =
.

Use Email Subject = Elog Notice: $subject
 

Command:  /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"

Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?

Thank you for responding.

I thought I provided the command at the end of the note:

/usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"

This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text.  The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.

For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.

Sorry for forgetting these details:  bash shell; linus version 2.6.32-696.el6.x86_64