>       Error: Command "config" is not allowed for user ""

Could it be related to the error messages thrown by "activate user"? see
https://elog.psi.ch/elogs/Forum/69479

K.O.

Hello Sir,

        I'v been a long time user fo Elog for about 14 years.  We use it for indexing our Zoning Board of Adjustment Meeting Minutes for Decision on Properties within the Town of Hampton.  Is it possibel to by-pass the SMTP mailer for building logins and password changes.   We are a small network where we deal wiht the customer face to face in reseting password and builing new users.  Having the user reset them selves doesn't happen and normally we just take a ticket and do the task for them. 

We are building a new user and take we have not done in 10 years.  In those ten years the decsion was made to The Town onto Office 365 E3 GCC  and remove the ole mail server.  Now I'm finding impossible to build a new user or reset a password without SMTP support.

Thank you in advance.

Hello,

I have just installed elog onto an ubuntu focal server using <sudo make install> and I am unable to create new entries.

When I access the log via a windows PC connected to the local network, I can see the demo logbook with the 1 test post, but I cannot create or edit anything.

Attempting to post throws the error:

New entry cannot be written to directory "/usr/local/elog/logbooks/demo/"

Please check that it exists and elogd has write access and disk is not full.

Please point me in the right direction to correctly set permissions and create aditional log books.

Thanks,

Dan

Hi all,

I have the same problem on Ubuntu 22.04. I have compiled from the latest tarball and copied all our logbooks from our old Ubuntu 18.04 server to a new Ubuntu 22.04. The logbooks does however not appear when I log in, so I assume ELOG doesn't have read access either?
Any hints on how to set the permissions correctly would be greatly appreciated.

Thanks,
Mikkel

Permissions are handled by the operating system and have nothing to do with elog. Make sure you run elog under an account which has write access to the desired directories. Consult Ubuntu documentation how to do that. Sometimes it's helpful to start elog interactively with the -v flag to see some verbose output. Maybe you can spot something there.

Stefan

Sometimes this can also be an SELinux issue, if you have that service running. Try "journalctl | grep denied" to see denied resources and consult the SELinux documentation on how to fix that.

I used "chown" to pass permissions from root to my deafult user, then restarted the service and now I can make posts. Thank you!