I attempted instead to build from the tar ball, and, except for a "fatal" git error, make built elogd, elog, and elconv.  I put the first in /usr/local/sbin, and the latter two in /usr/local/bin, and then restarted elogd, but this didn't work:

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

So, I backed these out and restored the previous executables, and access to the elog was restored, and the elogd.cfg accessed is the original one, but all logbooks are empty and requiring authentication.  The logbook directories still contain all the old entries, so I'm not sure what has happened.

Thanks for your advice.

Phil

OK.  I found the source of the logbook problem in an exchange from May 2015, so no need to answer this one.

But I would like to be able to upgrade to 3.x from 2.9, so any help with this will be much appreciated.

Phil

I did the following on CentOS 6.7 (Should work for Fedora and RHEL as well):

This should install all the required dependencies.

Is it possible to use wget to log into elog and export all of a logbook's data into a CSV file?

I can accomplish this perfectly when authentication IS NOT required by using:  wget --no-check-certificate -O e:\export.csv http://localhost:8080/demo/?mode=CSV1

However, I cannot accomplish it when authentication IS required by using:  wget --no-check-certificate -O e:\export.csv "http://localhost:8080/demo/?mode=CSV1&uname=agrant&upassword=skipper"

The latter appears to show that I've logged in, but the export file only contains a bunch of HTML tags, not the actual data as in the former.

How should I construct the wget command?

UPDATE:

After days of head banging and trying different syntax combinations, I finally stumbled on my own answer. It involved some syntax adjustments, and then splitting the task into these two consecutive operations:

      1. wget --no-check-certificate --cookies=on --save-cookies cookies.txt --keep-session-cookies -O e:\export1.csv "http://localhost:8080/demo/?uname=agrant&upassword=skipper"

      2. wget --no-check-certificate --cookies=on --load-cookies cookies.txt --keep-session-cookies -O e:\export2.csv http://localhost:8080/demo/?mode=CSV1

All is working fine now.

Hello,

Is it possible to remove the "active" checkbox a user sees when they click on "config"?  Alternatively, is it possible to have a new user arrive directly at the logbook they chose, rather than starting out at the config screen?

We are running elog-3.1.1 on SL6 with webserver authentication.  For the most part this works great, but somehow a few users become inactive after they login for the first time.  They claim they didn't un-check "active," but I can't think of any other way this would happen.

Many thanks,
Devin

Hello,

Has anyone implemented an email gateway for ELOG, allowing users to submit entries by sending an email?  Granted this should be possible using the elog client binary, but I thought I'd see if I've overlooked any examples or docs first.

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