Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 125 of 806  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1013   Thu Mar 24 11:28:13 2005 Smile Stephen A. Woodsaw@jlab.orgBug reportLinux Re: Crash with Protect Selection page = 1
> > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
> 
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
> 
> - Stefan

That was fast!  I put the elogd.c from the cvs on top of 2.5.8 and now I can run
the server with Protect Selection page=1 again.

Logins work OK if the username/password is valid.  However, if I try to login
with invalid authentication, the server crashes.  If I turn off the protect
selection page, then invalid authentication does not crash elogd.

Thanks, Steve
  1015   Thu Mar 24 12:09:55 2005 Smile Stephen A. Woodsaw@jlab.orgBug reportLinux Re: Crash with Protect Selection page = 1
> > Logins work OK if the username/password is valid.  However, if I try to login
> > with invalid authentication, the server crashes.  If I turn off the protect
> > selection page, then invalid authentication does not crash elogd.
> 
> Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
> 
> I fixed that as well and committed the changes.

That seems to do the trick!  Thanks, Steve
  1098   Mon Apr 18 17:02:20 2005 Question Stephen A. Woodsaw@jlab.org Linux2.5.8-3Directories in top groups
I am trying to unify several existing logbook collections that run on
seperate servers under a single server using groups.  For a top group, under
"[global topgroupname]", I would like to redefine the resource directory or
the logbook directory so that everything except for the .cfg is at it
original location.  However, it seems like "Resource dir" and "Logbook dir"
can not be redefined in the global section for specific groups.  Is it
possible to redefine these directories for each top group, or is it feature
that could be added?

I could probably do what I want with soft-links, but redefining the resource
dir just seems to be right way to do this.  (For one thing, I would like
different favicons for each group.)
  1102   Tue Apr 19 22:43:10 2005 Question Stephen A. Woodsaw@jlab.orgQuestionLinux1.632More questions about groups
I am running 2.5.8-3 with the elogd.c 1.632.  I have attached the config
file that I am using.   I have a top group "src", with logbooks "SRC
Analysis" and "SRC Mail" in it.  These two logbooks share the same password
file.  If one logs into one, I would like them to be not have to login to
the other.  If I put the password file name under [global src], I get this
behaviour, but the logbook selection page does not show my graphic or the
locks by the logbook names (instead it has the Alt text "This logbook
requires authentication."  If I remove the password from [global src] and
put it in each logbook individually, then my logbook selection page looks
OK, but I have to log into each logbook seperately.

Stephen
Attachment 1: elogd.cfg
[global]

Top group yourfriend = Your Friend Logbook
Top group xxxxx = Xxxxx Experiments
Top group src = SRC Analysis, SRC Mail

Show top groups = 0
Logbook tabs = 1

SMTP host = mailthingy.jlab.org
Use Email from = adminguy@jlab.org
Admin user = adminguy

URL = http://webserver.jlab.org/elogs/

Logfile = elog.log
Logging level = 3

usr=cdaq
grp=c-cdaq

[global xxxxx]
Logbook tabs = 0
;Main Tab = Welcome Page
Welcome Title = <p><p> <img src="hallc.gif" > <p><font size=3 color=white><b>Welcome to the E02-109/E04-001 analysis logbook. </b><p></font>
Restrict Edit = 1
URL = http://webserver.jlab.org/elogs/
Prepend on edit = Edited: $date \n \n
Theme = hallc
Admin user = christy

[Xxxxx Experiments]
Comment = Elog for E02-109/E04-001
Attributes = Author, Type, Category, Subject
Options Type = Calibrations, Efficiencies, Run Info, Other Corrections, Elastics, Cross Sections, MonteCarlo, General
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

[global yourfriend]
Logbook tabs = 0
SMTP host = mailthingy.jlab.org
;Main Tab = Welcome Page
Restrict Edit = 1
URL = http://webserver.jlab.org/elogs/
Prepend on edit = Edited: $date \n \n
Theme = hallc
Admin user = yourfriend

[Your Friend Logbook]
Theme = hallc
password file = elogpw_GRS
Self register = 3
Login user = yourfriend
Comment = Elog for Your Friend
Attributes = Type, Category, Subject
Options Type = Calibrations, Efficiencies, Run Info, Other Corrections, Elastics, Cross Sections, MonteCarlo, General
Extendable Options = Category
Required Attributes = Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

[global src]
Welcome Title = <p><p> <img src="bigbite.gif" > <p><font size=3 color=white><b>Welcome to the E01-015 analysis logbook. </b><p></font>
Theme = src
Password file = elogpw_SRC
Self register = 3

[SRC Analysis]
Prepend on edit = Edited: $date \n \n
;Password file = elogpw_SRC
;Self register = 3

Comment = Elog for E01-015
Attributes = Author, Detector, Subject
Options Detector = HRS, BigBite, Neutron Bars
Required Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Admin user = adminguy

[SRC Mail]
;Password file = elogpw_SRC
;Self register = 3

Comment = Archive of SRC Mailing list
Attributes = Subject, From
Required attributes = Subject, From
Quick filter = Date, From
Menu commands =  Find ,Login, Logout, Help, Delete
Allow Delete = adminguy


  1104   Fri Apr 22 18:16:25 2005 Reply Stephen A. Woodsaw@jlab.orgQuestionLinux1.632Re: More questions about groups
> Thanks for reporting this bug. I fixed it in the current CVS version.
I get my Icons and Graphics in the top group now.  Thanks for fixing it.
  1823   Mon May 8 18:23:17 2006 Question Stephen A. Woodsaw@jlab.orgRequestLinux Spec file change
Could the "Copyright:" line in the elog.spec file be changed to "License:" for the next release? Without this change an RPM can't be built on FC4 (RPM 4.4.1). With the change, rpms can still be built in Enterprise linux 3 (RPM 4.2.3).
  67628   Tue Nov 26 16:24:39 2013 Warning Stephenswgallman@bpa.govBug reportWindows2.9.2Crash 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 Reply Stephenswgallman@bpa.govBug reportWindows2.9.2Re: 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.

ELOG V3.1.5-3fb85fa6