# Error in running CCTM

**URL:** <https://forum.cmascenter.org/t/error-in-running-cctm/1061>\
**Category:** CMAQ\
**Created:** [October 23, 2019, 1:57am UTC](https://forum.cmascenter.org/t/error-in-running-cctm/1061 "2019-10-23T01:57:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Catalyst2682](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@Catalyst2682](https://forum.cmascenter.org/u/Catalyst2682)\
**Post date:** [October 23, 2019, 1:57am UTC](https://forum.cmascenter.org/t/error-in-running-cctm/1061/1 "2019-10-23T01:57:28Z")

</div>

Dear @lizadams, @cjcoats, @bbaek, @wong.david-c, @dazhong.yin, @tlspero,

I got this error while running cctm. I earlier got the same error using openmpi but installed mpich-3.3.1. Yet, the same error still came up. Although, I still have the openmpi on my workstation. Do I need to uninstall the openmpi? What should I do to resolve this error, please? It’s been days I have been on this. Kindly help please.

Attached is the log file.

* * *

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 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

* * *

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)

## \*\*\* 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:29387] 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 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

* * *

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)

## \*\*\* 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:29388] 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 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

* * *

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)

## \*\*\* 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:29389] 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 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

* * *

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)

## \*\*\* 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:29390] 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 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

* * *

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)

## \*\*\* 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:29391] 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 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

* * *

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)

## \*\*\* 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:29392] 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 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

* * *

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)

## \*\*\* 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:29393] 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 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

* * *

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)

\*\*\* 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:29394] 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!  
0.008u 0.028s 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  
Wed Oct 23 09:45:06 CST 2019  
exit

Thanks in anticipation.

Catalyst

[run.cctm.txt](https://forum.cmascenter.org/uploads/short-url/vn39OCatdQINtl44wEl9mtbUUpz.txt) (1.5 MB)

---

<div class="post-metadata">

**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, 6:39pm UTC](https://forum.cmascenter.org/t/error-in-running-cctm/1061/2 "2019-11-07T18:39:09Z")

</div>

Were you able to resolve this issue?  
If not, please send the output of these commands  
It may be that you need to set your LD\_LIBRARY\_PATH to include your openMPI install directory.

```auto
mpirun --version
mpiCC --showme:compile
mpiCC --showme:link

```

---

<div class="post-metadata">

**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:35pm UTC](https://forum.cmascenter.org/t/error-in-running-cctm/1061/3 "2019-11-08T18:35:39Z")

</div>

Dear @lizadams,

Yeah, I have resolved it and it’s working perfectly now.

Thanks a lot and regards,

Catalyst