ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 41 of 808

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6457 Entries

Goto page Previous 1, 2, 3 ... 40, 41, 42 ... 806, 807, 808 Next

ID	Date	Author	Author Email	Category	OS	ELOG Version	Subject
68502	Thu Dec 15 11:12:09 2016	stefano bonaldo	stefano.bonaldo.13@gmail.com	Bug report	Mac OSX	3.1.2	elogd crash on sorting the entries by an datetime attribute
Hello, I'm facing with a crash, which happen when I sort the entries by a datetime attribute (sort or rsort) and then i change the display mode from Full, Summary and Threaded. For example, the elogd crashes when I try to connect from the Full display to Summary in sort mode. The issue presents for example by entering with the following URL: http://host.name.com:8080/65+nm/?mode=summary&sort=Record+date Can you please help me? Here I reduced my elogd.cfg at minimum and I still get this issue: [global] port = 8080 [65 nm] Attributes = Record date Type Record date = datetime Preset Record date = $date List Display = Record date Start page = ?sort=Record date
67138	Thu Oct 27 11:29:08 2011	Andreas Luedeke	andreas.luedeke@psi.ch	Bug report	Linux	2.9.0-2414	elogd crash for special query
A query to a logbook can crash the demon. Query: https://pc8059.psi.ch:444/SwissFEL+Injector/?jcmd=Find&m0a=10&d0a=27&y0a=2011&npp=1&reverse=0 gdb dump: SSLServer listening on port 444 ... Program received signal SIGSEGV, Segmentation fault. show_elog_list (lbs=0xae72618, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:20797 20797 message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;
Attachment 1: elogd.cfg
[global] SMTP host = mail.psi.ch Language = german_UTF8 charset = UTF-8 SSL = 1 Port = 444 Authentication = Kerberos, File Password file = passwd.txt Admin user = luedeke Allow password change = 0 Self register = 0 Allowed encoding = 5 Allow HTML = 1 Suppress execute default = 0 Tab cellpadding = 2 Logfile = elog.log Date format = %a %d-%b-%Y Time format = %a %d-%b-%y %H:%M [SwissFEL Injector] Default encoding = 2 Comment = SwissFEL Injector Beam Development Guest Menu commands = New, Find, List, Login, Help Guest List Menu commands = New, Find, Login, Help Restrict edit time = 48 Admin user = luedeke, robot Login expiration = 8 Reverse sort = 1 Thumbnail size = 792> Attributes = When, Author, Entry, Status, System, Downtime, Beamtime, Coordinator, Shiftleader, Operators, Participants, Title List display = ID, When, Author, Entry, Status, System, Title Thread display = $entry time, $Author, $Entry, $Status, $System, "$Title" Quick filter = When, Entry, Status Start page = ?rsort=When Use Email Subject = ELOG $logbook: $Entry: $Title # When Type When = datetime Preset When = $date # Author #Preset Author = $long_name #Preset on reply Author = $long_name Preset on first reply Titel = Re: $Titel #Locked Attributes = Author Preset Author = $shell(if [ $short_name = "Anonym" ] ;then echo $Author;else echo \"$long_name, $Author\";fi) Preset on reply Author = $long_name # Entry Options Entry = Problem{1}, Measurement{2}, Shift-Summary{3}, Info{4}, Alarms{5} # depending on Entry, but not specific to one attribute {1,5} Show Attributes Edit = When, Author, Entry, Status, System, Title {1,5} Show Attributes = When, Author, Entry, Status, System, Title {2,4} Show Attributes Edit = When, Author, Entry, System, Title {2,4} Show Attributes = When, Author, Entry, System, Title {3} Show Attributes Edit = When, Author, Entry, Coordinator, Shiftleader, Operators, Participants, Downtime, Beamtime, Title {3} Required attributes = Coordinator, Shiftleader, Operators, Downtime, Beamtime, Title {3} Preset Title = Shift on $date {1,2,4,5} Preset Title = {1,5} Required attributes = When, Author, Entry, Status # Status {1} Options Status = open, work-in-progress, closed {1} Preset Status = open {5} Options Status = canceled, disabled, enabled {5} Preset Status = disabled # System {1,4,5} Options System = Beamdynamics, Controls, Diagnostics, Mains #{2} System = free text for measurement software, incl. version Show Attributes Edit = When, Author, Entry, Title # Downtime (only for Shift-Summary{3}) Type Downtime = numeric Comment Downtime = hours of shift not usable (waiting for repair, etc.) Format Downtime = 0, attribname, attribvalue, 8, 3 # Beamtime (only for Shift-Summary{3}) Type Beamtime = numeric Comment Beamtime = hours of shift useable for measurements Format Beamtime = 1, attribname, attribvalue, 8, 3 # Text {1,2,4,5} Preset Text = /usr/local/elog/logbooks/inc/clear.html {3} Preset Text = /usr/local/elog/logbooks/inc/FIN-summary.html
67915	Wed May 20 01:45:09 2015	Konstantin Olchanski	olchansk@triumf.ca	Bug report	Linux	3.1.0	elogd complains about unknown cookies
elogd is spewing these messages about unknown cookies: Received unknown cookie "is_returning" Received unknown cookie "__utma" Received unknown cookie "__utmz" Received unknown cookie "SSESSee3cc9c70bedf9a840203765bf409d7b" Received unknown cookie "SESSee3cc9c70bedf9a840203765bf409d7b" Received unknown cookie "MidasWikiUserID" Received unknown cookie "MidasWikiUserName" Received unknown cookie "MidasWiki_session" K.O.
68932	Tue Apr 23 14:06:36 2019	Alessio Sarti	alessio.sarti@uniroma1.it	Bug report	Mac OSX	3.1.4	elogd Service exited with abnormal code: 1
Dear all. I am running elog elogd 3.1.4 , revision ead6bbc6 on Macosx Mojave Darwin arpg-serv.ing2.uniroma1.it 18.5.0 Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64 I managed to compile and run without problems the elog source code. I can run it and have it properly displayed at boot time. After the server boot, for few hours, I have the elog ready at http://arpg-serv.ing2.uniroma1.it/elog but then, after few hours.. I get that the service stops and the elog is no longer accessible. So far I was able to track down the problems only to the /var/log/system.log file in which I find a not useful error message: Eg: Apr 23 14:00:46 arpg-serv com.apple.xpc.launchd[1] (ch.psi.elogd[85248]): Service exited with abnormal code: 1 I do not know I can I debug this nor why the code runs for few hours without problems... I just re-downloaded the code from scratch today, unloaded and then re-loaded the daemon but still it fails with the same error. I am sure that I can get it running again for few hours by re-booting. But I want to understand the source of the problem.. Anyone can be of help on this long standing issue? Thanks
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> &nbsp <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 ...
1571	Tue Jan 3 17:20:16 2006	Mike	mlmoore@pella.com	Bug report		V2.6.0	elogd 2.6.0 crash on password Forgot?
I have been having a repeatable crash on V2.6.0 everytime someone tries to recover a password using the option from the login screen. See attachment for a jpg of the message. This is occuring on windows 2003. But I have also tested it on windows XP and it occurs there as well. In addition on XP I did a generic installtion and added the password option to the DEMO application and it fails there as well. Mike
Attachment 1: elog-pw-crash.jpg

68279	Thu Mar 10 00:26:03 2016	Dave	david.levine@lmco.com	Question	Windows	2.71	elogd -m Error sending local entry: Error transmitting message
I'm running ELOG on a seperate Windows Servers. When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message" If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. Can anyone tell me why I get this error? ============================== Here is the command & output: c:\Program Files (x86)\ELOG>elogd -m Retrieving entries from "http://166.22.64.201/Equipment Log"... All entries identical Retrieving entries from "http://166.22.64.201/System Log"... Error sending local entry: Error transmitting message
Draft	Thu Mar 10 00:16:33 2016	Dave	david.levine@lmco.com	Question	Windows	2.71	elogd -m
I'm running ELOG on a seperate Windows Servers. When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message" If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. Can anyone tell me why I get this error? ============================== Here is the command & output: c:\Program Files (x86)\ELOG>elogd -m Retrieving entries from "http://166.22.64.201/Equipment Log"... All entries identical Retrieving entries from "http://166.22.64.201/System Log"... Error sending local entry: Error transmitting message

Goto page Previous 1, 2, 3 ... 40, 41, 42 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6