<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Debugging problems with mpiexec.hydra in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/Debugging-problems-with-mpiexec-hydra/m-p/1095065#M5089</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have provided an ifort + intelMPI build of a CFD solver to a customer using the Intel MPI runtime environment. &amp;nbsp; The customer's cluster uses a SGE scheduler. &amp;nbsp; &amp;nbsp;The user is attempting to run on a single node with mpirun using the default Hydra process manager, but the job hangs without any meaningful error messages. &amp;nbsp; &amp;nbsp;I instructed the user to run with I_MPI_HYDRA_DEBUG=1 and I_MPI_DEBUG=6 but I don't see anything unusual or unexpected in the output. &amp;nbsp; The last lines in the output are the following:&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;[mpiexec@compute-31] Launch arguments: /cm/shared/apps/sge/current/bin/linux-x64/qrsh -inherit -V compute-31.cm.cluster /a/fine/10.2/fine102/LINUX/_mpi/_impi5.0.3/intel64/bin/pmi_proxy --control-port compute-31.cm.cluster:46905 --debug --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk user --launcher sge --demux poll --pgid 0 --enable-stdin 1 --retries 10 --control-code 1687715305 --usize -2 --proxy-id 0&amp;nbsp;&lt;BR /&gt;
	[mpiexec@compute-31] STDIN will be redirected to 1 fd(s): 9&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;I ran a similar test on another cluster which worked correctly. &amp;nbsp;The following lines with the [proxy:0:0@nmc-0066] prefix appear directly after the last lines reported by the customer cluster.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;[mpiexec@nmc-0066] STDIN will be redirected to 1 fd(s): 9&lt;BR /&gt;
	[proxy:0:0@nmc-0066] Start PMI_proxy 0&lt;BR /&gt;
	[proxy:0:0@nmc-0066] STDIN will be redirected to 1 fd(s): 9&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;From these tests I think the hang is coming from pmi_proxy. &amp;nbsp; Are there any additional verbose or debugging modes that could help identify the problem on the user's cluster? &amp;nbsp;&lt;/P&gt;

&lt;P&gt;Thank your for your help,&lt;/P&gt;

&lt;P&gt;-David&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 14 Jun 2016 00:17:46 GMT</pubDate>
    <dc:creator>gutzwiller__david</dc:creator>
    <dc:date>2016-06-14T00:17:46Z</dc:date>
    <item>
      <title>Debugging problems with mpiexec.hydra</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Debugging-problems-with-mpiexec-hydra/m-p/1095065#M5089</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have provided an ifort + intelMPI build of a CFD solver to a customer using the Intel MPI runtime environment. &amp;nbsp; The customer's cluster uses a SGE scheduler. &amp;nbsp; &amp;nbsp;The user is attempting to run on a single node with mpirun using the default Hydra process manager, but the job hangs without any meaningful error messages. &amp;nbsp; &amp;nbsp;I instructed the user to run with I_MPI_HYDRA_DEBUG=1 and I_MPI_DEBUG=6 but I don't see anything unusual or unexpected in the output. &amp;nbsp; The last lines in the output are the following:&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;[mpiexec@compute-31] Launch arguments: /cm/shared/apps/sge/current/bin/linux-x64/qrsh -inherit -V compute-31.cm.cluster /a/fine/10.2/fine102/LINUX/_mpi/_impi5.0.3/intel64/bin/pmi_proxy --control-port compute-31.cm.cluster:46905 --debug --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk user --launcher sge --demux poll --pgid 0 --enable-stdin 1 --retries 10 --control-code 1687715305 --usize -2 --proxy-id 0&amp;nbsp;&lt;BR /&gt;
	[mpiexec@compute-31] STDIN will be redirected to 1 fd(s): 9&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;I ran a similar test on another cluster which worked correctly. &amp;nbsp;The following lines with the [proxy:0:0@nmc-0066] prefix appear directly after the last lines reported by the customer cluster.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;[mpiexec@nmc-0066] STDIN will be redirected to 1 fd(s): 9&lt;BR /&gt;
	[proxy:0:0@nmc-0066] Start PMI_proxy 0&lt;BR /&gt;
	[proxy:0:0@nmc-0066] STDIN will be redirected to 1 fd(s): 9&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;From these tests I think the hang is coming from pmi_proxy. &amp;nbsp; Are there any additional verbose or debugging modes that could help identify the problem on the user's cluster? &amp;nbsp;&lt;/P&gt;

&lt;P&gt;Thank your for your help,&lt;/P&gt;

&lt;P&gt;-David&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jun 2016 00:17:46 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Debugging-problems-with-mpiexec-hydra/m-p/1095065#M5089</guid>
      <dc:creator>gutzwiller__david</dc:creator>
      <dc:date>2016-06-14T00:17:46Z</dc:date>
    </item>
    <item>
      <title>David,</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Debugging-problems-with-mpiexec-hydra/m-p/1095066#M5090</link>
      <description>&lt;P&gt;David,&lt;/P&gt;

&lt;P&gt;Those&amp;nbsp;options enable&amp;nbsp;the full debug information that we provide.&amp;nbsp; If you would like assistance with resolving this issue, can you submit a ticket at Intel® Premier Support or provide the full Hydra debug output?&lt;/P&gt;

&lt;P&gt;James.&lt;BR /&gt;
	Intel Developer Support&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2016 19:03:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Debugging-problems-with-mpiexec-hydra/m-p/1095066#M5090</guid>
      <dc:creator>James_T_Intel</dc:creator>
      <dc:date>2016-06-23T19:03:32Z</dc:date>
    </item>
  </channel>
</rss>

