Dear all

I installed elog from the current stable repository on Debian 8 (jessie)

The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.

Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path) 

Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks

And I created a new logbook.

After restarting the elog service the second database is correctly created but both of them are still stored in  /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.

How can I specify the custom folder so that the new logbooks are written there?

Dear all

I installed elog from the current stable repository on Debian 8 (jessie)

The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.

Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path) 

Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks

And I created a new logbook.

After restarting the elog service the second database is correctly created but both of them are still stored in  /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.

How can I specify the custom folder so that the new logbooks a

We do run ELOG on a Linux server and see about weekly crashes, too. It seems to be connected to the authentication process (Kerberos, File), but we could not nail it down yet.

But we have set up a supervision process that checks every minute if the "elogd" process is still running. If not, it simply restarts it.

If ELOG is down for two minutes a week, this is fine for our users.

We have always had issues with eLOG crashing intermittently...  I upgraded from Server 2003 to Server 2008 about a year ago to try to reduce the issues...  which really didn't help.

The service now seems to crash every week...  (getting worse)...  Is anyone seeing these issues in Windows servers?  Any suggestions??

The elog client binary does not work with webserver authentication.  One fix would be to support both webserver and kerberos authentication (authentication = webserver, kerberos), similar to how you currently support 
"authentication = kerberos, file".

A more general discussion of the elog client binary with webserver authentication can be found at https://midas.psi.ch/elogs/Forum/68318 .

Many thanks,
Devin

Is it possible to submit entries using the elog client binary when the server is configured with webserver authentication (when the server requires the X-Forwarded-User header)?  One option would be if the server could support both webserver and kerberos (or even file) authentication, but neither 
"Authentication = Webserver, Kerberos" nor "Authentication = Webserver, File" seem to work.

In addition to using the elog binary to talk to the elog server directly, we've unsuccessfully tried using curl to post data to the apache server url (URL in elogd.cfg).  We can read entries using curl, but haven't yet been able to submit entries.

Any help would be greatly appreciated.

Many thanks,
Devin

I'm not sure I understand your question correctly.

If you want to remove options from an extendable option attribute, then you can just edit the logbook configuration file.

Hello,

We have accumulated some duplicate 'types' in one of our logbooks.  Is it possible to merge them?

Thanks,

John