Hi guys,

we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:

Authentication = Kerberos, File
Kerberos Realm = TEST.COM
Password file = ./pwd.xml

Even if the kinit comand is retrieving correctly a ticket for the user tsearch@TEST.COM(we see it using klist and tcpdump on lo interface), elogd kerberos authentication is not working.

We tried using tcpdump for troubleshooting but no traffic is generated on the loopback interface.

Did someone solve this problem or do you have an idea on how to make the kerberos authentication working?

Thanks

Hi,

we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.

When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.

Regards,
Oliver

We recently tried upgrading the ND280 elog instance to elog 3.1.0. [1] We seem to have some problems with this 'auto-save' functionality.  Specifically, it doesn't seem to play nice with the fact that we prefer to disable user's ability to edit old messages.  So we have (up to now), had the following set of commands specified in elogd.ccfg

Menu commands = List, New, Reply, Delete, Duplicate, Copy to, Move to, Find, Help

The problem is that we now get auto-saved messages, but no ability for the user to actually go back and finish the draft message.  You can see an example of this state in this test elog

http://neut17.triumf.ca:8080/demo/

Clicking on the draft message you can see that it can't be editted.  If you try to click 'new' then edit the draft, you get the message 'Error: Command "Edit" not allowed'.  So we had zombie draft messages, until we added the edit command back; but that defeats our preference that users not mess up old messages.

In general this auto-saving seems like a useful feature.  So the ideal solution for me would be to have some mode where users could edit/finish draft messages, but where we could still disable users from editting completed/finished messages.  Ie, where we can omit 'Edit' from the menu command, but still get auto-save.

A less ideal, but perhaps simpler solution would be that if an elog has omitted 'Edit' from the menu commands, then this auto-save/save functionality is disabled so that we don't get uneditable draft messages.

[1] https://midas.psi.ch/elogs/Forum/67855

Hi there,

our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?

Many thanks Mario

I have Split Elog to Two Top Group [Check the Config Below].

Problem = 

After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.

[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1

Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing

[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01

[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01

How do I enable SSL with port 443 in version ELOG V2.7.8-2294 and rename from localhost?

Server is running Windows 2008

We got http://servername:8080 to work and on the network just fine..

but everytime we try to change the port to 443 in global we cant get anything with https:// working 

port = 443

ssl = 1

url = https://servername

how do you customize the elog.exe or elogd for windows enviorment to listen on port 443 with specific hostname. please give an example.

Thanks...

Hi!

Tryed windows an linux version. On booth the "Register new User" dialog is not displaying a password line.
so what password is used for the new user? Further the user can't change his password, because he didn't know the old one.

And if an admin user trys to change the password of an other user, a error is displyed that the old password of the admin user is
wrong and nothing happens with the password of the non-admin user.

elog console (admin user awrzkrz changes the password of testuser1):

GET /demo/?cmd=Config&config=TestUser1&cfgpage=1&admin=1&cfg_user=TestUser1&active=1&new_user_name=TestUser1&new_full_name=TEST+User&new_user_email=test%40heaven.org&cmd=Change+password HTTP/1.1
Returned 1032 bytes
GET /demo/?config=TestUser1&newpwd=test1234&newpwd2=test1234 HTTP/1.1
Returned 20 bytes
GET /demo/?cmd=Change%20password&config=awrzkrz&fail=1 HTTP/1.1
Returned 1215 bytes
 

Thanks for help!

I recently ported an elog over to a new server running Ubuntu 20.10. Everything is working okay, except sometimes I get a strange unformatted appearance when I go to the elog page (see attachment). The happening of this seems random. For example, yesterday, when I started the elogd daemon everything looked fine, but when I log in today I get the unformatted appearance. Also, yesterday when I was setting things up, sometimes certain logbooks would have the formatting issue, and I could make this go away with a kill...restart cycle of elogd.

I downloaded the source code from here: https://elog.psi.ch/elog/download.html, selecting the elog-latest.tar.gz file.

I have tried viewing the elog on 3 different browsers (firefox, IE, Edge), result is the same every time.

Any thoughts about what the problem is?