Re: Server dropping SSL connection while uploading large files, posted by Erkcan Ozcan on Wed Jun 28 19:37:10 2017
|
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.
| Erkcan Ozcan wrote: |
|
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.
|
|
|
Re: Server dropping SSL connection while uploading large files, posted by Andreas Warburton on Wed Jun 28 22:20:38 2017
|
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.
| Erkcan Ozcan wrote: |
|
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.
| Erkcan Ozcan wrote: |
|
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.
|
|
|
|
Re: Server dropping SSL connection while uploading large files, posted by Stefan Ritt on Thu Jun 29 08:36:03 2017
|
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
| Erkcan Ozcan wrote: |
|
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.
| Erkcan Ozcan wrote: |
|
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.
|
|
|
|
Re: Server derived time, posted by Stefan Ritt on Thu Oct 30 03:30:59 2008
|
| Grant Jeffcote wrote: |
|
Hi Stefan,
Is it possible to derive the time in a 'date/time' attribute from the Elog server?
We would like all our entries in GMT/UTC time and unfortunately as the time is currently derived from the client machines there are often entry descrepancies if the regional settings are not set correctly.
The '$entry time' variable can be used but seems to put a 1970 date in the field so bears no relevancy to an 'Event' time?
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks
|
There are several methods to get the server time:
Via presets of attributes
Attributes = Author, Event time, ...
Preset Event time = $utcdate
which gives you actually the UTC time.
Via the editor
The editor toolbar contains a little clock. If you click on it, you insert the current server time (but localized, not UTC).
Hope one of the two methods work for you.
The problem with the conditional attributes in the find page is I believe fixed in the current version. |
Re: Server derived time, posted by Grant Jeffcote on Thu Oct 30 08:39:34 2008
|
| Stefan Ritt wrote: |
|
| Grant Jeffcote wrote: |
|
Hi Stefan,
Is it possible to derive the time in a 'date/time' attribute from the Elog server?
We would like all our entries in GMT/UTC time and unfortunately as the time is currently derived from the client machines there are often entry descrepancies if the regional settings are not set correctly.
The '$entry time' variable can be used but seems to put a 1970 date in the field so bears no relevancy to an 'Event' time?
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks
|
There are several methods to get the server time:
Via presets of attributes
Attributes = Author, Event time, ...
Preset Event time = $utcdate
which gives you actually the UTC time.
Via the editor
The editor toolbar contains a little clock. If you click on it, you insert the current server time (but localized, not UTC).
Hope one of the two methods work for you.
The problem with the conditional attributes in the find page is I believe fixed in the current version.
|
Thanks Stefan, the preset UTC date works well. RTFM on my part perhaps. 
I'm running version 2.7.5.2127 and am still having the issue with conditional attributes in the find area as mentioned above though.
Is it the latest SVN **.2135 that addresses this?
Many thanks |
|
Re: Server derived time, posted by Stefan Ritt on Mon Nov 3 13:15:52 2008
|
| Grant Jeffcote wrote: |
|
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks
|
Many people want conditional attributes on the find page, so I cannot remove it. Before adding another parameter to disable this optionally, I would like to ask you to first try the "Show attributes edit = ..." option, which is not evaluated in the "find" page. Maybe you can achieve what you want with this option. |
|
Re: Send email based on lookup of an attribute, posted by Stefan Ritt on Mon Apr 4 14:09:42 2016
|
> I'm trying to send an email based on an attribute, in other words, a lookup and not $user_email of the author.
>
> For instance, if I set a an attribute "Assignee" with a valid user full name (i.e. John Smith), I'd like to look up John Smith's
> email address from the password file and send him an email. I can't seem to find it something like that in the docs, I can write
> a script to do that, but was looking for a less cumbersom way of doing it. Thanks in advance.
Unfortunately such a feature is not implemented in the current version.
Stefan |
Re: Send e-mail based on a hierarchy of attributes?, posted by Andreas Luedeke on Wed Aug 26 09:18:17 2015
|
Yes, this can be done. See below for an example configuration.
Attributes = entrytype, category
Options entrytype = routine{1}, problem{2}
Options category = software, hardware
{1} Email category software =
{1} Email category hardware =
{2} Email category software = 1@opq.rst, 2@uvw.xyz
{2} Email category hardware = a@bcd.efg, h@ijk.lmn
| Phil Rubin wrote: |
|
Is there a way to distribute e-mail based on the consideration of several attributes and values? A simple example: attributes type and category have several different values, say, routine and problem for type and hardware and software for category, but one would only like messages sent when there's a problem to different sets of hardware or software types. Thus:
Email
type routine category hardware = no message
category software = no message
type problem category hardware = a@bcd.efg, h@ijk.lmn
category software = 1@opq.rst, 2@uvw.xyz
|
|
|