Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  06 Sep 2021, Andreas Suter, Forum, mhttpd crash 
    Reply  06 Sep 2021, Konstantin Olchanski, Forum, mhttpd crash 
       Reply  07 Sep 2021, Andreas Suter, Forum, mhttpd crash 
          Reply  17 Sep 2021, Stefan Ritt, Forum, mhttpd crash mhttpdScreenshot_2021-09-17_at_21.11.15_.png
Message ID: 2275     Entry time: 07 Sep 2021     In reply to: 2274     Reply to this: 2276
Author: Andreas Suter 
Topic: Forum 
Subject: mhttpd crash 
Dear Konstantin,

thanks for the prompt response, this helps a lot!

> 1) If you see a way to replicate this crash, or some way to reliably cause
> the crash within 5-10 minutes after starting mhttpd, please let me know. I can work with that
> and I wish to fix this problem very much.

I wished I could! This happens 3-4 times per year only, so close to impossible to trigger.

> 2) My "wrong socket" check calls abort() to produce a core dump. In my experience these core dumps
> are useless for debugging the present problem. There is just no way to examine the state of each
> thread and of each http request using gdb by hand.
> 3) this abort() causes linux to write a core dump, this takes a long time and I think it causes
> other MIDAS program to stop, timeout and die. You can try to fix this by disabling core dumps (set "enable core dumps"
> to "false" in ODB and set core dump size limit to 0), or change abort() to exit(). (You can also disable
> the "wrong socket" check, but most likely you will not like the result).

I changed now to exit() rather than abort on the production machine. Perhaps this should be the default?

ELOG V3.1.4-2e1708b5