> Ok, fixed. I do however not evaluate the conditional attribute, but just remove any
> empty attribute, I guess that makes more sense.

ok, it work perfectly, tnx .. I agree with you choice of course :-)

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

> Since updating to version 2.5.8 we have been having problems with the elogd 
> service crashing whenever anyone attempts to log out. We are using stunnel 
> 4.09 on a Win 2k system.

This problem has finally been identified and fixed. Please download the newest
version 2.5.9-2 which contains this fix.

> > Since updating to version 2.5.8 we have been having problems with the elogd 
> > service crashing whenever anyone attempts to log out. We are using stunnel 
> > 4.09 on a Win 2k system.
> 
> This problem has finally been identified and fixed. Please download the newest
> version 2.5.9-2 which contains this fix.

I will get right on this. Thank you for your efforts!