Hi, I used to have a similar problem with the MPI version while the serial one worked. In my case it was enough to export the LD_LIBRARY_PATH to point to where the libraries created during Nektar compilation ware. Best, Stan On 11.07.2016 19:10, Amitvikram Dutta wrote:

Hi all,

Recently I was made aware that there could be a possible problem with how nektar++ had been compiled on the cluster that I was trying to run it on. Apparently nektar++ had not been compiled with the MPI turned on with the result being that it was not parallelizing properly.

After I pointed this out to the system administrator he went on to fix this issue. After fixing this however, whenever I try to submit a job I get the following error

*mpirun has exited due to process rank 18 with PID 8273 on node pod16a5.ibb exiting improperly. There are two reasons this could occur:

1. this process did not call "init" before exiting, but others in the job did. This can cause a job to hang indefinitely while it waits for all processes to call "init". By rule, if one process calls "init", then ALL processes must call "init" prior to termination.

2. this process called "init", but exited without calling "finalize". By rule, all processes that call "init" MUST call "finalize" prior to exiting or it will be considered an "abnormal termination"

This may have caused other processes in the application to be terminated by signals sent by mpirun (as reported here).

* Note however, that when I try to run the same problem in serial mode there are no problems.

I was hoping someone could shed light on any well-known issues regarding this.

Sincerely, --

*Amitvikram Dutta*

*MASc Candidate** *

*Graduate Research Assistant *

*Okanagan CFD Laboratory*

*University of British Columbia | Okanagan Campus***

_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users