What does this error mean?

Kevin Van Workum vanw at tticluster.com
Mon Feb 4 15:19:46 EST 2008


Hi,

I managed to fix the problem. I had to get rid of all the <NULL string>
lines in the mpi libraries. I did this using:

# for f in `grep "<NULL string>" * | cut -f 3 -d ' '`; do sed -i 's/NULL
string/NULL_string/g' $f; done

That seemed to do the trick. Thanks for all your help.

Kevin

On 2/1/08, Supalov, Alexander <alexander.supalov at intel.com> wrote:
>
> Hi everybody,
>
> Looks like we need to have a short meeting to understand what's
> happening. What would you have time?
>
> Best regards.
>
> Alexander
>
> --
> Dr Alexander Supalov
> Intel GmbH
> Hermuelheimer Strasse 8a
> 50321 Bruehl, Germany
> Phone:          +49 2232 209034
> Mobile:          +49 173 511 8735
> Fax:              +49 2232 209029
>
>
> -----Original Message-----
> From: Kevin Van Workum [mailto:vanw at tticluster.com]
> Sent: Thursday, January 31, 2008 11:30 PM
> To: Thomas Zeiser
> Cc: Derbunovich, Andrey; Pete Wyckoff; Slavova, Gergana S; Supalov,
> Alexander; mpiexec at osc.edu
> Subject: Re: What does this error mean?
>
> On 1/30/08, Thomas Zeiser <thomas.zeiser at rrze.uni-erlangen.de> wrote:
> > Hi Andrey,
> > hi Kevin,
> >
> > On Wed, Jan 30, 2008 at 07:17:36PM +0300, Derbunovich, Andrey wrote:
> > > Kevin,
> > >
> > > Thank you. Actually we never test our library with this mpiexec
> version.
> >
> > we have Intel MPI 3.1.026 successfully running with torque-2.1.x
> > and Pete's mpiexec-0.82
> > (there are only sometimes timeout problem if quite large Infiniband
> > jobs start - but that's an other storry)
> >
> > > Did you able to use this mpiexec with earlier versions of the Intel
> MPI
> > > Library?
> > >
> > > Best regards,
> > > Andrey
> >
> > > > > > > > mpiexec: read_keyvals: keyval 1 key kvsname val
> > > > 53001.jman-spawn-0.
> > > > > > > > mpiexec: read_keyvals: keyval 2 key key val DAPL_PROVIDER.
> > > > > > > > mpiexec: read_keyvals: keyval 3 key value val <NULL.
> >
> > Kevin: what interconnect are you trying to use?
> >
> > as "DAPL_PROVIDER" appears here, it looks for me that you use
> > Infiniband or Myrinet and not plain ethernet - thus giving
> > additional potential for failures.
> >
> > Can you check if your job starts fine if you force Intel MPI to the
> > socks device by "export I_MPI_DEVICE=ssm".
> >
>
> I'm using plain Gbit ethernet. Still doesn't work with I_MPI_DEVICE=ssm.
>
> -- Kevin
> ---------------------------------------------------------------------
> Intel GmbH
> Dornacher Strasse 1
> 85622 Feldkirchen/Muenchen Germany
> Sitz der Gesellschaft: Feldkirchen bei Muenchen
> Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
> Registergericht: Muenchen HRB 47456 Ust.-IdNr.
> VAT Registration No.: DE129385895
> Citibank Frankfurt (BLZ 502 109 00) 600119052
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://email.osc.edu/pipermail/mpiexec/attachments/20080204/0460537b/attachment.htm


More information about the mpiexec mailing list