# CCTM build error **URL:** \ **Category:** Compiling\ **Created:** [November 6, 2018, 3:49am UTC](https://forum.cmascenter.org/t/cctm-build-error/396 "2018-11-06T03:49:53Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![epenning](https://avatars.discourse-cdn.com/v4/letter/e/da6949/32.png) [@epenning](https://forum.cmascenter.org/u/epenning)\ **Post date:** [November 6, 2018, 3:49am UTC](https://forum.cmascenter.org/t/cctm-build-error/396/1 "2018-11-06T03:49:53Z")
Hi all, I’m trying to build CCTM in CMAQv5.2.1 using gcc version 4.8.5 and getting the following error: x\_ppm.F:261.132: \_W0, DRCN\_E) 1 Error: There is no specific subroutine for the generic ‘noop\_comm’ at (1) x\_ppm.F:262.132: \_W1, DRCN\_W) 1 Error: There is no specific subroutine for the generic ‘noop\_comm’ at (1) make: \*\*\* [x\_ppm.o] Error 1 **ERROR** while running make command Online it looks like this error occurs when the arguments passed into a function are not of the correct type, e.g. an array where there should be a scalar. I found the problematic SUBST\_COMM function in x\_ppm.F in $CMAQ\_REPO/CCTM/src/hadv/yamo, but am not sure how or if I should edit it. Or, do you think this could be an issue with my compiler? Thank you, Elyse ---
**Author:** ![cgnolte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/cgnolte/32/53_2.png) [@cgnolte](https://forum.cmascenter.org/u/cgnolte)\ **Post date:** [November 7, 2018, 1:40pm UTC](https://forum.cmascenter.org/t/cctm-build-error/396/2 "2018-11-07T13:40:46Z")
The serial build is broken in v5.2.1 (both gcc and intel compilers). It has been fixed in v5.3 beta, which is available on GitHub. Alternatively, compile in parallel by uncommenting the line “set ParOpt” in the build script. ---
**Author:** ![Catalyst2682](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@Catalyst2682](https://forum.cmascenter.org/u/Catalyst2682)\ **Post date:** [October 17, 2019, 4:47pm UTC](https://forum.cmascenter.org/t/cctm-build-error/396/3 "2019-10-17T16:47:09Z")
Dear @cjcoats , @lizadams @cgnolte, @wong.david-c, @dazhong.yin I got this error while building CCTM: -DSUBST\_GLOBAL\_LOGICAL=SE\_GLOBAL\_LOGICAL -DSUBST\_LOOP\_INDEX=SE\_LOOP\_INDEX -DSUBST\_SUBGRID\_INDEX=SE\_SUBGRID\_INDEX -DSUBST\_PE\_COMM="./PE\_COMM.EXT" -DSUBST\_CONST="./CONST.EXT" -DSUBST\_FILES\_ID="./FILES\_CTM.EXT" -DSUBST\_EMISPRM="./EMISPRM.EXT" -DSUBST\_RXCMMN="/home/catalyst/Desktop/Build\_WRF/CMAQ-5.2/CCTM/src/MECHS/saprc99\_ae6\_aq/RXCM.EXT" -DSUBST\_RXDATA="/home/catalyst/Desktop/Build\_WRF/CMAQ-5.2/CCTM/src/MECHS/saprc99\_ae6\_aq/RXDT.EXT" -DSUBST\_PACTL\_ID="./PA\_CTL.EXT" -DSUBST\_PACMN\_ID="./PA\_CMN.EXT" -DSUBST\_PADAT\_ID="/PA\_DAT.EXT" -DSUBST\_MPI=“mpif.h” DEPV\_DEFN.F DEPV\_DEFN.F:147:12: ``` USE RXNS_DATA ! chemical mechanism data 1 ``` Fatal Error: Can’t open module file ‘rxns\_data.mod’ for reading at (1): No such file or directory compilation terminated. Makefile:402: recipe for target ‘DEPV\_DEFN.o’ failed make: \*\*\* [DEPV\_DEFN.o] Error 1 **ERROR** while running make command else if ( 0 ) then endif mv Makefile Makefile.gcc7.3.0 if ( -e Makefile.gcc7.3.0 && -e Makefile ) rm Makefile ln -s Makefile.gcc7.3.0 Makefile if ( 0 != 0 ) then if ( -e /home/catalyst/Desktop/Build\_WRF/CMAQ-5.2/CCTM/scripts/BLD\_CCTM\_36km\_gcc7.3.0/CCTM\_36km.cfg ) then mv CCTM\_36km.cfg.bld /home/catalyst/Desktop/Build\_WRF/CMAQ-5.2/CCTM/scripts/BLD\_CCTM\_36km\_gcc7.3.0/CCTM\_36km.cfg exit Kindly help. Thanks Catalyst ---
**Author:** ![wong.david-c](https://avatars.discourse-cdn.com/v4/letter/w/bcef8e/32.png) [@wong.david-c](https://forum.cmascenter.org/u/wong.david-c)\ **Post date:** [October 17, 2019, 6:11pm UTC](https://forum.cmascenter.org/t/cctm-build-error/396/4 "2019-10-17T18:11:58Z")
Hi Catalyst, It looks like (correct me if I am wrong) you are trying to build a coupled model but compiling the model with the bldit script. With the two-way model, you can’t do that. ---
**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\ **Post date:** [October 17, 2019, 6:39pm UTC](https://forum.cmascenter.org/t/cctm-build-error/396/5 "2019-10-17T18:39:50Z")
Is there a `rxns_data.mod` in your build-directory? If not, do _make RXNS\_DATA\_MODULE.o_ and try _make_ again. ---
**Author:** ![Catalyst2682](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@Catalyst2682](https://forum.cmascenter.org/u/Catalyst2682)\ **Post date:** [October 18, 2019, 12:29am UTC](https://forum.cmascenter.org/t/cctm-build-error/396/6 "2019-10-18T00:29:40Z")
Thanks for your response. However, I’m not building a coupled model or two-way model. Catalyst ---
**Author:** ![Catalyst2682](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@Catalyst2682](https://forum.cmascenter.org/u/Catalyst2682)\ **Post date:** [October 18, 2019, 12:34am UTC](https://forum.cmascenter.org/t/cctm-build-error/396/7 "2019-10-18T00:34:13Z")
Thanks for the response. There’s no rxns\_data.mod in my build\_directory. When I tried to do what you suggested, it says “No rule to make target…” ---
**Author:** ![wong.david-c](https://avatars.discourse-cdn.com/v4/letter/w/bcef8e/32.png) [@wong.david-c](https://forum.cmascenter.org/u/wong.david-c)\ **Post date:** [October 18, 2019, 12:35pm UTC](https://forum.cmascenter.org/t/cctm-build-error/396/8 "2019-10-18T12:35:37Z")
Hi Catalyst, Could you remove all \*.o \*.mod and try it again and send me the log file that captures the entire compiling process as well as the Makefile? ---
**Author:** ![Catalyst2682](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@Catalyst2682](https://forum.cmascenter.org/u/Catalyst2682)\ **Post date:** [October 21, 2019, 6:42am UTC](https://forum.cmascenter.org/t/cctm-build-error/396/9 "2019-10-21T06:42:04Z")
Dear @wong.david-c, @lizadams , @bbaek, @cjcoats, @dazhong.yin , @tlspero , I have solved the above error. However, I got the error below while running cctm model: ls -l /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc -rwxr-xr-x 1 catalyst catalyst 10970696 Oct 21 00:04 /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc size /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc text data bss dec hex filename 5106669 4544560 7101288 16752517 ff9f85 /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc unlimit limit cputime unlimited filesize unlimited datasize unlimited stacksize unlimited coredumpsize unlimited memoryuse unlimited vmemoryuse unlimited descriptors 4096 memorylocked 16384 kbytes maxproc 63329 maxlocks unlimited maxsignal 63329 maxmessage 819200 maxnice 0 maxrtprio 0 maxrttime unlimited set MPI = /home/catalyst/Desktop/Build\_WRF/LIBRARIES/openmpi/bin set TASKMAP = /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/machines cat /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/machines n001:8 set MPIRUN = /home/catalyst/Desktop/Build\_WRF/LIBRARIES/openmpi/bin/mpirun /home/catalyst/Desktop/Build\_WRF/LIBRARIES/openmpi/bin/mpirun -n 8 /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc /home/catalyst/Desktop/Build\_WRF/LIBRARIES/openmpi/bin/mpirun: Error: unknown option “-n” 0.001u 0.000s 0:00.00 0.0% 0+0k 0+0io 0pf+0w mkdir -p /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/cctm\_36km/logs/2016031 mv: No match. @ i = 30 + 1 end while ( 31 \< 31 ) date Mon Oct 21 14:35:11 CST 2019 exit The last section of the log file is posted above. I use openmpi. Thanks in anticipation. Catalyst ---
**Author:** ![Catalyst2682](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@Catalyst2682](https://forum.cmascenter.org/u/Catalyst2682)\ **Post date:** [October 21, 2019, 7:46am UTC](https://forum.cmascenter.org/t/cctm-build-error/396/10 "2019-10-21T07:46:24Z")
@wong.david-c, @lizadams, @dazhong.yin , @bbaek , Below is the last part of my CCTM script: #\> Executable call for multiple PE, set location of MPIRUN script #set MPIRUN = /usr/bin/mpiexec set MPI = /home/catalyst/Desktop/Build\_WRF/LIBRARIES/openmpi/bin #set TASKMAP = $BASE/machines #cat $TASKMAP set MPIRUN = $MPI/mpirun #time $MPIRUN -np $NPROCS $BLD/$EXEC #nohup time $MPIRUN -n $NPROCS WORKDIR/{EXEC}.sh \< /dev/null nohup time $MPIRUN --np $NPROCS BLD/{EXEC} \< /dev/null # time mpirun -r ssh -np $NPROCS $BLD/$EXEC #set MPIRUN = /public/software/mpi/mpich/3.2/intel/bin/mpiexec #set TASKMAP = $BASE/machines #set TASKMAP = /home/catalyst/Desktop/Build\_WRF/CMAQ-5.2/CCTM/scripts/machines #cat $TASKMAP # time $MPIRUN -machinefile $TASKMAP -np $NPROCS $BASE/$EXEC.sh \< /dev/null # time mpirun -np $NPROCS $BASE/$EXEC.sh # time $MPIRUN -launcher rsh -launcher-exec /usr/bin/rsh -f $TASKMAP -n $NPROCS BASE/{EXEC}.sh \< /dev/null #nohup time $MPIRUN -n $NPROCS WORKDIR/{EXEC}.sh \< /dev/null #nohup time $MPIRUN -n $NPROCS BASE/{EXEC}.sh \< /dev/null # ibrun BASE/{EXEC} -envall mkdir -p {OUTDIR}/logs/{STDATE} mv ./CTM\_LOG\_???.{CTM\_APPL} {OUTDIR}/logs/${STDATE} #setenv NEW\_START true # gzip ${EMIS\_1} @ i = $i + 1 end date exit Thanks Catalyst ---
**Author:** ![Catalyst2682](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@Catalyst2682](https://forum.cmascenter.org/u/Catalyst2682)\ **Post date:** [October 22, 2019, 2:14am UTC](https://forum.cmascenter.org/t/cctm-build-error/396/11 "2019-10-22T02:14:32Z")
@lizadams, @bbaek, @cjcoats, @tlspero, @wong.david-c, @hogrefe.christian , @cgnolte, @eyortizd This is the recent error I got: ## ls -l /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc -rwxr-xr-x 1 catalyst catalyst 11193024 Oct 22 14:24 /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc size /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc text data bss dec hex filename 4913497 4758192 7102728 16774417 fff511 /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc unlimit limit cputime unlimited filesize unlimited datasize unlimited stacksize unlimited coredumpsize unlimited memoryuse unlimited vmemoryuse unlimited descriptors 4096 memorylocked 16384 kbytes maxproc 63329 maxlocks unlimited maxsignal 63329 maxmessage 819200 maxnice 0 maxrtprio 0 maxrttime unlimited set MPIRUN = mpiexec set TASKMAP = /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/machines cat /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/machines n001:8 mpirun -np 8 /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc.sh mpirun was unable to launch the specified application as it could not access or execute an executable: Executable: /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/BLD\_saprc99\_ae6\_aq/CCTM\_saprc99\_ae6\_aq\_Linux4\_x86\_64gcc.sh Node: catalyst-Precision-Tower-3620 ## while attempting to start process rank 0. 8 total processes failed to start 0.014u 0.011s 0:00.02 100.0% 0+0k 0+16408io 4pf+0w mkdir -p /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/cctm\_36km/logs/2016031 mv: No match. @ i = 30 + 1 end while ( 31 \< 31 ) date Tue Oct 22 17:14:35 CST 2019 exit It seems the problem is due to openmpi. Your help will be greatly appreciated. Thanks and regards. Below is the updated error I got: It looks like orte\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_init failed –\> Returned value Error (-1) instead of ORTE\_SUCCESS ## \*\*\* An error occurred in MPI\_Init \*\*\* on a NULL communicator \*\*\* MPI\_ERRORS\_ARE\_FATAL (processes in this communicator will now abort, \*\*\* and potentially your MPI job) [catalyst-Precision-Tower-3620:00824] Local abort before MPI\_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! It looks like opal\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during opal\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_shmem\_base\_select failed –\> Returned value -1 instead of OPAL\_SUCCESS * * * It looks like MPI\_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI\_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## ompi\_mpi\_init: ompi\_rte\_init failed –\> Returned “Error” (-1) instead of “Success” (0) * * * It looks like orte\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_init failed –\> Returned value Error (-1) instead of ORTE\_SUCCESS ## \*\*\* An error occurred in MPI\_Init \*\*\* on a NULL communicator \*\*\* MPI\_ERRORS\_ARE\_FATAL (processes in this communicator will now abort, \*\*\* and potentially your MPI job) [catalyst-Precision-Tower-3620:00825] Local abort before MPI\_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! It looks like opal\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during opal\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_shmem\_base\_select failed –\> Returned value -1 instead of OPAL\_SUCCESS * * * It looks like MPI\_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI\_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## ompi\_mpi\_init: ompi\_rte\_init failed –\> Returned “Error” (-1) instead of “Success” (0) * * * It looks like orte\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_init failed –\> Returned value Error (-1) instead of ORTE\_SUCCESS ## \*\*\* An error occurred in MPI\_Init \*\*\* on a NULL communicator \*\*\* MPI\_ERRORS\_ARE\_FATAL (processes in this communicator will now abort, \*\*\* and potentially your MPI job) [catalyst-Precision-Tower-3620:00826] Local abort before MPI\_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! It looks like opal\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during opal\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_shmem\_base\_select failed –\> Returned value -1 instead of OPAL\_SUCCESS * * * It looks like MPI\_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI\_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## ompi\_mpi\_init: ompi\_rte\_init failed –\> Returned “Error” (-1) instead of “Success” (0) * * * It looks like orte\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_init failed –\> Returned value Error (-1) instead of ORTE\_SUCCESS ## \*\*\* An error occurred in MPI\_Init \*\*\* on a NULL communicator \*\*\* MPI\_ERRORS\_ARE\_FATAL (processes in this communicator will now abort, \*\*\* and potentially your MPI job) [catalyst-Precision-Tower-3620:00827] Local abort before MPI\_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! It looks like opal\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during opal\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_shmem\_base\_select failed –\> Returned value -1 instead of OPAL\_SUCCESS * * * It looks like MPI\_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI\_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## ompi\_mpi\_init: ompi\_rte\_init failed –\> Returned “Error” (-1) instead of “Success” (0) * * * It looks like orte\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_init failed –\> Returned value Error (-1) instead of ORTE\_SUCCESS ## \*\*\* An error occurred in MPI\_Init \*\*\* on a NULL communicator \*\*\* MPI\_ERRORS\_ARE\_FATAL (processes in this communicator will now abort, \*\*\* and potentially your MPI job) [catalyst-Precision-Tower-3620:00828] Local abort before MPI\_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! It looks like opal\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during opal\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_shmem\_base\_select failed –\> Returned value -1 instead of OPAL\_SUCCESS * * * It looks like MPI\_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI\_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## ompi\_mpi\_init: ompi\_rte\_init failed –\> Returned “Error” (-1) instead of “Success” (0) * * * It looks like orte\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_init failed –\> Returned value Error (-1) instead of ORTE\_SUCCESS ## \*\*\* An error occurred in MPI\_Init \*\*\* on a NULL communicator \*\*\* MPI\_ERRORS\_ARE\_FATAL (processes in this communicator will now abort, \*\*\* and potentially your MPI job) [catalyst-Precision-Tower-3620:00829] Local abort before MPI\_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! It looks like opal\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during opal\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_shmem\_base\_select failed –\> Returned value -1 instead of OPAL\_SUCCESS * * * It looks like MPI\_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI\_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## ompi\_mpi\_init: ompi\_rte\_init failed –\> Returned “Error” (-1) instead of “Success” (0) * * * ## Primary job terminated normally, but 1 process returned a non-zero exit code… Per user-direction, the job has been aborted. * * * It looks like orte\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_init failed –\> Returned value Error (-1) instead of ORTE\_SUCCESS ## \*\*\* An error occurred in MPI\_Init \*\*\* on a NULL communicator \*\*\* MPI\_ERRORS\_ARE\_FATAL (processes in this communicator will now abort, \*\*\* and potentially your MPI job) [catalyst-Precision-Tower-3620:00830] Local abort before MPI\_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! It looks like opal\_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during opal\_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## opal\_shmem\_base\_select failed –\> Returned value -1 instead of OPAL\_SUCCESS * * * It looks like MPI\_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI\_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here’s some additional information (which may only be relevant to an Open MPI developer): ## ompi\_mpi\_init: ompi\_rte\_init failed –\> Returned “Error” (-1) instead of “Success” (0) * * * mpirun detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: ## Process name: [[25693,1],0] Exit code: 1 mkdir -p /home/catalyst/Desktop/Build\_WRF/CMAQv5.0.2/scripts/cctm/cctm\_36km/logs/2016031 mv: No match. @ i = 30 + 1 end while ( 31 \< 31 ) date Tue Oct 22 09:51:15 CST 2019 exit Kindly help, please. It seems its an openmpi problem. Thanks Catalyst ---
**Author:** ![lizadams](https://avatars.discourse-cdn.com/v4/letter/l/49beb7/32.png) [@lizadams](https://forum.cmascenter.org/u/lizadams)\ **Post date:** [November 7, 2019, 4:05pm UTC](https://forum.cmascenter.org/t/cctm-build-error/396/12 "2019-11-07T16:05:12Z")
The Error is here: Error: unknown option “-n” Based on this, it looks like your mpirun command is expecting a different option to specify the number of processors. Please change the command to use -np rather than -n ---
**Author:** ![Catalyst2682](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@Catalyst2682](https://forum.cmascenter.org/u/Catalyst2682)\ **Post date:** [November 8, 2019, 6:33pm UTC](https://forum.cmascenter.org/t/cctm-build-error/396/13 "2019-11-08T18:33:45Z")
@lizadams, I have resolved it and it’s working perfectly now. Thanks and regards, Catalyst