Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon5.gif   Elog crashes with null Username, posted by Alan Grant on Sun Dec 18 08:51:47 2016 
    icon2.gif   Re: Elog crashes with null Username, posted by Stefan Ritt on Mon Dec 19 12:28:47 2016 
       icon2.gif   Re: Elog crashes with null Username, posted by Alan Grant on Mon Dec 19 19:42:05 2016 
       icon2.gif   Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 02:21:59 2017 
          icon2.gif   Re: Elog crashes with null Username, posted by Alan Grant on Fri Apr 21 05:27:35 2017 
             icon2.gif   Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 08:19:05 2017 
                icon2.gif   Re: Elog crashes with null Username, posted by Stefan Ritt on Fri Apr 21 10:57:07 2017 
                   icon2.gif   Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 12:18:57 2017 
Message ID: 68612     Entry time: Fri Apr 21 10:57:07 2017     In reply to: 68611     Reply to this: 68613
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Bug report  OS: Windows  ELOG Version: 3.1.2 
Subject: Re: Elog crashes with null Username 

I made a new release for you 3.1.3

Xuan Wu wrote:

No, We are using the released version 3.1.2

How to use the current git revision or is it a long time to wait for the next release?

Alan Grant wrote:

Are you using the current git revision Xuan?

Xuan Wu wrote:

We also meet this issue occasionally, so how can we get rid of this?

Stefan Ritt wrote:

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

 

 

 

 

ELOG V3.1.5-fe60aaf