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.

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

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).

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!

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

The maximum number or attributes is 100.

Is it possible to increase this?

Thanks!

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

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

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.

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. 

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

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.  

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.

Good morning,

I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.

Thank you in advance.

Leonardo

No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.

Stefan

Dear Stefan,

thanks to the answer you gave to my colleague. 

Now, attempting to follow your suggestion... If we will create several logbooks, one for each user,

1) there is a way to automatically duplicate all the entries in anoter "global" elog without loosing them and keeping them updated between the global and the individual logbooks? 

2) alternatively how I could activate a search in all these user logbooks (and only in this set of logbooks without searching in the others logbook present in the same file conf)? shall I gnereate a separated elog instance only for this set of logbooks? how to let this search to all option available only to a reduced number of "superusers" that are not "administrators?

thanks

Matteo

Keeping the global and individual logbooks in sync is not possible. So indded my proposal is a cumbersome solution in your case. We do have "restrict edit" which lets users only edit their own entries, but we do not have "restrict view". Maye some thought for a future version of elog.

Stefan

Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. Thing is I CAN send using other programs, but not with Elog. It is impertive I figure this out or have a work around.. but a 'work around' does not seem like a possible  task since all the work (forums and such) will be via my Elog server.

Thanx, John

ELOG has not change in the last years in that respect, but I know that mailer get more and more picky about encryption etc. So you probably have to convince your mailer to accept the pw as it comes from ELOG, or do not require a pw for that specific client.

Stefan

Good day. I am writing this post to ask how I can turn an elog website into a read-only version that will stay online for historical documention purposes.

I tried to search on Elog documentation but I had no success

Thank you and have a nice day

Use

Menu commands = List, Find, Help

to remove all command which let you create or edit entries (New, Reply, Edit, ...) 

Then do the same with "List menu commands = ..."

/Stefan

Hi,

I currently testing last ELOG version from git in a docker with LDAP activated (https://hub.docker.com/r/usinagaz/elog-ldap). The goal is to use it on Synology NAS server, associated with local LDAP server.

The reverse proxy is done by embedded DSM nginx, according to FDQN associated to ELOG service (elog.corp.com). In Docker, URL is set to elog.corp.com.

All is good, but when I post any enclosure in any elog post, the elogd exits and docker is automatically restarted. The browser shows an error 405 generated by nginx server.

Do you have any idea of the cause of this problem  ?

Thanks for help.

Laurent

Ok, i reply to myself as i could resolve the problem by changing the alpine Linux image to Debian light.

After debugging, the problem seems to be the compilation option used for alpine packets, which is not fully compatible when running on NAS Intel cpu.

The problem disappeared with Debian light, which should be less "aggressive" for optimization. I think the core is generated during imagemagick lib call (png, jpeg,pdf, ...).

Cheers