ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1765
|
Thu Mar 9 04:46:42 2006 |
 | Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1671 | Removing '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 |
 | Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1671 | Strange "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. |
|
1767
|
Thu Mar 9 21:10:18 2006 |
| Edmundo T Rodriguez | edrodrig@chpnet.org | Question | Linux | 2.6.1 | Problem 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 |
 | Steve Jones | steve.jones@freescale.com | Question | Linux | 2.6.1 | Re: 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 |
| Yoshio Imai | | Bug report | Linux | 2.6.1-1671 | Broken 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 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.6.1-1671 | Broken 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 |
| Yoshio Imai | | Bug report | Linux | 2.6.1-1671 | Broken 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 |
| Giorgio Croci Candiani | g.crocic@libero.it | Bug report | | 2.6.1 | Re: 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 |
|
|
ELOG V3.1.5-2eba886 |