Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 671 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  953   Sat Feb 19 18:39:52 2005 Entry Heiko Scheith.scheit@mpi-hd.mpg.deBug fixLinux2.5.7Problem with 'Show Attributes' option
There is a problem with the 'Show Attributes' option
causing the 'Format ...' options to be ignored.

See attachment for patch.
  66711   Wed Feb 17 17:02:38 2010 Question soren poulsensoren.poulsen@cern.chBug reportLinux2.7.8-2282Problem using attribute type

Hi,

This little logbook has a problem:

------------------------

Attributes = Author, Category, Type, Subject, Number

Type Number = numeric

Options Category = General{1}
{1} Options Type = Routine

------------------------

(it was of course more complicated to start with).

When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.

To avoid the problem, I just comment out the line "Type Number ... "

 

Is this a bug ?

Thanks for your time

Soren

 

(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the  problem).

 

 

 

 

 

  65758   Tue Feb 26 03:06:06 2008 Question Uweuweho@web.deQuestionWindows2.7.3Problem updating from 2.7.2 to 2.7.3

Hello,

I am trying to update from version V2.7.2-2041  to V2.7.3 but getting the attached error message. OS is Windows 2003. I installed the update on Windows XP without a problem. Does anybody know ho to solve that problem? Thanks!

Uwe

 

  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!
  1592   Fri Jan 13 03:21:32 2006 Cool Chris Warnerchristopher_warner@dcd.uscourts.govQuestionLinux Problem selecting ports
I had problems getting elog to run on port 8080 (or many others). I have it installed on Redhat Enterprise Linux rel 4. The only way I was able to get it working was using port 80. I would like to run it on a different port if possible but I'm not sure what is wrong.

Any Ideas
  69307   Mon Feb 22 12:29:16 2021 Question Stefano Lacaprarastefano.lacaprara@pd.infn.itQuestionLinuxELOG V3.1.3-Problem in logging with LDAP and passwd
Dear experts,
   I have a logbook which has authentication as follow

Authentication = LDAP, File
Password file = PASSWD.file
LDAP server = ldaps://it-ldap-XXX.XXX.XX:1636
LDAP userbase = ou=people,ou=RGY,o=XXX,c=XX
LDAP login attribute = uid
LDAP register = 0
Self register = 0
Allow password change = 0

Some of the my user (but not all) have issue in accessing this protected elogbook.
The ldap password is correct (we checked).
What I see in the log is as follow:

22-Feb-2021 11:25:51 [XXX.YYY.ZZZ.QQ] {Beam Run} LOGIN user "USERNAME" (attempt)
22-Feb-2021 11:25:59 [XXX.YYY.ZZZ.QQ] {Beam Run} LOGIN user "USERNAME" (attempt)

The user USERNAME is present in PASSWD.file.

For other user, for which the login works, I do see an (attempt) and then (success)

we tried the standard stuff: clear cache/cookies and with different browser. We also tried to remove the user from PASSWD.file and 
create it again, but nothing has worked.

Any suggestion how I can debug this problem?

Thanks in advance,
  Stefano
  66339   Fri May 1 08:05:42 2009 Question mike ciancimike2.cianci@comcast.netQuestionWindows2.7.5-2185Problem Naming Logbooks

I have a logbook named "Centaur" (instrument name) for a problem log on an instrument and a logbook named "CentaurNewLot" for

a logbook (Database Like - ELOG format) where we would log reagent lot number changes for that instrument.

The problem is that when I name the logbooks, like I have, it screws up the formatting (List page) of the second log book.

If I rename the second logbook something totally unrelated to the first logbook my originally intended formatting returns.

  2171   Tue Mar 20 13:45:20 2007 Question Ben Shepherdbjs54'at'dl'dot'ac'dot'ukQuestionLinux2.6.2-1739Private logbook - no guest access?
Hi,

I want to set up a logbook which you have to be logged in to be able to read entries. I've already got three logbooks which can be viewed by anyone but only logged-in users can modify them. For the fourth one, I want to have a private logbook which can't be read by 'guest' users. Is this possible?

cheers

ben
ELOG V3.1.5-3fb85fa6