| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68957
|
Wed May 1 11:08:10 2019 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.2 | Re: Last default = <n> | You say "Show Last Default = 31". This options applies only to the "Find" page, the option "Last Default = 31" works for the quick filter. Probably you have to change "Show Last Default" to "Last Default".
Stefan
| Alan Grant wrote: |
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default the display to Month, and also only search within the last month of entries.
| Stefan Ritt wrote: |
|
Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date", then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months", "Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last default = <n>" option you can only choose one of these seven options. Then this option is selected by default and the filter is applied accordingly. This lets you still change the date filter to a longer time period for example, but then with the penalty of longer search times.
So what you need is "Last default = 31" instead of 28 and it should work.
Stefan
| Alan Grant wrote: |
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.
A couple other side questions which are related:
The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.
Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!
|
|
|
|
|
68956
|
Wed May 1 11:06:04 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.2 | Re: Last default = <n> | It works for me. Have you tried other values (1, 3, 7, ..)? The key is that the quick filter changes to "Last month". If it does not, there must be some trivial error, like type in elogd.cfg, you modify the wrong logbook, have a very old version of elog etc.
Stefan
| Alan Grant wrote: |
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default the display to Month, and also only search within the last month of entries.
| Stefan Ritt wrote: |
|
Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date", then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months", "Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last default = <n>" option you can only choose one of these seven options. Then this option is selected by default and the filter is applied accordingly. This lets you still change the date filter to a longer time period for example, but then with the penalty of longer search times.
So what you need is "Last default = 31" instead of 28 and it should work.
Stefan
| Alan Grant wrote: |
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.
A couple other side questions which are related:
The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.
Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!
|
|
|
|
|
68955
|
Wed May 1 10:59:59 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 3.1.4 | Re: elogd Service exited with abnormal code: 1 | Ok, that helped. It looks to me that the strlcpy() function from MacOSC does not like overlapping stings as parameters. Funny that this does not happen on my Mac (Mojave 10.14.4). I fixed the two cases you reported (lines 18712 and 19021) and committed the changes to bitbucket, from where you can pull and test it again (see https://elog.psi.ch/elog/download.html for instructions). If it happens again, please report the line number in elogd.c like here (where it is 19021:7):
frame #8: 0x000000010006a7ac elogd`build_ref(ref="page6?&sort=Subject", size=256, mode="full", expand="", attach="", new_entries="") at elogd.c:19021:7
Good luck!
Stefan |
|
68954
|
Tue Apr 30 19:07:17 2019 |
 | John | secondcomingtechnologies@fastmail.com | Question | Linux | 3.1.2-bd75964 | Re: How to sort on any field? | Hi Andrea and thank you soo much for your kind and prompt reply! I believe the issue will be solved as I have the information I need to proceed. I was just wanting to verify that sorting indeed is alloud on ALL fields. I cannot send the exact config as it is a work project, but I can replicate with fake fields and data if necessary in the future. I believe my errors are because I am either using field names which are 'special' to the system, or some other limitation. I will try compiling and see if that helps.
John
| Andreas Luedeke wrote: |
|
Sorting does work fine, if you do it correctly. From your post I cannot even guess what you've tried - let alone tell you what you did wrong.
Please post your config, some example entries and a description of what you've tried, what you expected to happen and what actually happened. Screenshots are often very useful as well.
| John wrote: |
|
Hi, I was wondering if this is possible. I've tried to sort on anything other than the first few fields and although the screen refreshes like it is 'doing something', it does NOT sort. Sometimes it will take me to the last page of my data, but still no sorting. I use Debian Linux verson of Elog. There have been no other issues. I need to figure out how to do this without parsing it to another program first. Thanks again for this wonderful program :)
John
|
|
|
|
68953
|
Tue Apr 30 14:20:34 2019 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.2-bd75964 | Re: How to sort on any field? | Sorting does work fine, if you do it correctly. From your post I cannot even guess what you've tried - let alone tell you what you did wrong.
Please post your config, some example entries and a description of what you've tried, what you expected to happen and what actually happened. Screenshots are often very useful as well.
| John wrote: |
|
Hi, I was wondering if this is possible. I've tried to sort on anything other than the first few fields and although the screen refreshes like it is 'doing something', it does NOT sort. Sometimes it will take me to the last page of my data, but still no sorting. I use Debian Linux verson of Elog. There have been no other issues. I need to figure out how to do this without parsing it to another program first. Thanks again for this wonderful program :)
John
|
|
|
68952
|
Tue Apr 30 14:07:52 2019 |
| Alessio Sarti | alessio.sarti@uniroma1.it | Bug report | Mac OSX | 3.1.4 | Re: elogd Service exited with abnormal code: 1 | Actually it is a little bit more difficult than that.
I have restarted elogd and got a crash but this time it seems related to a different logbook...
Below the stack trace..
Alessio
2019-04-30 13:58:52.408845+0200 elogd[22152:2009063] detected source and destination buffer overlap
Process 22152 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
frame #0: 0x00007fff7a1272c6 libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill:
-> 0x7fff7a1272c6 <+10>: jae 0x7fff7a1272d0 ; <+20>
0x7fff7a1272c8 <+12>: movq %rax, %rdi
0x7fff7a1272cb <+15>: jmp 0x7fff7a121457 ; cerror_nocancel
0x7fff7a1272d0 <+20>: retq
Target 0: (elogd) stopped.
(lldb)
error: No auto repeat.
(lldb) thread backtrace all
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
* frame #0: 0x00007fff7a1272c6 libsystem_kernel.dylib`__pthread_kill + 10
frame #1: 0x00007fff7a1dcbf1 libsystem_pthread.dylib`pthread_kill + 284
frame #2: 0x00007fff7a0916a6 libsystem_c.dylib`abort + 127
frame #3: 0x00007fff7a091819 libsystem_c.dylib`abort_report_np + 177
frame #4: 0x00007fff7a0b5cb1 libsystem_c.dylib`__chk_fail + 48
frame #5: 0x00007fff7a0b5cc1 libsystem_c.dylib`__chk_fail_overlap + 16
frame #6: 0x00007fff7a0b5ce3 libsystem_c.dylib`__chk_overlap + 34
frame #7: 0x00007fff7a0b5d39 libsystem_c.dylib`__strlcpy_chk + 58
frame #8: 0x00000001000684e3 elogd`subst_param(str="&Type=%5EInfo%24", size=1500, param="last", value="") at elogd.c:18712:7
frame #9: 0x000000010004bbaa elogd`show_elog_list(lbs=0x0000000103801008, past_n=0, last_n=0, page_n=0, default_page=YES, info=0x0000000000000000) at elogd.c:20183:7
frame #10: 0x000000010008ee58 elogd`interprete(lbook="FOOTGsi2019", path="") at elogd.c:28543:7
frame #11: 0x000000010008f096 elogd`decode_get(logbook="FOOTGsi2019", string="?last") at elogd.c:28583:4
frame #12: 0x00000001000937fd elogd`process_http_request(request="GET /FOOTGsi2019/?last=_all_&Type=%5EInfo%24", i_conn=2) at elogd.c:29361:7
frame #13: 0x0000000100097744 elogd`server_loop at elogd.c:30375:20
frame #14: 0x000000010009a073 elogd`main(argc=3, argv=0x00007ffeefbffc20) at elogd.c:31403:4
frame #15: 0x00007fff79fec3d5 libdyld.dylib`start + 1
| Alessio Sarti wrote: |
|
I was finally able to catch the crash.
I paste below the info provided by lldb..
It seems that it has something to do with the 'first' logbook that contains 115 entries and is displayed in 6 pages.
But I do not know how to go any further...
Any idea on how to debug from now on?
Thanks!
2019-04-30 12:32:27.602782+0200 elogd[19289:1908166] detected source and destination buffer overlap
Process 19289 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
frame #0: 0x00007fff7a1272c6 libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill:
-> 0x7fff7a1272c6 <+10>: jae 0x7fff7a1272d0 ; <+20>
0x7fff7a1272c8 <+12>: movq %rax, %rdi
0x7fff7a1272cb <+15>: jmp 0x7fff7a121457 ; cerror_nocancel
0x7fff7a1272d0 <+20>: retq
Target 0: (elogd) stopped.
(lldb) thread backtrace all
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
* frame #0: 0x00007fff7a1272c6 libsystem_kernel.dylib`__pthread_kill + 10
frame #1: 0x00007fff7a1dcbf1 libsystem_pthread.dylib`pthread_kill + 284
frame #2: 0x00007fff7a0916a6 libsystem_c.dylib`abort + 127
frame #3: 0x00007fff7a091819 libsystem_c.dylib`abort_report_np + 177
frame #4: 0x00007fff7a0b5cb1 libsystem_c.dylib`__chk_fail + 48
frame #5: 0x00007fff7a0b5cc1 libsystem_c.dylib`__chk_fail_overlap + 16
frame #6: 0x00007fff7a0b5ce3 libsystem_c.dylib`__chk_overlap + 34
frame #7: 0x00007fff7a0b5d39 libsystem_c.dylib`__strlcpy_chk + 58
frame #8: 0x000000010006a7ac elogd`build_ref(ref="page6?&sort=Subject", size=256, mode="full", expand="", attach="", new_entries="") at elogd.c:19021:7
frame #9: 0x000000010006aaf6 elogd`show_page_filters(lbs=0x0000000102804308, n_msg=115, page_n=6, mode_commands=YES, mode="Summary") at elogd.c:19072:10
frame #10: 0x00000001000536b8 elogd`show_elog_list(lbs=0x0000000102804308, past_n=0, last_n=0, page_n=6, default_page=NO, info=0x0000000000000000) at elogd.c:21506:10
frame #11: 0x000000010008ee58 elogd`interprete(lbook="first", path="") at elogd.c:28543:7
frame #12: 0x000000010008f096 elogd`decode_get(logbook="first", string="?id") at elogd.c:28583:4
frame #13: 0x00000001000937fd elogd`process_http_request(request="GET /first?id=108&sort=Subject", i_conn=0) at elogd.c:29361:7
frame #14: 0x0000000100097744 elogd`server_loop at elogd.c:30375:20
frame #15: 0x000000010009a073 elogd`main(argc=3, argv=0x00007ffeefbffc20) at elogd.c:31403:4
frame #16: 0x00007fff79fec3d5 libdyld.dylib`start + 1
| Stefan Ritt wrote: |
|
What you recommend is enough. Just make sure to compile elogd with the flags mentioned before, and when you get the segment violation, do a stack trace inside the debugger to learn where the fault happend. Maybe also print the contents of some variables at the current location.
Stefan
| Alessio Sarti wrote: |
|
Thanks for the prompt feedback.
a) I confirm that the problems shows up also when running interactively the elog through elogd -p 8080
b) I am trying to catch the exit using lldb on the mac machine. I will be able to give you some feedback on that I hope in the next week (not easy access to the server)
c) What is the clean - recommended way to port everything on the linux machine and debug? I would do the following: download/install elog on a linux server, 'copy' all that now lives under /usr/local/elog on the mac one on the linux server, start the elog... is this ok? or there's anything else that I need to copy from the mac server to be sure to have the same environment?
Thanks again.
Alessio
| Stefan Ritt wrote: |
|
This kind of behavior we typically see if some elog entry is corrupt. After a few hours you might access this corrupt entry by accident, and then the server stops. If you see however this behavior on a fresh logbook with no corrupt entries, then the problem must lie somewhere else.
Do you see the same problem running under linux?
Do you see the same problem if you run elogd interactively (not through launchd)?
If you run elogd inside a debugger (like gdb or lldb), what does the debugger tell you when it crashes and you show the stack frames? Make sure to compile with -O0 and -g flags to include debug information in the executable.
Stefan
| Alessio Sarti wrote: |
|
Dear all.
I am running elog
elogd 3.1.4 , revision ead6bbc6
on Macosx Mojave
Darwin arpg-serv.ing2.uniroma1.it 18.5.0 Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64
I managed to compile and run without problems the elog source code.
I can run it and have it properly displayed at boot time. After the server boot, for few hours, I have the elog ready at http://arpg-serv.ing2.uniroma1.it/elog but then, after few hours.. I get that the service stops and the elog is no longer accessible.
So far I was able to track down the problems only to the
/var/log/system.log
file in which I find a not useful error message:
Eg: Apr 23 14:00:46 arpg-serv com.apple.xpc.launchd[1] (ch.psi.elogd[85248]): Service exited with abnormal code: 1
I do not know I can I debug this nor why the code runs for few hours without problems... I just re-downloaded the code from scratch today, unloaded and then re-loaded the daemon but still it fails with the same error.
I am sure that I can get it running again for few hours by re-booting. But I want to understand the source of the problem.. Anyone can be of help on this long standing issue?
Thanks
|
|
|
|
|
|
|
68951
|
Tue Apr 30 12:47:46 2019 |
| Alessio Sarti | alessio.sarti@uniroma1.it | Bug report | Mac OSX | 3.1.4 | Re: elogd Service exited with abnormal code: 1 | I was finally able to catch the crash.
I paste below the info provided by lldb..
It seems that it has something to do with the 'first' logbook that contains 115 entries and is displayed in 6 pages.
But I do not know how to go any further...
Any idea on how to debug from now on?
Thanks!
2019-04-30 12:32:27.602782+0200 elogd[19289:1908166] detected source and destination buffer overlap
Process 19289 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
frame #0: 0x00007fff7a1272c6 libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill:
-> 0x7fff7a1272c6 <+10>: jae 0x7fff7a1272d0 ; <+20>
0x7fff7a1272c8 <+12>: movq %rax, %rdi
0x7fff7a1272cb <+15>: jmp 0x7fff7a121457 ; cerror_nocancel
0x7fff7a1272d0 <+20>: retq
Target 0: (elogd) stopped.
(lldb) thread backtrace all
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
* frame #0: 0x00007fff7a1272c6 libsystem_kernel.dylib`__pthread_kill + 10
frame #1: 0x00007fff7a1dcbf1 libsystem_pthread.dylib`pthread_kill + 284
frame #2: 0x00007fff7a0916a6 libsystem_c.dylib`abort + 127
frame #3: 0x00007fff7a091819 libsystem_c.dylib`abort_report_np + 177
frame #4: 0x00007fff7a0b5cb1 libsystem_c.dylib`__chk_fail + 48
frame #5: 0x00007fff7a0b5cc1 libsystem_c.dylib`__chk_fail_overlap + 16
frame #6: 0x00007fff7a0b5ce3 libsystem_c.dylib`__chk_overlap + 34
frame #7: 0x00007fff7a0b5d39 libsystem_c.dylib`__strlcpy_chk + 58
frame #8: 0x000000010006a7ac elogd`build_ref(ref="page6?&sort=Subject", size=256, mode="full", expand="", attach="", new_entries="") at elogd.c:19021:7
frame #9: 0x000000010006aaf6 elogd`show_page_filters(lbs=0x0000000102804308, n_msg=115, page_n=6, mode_commands=YES, mode="Summary") at elogd.c:19072:10
frame #10: 0x00000001000536b8 elogd`show_elog_list(lbs=0x0000000102804308, past_n=0, last_n=0, page_n=6, default_page=NO, info=0x0000000000000000) at elogd.c:21506:10
frame #11: 0x000000010008ee58 elogd`interprete(lbook="first", path="") at elogd.c:28543:7
frame #12: 0x000000010008f096 elogd`decode_get(logbook="first", string="?id") at elogd.c:28583:4
frame #13: 0x00000001000937fd elogd`process_http_request(request="GET /first?id=108&sort=Subject", i_conn=0) at elogd.c:29361:7
frame #14: 0x0000000100097744 elogd`server_loop at elogd.c:30375:20
frame #15: 0x000000010009a073 elogd`main(argc=3, argv=0x00007ffeefbffc20) at elogd.c:31403:4
frame #16: 0x00007fff79fec3d5 libdyld.dylib`start + 1
| Stefan Ritt wrote: |
|
What you recommend is enough. Just make sure to compile elogd with the flags mentioned before, and when you get the segment violation, do a stack trace inside the debugger to learn where the fault happend. Maybe also print the contents of some variables at the current location.
Stefan
| Alessio Sarti wrote: |
|
Thanks for the prompt feedback.
a) I confirm that the problems shows up also when running interactively the elog through elogd -p 8080
b) I am trying to catch the exit using lldb on the mac machine. I will be able to give you some feedback on that I hope in the next week (not easy access to the server)
c) What is the clean - recommended way to port everything on the linux machine and debug? I would do the following: download/install elog on a linux server, 'copy' all that now lives under /usr/local/elog on the mac one on the linux server, start the elog... is this ok? or there's anything else that I need to copy from the mac server to be sure to have the same environment?
Thanks again.
Alessio
| Stefan Ritt wrote: |
|
This kind of behavior we typically see if some elog entry is corrupt. After a few hours you might access this corrupt entry by accident, and then the server stops. If you see however this behavior on a fresh logbook with no corrupt entries, then the problem must lie somewhere else.
Do you see the same problem running under linux?
Do you see the same problem if you run elogd interactively (not through launchd)?
If you run elogd inside a debugger (like gdb or lldb), what does the debugger tell you when it crashes and you show the stack frames? Make sure to compile with -O0 and -g flags to include debug information in the executable.
Stefan
| Alessio Sarti wrote: |
|
Dear all.
I am running elog
elogd 3.1.4 , revision ead6bbc6
on Macosx Mojave
Darwin arpg-serv.ing2.uniroma1.it 18.5.0 Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64
I managed to compile and run without problems the elog source code.
I can run it and have it properly displayed at boot time. After the server boot, for few hours, I have the elog ready at http://arpg-serv.ing2.uniroma1.it/elog but then, after few hours.. I get that the service stops and the elog is no longer accessible.
So far I was able to track down the problems only to the
/var/log/system.log
file in which I find a not useful error message:
Eg: Apr 23 14:00:46 arpg-serv com.apple.xpc.launchd[1] (ch.psi.elogd[85248]): Service exited with abnormal code: 1
I do not know I can I debug this nor why the code runs for few hours without problems... I just re-downloaded the code from scratch today, unloaded and then re-loaded the daemon but still it fails with the same error.
I am sure that I can get it running again for few hours by re-booting. But I want to understand the source of the problem.. Anyone can be of help on this long standing issue?
Thanks
|
|
|
|
|
|
68950
|
Tue Apr 30 09:34:52 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: exclude access to a number of users in one logbook | You have a look here: elog:68936
| Nikolas Patronis wrote: |
|
How can I exclude the access of a number of users in one (out of two) logbooks running in the same server and URL?
|
|
|