Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 726 of 796  Not logged in ELOG logo
ID Date Icon Author Author Emailup Category OS ELOG Version Subject
  1763   Wed Mar 8 20:19:14 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660[Segmentation Fault source identified] Verbose Output: Re: Crafted URL causes elog to coredump

Steve Jones wrote:

Steve Jones wrote:

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.


No, the above link just works fine, just click it.



Quote:
I was afraid to try Big grin . Ok, then the issue *might* be rev 1660. On my production version running 2.5.3 I get the expected "Invalid URL: <name>" box. Any suggestions on how to find out?



Steve Jones wrote:
Ok, here is what I found:



Steve Jones wrote:
Well, more data. When I have Top Groups defined and I go to create a new logbook via the eLog interface, the interface creates a URL of the form:
http://elog-test.company.com/EngineeringComputeChangeLogs/Test2/?cmd=Config

This causes eLog to crash -- so I am at a complete loss. I tried shortening the length of the top group name. It all seems to come back to the inclusion of the name of a logbook that doesn't exist yet?) although I confirmed that the eLog config file *is* updated and the logbook directory *is* created. So now I am trying to figure out how to debug this thing. Stefan, any clues?



Steve Jones wrote:

Ok, below is a capture of the eLog verbose output. eLog appears to do everything right up to whatever it is attempting to do at the last -- load the new logbook into config mode. The biggest difference that I see is the code is attempting to do:

1>
GET /ECCL/Test6/?cmd=Config HTTP/1.1

This also generates a segmentation fault:
2>
http://elog-test.company.com/ECCL/Test6?Cmd=Config

Whereas the interface issues the URL:

3>
GET http://elog-test.company.com/Test6/?cmd=Config

#1 and #2 cause a segmentation faults. #3 does not.

Does this help??

==== Return ================================
HTTP/1.1 200 Document follows
Server: ELOG HTTP 2.6.1-1671
Accept-Ranges: bytes
Expires: Thursday, 09-Mar-06 19:07:51 GMT
Connection: Keep-Alive
Keep-Alive: timeout=60, max=10
Content-Type: image/x-icon
Content-Length: 318






GET /TX30-CL/?cmd=Create+new+logbook&lbname=test4&template=&cmd=Create+new+logbook HTTP/1.1
Host: elog-test.company.com:1080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://elog-test.company.com:1080/TX30-CL/
Cookie: elmode=threaded; SITESERVER=ID=6c8b8ddc89cc07688479433b364c5b40; urem=0; unm=r4aajl; upwd=TDIwYXVyZW4=


Indexing logbook "TX30-IL" ... Found empty logbook "TX30-IL"
Indexing logbook "TX11-IL" ... Found empty logbook "TX11-IL"
Indexing logbook "TX32-IL" ... 
  ID   1, 040716a.log, ofs     0, thead, MD5=6E2FDFC052D1264222AA380DDF1878C1
  ID   2, 040716a.log, ofs   899, thead, MD5=2DA14909DFCD24EC3FADF388E0C9F7C7
  ID   3, 040812a.log, ofs     0, thead, MD5=D1B98E2B5E852BF3809EE4297B3DBA3D
  ID   4, 040824a.log, ofs     0, thead, MD5=E354BD9E899D89473D90A2E6FC32185A
  ID   5, 040827a.log, ofs     0, thead, MD5=CD519304C3B5054CD224426CBF76F83A
  ID   6, 040830a.log, ofs     0, thead, MD5=E5ACB49F9505D4A4721F07D116B08577
  ID   7, 040830a.log, ofs   548, thead, MD5=46F974CE0EEED711E22FDC4135EB1012
  ID   8, 040901a.log, ofs     0, thead, MD5=CB785F67B1F3EF8A541C95895F8ED43C
  ID   9, 040901a.log, ofs  1892, reply, MD5=65FAA0CA56828B6CF588A4C352AF84B7
  ID  10, 040910a.log, ofs     0, thead, MD5=5756F9BD237463A039FC36A089904733
  ID  11, 040915a.log, ofs     0, thead, MD5=4EAB52440A45ED05F4009EDF3A94D823
  ID  12, 040916a.log, ofs     0, thead, MD5=7C8E0F6DE412F38D2E56E6350F9532BF
  ID  13, 040916a.log, ofs   560, thead, MD5=46B0C32C42FE71A020B35D228D78CB0D
  ID  14, 040916a.log, ofs  1856, thead, MD5=8FFFF190194A526E210CA04C1621198A
  ID  15, 040927a.log, ofs     0, thead, MD5=98B992B2AD8007FAFD57C316AF9F651C
  ID  16, 041015a.log, ofs     0, thead, MD5=04D1D71581501BD91CD00214C42D72A5
  ID  17, 041108a.log, ofs     0, thead, MD5=B88733FCEA5F1DF6CA97A48CDD4415D2
  ID  18, 041207a.log, ofs     0, thead, MD5=EF8251801E33241D43998F4F16A685AA
  ID  19, 041220a.log, ofs     0, thead, MD5=6D4831B3F787D3D403CEA834D5332E3E
  ID  20, 041220a.log, ofs   845, thead, MD5=44E409286630E4CF9E4C86C39E575C2E
  ID  21, 041223a.log, ofs     0, reply, MD5=E282DA199A44B44E558757B6B306EFDE
  ID  22, 050107a.log, ofs     0, thead, MD5=F096677FA81DFA73793BEA4BFF0319F6
  ID  23, 050112a.log, ofs     0, thead, MD5=711670AF4FECE13BA446DB98C7F4A457
  ID  24, 050114a.log, ofs     0, thead, MD5=4E3FD5313294CE645D71B3D80B1073EA
  ID  25, 050117a.log, ofs     0, thead, MD5=D359C34C0AD0F9F67A5B1C9EB6427C2C
  ID  26, 050119a.log, ofs     0, thead, MD5=B9B083F9BB21C675DC23CA88C0651171
  ID  27, 050125a.log, ofs     0, thead, MD5=E98CD76BB9B0276A3281A95EABEA7288
  ID  28, 050203a.log, ofs     0, thead, MD5=7664924CDF3A33C0AC6A0A944BC0667C
  ID  29, 050223a.log, ofs     0, thead, MD5=D56D3760BDADF638CE90322B48485014
  ID  30, 050224a.log, ofs     0, thead, MD5=C51EAB967557EF89767BE38C5265DEB0
  ID  31, 050302a.log, ofs     0, thead, MD5=74E39EDB807510564EF4607BFF75C637
  ID  32, 050307a.log, ofs     0, thead, MD5=030B29888BCDC72CC877C33A2CBE8D7A
  ID  33, 050309a.log, ofs     0, thead, MD5=2CE00D7C075915210A5CC76C0489B477
  ID  34, 050310a.log, ofs     0, reply, MD5=0F8156FDCA1AD4F592ABEDC4AB3D20FE
  ID  35, 050401a.log, ofs     0, thead, MD5=581E6FA67DD9A32D0A44679DB03120CF
  ID  36, 050412a.log, ofs     0, thead, MD5=20ED554D75D05D0050319B069D3D758A
  ID  37, 050412a.log, ofs   799, reply, MD5=24A7ABD8C57FD13623E0018A8945DDDA
  ID  38, 050511a.log, ofs     0, thead, MD5=B92569DB76E44D354F3BADABE24C7F12
  ID  39, 050512a.log, ofs     0, thead, MD5=883461D019D1CFD0FA59DB017B17EF51
  ID  40, 050512a.log, ofs   481, thead, MD5=0A1765D83A97EDFCDB56258ABD8D0B76
  ID  41, 050512a.log, ofs  1580, thead, MD5=770303806E53660BB4334DA068EB4B3F
  ID  42, 050512a.log, ofs  2554, thead, MD5=24DD8C0F033ACC63B13386400B8BEF68
  ID  43, 050516a.log, ofs     0, thead, MD5=14B39EEAC23A3887582160E8A0F3FA02
  ID  44, 050517a.log, ofs     0, thead, MD5=954542ADDFA15303818BBFD9DA8D024F
  ID  45, 050517a.log, ofs   753, reply, MD5=B3D6BAECCD32470F8DD62A5DC31386A0
  ID  46, 050518a.log, ofs     0, reply, MD5=A86D57D87BC921B3A93D8248E76FDAE0
  ID  47, 050519a.log, ofs     0, thead, MD5=8276962204EE9A9178F53A4394B30582
  ID  48, 050524a.log, ofs     0, reply, MD5=E91633AE3B589E71BC746B21328ED2EB
  ID  49, 050617a.log, ofs     0, thead, MD5=E88998C375BE59A2F83139508BA23F14
  ID  50, 050712a.log, ofs     0, thead, MD5=79472FBFA452415B0EE46BFF609E3E71
  ID  51, 050718a.log, ofs     0, thead, MD5=D2B1760AAA84B9EF182AC9060EB4EF8D
  ID  52, 050803a.log, ofs     0, thead, MD5=8324112BB00FF3B780BBD477374CFFAB
  ID  53, 050803a.log, ofs   518, thead, MD5=BF43D5CEC1A2807A3B7A1C299536A0B2
  ID  54, 050803a.log, ofs   910, thead, MD5=92C4C73A66DB13FD76F9C0701CB38CCC
  ID  55, 050803a.log, ofs  1313, reply, MD5=78371758834EEF581F0CE8E8E86C079C
  ID  56, 050818a.log, ofs     0, thead, MD5=640E8D209B00DD8C4C40124C0DF84967
  ID  57, 050829a.log, ofs     0, thead, MD5=877B7BE835893E7D3FA7BDA50B551DD3
  ID  58, 050916a.log, ofs     0, thead, MD5=78682559B5F8EB1E6172311E02E44087
  ID  59, 050916a.log, ofs   904, thead, MD5=CE6F9A63104C1A3D85E37CF223EFF54D
  ID  60, 051029a.log, ofs     0, thead, MD5=3CEF5E7E47D465436042F3C54AA8B07E
  ID  61, 051128a.log, ofs     0, thead, MD5=A87CD1D9177FF1AE6088C21B41C4CDD2
  ID  62, 051129a.log, ofs     0, reply, MD5=B873F83F0C38A22B924FAAED7FE96804
  ID  63, 051212a.log, ofs     0, thead, MD5=344A55E1C431368E65A0E888229B1A83
  ID  64, 060202a.log, ofs     0, thead, MD5=52C0A072C25FC151C55F59CD5267B699
After sort:
  ID   1, 040716a.log, ofs     0
  ID   2, 040716a.log, ofs   899
  ID   3, 040812a.log, ofs     0
  ID   4, 040824a.log, ofs     0
  ID   5, 040827a.log, ofs     0
  ID   6, 040830a.log, ofs     0
  ID   7, 040830a.log, ofs   548
  ID   8, 040901a.log, ofs     0
  ID   9, 040901a.log, ofs  1892
  ID  10, 040910a.log, ofs     0
  ID  11, 040915a.log, ofs     0
  ID  12, 040916a.log, ofs     0
  ID  13, 040916a.log, ofs   560
  ID  14, 040916a.log, ofs  1856
  ID  15, 040927a.log, ofs     0
  ID  16, 041015a.log, ofs     0
  ID  17, 041108a.log, ofs     0
  ID  18, 041207a.log, ofs     0
  ID  19, 041220a.log, ofs     0
  ID  20, 041220a.log, ofs   845
  ID  21, 041223a.log, ofs     0
  ID  22, 050107a.log, ofs     0
  ID  23, 050112a.log, ofs     0
  ID  24, 050114a.log, ofs     0
  ID  25, 050117a.log, ofs     0
  ID  26, 050119a.log, ofs     0
  ID  27, 050125a.log, ofs     0
  ID  28, 050203a.log, ofs     0
  ID  29, 050223a.log, ofs     0
  ID  30, 050224a.log, ofs     0
  ID  31, 050302a.log, ofs     0
  ID  32, 050307a.log, ofs     0
  ID  33, 050309a.log, ofs     0
  ID  34, 050310a.log, ofs     0
  ID  35, 050401a.log, ofs     0
  ID  36, 050412a.log, ofs     0
  ID  37, 050412a.log, ofs   799
  ID  38, 050511a.log, ofs     0
  ID  39, 050512a.log, ofs     0
  ID  40, 050512a.log, ofs   481
  ID  41, 050512a.log, ofs  1580
  ID  42, 050512a.log, ofs  2554
  ID  43, 050516a.log, ofs     0
  ID  44, 050517a.log, ofs     0
  ID  45, 050517a.log, ofs   753
  ID  46, 050518a.log, ofs     0
  ID  47, 050519a.log, ofs     0
  ID  48, 050524a.log, ofs     0
  ID  49, 050617a.log, ofs     0
  ID  50, 050712a.log, ofs     0
  ID  51, 050718a.log, ofs     0
  ID  52, 050803a.log, ofs     0
  ID  53, 050803a.log, ofs   518
  ID  54, 050803a.log, ofs   910
  ID  55, 050803a.log, ofs  1313
  ID  56, 050818a.log, ofs     0
  ID  57, 050829a.log, ofs     0
  ID  58, 050916a.log, ofs     0
  ID  59, 050916a.log, ofs   904
  ID  60, 051029a.log, ofs     0
  ID  61, 051128a.log, ofs     0
  ID  62, 051129a.log, ofs     0
  ID  63, 051212a.log, ofs     0
  ID  64, 060202a.log, ofs     0
ok
Indexing logbook "AZ34-IL" ... Found empty logbook "AZ34-IL"
Indexing logbook "AZ50-IL" ... 
  ID   1, 040701a.log, ofs     0, thead, MD5=7FCEAF2572A38C0C115F4A00F1407BFA
After sort:
  ID   1, 040701a.log, ofs     0
ok
Indexing logbook "TX30-CL" ... 
  ID   1, 040604a.log, ofs     0, thead, MD5=BAC61554477BD5390A73F2974545C0A5
  ID   2, 040722a.log, ofs     0, thead, MD5=0829BF09B2B9B5BACC42329EAB14B25E
After sort:
  ID   1, 040604a.log, ofs     0
  ID   2, 040722a.log, ofs     0
ok
Indexing logbook "TX11-CL" ... Found empty logbook "TX11-CL"
Indexing logbook "TX32-CL" ... 
  ID 201, 060303a.log, ofs     0, thead, MD5=CC9C0C4FA6BFF7EEB368BA7CCE126629
After sort:
  ID 201, 060303a.log, ofs     0
ok
Indexing logbook "AZ34-CL" ... Found empty logbook "AZ34-CL"
Indexing logbook "AZ50-CL" ... Found empty logbook "AZ50-CL"
Indexing logbook "Approvals" ... Found empty logbook "Approvals"
Indexing logbook "Test" ... Found empty logbook "Test"
Indexing logbook "Test2" ... Found empty logbook "Test2"
Indexing logbook "Test3" ... Found empty logbook "Test3"
Created directory "test4"
Indexing logbook "test4" ... Found empty logbook "test4"
==== Return ================================
HTTP/1.1 302 Found
Server: ELOG HTTP 2.6.1-1671
Connection: Keep-Alive
Keep-Alive: timeout=60, max=10
Location: http://elog-test.company.com:1080/ECCL/test4/?cmd=Config
Content-Length: 20



<html>redir</html>


GET /ECCL/Test6/?cmd=Config HTTP/1.1
Host: elog-test.am.freescale.net:1080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://elog-test.company.com:1080/TX30-CL/
Cookie: SITESERVER=ID=6c8b8ddc89cc07688479433b364c5b40; urem=0; unm=r4aajl; upwd=TDIwYXVyZW4=


Segmentation fault
  1764   Wed Mar 8 22:33:56 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1671OPTION <attribute> not working right in [ global <name>] Top Group
I've verified that when the following is part of the definition of a [logbook] OR is part of a regular [global] config:
Options Completed = Open{a}, Closed{b}
{a} Preset CompletedDate = 
{b} Preset CompletedDate = $date

. . . the intended function (when option "Open" is selected the attribute "CompletedDate" is cleared; when the option "Closed" is selected the attribute "CompletedDate" is filled with the current date)

When this same code is moved to a [global <name>] config the function no longer works (the attribute "CompletedDate" is not set).

This for me is a show stopper as using Top Group has allowed me to create and use logbooks in a way that I could not under the old way (single [global]. I have verified that the same thing happens under 2.5.9.
  1765   Thu Mar 9 04:46:42 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1671Removing 'New' from "List Menu commands" prevents saving elogd.cfg
Strange as it mmay seem, when I attempt to remove the "New" menu item from "List Menu commands" in a logbook section, I am no longer able to Save the config file -- I am presented with a message saying "Error: Command "Save" not allowed". I have to manually edit the file, add that menu item back in, and then all is ok. This is on the system where I am using 'Top Groups', so the logbook is a part of one of the top groups.
  1766   Thu Mar 9 06:04:46 2006 Question Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1671Strange "bug?" report - disappearing data when attribute is "Locked"

Steve Jones wrote:
I have come across an issue where an attribute value is "blanked" upon either editing or replying. The interesting thing is this is a logbook entry that was "Moved" from one logbook to another, all under the same Top Group. All configs are done under the [global <topgroup>] so the attribute is not being reset on purpose. Most interesting of all is this only happens:

  • if the attribute is "locked" (the logbook being moved "To" locks most attributes)
  • if the attribute is of type "date"
  • if the logbook entry had been "moved" from another logbook


If the logbook entry is subsequently moved back, all works as it should - even the locked date attributes.
temporary workaround is to "unlock" the date attributes - which really messes with things if people decide to change the dates.
  1768   Fri Mar 10 06:12:55 2006 Reply Steve Jonessteve.jones@freescale.comQuestionLinux2.6.1Re: Problem submitting entries in ELOG after migrating from Windows to Linux

Edmundo T Rodriguez wrote:
I was able to install ELOG v2.61. in a Compaq ProLiant DL360 running with SUSE Linux v10
The migration/implementation went quiet well ...

ELOG v2.6.1 application came up find!.
I can login with No problems.
I can see previous logs entries, sort, etc.

But, I can NOT create any new-log (new entries) in any logbook. I get this message:
-----------------------------------------------------------------------------------
New entry cannot be written to directory
"/eLOGv261/logbooks/Administration/"

Please check that it exists and elogd has write access and disk is not full
Please use your browser's back button to go back
-----------------------------------------------------------------------------------
The previous logbooks where in ...

\Program Files\ELOG\logbooks\Administration
\MainFrame
\Unix
\OpenVMS
\RDBMS


New logbooks are in the following place ...

/eLOGv261/logbooks/Administration
/MainFrame
/Unix
/OpenVMS
/RDBMS


How can it read old log entries and I NOT create new ones?
I am sure I missing something. Can I know what?

Also, It will be good to have an entry in the ELOG web-site
explaining any migration steps from Window to Linux and reverse!

Please, help.
Thank you!




Steve Jones wrote:
The first place to look is at the permissions set on the existing directories and .log files plus the Owner and Group. (Not knowing how the files got from Windows to Linux is a little problematic but the translation of permissions is not straightforward.) Compare the settings with how you have eLog starting up on your linux box. Typically, when run as a daemon, it starts as ROOT then becomes the USER/GROUP that you specify in the .cfg file. It is likely that you will find a permission mismatch. As to why you can read but not write, with a permission mask of 744 and .log files owned by root but elogd running as nobody, you would be able to read the logs but not change them. Sounds like the permissions are similar on the directories as well. Perhaps you could post the info back here.
  1773   Tue Mar 14 17:51:52 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1668elogd 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
elogd-error-1.JPG
Attachment 2: elogd-error-2.JPG
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 &nbsp;&nbsp;&nbsp; <b>Scheduled for:</b> $PlannedDate &nbsp;&nbsp;&nbsp; <b>Change Status:</b> &nbsp <b>$ApproveState</b> and&nbsp;$Completed &nbsp;&nbsp;&nbsp; <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 ...
  1775   Wed Mar 15 21:42:25 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1668Re: 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 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1668Re: 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
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
elogd_2.JPG
ELOG V3.1.5-fe60aaf