Awesome！It's appreciated. Many Thanks!

When there are attachments in an entry, logbook is adding additional "MIME-Version" header to e-mail messages.

Spam filter in our university system is mostly giving warnings:

• X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"

But sometimes it is not redirecting further the message.

• Remote Server returned '< #5.6.0 smtp; 554 5.6.0 Bounce, id=27666-07 - BAD HEADER>'

In code I noticed there is always "MIME-Version" header added to the message and additionaly it is added again when a file is attached. I think it is not neccessary to add again this header.

> Hi,
>   I reopen this old thread since I'm having a similar problem.
> 
> I'm running ELOG V3.1.1-0767eb0 on ubuntu with webserver authentication, and I'd like to remove 'active' checkbox as well.
> 
> The problem that we found is that if any user click on the [Set None] button at the bottom of the Config page in order to unsubscribe from all mail notification,
> *all* the checkbox are toggled, not only those for the email notification. And this includes also the "active user" as well.

I can confirm that this bug is present even in this forum and in my current version (ELOG V3.1.3-aded4ae).
And I am positive that this is a bug: it was certainly not the intended behaviour.

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, 
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>
###

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>
> ###

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.