Re: Elog crashes with null Username, posted by Stefan Ritt on Fri Apr 21 10:57:07 2017
|
I made a new release for you 3.1.3
Xuan
Wu wrote:
No, We are using the released version 3.1.2 |
|
Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 12:18:57 2017
|
Awesome！It's appreciated. Many Thanks!
Stefan
Ritt wrote:
I made a new release for you 3.1.3 |
Limiting search data, posted by Alan Grant on Thu Apr 27 22:21:03 2017
|
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. |
|
Re: Limiting search data, posted by Stefan Ritt on Fri Apr 28 08:15:56 2017
|
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 |
|
Re: Limiting search data, posted by Andreas Luedeke on Fri Apr 28 11:59:30 2017
|
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. |
|
Re: Limiting search data, posted by Stefan Ritt on Fri Apr 28 12:33:55 2017
|
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): |
|
elogd hangs, posted by Alan Grant on Fri Aug 18 05:28:16 2017
|
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 |
|
Re: elogd hangs, posted by Stefan Ritt on Fri Aug 18 08:59:08 2017
|
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 |