Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 232 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  68612   Fri Apr 21 10:57:07 2017 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows3.1.2Re: 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)

 

 

 

 

 

  68613   Fri Apr 21 12:18:57 2017 Reply Xuan Wuwux@ihep.ac.cnBug reportWindows3.1.2Re: Elog crashes with null Username

Awesome!It's appreciated. Many Thanks!

Stefan Ritt wrote:

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)

 

 

 

 

 

 

  68614   Thu Apr 27 22:21:03 2017 Question Alan Grantagrant@winnipeg.caQuestionWindows3.1.2Limiting search data

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

  68615   Fri Apr 28 08:15:56 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.2Re: Limiting search data

I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?

Alan Grant wrote:

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

 

  68616   Fri Apr 28 11:59:30 2017 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows3.1.2Re: Limiting search data

I think I understand the question (although I have no answer):

When someone uses the "Find" page search, then there is an option to limit the search to e.g. the last year. If you search for a non existing string, it'll only search entries from the past year.

If people are instead using the quickfilter to search for the same non existing string, then all entries of all past years are searched for the string.

In both cases the result page will be empty, so "Entries per page" does not change anything. But in the second case the search might need an order of magnitude longer.

Stefan Ritt wrote:

I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?

Alan Grant wrote:

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

 

 

  68617   Fri Apr 28 12:33:55 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.2Re: Limiting search data

Ok, got it. Will put it on the to-do list.

Andreas Luedeke wrote:

I think I understand the question (although I have no answer):

When someone uses the "Find" page search, then there is an option to limit the search to e.g. the last year. If you search for a non existing string, it'll only search entries from the past year.

If people are instead using the quickfilter to search for the same non existing string, then all entries of all past years are searched for the string.

In both cases the result page will be empty, so "Entries per page" does not change anything. But in the second case the search might need an order of magnitude longer.

Stefan Ritt wrote:

I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?

Alan Grant wrote:

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

 

 

 

  68653   Fri Aug 18 05:28:16 2017 Question Alan Grantagrant@winnipeg.caQuestionWindows3.1.2elogd hangs

I have a very long standing problem with elog over the last few versions where almost daily the service will hang. Cannot even Restart elogd, that just hangs. Clients experience Page not Found. I can only get the service reinitialized by rebooting the VM machine. I have Elog verbose logging On plus a number of external triage monitors running but nothing is yielding clues beyond the precise time the hang occurs. Aside from providing the Config and log files what else can I provide for you to assist, and what other triage measures can you suggest I try? FYI, there can be up to 20 users at one time doing searches (not updates), and I've trimmed the depth of log files that can be searched so that the CPU/service doesn't bog down but that hasn't helped either. Inserts happen in the background using the elog client app (about 2 or 3 inserts per batch at sporadic times).

  68654   Fri Aug 18 08:59:08 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.2Re: elogd hangs

I have to figure out where elog hangs. I guess it must be some kind of endless loop, triggered by some corrupt data in one of the elog entries. Under linux this is fairly simple (just run elogd under the gdb debugger, wait until it hangs, then press ctrl-c and enter "where" to see a full stack dump where elogd is currently executing). Under Windows this is more difficult, since you need Visual C++ from Microsoft to do the debugging. One thing you can do however without VC is to check if the CPU time is consumed to 100% by elogd, indicating an endless loop.

Stefan

Alan Grant wrote:

I have a very long standing problem with elog over the last few versions where almost daily the service will hang. Cannot even Restart elogd, that just hangs. Clients experience Page not Found. I can only get the service reinitialized by rebooting the VM machine. I have Elog verbose logging On plus a number of external triage monitors running but nothing is yielding clues beyond the precise time the hang occurs. Aside from providing the Config and log files what else can I provide for you to assist, and what other triage measures can you suggest I try? FYI, there can be up to 20 users at one time doing searches (not updates), and I've trimmed the depth of log files that can be searched so that the CPU/service doesn't bog down but that hasn't helped either. Inserts happen in the background using the elog client app (about 2 or 3 inserts per batch at sporadic times).

 

ELOG V3.1.5-3fb85fa6