Exodus error

[Emmanuel-324]

Check these boxes if you have followed the posting rules.

• Q&A General is the most appropriate section for my question
• I have consulted the posting Guidelines on the Discussions front page
• I have searched the Discussions forum and my question has not been asked before
• I have searched the MOOSE website and the documentation does not answer my question
• I have formatted my post following the posting guidelines (screenshots as a last resort, triple back quotes around pasted text)

Question

Whenever I add 'exodus = true 'to my input script I get this error

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 19778 on node tc124 exited on signal 11 (Segmentation fault).

But without it everything works fine. Any reason?

Blow is my submission script

#!/bin/bash                                                                     
#SBATCH --job-name   Thermal_eigenstrain_test1                                            
#SBATCH --out  Thermal_eigenstrain_test1.out        
#SBATCH --nodes 1                                                              
#SBATCH --ntasks 2
#SBATCH --cpus-per-task 8
#SBATCH --account amcorrosion                                                  
##SBATCH --partition normal_q                                                   
#SBATCH --time=64:00:00    
##SBATCH --mem=gpu:pascal:4                                                     
#SBATCH --export=NONE # this makes sure the compute environment is clean        
#SBATCH --mail-user [email protected]
#SBATCH --mail-type=begin
#SBATCH --mail-type=end


module reset
module load apps site/tinkercliffs/easybuild/setup
module load apps site/tinkercliffs-rome/easybuild/setup
module load OpenMPI CMake
export CC=mpicc CXX=mpicxx FC=mpif90 F90=mpif90 F77=mpif77
mamba activate python-stack


cd "${submitdir}"
#rm kks_multiphase_largescale_large_csv*
#rm kks_multiphase_largescale_large_out.e*
mpirun --mca orte_base_help_aggregate 0 -np 2 /home/emmanuel324/projects/belson/belson-opt  -i  Thermal_eigenstrain_test1.i

[GiudGiud]

Hello

There s unfortunately not enough information to know.
You will need to use a debugger to get a backtrace. This is fairly easy for a seg fault, though a little harder in parallel unfortunately.
If you can reproduce the error in serial, it would make things easier for you

https://mooseframework.inl.gov/application_development/debugging.html

[Emmanuel-324]

Is it possible to copy and add the installed folder from the MOOSE repo and add to mine?

[Emmanuel-324]

@milljm @GiudGiud libmesh_diagnostic.log
config.log

[Emmanuel-324]

Below is the response from one of my cluster admins.

After maintenance, all the login and compute nodes in the cluster except for the 10 DGX GPU nodes were reprovisioned with Rocky 9. ARC decided that the software packages should be rebuilt from the ground up for the new OS.
 
 
Yes, please use Miniforge3:
 
module load Miniforge3/24.1.2-0
 
You will be able to install MOOSE via conda virtual environment in ARC clusters:
 
You can make a Conda Virtual Environment first:
conda create -p ~/path/to/env/
 
After activating it,
source activate ~/path/to/env/
 
and installing the version of python you need,
conda install python=XXX
 
Then you will be able to install moose according to the section "Install MOOSE" in this page:
https://mooseframework.inl.gov/getting_started/installation/conda.html
 
Regarding virtual environment, please find information here:
https://www.docs.arc.vt.edu/usage/miniforge-virtual-environments.html
 
 
Let me know if it helps.
 

[Emmanuel-324]

Following the conda environment installation worked