| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68943
|
Thu Apr 25 11:27:21 2019 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 3.1.4 | Re: elogd Service exited with abnormal code: 1 |
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
|
|
|
|
|
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
|
|
|
|
68941
|
Wed Apr 24 11:56:24 2019 |
| Heinz Junkes | junkes@fhi-berlin.mpg.de | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
I ask my users where they had the problems and then create a demo for testing.
Thanks Heinz
| Stefan Ritt wrote: |
|
So you are telling me that "Restrict edit time" is not working correctly? In order to fix any problem, I have to reproduce it. Can you post a minimel elogd.cfg file with which I can reproduce the problem?
Stefan
| Heinz Junkes wrote: |
|
Sorry,
I meant "read only" by using "Restrict edit time" settings. e.g.
Restrict edit time = 24
I understand this to mean that an entry should not be able to be modified after 24 hours.
Heinz
| Stefan Ritt wrote: |
|
There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.
Stefan
| Heinz Junkes wrote: |
|
Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have forbidden further editing.
Heinz
| Stefan Ritt wrote: |
|
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list.
Stefan
| Heinz Junkes wrote: |
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz
| Heinz Junkes wrote: |
|
submissions via the elog - program can overwrite entries even if the user has no edit rights
|
|
|
|
|
|
|
|
|
68940
|
Wed Apr 24 11:30:37 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
So you are telling me that "Restrict edit time" is not working correctly? In order to fix any problem, I have to reproduce it. Can you post a minimel elogd.cfg file with which I can reproduce the problem?
Stefan
| Heinz Junkes wrote: |
|
Sorry,
I meant "read only" by using "Restrict edit time" settings. e.g.
Restrict edit time = 24
I understand this to mean that an entry should not be able to be modified after 24 hours.
Heinz
| Stefan Ritt wrote: |
|
There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.
Stefan
| Heinz Junkes wrote: |
|
Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have forbidden further editing.
Heinz
| Stefan Ritt wrote: |
|
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list.
Stefan
| Heinz Junkes wrote: |
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz
| Heinz Junkes wrote: |
|
submissions via the elog - program can overwrite entries even if the user has no edit rights
|
|
|
|
|
|
|
|
68939
|
Wed Apr 24 11:03:26 2019 |
| Heinz Junkes | junkes@fhi-berlin.mpg.de | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
Sorry,
I meant "read only" by using "Restrict edit time" settings. e.g.
Restrict edit time = 24
I understand this to mean that an entry should not be able to be modified after 24 hours.
Heinz
| Stefan Ritt wrote: |
|
There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.
Stefan
| Heinz Junkes wrote: |
|
Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have forbidden further editing.
Heinz
| Stefan Ritt wrote: |
|
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list.
Stefan
| Heinz Junkes wrote: |
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz
| Heinz Junkes wrote: |
|
submissions via the elog - program can overwrite entries even if the user has no edit rights
|
|
|
|
|
|
|
68938
|
Wed Apr 24 10:29:00 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.
Stefan
| Heinz Junkes wrote: |
|
Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have forbidden further editing.
Heinz
| Stefan Ritt wrote: |
|
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list.
Stefan
| Heinz Junkes wrote: |
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz
| Heinz Junkes wrote: |
|
submissions via the elog - program can overwrite entries even if the user has no edit rights
|
|
|
|
|
|
68937
|
Wed Apr 24 10:21:58 2019 |
| Heinz Junkes | junkes@fhi-berlin.mpg.de | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have forbidden further editing.
Heinz
| Stefan Ritt wrote: |
|
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list.
Stefan
| Heinz Junkes wrote: |
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz
| Heinz Junkes wrote: |
|
submissions via the elog - program can overwrite entries even if the user has no edit rights
|
|
|
|
|
68936
|
Wed Apr 24 10:15:23 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | elogd 3.1.4 | Re: elog program does not respect "Allow edit" list |
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list.
Stefan
| Heinz Junkes wrote: |
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz
| Heinz Junkes wrote: |
|
submissions via the elog - program can overwrite entries even if the user has no edit rights
|
|
|