| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67628
|
Tue Nov 26 16:24:39 2013 |
 | Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | Crash report involving propagate and replies | Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option? |
| Attachment 1: elogd.cfg
|
[global]
port = 443
SSL = 1
SMTP host = *******
URL = ******
; URL = ******
Allow passwordchange = 1
Self Register = 0
Logfile = D:\ELOG\Log\Logging.txt
[CSM Log]
; Main settings
Password file = D:\ELOG\Password\Admin.xml
Theme = default
List Menu commands = New, Find, List, Config, Change password, Logout, Last Day
; E-mail
; Look and Feel
Use Lock = 1
Fix text = 0
Propagate Attributes = Status
Allow Delete = Noone
; Allow Edit = Noone
Allow Duplicate = Noone
Allow Import = Noone
Allow Select = noone
; Suppress default = 1
Sort Attribute Options System = 1
Sort Attribute Options Sub-System = 1
List after submit = 1
Display mode = summary
Quote on reply = 1
Entries per page = 30
Refresh = 240
Default Encoding = 1
Quick filter = Date, Type, System, Sub-System, Status, subtext
Time format = %A, %B %d, %Y, %H:%M
Page Title = ELOG - $type
Reverse sort = 1
Restrict edit time = 24
ID Display = $message id
Extendable options = System, Sub-System
Type Time of Event = datetime
Preset Time of Event = $date
List Display = ID, Time of Event, Author, Type, System, Sub-System, Status
Allow branching = 0
Reply String =
Summary lines = 5
Prepend on reply = \nAdded on $date by $long_name\n\n
; Log Header
Preset Author = $long_name
Locked Attributes = Author
Preset on reply Author = $long_name
Required Attributes = Author, Type, System, Status, Time of Event
Preset on reply Time of Event = $date
Preset on edit Author = $long_name
Attributes = Time of Event, Author, Type, System, Sub-System, Status,
;Notification
Options Type = Test1{1}, Test2{2}, Test3{3}, Test4{4}, Test5{5}
Style Type Shift Change = background-color:yellow
{5} Preset Status = Closed
Options Status = Open, Closed
Cell Style Status Closed = background-color:#1f9400
Cell Style Status Open = background-color:#a10000
; Event Time options
; Type Event Time = datetime
; Subst Event Time = $date
; Options
{1} Options System = Test
; Options
{2} Options System = Test
; Options
{3} Options System = Test
; Turnover
{5} MOptions System = Test
{5} MOptions Sub-System = Test
|
|
67630
|
Wed Nov 27 15:22:37 2013 |
 | Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| David Pilgram wrote: |
|
| Stephen wrote: |
|
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?
|
Hi Stephen,
I see that you don't allow branching in your threads. Why do you need to propagate the Status throughtout the thread? Why not just mark the latest entry and (incase it is necessary) 'collapse to last = 1'
I'm not saying that the bug (if bug it is, rather than a preset limitation) you've found should not be fixed, but I'm puzzled as to why you happen to use the feature. I can see the point if an initial entry provides a whole tree of branches (and a limit of 10 is rather limiting). OK, I know if it is historic, it cannot easily be changed because of other users. Or if some users will primarily be responding to emails rather viewing the logbook via a browser. I'm a single (ab)user elog system myself, so I'm very tolerant of changing how elog works if it offers an improvement.
|
Thank you for the reply, the not allowing branching was added during the troubleshooting phase of the crashing. Initially I thought the branches caused the issue because crashing only occured on log notes that branched as I only saw the crash on notes that branched, this proved not to be the case. Even with branches the system will crash once there are 10 replies in the note with propagate on.
As for use case, with a few users I needed a way to represent a note as open so that the next person knew work still needed to be done. Once work was completed all notes close, the reason for not using edit is so I have a clear record of what happened (although I may need to change to edit if 10 is the max). I will experiment with the collapse to last to see how it looks. Any other suggestions would be helpful. |
|
67633
|
Mon Dec 2 23:02:45 2013 |
| Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| Andreas Luedeke wrote: |
|
| Stephen wrote: |
|
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?
|
Bad news: I cannot reproduce your problem with the latest elog version 2.9.2 (e7ba466) on scientific linux 6.0
I had to remove some lines in your config, since I don't have your password file.
I'll attach the config file, please have a look if it crashes on your server with the latest elogd version.
Andreas
|
Thanks for the reply, I tried the very basic cfg and the second one you offered. Running 2.9.2-2475 on a Windows 2008 R2 V.Server, I still crashed on attempt 10 never fail. Windows detects the failure and gives this message:
Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc00000fd
Fault offset: 0x00065127
Faulting process id: 0x340
Faulting application start time: 0x01ceefa87fea0aea
Faulting application path: D:\ELOG\elogd.exe
Faulting module path: D:\ELOG\elogd.exe
Report Id: ceccc3da-5b9b-11e3-80f1-5ac95c924b0b
It only happens when propagate is on, I have to be missing some security setting in Windows maybe? Don't know if that helped at all, but I'm out of ideas. |
|
67659
|
Fri Jan 24 18:59:17 2014 |
| Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| Stefan Ritt wrote: |
|
| Stephen wrote: |
|
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?
|
Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?
/Stefan
|
Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.
PS. If anyone else has managed to compile this could you give me a hand =) |
|
67660
|
Wed Jan 29 17:13:55 2014 |
| Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| Stephen wrote: |
|
| Stefan Ritt wrote: |
|
| Stephen wrote: |
|
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?
|
Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?
/Stefan
|
Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.
PS. If anyone else has managed to compile this could you give me a hand =)
|
This resolved the issue, thanks for the help. I have tested it on server machines and was able to go over 10 each time.
Thank you for resolving this issue for me. |
|
2089
|
Fri Nov 24 11:01:22 2006 |
 | Stephane LE | stephane.le@synchrotron-soleil.fr | Question | All | | How to do a preset on MOptions attributes ? | Hi,
I'm new to elog and I was wondering if it is possible to do some presets on MOptions attributes when displaying a new form ? I've read the elogd config page but couldn't find how to do it.
Thanks for your help,
stephane |
|
2090
|
Fri Nov 24 14:40:42 2006 |
| Stephane LE | stephane.le@synchrotron-soleil.fr | Question | All | | Re: How to do a preset on MOptions attributes ? | easy...
Preset MyAttribute = choice1 | choice2 | choice3 |
|
167
|
Mon Nov 25 18:10:04 2002 |
| Stephan Egli | Stephan.Egli@psi.ch | Request | | | Show all common attributes | In the "find" command, when searching over all logbooks, it
would be nice to see ALL attributes, which are common for all
logbooks (e.g. typically the author name), not just
logbook name, date and text. |
|