| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2022
|
Fri Oct 27 13:02:50 2006 |
 | Alexandre Lindote | alex@lipc.fis.uc.pt | Question | Linux | 2.6.2-1699 | Re: ELCode |
| Alexandre Lindote wrote: | Hi,
can you think of any obvious reason why the ELCode would not work in the logbooks I set up?
|
Ok, I think I found the problem... For some reason the elcode.js file was only in /usr/local/elog/scripts, but it was supposed to be in
/usr/local/elog/themes/default/ as well.
Creating a symlink between the two solved that problem. I can now do most things with the ELCode, but inserting images is still failing. I get this message from the firefox javascript console:
text.value has no properties (line 32 of elcode.js)
Any thoughts?
Alex |
|
2026
|
Tue Oct 31 20:05:07 2006 |
 | Alexandre Lindote | alex@lipc.fis.uc.pt | Question | Linux | 2.6.2-1739 | calling a shell in the Options tag | Hi,
is it possible to run a shell script in an "Options" tag, as it is with the "Preset", "Subst", and so on?
I need to have something like this:
Options Update of = $shell(/home/alex/zeplin3/elog/z3elog-mirror/documents/ext_docs.sh MinGen)
the script returns a line with comma separated values...
Thanks
Alex |
|
2029
|
Wed Nov 1 09:53:05 2006 |
| Alexandre Lindote | alex@lipc.fis.uc.pt | Question | Linux | 2.6.2-1739 | Re: calling a shell in the Options tag |
| Steve Jones wrote: |
| Alexandre Lindote wrote: | Hi,
is it possible to run a shell script in an "Options" tag, as it is with the "Preset", "Subst", and so on?
I need to have something like this:
Options Update of = $shell(/home/alex/zeplin3/elog/z3elog-mirror/documents/ext_docs.sh MinGen)
the script returns a line with comma separated values...
Thanks
Alex |
| Steve Jones wrote: |
Alex, have you tried it? Novel idea!
|
|
Yes, I have. It doesn't seem to... 
I just get one option, which is the shell line itself.
Something like:
--- Please select ---
$shell(/home/alex/zeplin3/elog/z3elog-mirror/documents/ext_docs.sh MinGen)
Cheers
Alex |
|
2120
|
Thu Jan 18 16:29:43 2007 |
| Alexandre Lindote | alex@lipc.fis.uc.pt | Question | Linux | Mac OSX | 2.6.3-1762 | Synchronization using https | Hi,
I have an elog server running on a linux desktop machine inside our institutional firewall. It can be accessed from inside the firewall directly using http, but users from outside have to use https, with apache (and its ssl module) controlling the access.
I also set up another server on my laptop, just for backup purposes, and synchronized it inside the firewall (using a direct http connection). No problems there!
Now we want to have several servers set up (in different institutions), and have them synchronized automatically. For this I installed elog on a mac server (in another institution, so outside our firewall), also accessible only through https (again using apache).
I configured all the required mirror settings, but always get an error: "Remote server is not an ELOG server".
I've tried changing the status of the 2 machines (server-client), but get the same error...
I also tried different approaches for the Mirror server parameter, like
https://the.remote.server
https://the.remote.server:443
http://the.remote.server:443
but no luck...
Running elog with the -D flag off issued this message:
| Quote: | HTTP/1.1 401 Authorization Required
Date: Thu, 18 Jan 2007 15:22:10 GMT
Server: Apache/1.3.33 (Darwin) DAV/1.0.3 mod_ssl/2.8.24 OpenSSL/0.9.7l
WWW-Authenticate: Basic realm="zeplin2"
Connection: close
Content-Type: text/html; charset=iso-8859-1
Authorization Required
This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.
Apache/1.3.33 Server at shalott.pp.rl.ac.uk Port 80
|
The servers have user level passwords, and I'm mirroring with Mirror user parameter set to the administrator...
Any ideas?
Thanks in advance
Alex |
|
68932
|
Tue Apr 23 14:06:36 2019 |
 | Alessio Sarti | alessio.sarti@uniroma1.it | Bug report | Mac OSX | 3.1.4 | elogd Service exited with abnormal code: 1 | 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 |
|
68942
|
Thu Apr 25 11:16:06 2019 |
| Alessio Sarti | alessio.sarti@uniroma1.it | Bug report | Mac OSX | 3.1.4 | Re: elogd Service exited with abnormal code: 1 | 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
|
|
|
|
|
|
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
|
|
|
|
|
|
|