ELOG Forum

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

68955

Wed May 1 10:59:59 2019

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

68959

Thu May 2 09:47:41 2019

Alessio Sarti

alessio.sarti@uniroma1.it

Bug report

Mac OSX

3.1.4

Re: elogd Service exited with abnormal code: 1

Thanks a lot for providing a quick fix!

The elog is now happily running since two days without problems :)

I will get back to you in case anything else shows up.

Thanks a lot again.

Stefan Ritt wrote:

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

1774

Wed Mar 15 09:28:42 2006

Re: elogd 2.6.1 program Crash is repeatable under Windows

Steve Jones wrote:

Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment.

Steve,

again I could not reproduce your problem. See the attached screenshots. It just works fine with me (of course I miss the HTML files for the header and footer). I use however the most recent version of elog (Revision 1675). I also have a different password file. So try the following:

- look into your password file (it's a simple XML text file), it should contain something like

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
  <user>
    <name>stefan</name>
    <password>zFDkjoZsg==</password>
    <full_name>Stefan Ritt</full_name>
    <email>stefan.ritt@psi.ch</email>
    <last_logout>Thu Feb 23 15:35:19 2006</last_logout>
    <last_activity>Wed Mar 15 09:22:02 2006</last_activity>
    <email_notify>
      <logbook>demo</logbook>
    </email_notify>
  </user>
</list>

- make sure that you have the most recent version of elogd. Try at least elog261-3.exe under Windows.

- are you sure you need top groups? Top groups are ment for groups of logbooks which are completele unrelated, like from different departments, with different admins etc. Historically top groups were implemented because some elog installations had several elogd servers running in parallel for different departments. In you case, I suspect that "normal" groups might be enough, like:

Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL

Attachment 1: Capture.jpg

Attachment 2: Capture.jpg

1775

Wed Mar 15 21:42:25 2006

Steve Jones

steve.jones@freescale.com

Bug report

All

2.6.1-1668

Re: elogd 2.6.1 program Crash is repeatable under Windows

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
  <user>
    <name>stefan</name>
    <password>zFDkjoZsg==</password>
    <full_name>Stefan Ritt</full_name>
    <email>stefan.ritt@psi.ch</email>
    <last_logout>Thu Feb 23 15:35:19 2006</last_logout>
    <last_activity>Wed Mar 15 09:22:02 2006</last_activity>
    <email_notify>
      <logbook>demo</logbook>
    </email_notify>
  </user>
</list>

Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL

Aacck! I thought sure that this would do it for you. Ok, to answer your last question first:
1> I am reasonably sure that I need top groups. The logbooks with the -CL extension have a common attribute structure. The logbooks with the -IL extension have a common attribute structure. Neither group is the same. Prior to using Top Group I was using a global config for the -CL's but manually maintaining consistent -IL configs was horrible. Top Group solved my problem: maintaining only two config "areas" as opposed to many is very efficient. Do you have another way of doing this other than running two instances of eLog?

2> My password file on Windows is

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
  <user>
    <name>r4aajl</name>
    <password>TDIwYXVyZW4=</password>
    <full_name>Steve Jones</full_name>
    <last_logout>0</last_logout>
    <last_activity>Tue Mar 14 10:35:04 2006</last_activity>
    <email>steve.jones@freescale.com</email>
    <email_notify>
      <logbook>TX30-CL</logbook>
      <logbook>TX11-CL</logbook>
      <logbook>TX32-CL</logbook>
      <logbook>AZ34-CL</logbook>
      <logbook>AZ50-CL</logbook>
      <logbook>Approvals-CL</logbook>
      <logbook>FL29-CL</logbook>
      <logbook>IL108-CL</logbook>
      <logbook>ZIL05-CL</logbook>
      <logbook>Template-CL</logbook>
    </email_notify>
  </user>
</list>

3> I see your screen shots. Try going in and creating a new logbook and tell me if it dies. In the meantime is the latest version available in compiled form for Windows? If so, I'll install it and try again. At this point I am looking at starting a new config file from scratch but unless you can suggest another way I think Top Group is my only option.

1776

Wed Mar 15 23:46:54 2006

Steve Jones

steve.jones@freescale.com

Bug report

All

2.6.1-1668

Re: elogd 2.6.1 program Crash is repeatable under Windows

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
  <user>
    <name>stefan</name>
    <password>zFDkjoZsg==</password>
    <full_name>Stefan Ritt</full_name>
    <email>stefan.ritt@psi.ch</email>
    <last_logout>Thu Feb 23 15:35:19 2006</last_logout>
    <last_activity>Wed Mar 15 09:22:02 2006</last_activity>
    <email_notify>
      <logbook>demo</logbook>
    </email_notify>
  </user>
</list>

Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
  <user>
    <name>r4aajl</name>
    <password>TDIwYXVyZW4=</password>
    <full_name>Steve Jones</full_name>
    <last_logout>0</last_logout>
    <last_activity>Tue Mar 14 10:35:04 2006</last_activity>
    <email>steve.jones@freescale.com</email>
    <email_notify>
      <logbook>TX30-CL</logbook>
      <logbook>TX11-CL</logbook>
      <logbook>TX32-CL</logbook>
      <logbook>AZ34-CL</logbook>
      <logbook>AZ50-CL</logbook>
      <logbook>Approvals-CL</logbook>
      <logbook>FL29-CL</logbook>
      <logbook>IL108-CL</logbook>
      <logbook>ZIL05-CL</logbook>
      <logbook>Template-CL</logbook>
    </email_notify>
  </user>
</list>

Ok, I completed stripped any attributes and only defined top groups. eLog no longer crashes but returns a completely invalid page with invalid links when I attempt to create a new logbook - see screenshot below. This is good as it means something in the config was causing things to blowup. I have also attached my stripped out config.

Incidently, I added another screenshot - an invalid link when I *delete* a logbook gets returned "http://localhost:8080/Test4-CL/Engineering%20Compute%20Change%20Logs/". Definitely not a correct URL.

Quote:

Attachment 1: elog_1.JPG

Attachment 2: elogd.cfg

[global]
port = 8080

Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Move To, Help
Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin

Show top groups = 1

Top Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, ZIL05-CL, Approvals-CL, Template-CL, Test-CL, Test2-CL, Test3-CL, Test4-CL

Top Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, ZIL05-IL, Template-IL

[global Engineering Compute Change Logs]

Welcome Title = <bold><font size="+3"><b>Design Technology</b></font>
<font size="+2">
Engineering Compute Change Log Facility</a></font>

Pick the correct site and register all SIGNIFICANT Engineering Infrastructure <b>Planned Changes</b>.
<a href="elogadm@freescale.com">Send questions to the eLog Admin</a></bold>

<font size="-1"><table width="100%"><tr><td align="left" valign="top"><a href= "http://twiki.freescale.net/bin/view.cgi/CUE/OperationalChangeControl">ISO17799: Operational Change Control, Sec8.1.2</a></td><td align="right" valign="top"><a href="http://elog-test.am.freescale.net/Engineering%20Compute%20Incident%20Logs/">Looking for the Incident Logs?</a></td></tr></table></font>





[global Engineering Compute Incident Logs]


Welcome Title = <bold><font size="+3"><b>Design Technology</b></font>
<font size="+2">
Engineering Compute Incident Log Facility</a></font>

Pick the correct site and enter an Incident <b>that has already happened</b>. Questions to be answered are provided.
<a href="elogadm@freescale.com">Send questions to the eLog Admin</a></bold>

<font size="-1"><table width="100%"><tr><td align="left" valign="top"><a href= "http://twiki.freescale.net/bin/view.cgi/CUE/OperationalChangeControl">ISO17799: Operational Change Control, Sec8.1.2</a></td><td align="right" valign="top"><a href="http://elog-test.am.freescale.net/Engineering%20Compute%20Change%20Logs/">Looking for the Change Logs?</a></td></tr></table></font>



[TX30-IL]
Page Title = $logbook Post Incident Log - $Short Summary

[TX11-IL]
Page Title = $logbook Post Incident Log - $Short Summary

[TX32-IL]
Page Title = $logbook Post Incident Log - $Short Summary

[AZ34-IL]
Page Title = $logbook Post Incident Log - $Short Summary

[AZ50-IL]
Page Title = $logbook Post Incident Log - $Short Summary

[FL29-IL]
Page Title = $logbook Post Incident Log - $Short Summary

[IL108-IL]
Page Title = $logbook Post Incident Log - $Short Summary

[ZIL05-IL]
Page Title = $logbook Post Incident Log - $Short Summary

[Template-IL]
Hidden = 1
Page Title = $logbook Post Incident Log - $Short Summary


[TX30-CL]
Page Title = $logbook Change Log - $Subject


[TX11-CL]
Page Title = $logbook Change Log - $Subject


[TX32-CL]
Page Title = $logbook Change Log - $Subject

[AZ34-CL]
Page Title = $logbook Change Log - $Subject



[AZ50-CL]
Page Title = $logbook Change Log - $Subject



[Approvals-CL]
Page Title = Global $logbook list - $Subject



[FL29-CL]
Page Title = $logbook Change Log - $Subject



[IL108-CL]
Page Title = $logbook Change Log - $Subject



[ZIL05-CL]
Page Title = $logbook Change Log - $Subject


[Template-CL]
Hidden = 1
Page Title = $logbook Change Log - $Subject

[Test-CL]
Hidden = 1
Page Title = $logbook Change Log - $Subject

[Test2-CL]

[Test3-CL]

[Test4-CL]

Attachment 3: elogd_2.JPG

1777

Tue Mar 21 00:05:43 2006

Steve Jones

steve.jones@freescale.com

Bug report

All

2.6.1-1668

Re: elogd 2.6.1 program Crash is repeatable under Windows

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
  <user>
    <name>stefan</name>
    <password>zFDkjoZsg==</password>
    <full_name>Stefan Ritt</full_name>
    <email>stefan.ritt@psi.ch</email>
    <last_logout>Thu Feb 23 15:35:19 2006</last_logout>
    <last_activity>Wed Mar 15 09:22:02 2006</last_activity>
    <email_notify>
      <logbook>demo</logbook>
    </email_notify>
  </user>
</list>

Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
  <user>
    <name>r4aajl</name>
    <password>TDIwYXVyZW4=</password>
    <full_name>Steve Jones</full_name>
    <last_logout>0</last_logout>
    <last_activity>Tue Mar 14 10:35:04 2006</last_activity>
    <email>steve.jones@freescale.com</email>
    <email_notify>
      <logbook>TX30-CL</logbook>
      <logbook>TX11-CL</logbook>
      <logbook>TX32-CL</logbook>
      <logbook>AZ34-CL</logbook>
      <logbook>AZ50-CL</logbook>
      <logbook>Approvals-CL</logbook>
      <logbook>FL29-CL</logbook>
      <logbook>IL108-CL</logbook>
      <logbook>ZIL05-CL</logbook>
      <logbook>Template-CL</logbook>
    </email_notify>
  </user>
</list>

Steve Jones wrote:

BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No.

1788

Mon Apr 3 17:09:19 2006

Re: elogd 2.6.1 program Crash is repeatable under Windows

Steve Jones wrote:

There is a 2.6.1-4 version for Windows for download, which contains the most recent code.

Goto page Previous 1, 2, 3 ... 193, 194, 195 ... 794, 795, 796 Next

ELOG V3.1.5-2eba886