{"id":164605,"date":"2021-12-06T08:28:07","date_gmt":"2021-12-06T08:28:07","guid":{"rendered":"\/forum\/forums\/topic\/mpi-problem-when-running-system-coupling-on-linux-hpc-cluster\/"},"modified":"2022-01-11T13:46:37","modified_gmt":"2022-01-11T13:46:37","slug":"mpi-problem-when-running-system-coupling-on-linux-hpc-cluster","status":"closed","type":"topic","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/mpi-problem-when-running-system-coupling-on-linux-hpc-cluster\/","title":{"rendered":"(MPI?) problem when running System Coupling on Linux HPC cluster"},"content":{"rendered":"
\n
\n

Hi all,<\/p>\n

I'm running into troubles with my FSI simulations using Ansys System Coupling on a Linux Centos8 HPC cluster with openMPI. The SLURM environment is used to schedule the jobs. Ansys 2021R2 is used. My simulation runs fine on my own laptop, but gives an error message when running on the cluster. I will attach the error message in a comment, since it's too long to fit in the question section. Both Fluent as Mechanical do not give an error message before the system coupling process is interrupted. <\/p>\n

The debug information from system coupling shows that it is able to get the Fluent mesh and also the nodes and elements of the mechanical mesh, but the trace stops after obtaining the elements (see second command).<\/p>\n

\n
\nAnsys2021R2-FSI.7z
\n<\/a><\/p>\n","protected":false},"template":"","class_list":["post-164605","topic","type-topic","status-closed","hentry","topic-tag-2-way-fsi","topic-tag-cluster","topic-tag-hpc","topic-tag-linux","topic-tag-system-coupling"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t