<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">I’m using MPICH 3.3.2, Torque 5.1.1.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve discussed something like this with you guys before – is there any way to have MPICH shut down the
<o:p></o:p></p>
<p class="MsoNormal">entire job after a seg fault, rather than running forever? You’ve said that what really needs to be done
<o:p></o:p></p>
<p class="MsoNormal">is to locate and fix the bug causing it, which is right, but I’m just worried that a non-terminating job would
<o:p></o:p></p>
<p class="MsoNormal">be confusing to the user that encounters it, if some new unanticipated seg fault were generated in the future.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I know that I can’t put MPI_Finalize() or any non-async safe code in my signal handler. It helps a little bit<o:p></o:p></p>
<p class="MsoNormal">to print a backtrace from the signal handler (I know, I/O is also not safe).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is there anything else that can be done? Here are the MPICH error messages written some minutes after the
<o:p></o:p></p>
<p class="MsoNormal">seg fault occurs, when the job is ending and all of the good processes are calling MPI_Finalize().
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Kurt<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[proxy:0:0@n001.cluster.com] [proxy:1:0@n001.cluster.com] [proxy:3:0@n001.cluster.com] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878):
assert (!closed) failed<o:p></o:p></p>
<p class="MsoNormal">[proxy:4:0@n001.cluster.com] assert (!closed) failed<o:p></o:p></p>
<p class="MsoNormal">assert (!closed) failed<o:p></o:p></p>
<p class="MsoNormal">[proxy:0:0@n001.cluster.com] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): [proxy:1:0@n001.cluster.com] [proxy:3:0@n001.cluster.com] [proxy:5:0@n001.cluster.com] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): assert
(!closed) failed<o:p></o:p></p>
<p class="MsoNormal">HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): [proxy:6:0@n001.cluster.com] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): callback returned error status<o:p></o:p></p>
<p class="MsoNormal">[proxy:4:0@n001.cluster.com] [proxy:8:0@n001.cluster.com] callback returned error status<o:p></o:p></p>
<p class="MsoNormal">callback returned error status<o:p></o:p></p>
<p class="MsoNormal">[proxy:9:0@n001.cluster.com] assert (!closed) failed<o:p></o:p></p>
<p class="MsoNormal">HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): [proxy:0:0@n001.cluster.com] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): [proxy:1:0@n001.cluster.com] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): [proxy:3:0@n001.cluster.com]
[proxy:10:0@n001.cluster.com] [proxy:5:0@n001.cluster.com] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): assert (!closed) failed<o:p></o:p></p>
<p class="MsoNormal">main (pm/pmiserv/pmip.c:200): callback returned error status<o:p></o:p></p>
<p class="MsoNormal">main (pm/pmiserv/pmip.c:200): assert (!closed) failed<o:p></o:p></p>
<p class="MsoNormal">main (pm/pmiserv/pmip.c:200): HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): assert (!closed) failed<o:p></o:p></p>
<p class="MsoNormal">[proxy:6:0@n001.cluster.com] demux engine error waiting for event<o:p></o:p></p>
<p class="MsoNormal">[proxy:4:0@n001.cluster.com] demux engine error waiting for event<o:p></o:p></p>
<p class="MsoNormal">[proxy:8:0@n001.cluster.com] demux engine error waiting for event<o:p></o:p></p>
<p class="MsoNormal">callback returned error status<o:p></o:p></p>
<p class="MsoNormal">assert (!closed) failed<o:p></o:p></p>
<p class="MsoNormal">[proxy:9:0@n001.cluster.com] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): main (pm/pmiserv/pmip.c:200): HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): [proxy:5:0@n001.cluster.com] callback returned error status<o:p></o:p></p>
<p class="MsoNormal">[proxy:10:0@n001.cluster.com] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): callback returned error status<o:p></o:p></p>
<p class="MsoNormal">demux engine error waiting for event<o:p></o:p></p>
<p class="MsoNormal">main (pm/pmiserv/pmip.c:200): [proxy:8:0@n001.cluster.com] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): [proxy:7:0@n001.cluster.com] callback returned error status<o:p></o:p></p>
<p class="MsoNormal">[proxy:6:0@n001.cluster.com] demux engine error waiting for event<o:p></o:p></p>
<p class="MsoNormal">main (pm/pmiserv/pmip.c:200): callback returned error status<o:p></o:p></p>
<p class="MsoNormal">[proxy:9:0@n001.cluster.com] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): main (pm/pmiserv/pmip.c:200): demux engine error waiting for event<o:p></o:p></p>
<p class="MsoNormal">[proxy:10:0@n001.cluster.com] main (pm/pmiserv/pmip.c:200): assert (!closed) failed<o:p></o:p></p>
<p class="MsoNormal">demux engine error waiting for event<o:p></o:p></p>
<p class="MsoNormal">main (pm/pmiserv/pmip.c:200): demux engine error waiting for event<o:p></o:p></p>
<p class="MsoNormal">[proxy:7:0@n001.cluster.com] demux engine error waiting for event<o:p></o:p></p>
<p class="MsoNormal">HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): callback returned error status<o:p></o:p></p>
<p class="MsoNormal">[proxy:7:0@n001.cluster.com] main (pm/pmiserv/pmip.c:200): demux engine error waiting for event<o:p></o:p></p>
</div>
</body>
</html>