| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67603
|
Wed Nov 6 09:04:32 2013 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 2.9.2-2494 | Re: Compilation failure on Mac OSX 10.9 |
| A.G. Schubert wrote: |
|
When compiling elog on OSX 10.9 (Mavericks), I get the error below.
Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.
|
All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.
Best regards,
Stefan |
|
67605
|
Thu Nov 7 02:18:17 2013 |
| A.G. Schubert | alexis4@stanford.edu | Bug report | Mac OSX | 2.9.2-2494 | Re: Compilation failure on Mac OSX 10.9 |
| Stefan Ritt wrote: |
|
| A.G. Schubert wrote: |
|
When compiling elog on OSX 10.9 (Mavericks), I get the error below.
Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.
|
All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.
Best regards,
Stefan
|
Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74. I undid my changes to Makefile, tried to compile, but got the same errors.
I then pulled down elog and mxml with git, and these are working for me with no errors. Thanks! |
|
67606
|
Thu Nov 7 08:08:12 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 2.9.2-2494 | Re: Compilation failure on Mac OSX 10.9 |
| A.G. Schubert wrote: |
|
| Stefan Ritt wrote: |
|
| A.G. Schubert wrote: |
|
When compiling elog on OSX 10.9 (Mavericks), I get the error below.
Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.
|
All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.
Best regards,
Stefan
|
Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74. I undid my changes to Makefile, tried to compile, but got the same errors.
I then pulled down elog and mxml with git, and these are working for me with no errors. Thanks!
|
SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon. |
|
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
|
|
67629
|
Tue Nov 26 21:49:42 2013 |
| David Pilgram | David.Pilgram@epost.org.uk | 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 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. |
|
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. |
|
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
|
|
|