Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 726 of 795  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6360 Entries 
Goto page Previous  1, 2, 3 ... 725, 726, 727 ... 793, 794, 795   Next  
ID Date Icon Author Author Emailup Category OS ELOG Version Subject
  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.
  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:
  1777   Tue Mar 21 00:05:43 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:

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:
Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment.


Steve,

again I could not reproduce your problem. See the attached screenshots. It just works fine with me (of course I miss the HTML files for the header and footer). I use however the most recent version of elog (Revision 1675). I also have a different password file. So try the following:

- look into your password file (it's a simple XML text file), it should contain something like
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
  <user>
    <name>stefan</name>
    <password>zFDkjoZsg==</password>
    <full_name>Stefan Ritt</full_name>
    <email>stefan.ritt@psi.ch</email>
    <last_logout>Thu Feb 23 15:35:19 2006</last_logout>
    <last_activity>Wed Mar 15 09:22:02 2006</last_activity>
    <email_notify>
      <logbook>demo</logbook>
    </email_notify>
  </user>
</list>

- make sure that you have the most recent version of elogd. Try at least elog261-3.exe under Windows.

- are you sure you need top groups? Top groups are ment for groups of logbooks which are completele unrelated, like from different departments, with different admins etc. Historically top groups were implemented because some elog installations had several elogd servers running in parallel for different departments. In you case, I suspect that "normal" groups might be enough, like:
Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL


Aacck! I thought sure that this would do it for you. Ok, to answer your last question first:
1> I am reasonably sure that I need top groups. The logbooks with the -CL extension have a common attribute structure. The logbooks with the -IL extension have a common attribute structure. Neither group is the same. Prior to using Top Group I was using a global config for the -CL's but manually maintaining consistent -IL configs was horrible. Top Group solved my problem: maintaining only two config "areas" as opposed to many is very efficient. Do you have another way of doing this other than running two instances of eLog?

2> My password file on Windows is
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
  <user>
    <name>r4aajl</name>
    <password>TDIwYXVyZW4=</password>
    <full_name>Steve Jones</full_name>
    <last_logout>0</last_logout>
    <last_activity>Tue Mar 14 10:35:04 2006</last_activity>
    <email>steve.jones@freescale.com</email>
    <email_notify>
      <logbook>TX30-CL</logbook>
      <logbook>TX11-CL</logbook>
      <logbook>TX32-CL</logbook>
      <logbook>AZ34-CL</logbook>
      <logbook>AZ50-CL</logbook>
      <logbook>Approvals-CL</logbook>
      <logbook>FL29-CL</logbook>
      <logbook>IL108-CL</logbook>
      <logbook>ZIL05-CL</logbook>
      <logbook>Template-CL</logbook>
    </email_notify>
  </user>
</list>

3> I see your screen shots. Try going in and creating a new logbook and tell me if it dies. In the meantime is the latest version available in compiled form for Windows? If so, I'll install it and try again. At this point I am looking at starting a new config file from scratch but unless you can suggest another way I think Top Group is my only option.


Ok, I completed stripped any attributes and only defined top groups. eLog no longer crashes but returns a completely invalid page with invalid links when I attempt to create a new logbook - see screenshot below. This is good as it means something in the config was causing things to blowup. I have also attached my stripped out config.

Incidently, I added another screenshot - an invalid link when I *delete* a logbook gets returned "http://localhost:8080/Test4-CL/Engineering%20Compute%20Change%20Logs/". Definitely not a correct URL.


Steve Jones wrote:
BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No.
Goto page Previous  1, 2, 3 ... 725, 726, 727 ... 793, 794, 795   Next  
ELOG V3.1.5-fe60aaf