I’m not sure why this would be happening. These error outputs go through the
“show_help” functionality, and we specifically target it at stderr:
/* create an output stream for us */
OBJ_CONSTRUCT(&lds, opal_output_stream_t);
lds.lds_want_stderr = true;
orte_help_output = opal_outp
Dear list readers,
I have some problems with OpenMPI 3.1.1. In some node combos, I got the error
(libibverbs: GRH is mandatory For RoCE address handle; *** Error in
`/apps/brussel/CO7/ivybridge-ib/software/OpenMPI/3.1.1-GCC-7.3.0-2.30/bin/orted':
double free or corruption (out): 0x2aaab4001
It sounds like what you’re asking is “how do I get the best performance from
Open MPI in AWS?”.
The TCP BTL is your best option for performance in AWS. RoCE is going to be a
bunch of work to get setup, and you’ll still end up with host processing of
every packet. There are a couple simple ins
I investigated a this a bit and found that the (latest ?) v3 branches
have the expected behavior
(e.g. the error messages is sent to stderr)
Since it is very unlikely Open MPI 2.1 will ever be updated, I can
simply encourage you to upgrade to a newer Open MPI version.
Latest fully supported
Gilles Gouaillardet wrote:
I investigated a this a bit and found that the (latest ?) v3 branches
have the expected behavior
(e.g. the error messages is sent to stderr)
Since it is very unlikely Open MPI 2.1 will ever be updated, I can
simply encourage you to upgrade to a newer Open MPI versi
It seems I got it wrong :-(
Can you please give the attached patch a try ?
FWIW, an other option would be to opal_output(orte_help_output, ...) but
we would have to make orte_help_output "public first.
Cheers,
Gilles
On 9/11/2018 11:14 AM, emre brookes wrote:
Gilles Gouaillardet wro
Looks like there is a place in orte/mca/state/state_base_fns.c:850 that also
outputs to orte_clean_output instead of using show_help. Outside of those two
places, everything else seems to go to show_help.
> On Sep 10, 2018, at 8:58 PM, Gilles Gouaillardet wrote:
>
> It seems I got it wrong :-
