| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68629
|
Sat Jun 10 07:05:24 2017 |
 | Erkcan Ozcan | erkcan@gmail.com | Bug report | Linux | V3.1.3-aded4ae | Server dropping SSL connection while uploading large files | 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. |
|
68632
|
Tue Jun 20 14:32:29 2017 |
 | Niklas Hoglund | niklas@hoglund.pp.se | Bug report | Windows | 3.1.3 | my elogd crashes when editing the configuration | Hi,
my elogd crashes sometimes when I click on the "Change config" button. What info should I collect more than below/attached?
In windows EventViewer I see this printouts:
###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-06-20T12:25:30.000000000Z" />
<EventRecordID>28059</EventRecordID>
<Channel>Application</Channel>
<Computer>NIKLAS</Computer>
<Security />
</System>
- <EventData>
<Data>108889037262</Data>
<Data>1</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>c0000005</Data>
<Data>00064eea</Data>
<Data />
<Data />
<Data>C:\Users\hognik\AppData\Local\Temp\WER9155.tmp.WERInternalMetadata.xml</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_08bd38b0</Data>
<Data />
<Data>0</Data>
<Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data>
<Data>0</Data>
<Data>94c2d6a18797708666faf33a7273855a</Data>
</EventData>
</Event>
###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-06-20T12:24:47.000000000Z" />
<EventRecordID>28058</EventRecordID>
<Channel>Application</Channel>
<Computer>NIKLAS</Computer>
<Security />
</System>
- <EventData>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>c0000005</Data>
<Data>00064eea</Data>
<Data>1568</Data>
<Data>01d2e9c028b88983</Data>
<Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
<Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
<Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data>
<Data />
<Data />
</EventData>
</Event>
###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-06-20T12:24:07.000000000Z" />
<EventRecordID>28057</EventRecordID>
<Channel>Application</Channel>
<Computer>NIKLAS</Computer>
<Security />
</System>
- <EventData>
<Data>108889037262</Data>
<Data>1</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>c0000005</Data>
<Data>00064eea</Data>
<Data />
<Data />
<Data>C:\Users\hognik\AppData\Local\Temp\WERBE94.tmp.WERInternalMetadata.xml
C:\Users\hognik\AppData\Local\Temp\WERCA4D.tmp.appcompat.txt triagedump.dmp
C:\Users\hognik\AppData\Local\Temp\WERCB77.tmp.WERDataCollectionFailure.txt</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_0a4ff4e6</Data>
<Data />
<Data>0</Data>
<Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data>
<Data>4104</Data>
<Data>94c2d6a18797708666faf33a7273855a</Data>
</EventData>
</Event>
###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-06-20T12:23:53.000000000Z" />
<EventRecordID>28056</EventRecordID>
<Channel>Application</Channel>
<Computer>NIKLAS</Computer>
<Security />
</System>
- <EventData>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>c0000005</Data>
<Data>00064eea</Data>
<Data>2338</Data>
<Data>01d2e9baf6174f0f</Data>
<Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
<Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
<Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data>
<Data />
<Data />
</EventData>
</Event>
### |
| Attachment 1: WindowsCrashFiles.zip
|
|
Draft
|
Thu Jun 22 20:55:36 2017 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 3.1.3 | Re: my elogd crashes when editing the configuration | Might be some bad data in your elogd.cfg file. Have a look at that file with a text editor to see if there's anything wrong. Start with a pristine config file from the
> Hi,
> my elogd crashes sometimes when I click on the "Change config" button. What info should I collect more than below/attached?
>
> In windows EventViewer I see this printouts:
>
> ###
> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
> <Provider Name="Windows Error Reporting" />
> <EventID Qualifiers="0">1001</EventID>
> <Level>4</Level>
> <Task>0</Task>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2017-06-20T12:25:30.000000000Z" />
> <EventRecordID>28059</EventRecordID>
> <Channel>Application</Channel>
> <Computer>NIKLAS</Computer>
> <Security />
> </System>
> - <EventData>
> <Data>108889037262</Data>
> <Data>1</Data>
> <Data>APPCRASH</Data>
> <Data>Not available</Data>
> <Data>0</Data>
> <Data>elogd.exe</Data>
> <Data>0.0.0.0</Data>
> <Data>58f9c864</Data>
> <Data>elogd.exe</Data>
> <Data>0.0.0.0</Data>
> <Data>58f9c864</Data>
> <Data>c0000005</Data>
> <Data>00064eea</Data>
> <Data />
> <Data />
> <Data>C:\Users\hognik\AppData\Local\Temp\WER9155.tmp.WERInternalMetadata.xml</Data>
>
> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_08bd38b0</Data>
>
> <Data />
> <Data>0</Data>
> <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data>
> <Data>0</Data>
> <Data>94c2d6a18797708666faf33a7273855a</Data>
> </EventData>
> </Event>
> ###
>
> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
> <Provider Name="Application Error" />
> <EventID Qualifiers="0">1000</EventID>
> <Level>2</Level>
> <Task>100</Task>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2017-06-20T12:24:47.000000000Z" />
> <EventRecordID>28058</EventRecordID>
> <Channel>Application</Channel>
> <Computer>NIKLAS</Computer>
> <Security />
> </System>
> - <EventData>
> <Data>elogd.exe</Data>
> <Data>0.0.0.0</Data>
> <Data>58f9c864</Data>
> <Data>elogd.exe</Data>
> <Data>0.0.0.0</Data>
> <Data>58f9c864</Data>
> <Data>c0000005</Data>
> <Data>00064eea</Data>
> <Data>1568</Data>
> <Data>01d2e9c028b88983</Data>
> <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
> <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
> <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data>
> <Data />
> <Data />
> </EventData>
> </Event>
>
> ###
>
> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
> <Provider Name="Windows Error Reporting" />
> <EventID Qualifiers="0">1001</EventID>
> <Level>4</Level>
> <Task>0</Task>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2017-06-20T12:24:07.000000000Z" />
> <EventRecordID>28057</EventRecordID>
> <Channel>Application</Channel>
> <Computer>NIKLAS</Computer>
> <Security />
> </System>
> - <EventData>
> <Data>108889037262</Data>
> <Data>1</Data>
> <Data>APPCRASH</Data>
> <Data>Not available</Data>
> <Data>0</Data>
> <Data>elogd.exe</Data>
> <Data>0.0.0.0</Data>
> <Data>58f9c864</Data>
> <Data>elogd.exe</Data>
> <Data>0.0.0.0</Data>
> <Data>58f9c864</Data>
> <Data>c0000005</Data>
> <Data>00064eea</Data>
> <Data />
> <Data />
> <Data>C:\Users\hognik\AppData\Local\Temp\WERBE94.tmp.WERInternalMetadata.xml
> C:\Users\hognik\AppData\Local\Temp\WERCA4D.tmp.appcompat.txt triagedump.dmp
> C:\Users\hognik\AppData\Local\Temp\WERCB77.tmp.WERDataCollectionFailure.txt</Data>
>
> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_0a4ff4e6</Data>
>
> <Data />
> <Data>0</Data>
> <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data>
> <Data>4104</Data>
> <Data>94c2d6a18797708666faf33a7273855a</Data>
> </EventData>
> </Event>
>
> ###
>
> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
> <Provider Name="Application Error" />
> <EventID Qualifiers="0">1000</EventID>
> <Level>2</Level>
> <Task>100</Task>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2017-06-20T12:23:53.000000000Z" />
> <EventRecordID>28056</EventRecordID>
> <Channel>Application</Channel>
> <Computer>NIKLAS</Computer>
> <Security />
> </System>
> - <EventData>
> <Data>elogd.exe</Data>
> <Data>0.0.0.0</Data>
> <Data>58f9c864</Data>
> <Data>elogd.exe</Data>
> <Data>0.0.0.0</Data>
> <Data>58f9c864</Data>
> <Data>c0000005</Data>
> <Data>00064eea</Data>
> <Data>2338</Data>
> <Data>01d2e9baf6174f0f</Data>
> <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
> <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
> <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data>
> <Data />
> <Data />
> </EventData>
> </Event>
> ### |
|
68634
|
Wed Jun 28 19:37:10 2017 |
| Erkcan Ozcan | erkcan@gmail.com | Bug report | Linux | V3.1.3-aded4ae | Re: Server dropping SSL connection while uploading large files | 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.
|
|
|
68635
|
Wed Jun 28 22:20:38 2017 |
| Andreas Warburton | awarburt@physics.mcgill.ca | Bug report | Linux | V3.1.3-aded4ae | Re: Server dropping SSL connection while uploading large files | 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.
|
|
|
|
68636
|
Thu Jun 29 08:36:03 2017 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | V3.1.3-aded4ae | Re: Server dropping SSL connection while uploading large files | 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.
|
|
|
|
68652
|
Fri Aug 18 01:02:41 2017 |
| Travis Unkel | travisunkel@gmail.com | Bug report | Linux | 3.1.3 | Re: Path disclosure on unfound file | I am having the same issue. If you go to midas.psi.ch/elogs/12345.htm you get the path disclosure issue.
| Stefan Ritt wrote: |
|
What URL did you use? If I try here on this forum I get:
which looks fine to me.
| Bruce Bush wrote: |
|
Greetings,
Running elog 3.1.0 on CentOS 6.6. When I try to access a nonexistent file, elog reveals a path in the 404 page. For example:
Not Found
The requested file /usr/local/elog/themes/default/blortblortblort7854.htm was not found on this server
ELOG version 3.1.0
Is there any way to use a custom 404 page with elog, or to make it stop displaying the file information?
Thank you,
bb
|
|
|
|
68666
|
Mon Aug 21 11:22:09 2017 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 3.1.3-aded4ae | Problems with german_UTF8 language | Hi Stefan,
since recently (a few weeks) ELOG confuses the language translations.
Individual language strings are translated into garbage; most other strings are fine.
Currently I see the string "please select" translated into "ressed" (see attached picture), instead of what's written correctly in the language file "bitte auswählen".
But with every restart the corrupted strings vary: other strings are affected and other garbage strings are shown - some of them unreadable binary code (see Attachment 2).
I have the same version running in English: I see no problems there.
Kind regards
Andreas |
| Attachment 1: elog_lang_bug.png
|
|
| Attachment 2: elog_lang_config_bug.png
|
|
|