[MOAB-dev] buildbot failure in Fathom on moab-par

[James Porter]

There is really something very bizarre happening on gnep. Every once in a while the buildbot master dies (and my mpd with it), though the slave and the SVN poller still appear to be running. Time to talk to systems, I guess.

- Jim

On 09/30/10, moab-dev at mcs.anl.gov wrote:

> The Fathomatic has detected a failed build of moab-par on Fathom.
> Full details are available at:
>  http://gnep.mcs.anl.gov:8010/builders/moab-par/builds/287
> 
> Buildbot URL: http://gnep.mcs.anl.gov:8010/
> 
> Buildslave for this Build: gnep
> 
> Build Reason: The Nightly scheduler named 'nightly' triggered this build
> Build Source Stamp: None
> Blamelist: 
> 
> BUILD FAILED: failed test
> 
> LOG EXCERPT:
> the MPICH2 Installation Guide.
> FAIL: uber_parallel_test
> mpiexec_gnep.mcs.anl.gov: cannot connect to local mpd (/tmp/mpd2.console_jvporter); possible causes:
>   1. no mpd is running on this host
>   2. an mpd is running but was started without a "console" (-n option)
> In case 1, you can start an mpd on this host with:
>     mpd &
> and you will be able to run jobs just on this host.
> For more details on starting mpds on a set of hosts, see
> the MPICH2 Installation Guide.
> FAIL: scdtest
> mpiexec_gnep.mcs.anl.gov: cannot connect to local mpd (/tmp/mpd2.console_jvporter); possible causes:
>   1. no mpd is running on this host
>   2. an mpd is running but was started without a "console" (-n option)
> In case 1, you can start an mpd on this host with:
>     mpd &
> and you will be able to run jobs just on this host.
> For more details on starting mpds on a set of hosts, see
> the MPICH2 Installation Guide.
> FAIL: pcomm_serial
> mpiexec_gnep.mcs.anl.gov: cannot connect to local mpd (/tmp/mpd2.console_jvporter); possible causes:
>   1. no mpd is running on this host
>   2. an mpd is running but was started without a "console" (-n option)
> In case 1, you can start an mpd on this host with:
>     mpd &
> and you will be able to run jobs just on this host.
> For more details on starting mpds on a set of hosts, see
> the MPICH2 Installation Guide.
> FAIL: parallel_hdf5_test
> mpiexec_gnep.mcs.anl.gov: cannot connect to local mpd (/tmp/mpd2.console_jvporter); possible causes:
>   1. no mpd is running on this host
>   2. an mpd is running but was started without a "console" (-n option)
> In case 1, you can start an mpd on this host with:
>     mpd &
> and you will be able to run jobs just on this host.
> For more details on starting mpds on a set of hosts, see
> the MPICH2 Installation Guide.
> FAIL: mhdf_parallel
> mpiexec_gnep.mcs.anl.gov: cannot connect to local mpd (/tmp/mpd2.console_jvporter); possible causes:
>   1. no mpd is running on this host
>   2. an mpd is running but was started without a "console" (-n option)
> In case 1, you can start an mpd on this host with:
>     mpd &
> and you will be able to run jobs just on this host.
> For more details on starting mpds on a set of hosts, see
> the MPICH2 Installation Guide.
> FAIL: parallel_write_test
> ===================
> 8 of 8 tests failed
> ===================
> 
> sincerely,
>  -The Fathomatic