Dear Stefan,

thanks to the answer you gave to my colleague. 

Now, attempting to follow your suggestion... If we will create several logbooks, one for each user,

1) there is a way to automatically duplicate all the entries in anoter "global" elog without loosing them and keeping them updated between the global and the individual logbooks? 

2) alternatively how I could activate a search in all these user logbooks (and only in this set of logbooks without searching in the others logbook present in the same file conf)? shall I gnereate a separated elog instance only for this set of logbooks? how to let this search to all option available only to a reduced number of "superusers" that are not "administrators?

thanks

Matteo

Hi,

I'm trying to set up elogd, running on port 8080 behind an Apache server on port 80, using mod_proxy to redirect
to the elogd server, and the recommended

Redirect permanent /elogbook http://example.com/elogbook/
ProxyPass /elogbook/         http://example.com:8080/

This works well for non-password-protected logbooks, but for password protected (that I can access fine via port
8080), I keep getting shown the Login page, even with valid username / password.    

Poking around the code, it appears (probably not too surprisingly) that the issue lies in check_login().  
For example, 

   /* if invalid or no session ID, show login page */
  if (!skip_sid_check && !sid_check(sid, user_name)) {
      if (isparam("redir"))
         strlcpy(str, getparam("redir"), sizeof(str));
      else
         strlcpy(str, isparam("cmdline") ? getparam("cmdline") : _cmdline, sizeof(str));
      /* avoid recursive loops with ?cmd=Login */
      if (stristr(str, loc("Login")))
         str[0] = 0;
      /*  added write_logfile here...
          char mstr[250];
          sprintf(mstr, "show_login B %s isparam: %d, cmd: %d, skip_sid_check: %d, sid_check: %d",
                         user_name,  isparam("redir"), isparam("cmdline"), skip_sid_check, sid_check(sid,
user_name));
           write_logfile(lbs, mstr);

        */
      show_login_page(lbs, str, 0);
      return FALSE;
}

and the logfile shows that user_name is blank(!!) and redir, cmdline, skip_sid_check, and sid_check(sid,
user_name) all to be 0.   In fact, isparam("unm") and isparam("upwd") are also 0, which explains why user_name
is blank.   But the log file also shows

LOGIN user "username" (attempt)
LOGIN user "username" (success)

just prior to this!

I'd guess that the form POST methods aren't being forwarded correctly, but I haven't looked at it in any more
detail.   

Is there a way to make this (password protecting logbooks while also using a proxy to Apache) work?

Thanks!

> I don't remember the details, but originally had the same trouble. I think a "/" at the end of a url got me somewhere. 
> I have defined...
> 
> URL = http://somewhere.edu/elog
> 
> ...in the config file, and my redirect looks like this:
> 
> Redirect /elog http://somewhere.edu/elog/
> ProxyPass /elog/ http://somewhere.edu:8080/
> ProxyPassReverse /elog/ http://somewhere.edu:8080/


Yes, that did it:  Adding the URL to the config file was the key.

Thanks!

> > What other information can I provide that might assist in diagnosing this?
> 
> Please send me your elogd.cfg configuration file.

Stefan - I am having the exact same problem as outlined here. I sent you an
email with a somewhat complicated config file. Attached to this message is a
much simpler one. 

With this file, if you remove the B5 server (remove it from top group a2, and
remove the [b5] entry) the crash does not happen. If the B5 server (or any
additional server) is in the file, then the problem occurs.

For me, there are 3 places where the crash happens:
- on logout
- when an invalid username/password is used to login
- when you login to A1, then try to go to A2

This is happening on elog v2.5.9-1 (built May 2, 2005, 12:17:18 revision 1.642)

I have tried on windows 2000 and 2003 servers, and it seems to happen on both of
them.

Matt

Another quick update on this, it looks like the bug was introduced in version
2.5.8-2 built Mar 30 2005, 11:04:33, revision 1.611

version 2.5.8-1 built Mar 21 2005, 17:28:54, revision 1.592 does not exhibit the
behavior.


Matt

We have used ELog for some time now (within the IT industry) for several things (on-call tracking, after-hours work, knowledge base and a few other uses in development).  Now that we have a good base of data, we would like to do some trending analysis.  We have used Excel in the past for this, but it is rather time consuming.  Does anyone have recommendations for tools (hopefully open source) they have used?  I know nearly anything will since ELog uses flat files, but I'm looking for recommendations that you all know works well.