I'm having some confusion with configuring my logbook.  In the global section of the logbook I have the quick filter enabled, but it is not a drop down list, only an editable text field:

I think it is an attributes issue, but I'm having some trouble making sense of those from the syntax page.  Here is my config file:

[global]

port = 8080

usr = vulcanstaff

Max content length = 1073741824

Menu commands = New, Edit, Delete, Reply, Find, Last day, Move to, Copy to, Import, Help

RSS Title = $subject, posted by $author on $entry time

RSS Entries = 10

Quick filter = Date, Subject, Subtext

Use Lock = 1

Reverse sort = 1

Required Attributes = Author, Subject

[Experiment_Logbook]

Theme = default

Comment = Experiment Logbook

Attributes = Author, Author Email, Type, Category, Subject

Options Type =  Other

Options Category = Start Up

Extendable Options =Category

Page Title = $Subject

You get a drop-down list if you define several options for an attribut, like

Options Category = Start Up, Start Down, Other

The you can select one of the categories from the drop-down list.

I forgot to mention - this is for searching the logbook.   So would the config file look more like this:

[global]

port = 8080

usr = vulcanstaff

Max content length = 1073741824

Menu commands = New, Edit, Delete, Reply, Find, Last day, Move to, Copy to, Import, Help

RSS Title = $subject, posted by $author on $entry time

RSS Entries = 10

Options Category = Date, Subject, Subtext

Quick filter = Date, Subject, Subtext

Use Lock = 1

Reverse sort = 1

Required Attributes = Author, Subject

I know that this is for searching. But you don't get the point. You have attributes, like Date, Category, Subject. Each attribute can either contain arbitrary text (like the subject), or one of a set of predefined values. So category can be, let's day, "one", "two", "three". You define the possible options of the category with

Options Category = one, two, three

If you then define the quick filter

Quick filter = Category

then you get for the category a drop-down box where you can select "one", "two" or "three". If you do so, elog shows all logbook entries where the category attribute has the selected value.

I hope that this is clearer now. 

Thanks Stefan, I think I understand, and now I see the options definition on the syntax page.  I apologize for taking up your time and thank you for the great software.  I think this is right now:

Options Search = Date, Subject, Subtext

Quick filter = Search

No this is not right. Better read the manual carefully, then come back here again. 

Hello,

I'm not able to authenticate to a logbook using my text based browser links, so I've started investigating with wget hoping solving the problem one will lead to a solution for the other.  I've seen some examples on how to use wget to parse logbook entries in this forum, but my attempts keep returning the login page.  Any advice would be helpful and appreciated.  Here are a couple of the command line arguments I've tried:

wget --save-cookies cookie.txt --keep-session-cookies -d "http://hostname/LOGBOOK?unamee=YYY&upassword=XXX" -O elog.txt

wget --save-cookies cookie.txt --keep-session-cookies -d --post-data="redit=&uname=YYY&upassword=XXX&remember=1" -e robots=off "http://hostname/LOGBOOK" -O elog.txt

After these executions, my cookies.txt file remains empty.  Running subsequent command with "--load-cookies=cookies.txt" still points me to the login page.

Many Thanks,

Chris 

I've just checked that 'wget --no-check-certificate --save-cookies cookie.txt --keep-session-cookies -d "https://elog-gfa.psi.ch/SLS?uname=uuu&upassword=ppp" -O elog.txt'

created a file cookie.txt. The file contains three lines of data if uname and upassword are a valid login, and it is empty (beside of three comment lines) if they are not a valid login (wrong user or wrong password).

Could it be related to the set-up of your particular logbook?

In a configuration with elog running (8080) under Apache (80) [as explained in admin guide], what is the syntax for tunnelling in with ssh, of both the ssh command and the browser locator?

Maybe some more information will help with the question.  Here's the results of my playing around with URL = /host.domain/subdir in elog.cfg.  Commented out, I can access locally with http://localhost:8080 and tunnelled (1234:host.domain:8080) with http://localhost:1234, with and without Apache (i.e., Apache is bypassed?).  URL = /host.domain/elog in elog.cfg works locally with browser locator localhost:8080 (of course), localhost/elog, and host.domain/elog, but the tunnel directly to 8080 no longer works, nor does http://localhost:4321/elog (even though this ends up showing the same URL on the remote browser as on the local browser) (4321:host.domain:80).  http://localhost:4321 brings up the Apache window.  Every other URL assignment I tried failed both locally and remotely, so, I assume the ssh tunnel directive is wrong, or the browser locator, or maybe still URL = .  Anyway, my question is, what am I doing wrong?

Is there a limit on the number of conditions that can be simultaneously active in a log?  When I activate more than 10 conditions I start to see side effects with other conditions being deactivated.  I think this is due to the hard-coded array size of 10 for clist in the match_param function in elogd.c.  If so, could this limit be increased?  

Are there other limits on the number of conditions, or the length of condition names?  If I've understood the code right, the _condition string holds a comma-separated list of the active conditions, so the 256 byte length of this will also put some limit on the number of conditions that can be active.

Ups. I never imagined that someone would use more than 10 conditions. I'm not 100% sure if the problem is the clist array, but can you try to set it to 20 and see if it gets better? You can also send me your config file and I can try it myself. 

I'll try increasing the list size(s), and will also prepare a simplified config file for you to look at.  Maybe there is a another way to implement what I am trying to achieve?  

In general terms I am trying to give an e-log a "memory" of what has been recorded previously in order to constrain what is permissible to record next.  I do this by starting a log with an initial entry, then alter the config so that users can add records only by duplicating the last record.  The log records the current state of some variables, and allows users to record changes to the state of any of these variables. Conditions are used to constrain the permitted state changes, depending on the current state; conditions are also used, with subst options, to update the current state variables when changes are made.

Specifically, we have "Mate-Demate" logs for connectors to record when connectors are mated and demated.  Previously we just had an attribute for each connector in an assembly with options "Mate", "Demate" and "-" to indicate that either a mate or demate was carried out or that the connector was not touched on this occasion (although others were).  My cunning plan was to ensure that a "Demate" (or no-op) was possible only if the connector is currently mated, and conversely that a "Mate" (or no-op) was possible only if the connector is currently demated.  For each connector (e.g. ConnectorA), there are now two attributes

• "ConnectorA state", to record the current state, and
• "ConnectorA" to record any change.

A new record can be created only by duplicating the last record, thus copying the current state of the connectors, and for each connector the relevant config file entries are like this:

Show Attributes = ConnectorA
Show Attributes Edit = ConnectorA state, ConnectorA
Locked Attributes = ConnectorA state
Preset on duplicate ConnectorA = -
Options ConnectorA state = Mate{1}, Demate{2}
{2} Options ConnectorA = -, Mate{3}
{1} Options ConnectorA = -, Demate{3}
{3} Subst ConnectorA state = $ConnectorA

Hello,

we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg

[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1

So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.

The file is not saved. If I remove the 3 lines the logbook opens without any problems.

I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.

Would you please help solving the File password problem?

Best Regards

Michael

Just two hints:

• The file mentioned as "Password file" should be writeable for the "elogd" process. It is needed for both, Kerberos and File authentication. Better not specify the full path, it should assume the file in the logbook directory.
• The command "Self Authentication = 1" does not exist. Maybe you mean "Self register = 1"?

Thank you for the answer, but it didn't solve the problem.

• I used Self Register instead of Self Authentication. I deleted the complete path and only used the Filename.

• The Account which is used to start the Elogd process is local system. System has full right at the logbook directory

 Should I use an Admin Account for the elogd process? The error message is always the same (page not reachable) The File is also not created in the logbook dir.

I once had problems with the local system account, so I used my own account to start the service and that worked. For trial, you can also start the elogd.exe program manually (not as a service) in a DOS box and see if it can create the password file. 

 That worked for me. Used an Account instead of local system and everything is OK. Thanks for your help.

Hi,

I have logbook A and logbook B.  Is it possible to move one type of entries in logbook A to logbook B?  If yes, may I know how you do it?  Thank you.

Ze

•  You can add the "Move to = B" command in logbook A.
• Then you add "select" in "List Menu commands = ..., select, ...".
• Now you "Find" all entries of the type you want (for convenience choose "Display 9999 entries per page").
• You press "toggle all" and then "Move to B"

Hi All,

I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?

Regards,

Per

I solved it.
I don't really know if I really needed to compile it but I complied this on the NAS itself so now it is 100% compatible (I believe)

Per

 I managed to package Elog v2.92 build 2462 into and QNAP installer QPKG package.

This is for x86 based QNAP NAS only.

Note: You must have adduser package installed prior to installation.
Login to the NAS with SSH and type:
apt-get update
apt-get install adduser

BR,

Per

If I have a couple of attachments in a log book entry, I can link to that entry "http://example.edu/elog/Sandbox/7", I get the appropriate log in page, and after logging it, it takes me to the entry.

However, if I link directly an attachment, "http://example.edu/elog/Sandbox/7/1", I receive a plain log in page that doesn't have the stylesheet applied, and logging in, I am directed to " http://example.edu/elog/Sandbox/7/" which throws an invalid error. If I am already logged in the browser, it links correctly. 

I assume the problem must stem from messed up relative URL somewhere, hence the lack of stylesheet, or from the redirect incorrectly handling the /. (Looking at the source for the two login pages, the only difference is "<input type=hidden name=redir value="7">" versus "<input type=hidden name=redir value="7/1">". ) But that reaches the end of my ability...

This breaks the attachment links in emails.

Any help would be much appreciated!