Re: inactive users, posted by Stefano Lacaprara on Wed May 31 16:02:46 2017
|
Hi,
a possible solution is to change the current SetAll() and SetNone() javascript functions to something like:
|
Server dropping SSL connection while uploading large files, posted by Erkcan Ozcan on Sat Jun 10 07:05:24 2017
|
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. |
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. |
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 |
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 |
Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Fri Jul 14 19:26:06 2017
|
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 |
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 08:50:16 2017
|
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?
Phil |
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Wed Jul 19 08:59:52 2017
|
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" |