ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1773
|
Tue Mar 14 17:51:52 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1668 | elogd 2.6.1 program Crash is repeatable under Windows | Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment. |
Attachment 1: elogd-error-1.JPG
|
|
Attachment 2: elogd-error-2.JPG
|
|
Attachment 3: elogd.cfg.new
|
[global]
####################################################################
# This [global] section contains settings common to all logbooks
# If an individual logbook setting should be the same in all
# logbooks, it can be copied into this section. If it is present
# in this section and in a logbook section, the one in the logbook
# section has precedence.
####################################################################
# Tell eLog to use tabbed UI
# Switches on (1) and off (0) logbook tabs
logbook tabs = 1
# Language can be english, french, spanish, german, dutch, brazilian
Language = english
# Limit the size of attachments to 1MB
Max content length = 1024000
# Point to the localhost as the email relay
SMTP host = 127.0.0.1
;SMTP host = mailserv2.am.freescale.net
# The builtin webserver (eLog is not using Apache) uses port 8080
port = 8080
# User and Group under which the elogd daemon is started under Unix
# Logfiles generate by the daemon are owned by this user
Usr = nobody
Grp = essadm
# URL used for the URL link in email notification and the browser.
URL = http://127.0.0.1:8080/
#---------------------------
# Access control
#---------------------------
# Allow users to register with approval from moderator (Admin). All LogBooks pull from one password file
Self register = 1
Password file = elogpasswd
Admin user = r4aajl
# To log all user login/logout activity, plus writes
Logfile = logs/elogaccess.log
Logging level = 2
; Turn logbook locking OFF
;
Use Lock = 0
###############################################################################################
# Optional Welcome Title can be customized, GIF image has to be in same directory as elogd.cfg
###############################################################################################
Welcome Title = <center><bold><font size="+3"><b>Design Technology, Engineering Compute</b></font> <font size="+2"><a href="http://elog-test.am.freescale.net/Engineering%20Compute%20Incident%20Logs/">Incident Log Facility</a> <a href="http://elog-test.am.freescale.net/Engineering%20Compute%20Change%20Logs/">Change Log Facility</a></font>
Purpose: to capture <b>Planned Changes</b> and <b>Unplanned Incidents</b> to the Engineering Infrastructure that are deemed SIGNIFICANT and/or OPERATIONAL in nature. The Logging facility is implemented per Freescale policy as documented in:
<a href= "http://twiki.freescale.net/bin/view.cgi/CUE/OperationalChangeControl">ISO17799: Operational Change Control, Sec8.1.2</a>. <a href="elogadm@freescale.com">Send questions to the eLog Admin</a></bold></center>
#---------------------------
# General options
#---------------------------
# Use the 'default' theme under the themes/ directory
Theme = default
#############################
# Some Look And Feel values
#############################
Admin textarea = 115, 24
# Lines for message entry window
Message Height = 6
# Characters per line for message entry
Message Width = 130
# Date/Time format as passed to the strftime() function and used to display the entry date
Date format = %B %d, %Y
Time format = %B %d, %Y
# Provide more menu options to the user
;
Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Move To, Help
Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
#----------------------------
# Define the major area groupings - Log type
# <site>-CL is for change logs by site
# <site>-IL is for incident logs by site
;
Top text = FreescaleBanner.html
Show top groups = 1
Top Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, ZIL05-CL, Approvals-CL, Template-CL
Top Group Engineering Compute Incident Logs = TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, ZIL05-IL, Template-IL
#Top Group zDemo = DemoChangeLog, DemoIncidentLog, DemoShutdownLog, DemoDCChangeLog
#---------------------------
# Flags
#---------------------------
# Send plain text emails
Email Encoding = 1
#
[global Engineering Compute Incident Logs]
#-------------------------------------------------------------------------------------------------------------
# Define the global attributes of the Incident Log
#-------------------------------------------------------------------------------------------------------------
Main Tab = Home Page, Global Incident Logs
Welcome Title = <bold><font size="+3"><b>Design Technology</b></font> <font size="+2"> Engineering Compute Incident Log Facility</a></font>
Pick the correct site and enter an Incident <b>that has already happened</b>. Questions to be answered are provided. <a href="elogadm@freescale.com">Send questions to the eLog Admin</a></bold>
<font size="-1"><table width="100%"><tr><td align="left" valign="top"><a href= "http://twiki.freescale.net/bin/view.cgi/CUE/OperationalChangeControl">ISO17799: Operational Change Control, Sec8.1.2</a></td><td align="right" valign="top"><a href="http://elog-test.am.freescale.net/Engineering%20Compute%20Change%20Logs/">Looking for the Change Logs?</a></td></tr></table></font>
Top text = FreescaleBanner-IL.html
Bottom text = IncidentLogFooter.html
Page Title = Engineering Compute Post Incident Logs
Quick filter = Date, Duration
Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Help
Message Height = 30
Attributes = Author, Date of Occurrance, Duration, EmailAddr, EmailNotify, Incident Coordinator, Short Summary
; Put these attributes on the same line as the preceeding attribute
;Format Date of Occurrance = 1
Format Duration = 1
;Format EmailNotify = 1
;
; The summary listing limits the displayed fields
List display = Edit, Delete, Date, Author, Incident Coordinator, Date of Occurrance, Short Summary
Summary lines = 0
Display mode = threaded
Expand default = 0
Reverse sort = 1
Thread display = "Happened on: $Date of Occurrance. $short summary. Incident Coordinator: $Incident Coordinator."
Preset Author = $long_name
Locked Attributes = Author
Type Date of Occurrance = date
Date format = %B %d, %Y
Time format = %B %d, %Y
Subst on edit short summary = UPDATE: $short summary
Subst on reply short summary = UPDATE: $short summary
Comment EmailAddr =
Tooltip EmailAddr = People to notify. Use full email addr separated w/commas.
MOptions EmailNotify = Notify Local EC, Notify ALL EC
; This attribute is used globally, so set to "nul"
Comment EmailNotify =
Tooltip EmailNotify = Select whom to notify, EC list is pre-loaded. Use 'Manual Email Addresses' for all others.
Options Incident Coordinator = ?
Tooltip Incident Coordinator = Who Responded? If it is the author, just leave blank
Extendable Options = Incident Coordinator
Options Duration = < 1 hr, 1-12 hrs, 24 hrs, 72 hrs, 1 week, 1 month, > 1 month
Tooltip Duration = Pick an Outage Duration. These coincide with BIA outage categories
Required Attributes = Date of Occurrance, Incident Coordinator, Duration, Short Summary
Preset text = IncidentLogFooter.incl
; Email Preferences
Use Email Subject = "[eLOG: $logbook]: $short summary"
Email EmailNotify "Notify Local EC" = elogadm@freescale.com
Email EmailNotify "Notify ALL EC" = elogadm@freescale.com
Email All = $EmailAddr
[global Engineering Compute Change Logs]
#-------------------------------------------------------------------------------------------------------------
# Define the global attributes of the Change Log
#-------------------------------------------------------------------------------------------------------------
Main Tab = Home Page, Global Change Logs
Welcome Title = <bold><font size="+3"><b>Design Technology</b></font> <font size="+2"> Engineering Compute Change Log Facility</a></font>
Pick the correct site and register all SIGNIFICANT Engineering Infrastructure <b>Planned Changes</b>. <a href="elogadm@freescale.com">Send questions to the eLog Admin</a></bold>
<font size="-1"><table width="100%"><tr><td align="left" valign="top"><a href= "http://twiki.freescale.net/bin/view.cgi/CUE/OperationalChangeControl">ISO17799: Operational Change Control, Sec8.1.2</a></td><td align="right" valign="top"><a href="http://elog-test.am.freescale.net/Engineering%20Compute%20Incident%20Logs/">Looking for the Incident Logs?</a></td></tr></table></font>
#####################################################################################################
#These are options that are applied to all CL LogBooks, dictate what info is needed
#########################################
# Define the attributes for all logbooks
#
Attributes = SiteBook, Author, LastRevision, Subject, PlannedDate, Significance, ApprovalRequired, ApproverName, ApproveState, FunctionalArea, Operation, Category, HardwareName, EmailNotify, Manual Email Addresses, Completed, DateCompleted
Required Attributes = Author, PlannedDate, FunctionalArea, Operation, Significance, Subject, Completed, ApprovalRequired
Top text = FreescaleBanner-CL.html
Bottom text = ChangeLogFooter.html
Page Title = Engineering Compute Change Logs
Message Height = 30
#########################################
# The message field gets pre-loaded text
Preset text = ChangeLogInclude.incl
#########################################
# Set some attributes to DATE type
#
Type PlannedDate = date
Tooltip PlannedDate = When is this change planned to occur?
Type DateCompleted = date
#########################################
# Make sure that certain log field entries are not changed later
#
Fixed Attributes Edit = SiteBook
Preset SiteBook = $logbook
Fixed Attributes Edit = Author
Preset Author = $long_name
Preset ApproverName =
Preset ApprovalState = Not Approved
Preset Completed = Open
Locked Attributes = SiteBook, Author, LastRevision, DateCompleted, ApproverName, ApproveState
#####################################################################################################
# Tell some attributes to go on the same line as the preceeding attribute
#
#### Put Author on same line as SiteBook
Format Author = 1
#### Put 'LastRevision' on the same line as 'Author'
Format LastRevision = 1
#### Put 'DateCompleted' on the same line as 'Completed'
Format DateCompleted = 1
#### Put 'ApproverName' on same line as 'ApprovalRequired'
Format ApproverName = 1
#### Put 'ApproveState' on same line as 'ApprovalRequired'
Format ApproveState = 1
#####################################################################################################
# The summary listing limits the displayed fields
List display = Edit, Delete, Author, PlannedDate, FunctionalArea, Operation, HardwareName, Subject
Summary lines = 0
Display mode = threaded
Expand default = 1
Reverse sort = 1
Quick Filter = ApprovalRequired, PlannedDate, Completed
Thread display = <b>What:</b> $subject <b>Scheduled for:</b> $PlannedDate <b>Change Status:</b>   <b>$ApproveState</b> and $Completed <b>Completed Date:</b> $DateCompleted
Entries per page = 10
#####################################################################################################
# add last revision and change subjectline on each edit/reply
Subst on edit lastrevision = REVISED: $date by $long_name
Subst on reply lastrevision = REVISED: $date by $long_name
Subst on reply subject = UPDATED: $subject
#####################################################################################################
# Start defining how the form works
##################################################
# Define FunctionalArea
#
Options FunctionalArea = NFS{1}, LDAP{2}, LoadBalancer{3}, LSF{4}, SunRay{5}, Tarantella{6}, Vital Server{7}, ClearCase{8}, CFEngine{9}, DataCenter{10}, Compute{11}, Network{12}
##################################################
# Define Operation
#
{1} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{2} Options Operation = Schema Change, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{3} Options Operation = New Service Added, Configuration Change, Maintenance, SW Installation, SW Upgrade, Patch Applied
{4} Options Operation = Schema Change, Queue Change, License Change, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{5} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Firmware Upgrade, Patch Applied
{6} Options Operation = WebTop Change, Server Added, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{7} Options Operation = New Service Added, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{8} Options Operation = New VOB, New View, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{9} Options Operation = SW Upgrade, Configuration Change, Patch Applied
{10} Options Operation = New HW Install, HW Maintenance, Power/UPS, HVAC, Network HW
{11} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{12} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
Tooltip FunctionalArea = The predefined Operations areas under which a Change may be scheduled.
Tooltip Operation = Choose FUNCTIONALAREA first
##################################################
# Define Category
#
{1} Options Category = HP, Celera, Sun, Brocade, StorageTek, EMC
{2} Options Category = Supplier, Hub, Consumer,Gateway, Client
{3} Options Category = F5, CSS
{4} Options Category = Master
{5} Options Category = SunrayServer
{6} Options Category = TTServer, DesktopServer
{7} Options Category = WWW, NIS, LISTSRV, NTP, DNS, MTA, TWIKI, ELOG, LOGGING HOST, GSH
{8} Options Category = VOB, VIEW
{9} Options Category = ?
{10} Options Category = Cisco, Netbotz, Liebert Paging
{11} Options Category = HPUX, Solaris, Linux
{12} Options Category = Cisco
Tooltip Category = Optional attribute. Please use for furthur classification.
##################################################
# Define Significance
#
MOptions Significance = Routine, Multiple User Impact, Requires EC Communication, Deviates from EC Standard
Tooltip Significance = Why is this entry being created - what is the SIGNIFICANCE of the change?
##################################################
# Define EmailNotify
#
MOptions EmailNotify = Email to EC, Email to EC Admins, Other email (please complete "Manual Email Addresses" field)
Tooltip EmailNotify = Select whom to notify, EC list is pre-loaded. Use 'Manual Email Addresses' for all others.
##################################################
... 464 more lines ...
|
1774
|
Wed Mar 15 09:28:42 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
Steve Jones wrote: | Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment. |
Steve,
again I could not reproduce your problem. See the attached screenshots. It just works fine with me (of course I miss the HTML files for the header and footer). I use however the most recent version of elog (Revision 1675). I also have a different password file. So try the following:
- look into your password file (it's a simple XML text file), it should contain something like
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
<user>
<name>stefan</name>
<password>zFDkjoZsg==</password>
<full_name>Stefan Ritt</full_name>
<email>stefan.ritt@psi.ch</email>
<last_logout>Thu Feb 23 15:35:19 2006</last_logout>
<last_activity>Wed Mar 15 09:22:02 2006</last_activity>
<email_notify>
<logbook>demo</logbook>
</email_notify>
</user>
</list>
- make sure that you have the most recent version of elogd. Try at least elog261-3.exe under Windows.
- are you sure you need top groups? Top groups are ment for groups of logbooks which are completele unrelated, like from different departments, with different admins etc. Historically top groups were implemented because some elog installations had several elogd servers running in parallel for different departments. In you case, I suspect that "normal" groups might be enough, like:
Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs = TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL
|
Attachment 1: Capture.jpg
|
|
Attachment 2: Capture.jpg
|
|
1775
|
Wed Mar 15 21:42:25 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
Steve Jones wrote: |
Stefan Ritt wrote: |
Steve Jones wrote: | Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment. |
Steve,
again I could not reproduce your problem. See the attached screenshots. It just works fine with me (of course I miss the HTML files for the header and footer). I use however the most recent version of elog (Revision 1675). I also have a different password file. So try the following:
- look into your password file (it's a simple XML text file), it should contain something like
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
<user>
<name>stefan</name>
<password>zFDkjoZsg==</password>
<full_name>Stefan Ritt</full_name>
<email>stefan.ritt@psi.ch</email>
<last_logout>Thu Feb 23 15:35:19 2006</last_logout>
<last_activity>Wed Mar 15 09:22:02 2006</last_activity>
<email_notify>
<logbook>demo</logbook>
</email_notify>
</user>
</list>
- make sure that you have the most recent version of elogd. Try at least elog261-3.exe under Windows.
- are you sure you need top groups? Top groups are ment for groups of logbooks which are completele unrelated, like from different departments, with different admins etc. Historically top groups were implemented because some elog installations had several elogd servers running in parallel for different departments. In you case, I suspect that "normal" groups might be enough, like:
Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs = TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL
|
Aacck! I thought sure that this would do it for you. Ok, to answer your last question first:
1> I am reasonably sure that I need top groups. The logbooks with the -CL extension have a common attribute structure. The logbooks with the -IL extension have a common attribute structure. Neither group is the same. Prior to using Top Group I was using a global config for the -CL's but manually maintaining consistent -IL configs was horrible. Top Group solved my problem: maintaining only two config "areas" as opposed to many is very efficient. Do you have another way of doing this other than running two instances of eLog?
2> My password file on Windows is
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
<user>
<name>r4aajl</name>
<password>TDIwYXVyZW4=</password>
<full_name>Steve Jones</full_name>
<last_logout>0</last_logout>
<last_activity>Tue Mar 14 10:35:04 2006</last_activity>
<email>steve.jones@freescale.com</email>
<email_notify>
<logbook>TX30-CL</logbook>
<logbook>TX11-CL</logbook>
<logbook>TX32-CL</logbook>
<logbook>AZ34-CL</logbook>
<logbook>AZ50-CL</logbook>
<logbook>Approvals-CL</logbook>
<logbook>FL29-CL</logbook>
<logbook>IL108-CL</logbook>
<logbook>ZIL05-CL</logbook>
<logbook>Template-CL</logbook>
</email_notify>
</user>
</list>
3> I see your screen shots. Try going in and creating a new logbook and tell me if it dies. In the meantime is the latest version available in compiled form for Windows? If so, I'll install it and try again. At this point I am looking at starting a new config file from scratch but unless you can suggest another way I think Top Group is my only option. |
1776
|
Wed Mar 15 23:46:54 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
Steve Jones wrote: |
Steve Jones wrote: |
Stefan Ritt wrote: |
Steve Jones wrote: | Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment. |
Steve,
again I could not reproduce your problem. See the attached screenshots. It just works fine with me (of course I miss the HTML files for the header and footer). I use however the most recent version of elog (Revision 1675). I also have a different password file. So try the following:
- look into your password file (it's a simple XML text file), it should contain something like
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
<user>
<name>stefan</name>
<password>zFDkjoZsg==</password>
<full_name>Stefan Ritt</full_name>
<email>stefan.ritt@psi.ch</email>
<last_logout>Thu Feb 23 15:35:19 2006</last_logout>
<last_activity>Wed Mar 15 09:22:02 2006</last_activity>
<email_notify>
<logbook>demo</logbook>
</email_notify>
</user>
</list>
- make sure that you have the most recent version of elogd. Try at least elog261-3.exe under Windows.
- are you sure you need top groups? Top groups are ment for groups of logbooks which are completele unrelated, like from different departments, with different admins etc. Historically top groups were implemented because some elog installations had several elogd servers running in parallel for different departments. In you case, I suspect that "normal" groups might be enough, like:
Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs = TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL
|
Aacck! I thought sure that this would do it for you. Ok, to answer your last question first:
1> I am reasonably sure that I need top groups. The logbooks with the -CL extension have a common attribute structure. The logbooks with the -IL extension have a common attribute structure. Neither group is the same. Prior to using Top Group I was using a global config for the -CL's but manually maintaining consistent -IL configs was horrible. Top Group solved my problem: maintaining only two config "areas" as opposed to many is very efficient. Do you have another way of doing this other than running two instances of eLog?
2> My password file on Windows is
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
<user>
<name>r4aajl</name>
<password>TDIwYXVyZW4=</password>
<full_name>Steve Jones</full_name>
<last_logout>0</last_logout>
<last_activity>Tue Mar 14 10:35:04 2006</last_activity>
<email>steve.jones@freescale.com</email>
<email_notify>
<logbook>TX30-CL</logbook>
<logbook>TX11-CL</logbook>
<logbook>TX32-CL</logbook>
<logbook>AZ34-CL</logbook>
<logbook>AZ50-CL</logbook>
<logbook>Approvals-CL</logbook>
<logbook>FL29-CL</logbook>
<logbook>IL108-CL</logbook>
<logbook>ZIL05-CL</logbook>
<logbook>Template-CL</logbook>
</email_notify>
</user>
</list>
3> I see your screen shots. Try going in and creating a new logbook and tell me if it dies. In the meantime is the latest version available in compiled form for Windows? If so, I'll install it and try again. At this point I am looking at starting a new config file from scratch but unless you can suggest another way I think Top Group is my only option. |
Ok, I completed stripped any attributes and only defined top groups. eLog no longer crashes but returns a completely invalid page with invalid links when I attempt to create a new logbook - see screenshot below. This is good as it means something in the config was causing things to blowup. I have also attached my stripped out config.
Incidently, I added another screenshot - an invalid link when I *delete* a logbook gets returned "http://localhost:8080/Test4-CL/Engineering%20Compute%20Change%20Logs/". Definitely not a correct URL.
Quote: | |
Attachment 1: elog_1.JPG
|
|
Attachment 2: elogd.cfg
|
[global]
port = 8080
Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Move To, Help
Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
Show top groups = 1
Top Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, ZIL05-CL, Approvals-CL, Template-CL, Test-CL, Test2-CL, Test3-CL, Test4-CL
Top Group Engineering Compute Incident Logs = TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, ZIL05-IL, Template-IL
[global Engineering Compute Change Logs]
Welcome Title = <bold><font size="+3"><b>Design Technology</b></font> <font size="+2"> Engineering Compute Change Log Facility</a></font>
Pick the correct site and register all SIGNIFICANT Engineering Infrastructure <b>Planned Changes</b>. <a href="elogadm@freescale.com">Send questions to the eLog Admin</a></bold>
<font size="-1"><table width="100%"><tr><td align="left" valign="top"><a href= "http://twiki.freescale.net/bin/view.cgi/CUE/OperationalChangeControl">ISO17799: Operational Change Control, Sec8.1.2</a></td><td align="right" valign="top"><a href="http://elog-test.am.freescale.net/Engineering%20Compute%20Incident%20Logs/">Looking for the Incident Logs?</a></td></tr></table></font>
[global Engineering Compute Incident Logs]
Welcome Title = <bold><font size="+3"><b>Design Technology</b></font> <font size="+2"> Engineering Compute Incident Log Facility</a></font>
Pick the correct site and enter an Incident <b>that has already happened</b>. Questions to be answered are provided. <a href="elogadm@freescale.com">Send questions to the eLog Admin</a></bold>
<font size="-1"><table width="100%"><tr><td align="left" valign="top"><a href= "http://twiki.freescale.net/bin/view.cgi/CUE/OperationalChangeControl">ISO17799: Operational Change Control, Sec8.1.2</a></td><td align="right" valign="top"><a href="http://elog-test.am.freescale.net/Engineering%20Compute%20Change%20Logs/">Looking for the Change Logs?</a></td></tr></table></font>
[TX30-IL]
Page Title = $logbook Post Incident Log - $Short Summary
[TX11-IL]
Page Title = $logbook Post Incident Log - $Short Summary
[TX32-IL]
Page Title = $logbook Post Incident Log - $Short Summary
[AZ34-IL]
Page Title = $logbook Post Incident Log - $Short Summary
[AZ50-IL]
Page Title = $logbook Post Incident Log - $Short Summary
[FL29-IL]
Page Title = $logbook Post Incident Log - $Short Summary
[IL108-IL]
Page Title = $logbook Post Incident Log - $Short Summary
[ZIL05-IL]
Page Title = $logbook Post Incident Log - $Short Summary
[Template-IL]
Hidden = 1
Page Title = $logbook Post Incident Log - $Short Summary
[TX30-CL]
Page Title = $logbook Change Log - $Subject
[TX11-CL]
Page Title = $logbook Change Log - $Subject
[TX32-CL]
Page Title = $logbook Change Log - $Subject
[AZ34-CL]
Page Title = $logbook Change Log - $Subject
[AZ50-CL]
Page Title = $logbook Change Log - $Subject
[Approvals-CL]
Page Title = Global $logbook list - $Subject
[FL29-CL]
Page Title = $logbook Change Log - $Subject
[IL108-CL]
Page Title = $logbook Change Log - $Subject
[ZIL05-CL]
Page Title = $logbook Change Log - $Subject
[Template-CL]
Hidden = 1
Page Title = $logbook Change Log - $Subject
[Test-CL]
Hidden = 1
Page Title = $logbook Change Log - $Subject
[Test2-CL]
[Test3-CL]
[Test4-CL]
|
Attachment 3: elogd_2.JPG
|
|
1777
|
Tue Mar 21 00:05:43 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
Steve Jones wrote: |
Steve Jones wrote: |
Steve Jones wrote: |
Stefan Ritt wrote: |
Steve Jones wrote: | Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment. |
Steve,
again I could not reproduce your problem. See the attached screenshots. It just works fine with me (of course I miss the HTML files for the header and footer). I use however the most recent version of elog (Revision 1675). I also have a different password file. So try the following:
- look into your password file (it's a simple XML text file), it should contain something like
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
<user>
<name>stefan</name>
<password>zFDkjoZsg==</password>
<full_name>Stefan Ritt</full_name>
<email>stefan.ritt@psi.ch</email>
<last_logout>Thu Feb 23 15:35:19 2006</last_logout>
<last_activity>Wed Mar 15 09:22:02 2006</last_activity>
<email_notify>
<logbook>demo</logbook>
</email_notify>
</user>
</list>
- make sure that you have the most recent version of elogd. Try at least elog261-3.exe under Windows.
- are you sure you need top groups? Top groups are ment for groups of logbooks which are completele unrelated, like from different departments, with different admins etc. Historically top groups were implemented because some elog installations had several elogd servers running in parallel for different departments. In you case, I suspect that "normal" groups might be enough, like:
Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs = TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL
|
Aacck! I thought sure that this would do it for you. Ok, to answer your last question first:
1> I am reasonably sure that I need top groups. The logbooks with the -CL extension have a common attribute structure. The logbooks with the -IL extension have a common attribute structure. Neither group is the same. Prior to using Top Group I was using a global config for the -CL's but manually maintaining consistent -IL configs was horrible. Top Group solved my problem: maintaining only two config "areas" as opposed to many is very efficient. Do you have another way of doing this other than running two instances of eLog?
2> My password file on Windows is
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
<user>
<name>r4aajl</name>
<password>TDIwYXVyZW4=</password>
<full_name>Steve Jones</full_name>
<last_logout>0</last_logout>
<last_activity>Tue Mar 14 10:35:04 2006</last_activity>
<email>steve.jones@freescale.com</email>
<email_notify>
<logbook>TX30-CL</logbook>
<logbook>TX11-CL</logbook>
<logbook>TX32-CL</logbook>
<logbook>AZ34-CL</logbook>
<logbook>AZ50-CL</logbook>
<logbook>Approvals-CL</logbook>
<logbook>FL29-CL</logbook>
<logbook>IL108-CL</logbook>
<logbook>ZIL05-CL</logbook>
<logbook>Template-CL</logbook>
</email_notify>
</user>
</list>
3> I see your screen shots. Try going in and creating a new logbook and tell me if it dies. In the meantime is the latest version available in compiled form for Windows? If so, I'll install it and try again. At this point I am looking at starting a new config file from scratch but unless you can suggest another way I think Top Group is my only option. |
Ok, I completed stripped any attributes and only defined top groups. eLog no longer crashes but returns a completely invalid page with invalid links when I attempt to create a new logbook - see screenshot below. This is good as it means something in the config was causing things to blowup. I have also attached my stripped out config.
Incidently, I added another screenshot - an invalid link when I *delete* a logbook gets returned "http://localhost:8080/Test4-CL/Engineering%20Compute%20Change%20Logs/". Definitely not a correct URL.
Steve Jones wrote: | BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No. |
|
1778
|
Thu Mar 23 14:49:07 2006 |
| Lars Jorgensen | lars.jorgensen@jppol.dk | Request | Linux | | Re: implement 'hide attribute' and 'sort attribute' | > > Only the sorting (of the entry mask!) is missing! :)
>
> Ok, I put that on my wish list. So once the second or third person asks for it, I will
> implement it (;-)
I'm asking! :-)
I have a few Extendable Options attributes, and it would be extremely nice if they got sorted as users put them
in. So that when you select the drop-down box, alle options are sorted.
Lars |
1779
|
Thu Mar 23 21:52:03 2006 |
| Steve Jones | steve.jones@freescale.com | Request | Linux | | Re: implement 'hide attribute' and 'sort attribute' | > > > Only the sorting (of the entry mask!) is missing! :)
> >
> > Ok, I put that on my wish list. So once the second or third person asks for it, I will
> > implement it (;-)
>
> I'm asking! :-)
>
> I have a few Extendable Options attributes, and it would be extremely nice if they got sorted as users put them
> in. So that when you select the drop-down box, alle options are sorted.
>
>
> Lars
Agreed - that would be nice |
1780
|
Fri Mar 31 22:14:38 2006 |
| Chris Warner | christopher_warner@dcd.uscourts.gov | Question | Linux | 2.61 | Anonymous vs user posts | If I have a logbook that will let both registered users Anonymous users post. I would like the author attribute to default to the value in $long_name but if the post is Anonymous display a default text string "Anonymous". Is it possible to do this? |
|
ELOG V3.1.5-2eba886 |
|
|
| |