RE: mpirun was unable to find the specified executable file

From: Vermaas, Joshua (Joshua.Vermaas_at_nrel.gov)
Date: Fri Aug 02 2019 - 12:16:11 CDT

Super basic question: but are you using an MPI executable? I've seen this error before if you are accidentally using a multicore binary with MPI, which can't possibly work.

-Josh

On 2019-08-02 10:36:02-06:00 owner-namd-l_at_ks.uiuc.edu wrote:

Thanks for the reply
I tried using namd2 instead of namd and the following error popped up
--------------------------------------------------------------------------------------------------------------------
Charm++: standalone mode (not using charmrun)
Charm++: standalone mode (not using charmrun)
Charm++> Running in Multicore mode: 1 threads
Charm++: standalone mode (not using charmrun)
Charm++: standalone mode (not using charmrun)
Charm++> Running in Multicore mode: 1 threads
Charm++> Running in Multicore mode: 1 threads
Charm++> Running in Multicore mode: 1 threads
--------------------------------------------------------------------------
Primary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 0 on node vasi exited on signal 11 (Segmentation fault).

-----------------------------------------------------------------------------------------------------------------------------
Its the tutorial file. in the tutorial, it says for 16 replicas and I changed it to 4 replicas and did the necessary changes in other files too.

On Fri, Aug 2, 2019 at 8:45 PM Roshan Shrestha <roshanpra_at_gmail.com<mailto:roshanpra_at_gmail.com>> wrote:
Using namd2 command instead of namd alone should solve the issue I guess.
Best regards

On Fri, 2 Aug 2019, 20:48 mariano spivak, <mariano_at_ks.uiuc.edu<mailto:mariano_at_ks.uiuc.edu>> wrote:
Hi, I believe that the problem is that the command that you want is not "namd".
Try in the terminal: which namd
If it does not find the command, then you might want to try "namd2" instead--_000_BYAPR09MB258440AF3D57EC70CBA5E4CEE4D90BYAPR09MB2584namp_--

This archive was generated by hypermail 2.1.6 : Tue Dec 10 2019 - 23:20:54 CST