ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67631
|
Mon Dec 2 09:27:35 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
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've just checked that elogd can handle "Propagate Attributes" for more than 10 replies without crashing (I've attached my config, you can see if it works for you.)
Therefore it has to be something else in your configuration that causes this behaviour, or a combination of things.
Could you strip off the configuration further, that it contains the minimal content to cause elogd to crash? Or can you use a debugger on your system?
Cheers
Andreas
⇄
English (auto-detected) » English
⇄
English (auto-detected) » English
⇄
English (auto-detected) » English
⇄
English (auto-detected) » English
⇄
English (auto-detected) » English
⇄
English (auto-detected) » English
|
Attachment 1: elogd.cfg
|
[global]
port = 8080
[TestXmlImportOfDate]
Attributes = x
Type x = date
Propagate Attributes = x
|
67632
|
Mon Dec 2 09:58:42 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
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?
|
⇄
English (auto-detected) » English
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.
⇄
English (auto-detected) » English
Andreas
⇄
English (auto-detected) » English
⇄
English (auto-detected) » English
|
Attachment 1: elogd.cfg
|
[global]
SMTP host = mail.psi.ch
Authentication = File
port = 443
SSL = 1
Allow passwordchange = 1
Self Register = 0
Logfile = /usr/local/elog/elog.log
[CSM Log]
; Main settings
Password file = /usr/local/elog/elogPw.txt
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
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
|
Attachment 2: elog.png
|
|
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. |
67634
|
Tue Dec 3 11:30:43 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
Stephen wrote:
|
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.
|
Can you compile elog? Then I would suggest that you download the latest version from GIT an recompile it. You'll find help for that here: https://midas.psi.ch/elog/download.html
I have no experience with compilation on Windows (I try not to touch it, and if I have to I use a long stick ;-)
⇄
English (auto-detected) » English
|
67643
|
Fri Jan 3 21:33:40 2014 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
Andreas Luedeke wrote: |
Stephen wrote:
|
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.
|
Can you compile elog? Then I would suggest that you download the latest version from GIT an recompile it. You'll find help for that here: https://midas.psi.ch/elog/download.html
I have no experience with compilation on Windows (I try not to touch it, and if I have to I use a long stick ;-)
⇄
English (auto-detected) » English
|
I have been able to compile Elogd successfully in Windows with Visual Studio 2010 but not with Elog. Attached are errors, it complaint about buffer[i] type char * being assigned type void *. If anyone has been successful compile the elog, please give me a hint. Thanks. |
Attachment 1: error1.jpg
|
|
Attachment 2: error2.jpg
|
|
Attachment 3: error3.jpg
|
|
67644
|
Mon Jan 6 10:25:03 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
Hung Dao wrote: |
I have been able to compile Elogd successfully in Windows with Visual Studio 2010 but not with Elog. Attached are errors, it complaint about buffer[i] type char * being assigned type void *. If anyone has been successful compile the elog, please give me a hint. Thanks.
|
Just put (char *) in front of all malloc(). I will include the fix in the next official version.
/Stefan |
67645
|
Mon Jan 6 10:32:43 2014 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
Hung Dao wrote: |
Andreas Luedeke wrote: |
Stephen wrote:
|
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.
|
Can you compile elog? Then I would suggest that you download the latest version from GIT an recompile it. You'll find help for that here: https://midas.psi.ch/elog/download.html
I have no experience with compilation on Windows (I try not to touch it, and if I have to I use a long stick ;-)
⇄
English (auto-detected) » English
|
I have been able to compile Elogd successfully in Windows with Visual Studio 2010 but not with Elog. Attached are errors, it complaint about buffer[i] type char * being assigned type void *. If anyone has been successful compile the elog, please give me a hint. Thanks.
|
You don't need "elog" to run the logbook, the executable "elog" is only needed to create entries without the web interface. Stefan should adapt "elog.c" some day to be compatible with the default switches of modern, paranoid compilers; but for the moment you can ignore this.
⇄
English (auto-detected) » English
If you use the newly created "elogd", does that reproduce the former problem? |
67647
|
Sun Jan 12 04:48:12 2014 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
Andreas Luedeke wrote: |
Hung Dao wrote: |
Andreas Luedeke wrote: |
Stephen wrote:
|
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.
|
Can you compile elog? Then I would suggest that you download the latest version from GIT an recompile it. You'll find help for that here: https://midas.psi.ch/elog/download.html
I have no experience with compilation on Windows (I try not to touch it, and if I have to I use a long stick ;-)
⇄
English (auto-detected) » English
|
I have been able to compile Elogd successfully in Windows with Visual Studio 2010 but not with Elog. Attached are errors, it complaint about buffer[i] type char * being assigned type void *. If anyone has been successful compile the elog, please give me a hint. Thanks.
|
You don't need "elog" to run the logbook, the executable "elog" is only needed to create entries without the web interface. Stefan should adapt "elog.c" some day to be compatible with the default switches of modern, paranoid compilers; but for the moment you can ignore this.
⇄
English (auto-detected) » English
If you use the newly created "elogd", does that reproduce the former problem?
|
I don't see it has crashed when testing your cfg. However, one thing I must do is to comment out the alarm_handler function in order to compile the elogd successfully. Otherwise, it shows an undefined alarm, see in the 2nd attachment. Although it did not crash as tested with your cfg, I have experienced the new version sometimes crashed on our system but then it self restarted (different scenario since my cfg does not use Propagate. I have not been able to narrow down yet. |
Attachment 1: test.jpg
|
|
Attachment 2: test2.jpg
|
|
|