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

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

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

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.

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

Thanks for answering. Just tried your suggestion with different browsers
(firefox, chrome, brave) but the error message still appears when adding a
new user.

By the way, i justed noticed that if you click "back" followed by "cancel" you
enter the logbook as the user you just added. It seems that although elogd
throws an error, the user is added. Weird.

Since most of our users don't trust open source software, the error message
will only confuse them. So, is there any way to avoid this message from
appearing?

Perhaps a few words about our use case:
We are a german non profit organisation in disaster control. Since 2007 we use
elog as mobile mission journal in our unit. We adapted elog to run from
usb-stick, so all our first-responders have to do is to plug it into a laptop
and they are ready to go.
We also hand the adapted installation to other organisations like local fire
department or red cross units and offer them a short (2 hour) course on how to
use it. Since the windows-release is the most requested, it would be confusing
for them if an error message appears every time a new user is added.

So if you have any further ideas, I would appreciate that.

Uwe