I was facing one of those cryptic MPI error messages on Ranger, where your job quits without any useful error message. It turns out that this parameter file had
CarpetIOHDF5::one_file_per_group = "yes" CarpetIOHDF5::out2D_vars = " ADMBase::gxx"
and CarpetIOHDF5 would try to loop over the group variables when just one of them was selected. As a result it has accessed memory address that it was not supposed to, consequently killing the job.
I have attached the stack back trace.