Thanks, that fixed it...

Hi,

we're using elog to handle various logbooks. It's a great tool by the way. 
While replacing the Win32 2.7.8 Release with Release 3.1.4-2, we ran into the 
following problem.

Since elog is for internal usage only, we allow users to self-register if they 
are new. Therefore  "Self register = 1" is set in the [global]-area.

Using the Win32-Release of elog, it worked fine while using Release 2.7.8 or 
2.8.0. Starting with Release 3.x everytime you try do add a user, the following 
error occurs:

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

No matter if the user self-registers or is added by an elog-admin-user. We 
tried various 3.x Releases from 3.1.0-1 up to the latest 3.1.4-2. 
The error-message remains the same. Curious, although an error-message occurs, 
the user is added and able to use all logbooks. We also ran elogd in 
Debug-Mode (-v3), but the output didn't give a clue.

By the way using the same configuration on a linux-based installation (Debian 
and RaspiOS) self-registration works smooth. No error-message occurs.

So what could be the problem? Any suggestion is greatly appreciated.

Thanks in advance. 

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

I have been using elog for over 10 years. Suddenly my elog installation has changed (probably from a recent update. My /etc/elogd.cfg has changed to the original demo configuration. Even after changing it to my configuration from backup none of the entries for the logbooks apper even though the tabs for the logboos are ther all logbooks are empty. I have looced at the logbook files and the entries seem to be there but are not showing on the web interface. Has something changed? Is there a new location for the logbooks and other files? Is there a change from the 32-bit to the 64-bit version that will cause this. I am running CentOS 7 fully patched and updated. Will there be a CentOS 8 compatible version?

I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and logbooks to the new server.

rsync -av root@old.elog.server:/usr/local/elog /usr/local/
 

On the new server all of the 2020 entries are missing and there does not appear to be a 2020 logbook on either server but I can still access the 2020 entries on the old server. Where might they be and how do I get them over to the new server.

Old server says version is ELOG V3.1.4-unknown and new server says version is ELOG V3.1.4-966e3dd

Bothe servers a fully updated CentOS 7.

On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.

On the old server after stopping elogd i get:

/usr/sbin/elogd -v 3

Cannot open "elogd.cfg": No such file or directory

Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.

My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.

Thank-you. That is good information to have. 

What is the default if you you do not specify anything in elogd.cfg? I assume it is  /usr/local/elog otherwise it would not see the existing logbooks.

With a default Linux RPM install, where else would the logbooks be? Still looking for a 2020 directory on either server.

Bruce

Hello,

I have a quick question regarding how to display text using the "Top text" 
feature in the elogd.cfg file.  I've made an entry that looks like the 
following:

Top text = <h1>TEXT TO DISPLAY</h1>

But instead of getting just "TEXT TO DISPLAY" I get something like this:

----begin page ---
/usr/local/elog         "TEXT TO DISPLAY"

...rest of page 

----end page ---

...that is, on the far left at the top of the page in unformatted text 
is "/usr/local/elog/" prepended to the text I want do display. 

I don't know if this is a bug, or (more likely) something misconfigured in 
my setup. But any help that could be provided would be most greatful.

Thanks,

Val