Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 427 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  66459   Wed Jul 22 16:30:48 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.6r2233Re: Crashes when editing entries

T. Ribbrock wrote:

Nonetheless, given that this set-up has been a great help for us - if you ever get the chance to make this work (even) better, I'd be most grateful.

Well, for that I have to reproduce the problem. So best would be if you strip it down to the bare minimum in order to reproduce this reliably. Then you zip everything and send it to me. Then tell me what I have to edit and submit in order to stimulate the crash. Once this is successful, I can fix it.

  66460   Wed Jul 22 16:52:13 2009 Reply T. Ribbrockemgaron+elog@ribbrock.orgBug reportLinux2.7.6r2233Re: Crashes when editing entries

Stefan Ritt wrote:

T. Ribbrock wrote:

Nonetheless, given that this set-up has been a great help for us - if you ever get the chance to make this work (even) better, I'd be most grateful.

Well, for that I have to reproduce the problem. So best would be if you strip it down to the bare minimum in order to reproduce this reliably. Then you zip everything and send it to me. Then tell me what I have to edit and submit in order to stimulate the crash. Once this is successful, I can fix it.

Thank you - I shall look into that, though it'll probably take a while to prepare it.

  66472   Tue Jul 28 16:30:46 2009 Entry T. Ribbrockemgaron+elog@ribbrock.orgBug reportLinux2.7.6r2233Odd problem (bug?) with certain attribute

I have the following simple test logbook:

; General
List display = Edit, Hostname, OS, Size
Entries per page = 150
Quick filter = OS
Date Format = %d/%m/%Y
Summary Lines = 0

; Attributes
Attributes = Hostname, OS, CPU,Size
Required Attributes = Hostname
Sort Attributes = Hostname

; Message part: log is text only, but elog is allowed
Default encoding = 0
Allowed encoding = 2

For some strange reasons, I'm having problems with the "Size" attribute, which I have added later. If I start adding/editing entries, at some point, the "Size" attribute will stay at "0" and will not accept any further changes. I've tried to pare down the config to maybe find which statement could be causing this, but to no avail. The only thing I can say is taht id doesn not seem to happen if the configuration consist of the sole line

Attributes = Hostname, OS, CPU,Size

I'm quite puzzled as to what is going on here (the original problems stems from a more complicated logbook) - I'm not even 100% sure whether this happens due to a bug or not.

 

Regards,

 

Thomas

  66473   Tue Jul 28 16:57:39 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.6r2233Re: Odd problem (bug?) with certain attribute

T. Ribbrock wrote:

I have the following simple test logbook:

; General
List display = Edit, Hostname, OS, Size
Entries per page = 150
Quick filter = OS
Date Format = %d/%m/%Y
Summary Lines = 0

; Attributes
Attributes = Hostname, OS, CPU,Size
Required Attributes = Hostname
Sort Attributes = Hostname

; Message part: log is text only, but elog is allowed
Default encoding = 0
Allowed encoding = 2

For some strange reasons, I'm having problems with the "Size" attribute, which I have added later. If I start adding/editing entries, at some point, the "Size" attribute will stay at "0" and will not accept any further changes. I've tried to pare down the config to maybe find which statement could be causing this, but to no avail. The only thing I can say is taht id doesn not seem to happen if the configuration consist of the sole line

Attributes = Hostname, OS, CPU,Size

I'm quite puzzled as to what is going on here (the original problems stems from a more complicated logbook) - I'm not even 100% sure whether this happens due to a bug or not.

That's indeed a strange bug, and thanks to your detailed explanation I could easily reproduce it. The problem was that in the ELCode toolbar there is already a "SIZE" parameter, which gets submitted instead of your "size" attribute. Therefore whatever you submit as "size", gets replaced by zero (since the SIZE drop-down box usually sits at zero). So you can either go and change your "size" attribute into someting else like "Memory Size", or you upgrade to version 2244, where I fixed this problem.

  66474   Tue Jul 28 17:10:13 2009 Reply T. Ribbrockemgaron+elog@ribbrock.orgBug reportLinux2.7.6r2233Re: Odd problem (bug?) with certain attribute

Stefan Ritt wrote:

That's indeed a strange bug, and thanks to your detailed explanation I could easily reproduce it. The problem was that in the ELCode toolbar there is already a "SIZE" parameter, which gets submitted instead of your "size" attribute. Therefore whatever you submit as "size", gets replaced by zero (since the SIZE drop-down box usually sits at zero). So you can either go and change your "size" attribute into someting else like "Memory Size", or you upgrade to version 2244, where I fixed this problem.

 Very nice, thank you! Given that I also still have to test the fix you made for the crash problem with "shared" logbooks (I assume it's also present in 2244), I'll upgrade and report back (probably tomorrow).

  66482   Wed Jul 29 13:23:41 2009 Agree T. Ribbrockemgaron+elog@ribbrock.orgBug reportLinux2.7.6r2233Re: Odd problem (bug?) with certain attribute

T. Ribbrock wrote:

 Very nice, thank you! Given that I also still have to test the fix you made for the crash problem with "shared" logbooks (I assume it's also present in 2244), I'll upgrade and report back (probably tomorrow).

 2244 is now running, and indeed, the "Size" attribute works now. Thank you!

  66483   Wed Jul 29 14:48:34 2009 Agree T. Ribbrockemgaron+elog@ribbrock.orgBug reportLinux2.7.6r2233Re: Crashes when editing entries

By now, I've installed 2244 and ran some rudimentary tests. So far, I was not able to reproduce the crash anymore. Looking good!

  66545   Wed Sep 16 16:37:35 2009 Question Chuck BrostBrost_chuck@solarturbines.comQuestionWindows2.7.6-2236Elog & SSL Export to CSV , Problem

 

We use eLOG with IE. Once we turned on SSL, it is no longer possible to "Export to CSV" and save the output.

The error that we get is:

Internet Explorer was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later.

This is documented on Microsoft's site: http://support.microsoft.com/kb/316431

It is considered a feature with no fix. Basically the browser is honoring a request from the server which is "Pragma: no-cache". Problem can be reproduced in IE versions 6 through 8.
 

ELOG V3.1.5-3fb85fa6