Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 213 of 796  Not logged in ELOG logo
ID Dateup Icon Author Author Email Category OS ELOG Version Subject
  1767   Thu Mar 9 21:10:18 2006 Question Edmundo T Rodriguezedrodrig@chpnet.orgQuestionLinux2.6.1Problem submitting entries in ELOG after migrating from Windows to Linux
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!
  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.
  1769   Mon Mar 13 12:51:36 2006 Question Yoshio ImaiBug reportLinux2.6.1-1671Broken thread structure in Forum?
Hi!

I noticed that this thread seems to be broken in the Forum. When I view the thread start in single view (http://midas.psi.ch/elogs/Forum/1739), I have access to all subsequent posts, but the first reply seems to be interpreted like a new thread, i.e. when clicking onto it (http://midas.psi.ch/elogs/Forum/1741), the thread start is no longer displayed and accessible in the list of posts. Is this intentional, or is it a bug?

Yoshio
  1770   Mon Mar 13 12:57:33 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.1-1671Broken thread structure in Forum?

Yoshio Imai wrote:
I noticed that this thread seems to be broken in the Forum. When I view the thread start in single view (http://midas.psi.ch/elogs/Forum/1739), I have access to all subsequent posts, but the first reply seems to be interpreted like a new thread, i.e. when clicking onto it (http://midas.psi.ch/elogs/Forum/1741), the thread start is no longer displayed and accessible in the list of posts. Is this intentional, or is it a bug?


Some how it got screwed up, such that ID 1741 did not have a back-link to 1739. I have no clue how this could have happened, but I fixed it by manually editing the log file.
  1771   Mon Mar 13 13:19:09 2006 Reply Yoshio ImaiBug reportLinux2.6.1-1671Broken thread structure in Forum?

Stefan Ritt wrote:
I have no clue how this could have happened, but I fixed it by manually editing the log file.


I also have never come across anything like this in our logbooks (approx. 10000 entries), so it doesn't look like a bug.
  1772   Tue Mar 14 17:11:10 2006 Reply Giorgio Croci Candianig.crocic@libero.itBug report 2.6.1Re: Access to global configuration in v2.6.1
> > or maybe browser cookies. 
> 
> That rings a bell. If you change user permissions (like password file/no password file/rename logbooks) you might be
> fooled by old cookies. Just delete all cookies in your browser and try again.

Hi,
here I am at it again. Since my first posts, I tried to install the latest version of elog out-of-the-box on one pair of
PCs from scratch (fresh elog install on new, just-installed PCs, OS WinXP Pro and Win2000), but with no results. No
trace of the global configuration menu or the buttons to reach it.
Neither taking a look at the code has helped, I could not figure out exactly where the button bar was generated.
Didn't anybody other point out a similar behaviour? Do you have any suggestion for any tests to carry out?
Thanks
GiorgioCC
  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 ...
  1774   Wed Mar 15 09:28:42 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.6.1-1668Re: 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
Capture.jpg
Attachment 2: Capture.jpg
Capture.jpg
ELOG V3.1.5-fe60aaf