> It's hard to tell the problem from what you report. Have you tried the latest
> release http://midas.psi.ch/elog/download/windows/elog258-6.exe ? There were
> some problems with the password file in 2.5.8 versions prior to patch level 6.

Yes, I am up to date with the latest version (2.5.8-6).

What other information can I provide that might assist in diagnosing this?

> What other information can I provide that might assist in diagnosing this?

Please send me your elogd.cfg configuration file.

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

Just upgraded from stable running 2.5.2-2 to 2.5.9-2 in case of the usable
Duplicate function. After the problem discribed below i made a new, clean
installation again and played araound with the demo logbook, copying my
testlogbook (part of a real used and under 2.5.2-2 working logbook) into the
demo cfg file. 

ia figured out two serious problems:

1. If I copy the following section to the global into the demo lgbook,
elogd.exe crashes emediatly ewhile starting as a prozess:

[global]
Language = German
Theme = default
logbook tabs = 1
main tab = INHALT
welcome title = <b><big>Ulrich Rolf Trüssel</big></b>
Adressverwaltung
(Geschäft & Privat)
Mensch-Tier
Coaching&trade;&nbsp;&nbsp;-&nbsp;&nbsp;Mensch-Hund
Coaching&trade;
Interessengemeinschaft Familienhund&reg; - Regionalgruppe
Zentralschweiz
Lorenz Tierschule
port = 8080
Theme = default
Message Width = 100
Message Height = 25
Filtered browsing = 1
Suppress default = 2
Suppress Email on Edit = 0
Email Format = 0
Filtered browsing = 1
HTML default = 3
Reverse sort = 1

2. problem (the ting) that made me playing with teh demo cfg:
There are totally 8 logbooks running, but just one has this strange problem
of not giving a link to to the datasets in full and summary mode. I cutted
down all the stuff back to this only lines:

[Adresse2]
Attributes = Kundensegment, Duzis, Hauptadresse, Selektion, Sperre, Adresse,
Unterlagenversand, Empf. gegeben, Gruppe, Mitglied, URT, IGFH, Letzte
Anmeldung, IGFH Gruppe, IGFH JB, Anrede, Titel, Briefanrede, Vorname, Name,
Firma, Abteilung, Adresse Zusatz, Strasse, Landeskennung, PLZ, Ortschaft,
Postfach, Postfach PLZ, Postfach Ort, Telefon Geschäft, Telefon Privat,
Telefax, Telefon Mobil, EMail, HomePage, Funktion, Beruf, Geburtstag, Name
Hund, Rasse, Sex, Wurfdatum, Anmeldung, Impfbüchlein, Welpenkurs,
Erziehungskurs, Hundesport, Bestätigung, OCCH LN, Andere Kurse, Weitere
Hunde/Tiere, Referenzen, KlientIn/KundIn
List Display = Name, Vorname

and got still the same problem. if i create a new logbook it will works,
also ut works under 2.5.2-2 but not longer under 2.5.3 up (even not
2.5.9-2). any idea? mening this may be a VERY basic logbook... trued with
list display etc. around, nothinh happen. Need to go back to 2.5.2-2 where
this wasn't a problem? 

thanjs for any idea of this to problems...

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