ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 213 of 796

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Show attachments

6363 Entries

Goto page Previous 1, 2, 3 ... 212, 213, 214 ... 794, 795, 796 Next

Thu Mar 9 21:10:18 2006

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:

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

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

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

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

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.

1774

Wed Mar 15 09:28:42 2006

Re: elogd 2.6.1 program Crash is repeatable under Windows

Steve Jones wrote:

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

Goto page Previous 1, 2, 3 ... 212, 213, 214 ... 794, 795, 796 Next

ELOG V3.1.5-2eba886