| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69719
|
Mon Jan 8 21:08:43 2024 |
 | David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | ELOG V3.1.3-a38 | Re: Maximum number of attributes | As for my suggestion earlier, now I'm at my computer with working elog. I think that the following four lines (three I guess already there but need alteration for this) need to appear in your elogd.conf file. The first three should also include any other thing you need to display etc. I've cut this down to the bear bones, and ... means anything else you want to add.
Attributes = Die, Organisation, ...
List display = Die, Organisation. ...
Thread display = $Die: $Organisation ...
Preset Die = D_#####
Now the first time you run this, it will give D_00001. You can edit that to D_00100 and it will increment from there. You may wish to have two types of user, those who can start a new thread, such as yourself, and others who can contribute but not start a new thread / new Die discussion.
Now it may be that the attribute name you gave D_001 etc can be used where I have used "Die" here, which would appear to give a seemless transition. and perhaps without the need of editing the first new thread.
I have tried these as changes to an existing logbook on my system. and they appeared to work fine. but in my case as a single user, I could always change the Die number, a feature I guess you do not want. I guess there is a way in the config file, but I'm running out of steam for today. David.
| David Pilgram wrote: |
|
Or what about the "ticket number" feature? Every new entry thread (sorry, confusing terminology on my part) would increment the ticket number by one, and there is no limit as far as I am aware. This is all explained in the elogd configuration documentation.
| Stefan Ritt wrote: |
|
Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in full text search.
Stefan
| Dr Marta Divall wrote: |
|
To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome.
| David Pilgram wrote: |
|
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes. In your case suffixes may be better, but I hope you get the point.
Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.
| Dr Marta Divall wrote: |
|
Dear Stefan,
Thansk for the super fast response! To keep the stability of the system we will look for a different solution then.
Best,
Marta
| Stefan Ritt wrote: |
|
You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.
Best,
Stefan
| Dr Marta Divall wrote: |
|
The maximum number or attributes is 100.
Is it possible to increase this?
Thanks!
|
|
|
|
|
|
|
|
|
69720
|
Thu Jan 18 13:56:59 2024 |
 | Sarah Kuckuk | sarah.kuckuk@uni-tuebingen.de | Question | All | V3.1.3-7933898 | Let the user decide which columns should be displayed | Hello
I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot of fields and it would help the usefulness of our elog a lot.
(If there is an obvious possibility that I missed I'm sorry).
Thanks a lot! |
|
69722
|
Mon Jan 22 08:22:33 2024 |
| Nicola | nicolamori@aol.com | Question | Linux | V3.1.3-7933898 | How to not expose elog port when running under a reverse proxy | I am running elog under Apache as explained in the administrator's guide. Everything works fine, butmy IT service complains about the elog port being publicly exposed, so I have to fix this. As far as I understand when running under a reverse proxy there's no need for the port to be publiuclyexposed, but I cannot find how to configure the elog server to expose it only locally |
|
69723
|
Mon Jan 22 12:15:26 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | V3.1.3-7933898 | Re: Let the user decide which columns should be displayed | There is a general display option "List display", but that applies for all users. For the download, you can load the CSV file into a spreadsheet program and then delete some columns.
Stefan
| Sarah Kuckuk wrote: |
|
Hello
I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot of fields and it would help the usefulness of our elog a lot.
(If there is an obvious possibility that I missed I'm sorry).
Thanks a lot!
|
|
|
69724
|
Mon Jan 22 20:50:50 2024 |
| Frank Heyroth | heyroth (at) cmat.uni-halle.de | Question | Linux | V3.1.3-7933898 | Re: How to not expose elog port when running under a reverse proxy | Hi,
as I understand right you can do this in the elogd.cfg via
Interface = 127.0.0.1
port = 8080
however than this can be changed by any user how has global admin rights in elog.
So I changed the line in the elogd.service startscript
ExecStart=/usr/local/sbin/elogd -D -p 8080 -n 127.0.0.1 -c /usr/local/elog/elogd.cfg
I hope this has the priority (not tested).
| Nicola wrote: |
|
I am running elog under Apache as explained in the administrator's guide. Everything works fine, butmy IT service complains about the elog port being publicly exposed, so I have to fix this. As far as I understand when running under a reverse proxy there's no need for the port to be publiuclyexposed, but I cannot find how to configure the elog server to expose it only locally
|
|
|
69727
|
Sun Feb 18 11:43:07 2024 |
| James | richo-sm@outlook.com | Question | Linux | Windows | 3.1.4 | Webserver Auth Method and Self Registration | Hi there. I have been testing a set-up of elog behind an Apache reverse proxy using the Webserver auth method. Apache has been configured for LDAPS with Active Directory allowing us to restrict Elogs by AD group, something not able to be done with the LDAP module.
Testing with Elog 3.1.4 (on Windows) and also Elog 3.1.5 (compiled on Ubuntu 20.04) I experience an issue that when the user logs in for the first time using the above they get the self registration box asking for name and email, and then once they hit save they get an error that says: "Error: Command "Config" not allowed". Once the error is dismissed it never comes back, but its confusing for users who call for help when they first see it.
Is there a way to skip the self registration with the Webserver auth method? and if not is there a reason for the error?
Attached is a copy of the error and an elog config file. Any ideas?
PS. As a side piece the logout options for Webserver needs some enhancement, maybe an option to close the web browser or tab so that it does not retain the logged in cookies. |
| Attachment 1: login-error.png
|
|
| Attachment 2: elogd.cfg
|
[global]
port = 8080
SSL = 0
Page title = Company X
Entries per page = 25
List page title = Company X
Login page title = Company X
Logbook tabs = 0
Menu commands = Back, New, Find, Download, Logout
List Menu commands = New, Find, Logout
Password file = password.pwd
Max content length = 100000
Allow password change = 0
Enable attachments = 0
Show attachments = 0
Hide attachments = 1
List after submit = 1
Logout to main = 0
Allowed encoding = 5
Default encoding = 1
Welcome title = Electronic LogBook
Summary line = 5
Summary line depth = 100
Show top groups = 0
Search all logbooks = 0
Refresh = 300
Login expiration = 0
Reply string =
Suppress default = 2
Thread display = $category entered by $author on $Entry time
Thread icon = Icon
Preset on reply author = $long_name
All display limit = 300
Start page = ?last=31
Bottom text =
Botton text login =
Resolve host names = 1
Suppress Email on edit = 3
[demo]
Theme = default
Hidden = 1
Authentication = File
Comment = General Linux Tips & Tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Logout to URL = https://intranet.xyz/
[elog]
Hidden = 1
Authentication = Webserver
LDAP register = 0
Self register = 0
Theme = default
Comment = Elog Site
Preset Author = $long_name
Locked Attributes = Author
Attributes = Category, Codes, Synopsis, Event Date, Author
Options Synopsis = Yes, No
Style Synopsis Yes = background-color:yellow
Style Medical Yes = background-color:green
Type Event Date = datetime
Preset Event Date = $datetime
Date format %A %B %d %Y %H:%M
List Display = ID, Event Date, Category, Codes, Synopsis, Date, Author
MOptions Category = Test 1, Test 2
MOptions Codes = MED, ACH
Required Attributes = Author, Event Date, Codes
Style Codes MED = background-color:green
Page Title = Company X
Reverse sort = 1
Quick filter = Date, Category, Codes
Sort Attributes = Event Date
Logfile = Elog.log
Logging level = 3
Logout to URL = https://intranet.xyz/
Bottom text =
|
|
69728
|
Tue Feb 20 11:44:30 2024 |
| scott | shiva.ps@stfc.ac.uk | Question | Linux | Other | all | ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer | Hi,
As there is no ELOG available in Epel repository for Rocky9, I tried to install ELOG from https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm and ended with the below error in Rocky 9.
=======================================
[root@test.com]# wget https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
--2024-02-20 10:11:32-- https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
Resolving elog.psi.ch (elog.psi.ch)... 192.33.120.112
Connecting to elog.psi.ch (elog.psi.ch)|192.33.120.112|:443... connected.
ERROR: The certificate of ‘elog.psi.ch’ is not trusted.
ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer.
=======================================
Could someone guide me on how to install Elog in Rocky 9 securely? |
|
69729
|
Tue Feb 20 11:49:19 2024 |
| scott | shiva.ps@stfc.ac.uk | Question | Linux | Other | all | ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer | Hi,
As there is no ELOG available in Epel repository for Rocky9, I tried to install ELOG from https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm and ended with the below error in Rocky 9.
=======================================
[root@test.com]# wget https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
--2024-02-20 10:11:32-- https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
Resolving elog.psi.ch (elog.psi.ch)... 192.33.120.112
Connecting to elog.psi.ch (elog.psi.ch)|192.33.120.112|:443... connected.
ERROR: The certificate of ‘elog.psi.ch’ is not trusted.
ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer.
=======================================
Could someone guide me on how to install Elog in Rocky 9 securely? |
|