-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test simulation issue #88
Comments
can you share some more info:
|
Thanks for reply Takis, The operating system is Ubuntu 22.04 and tried compilation from source code, not using docker. I would greatly appreciate it if you could provide your comments on it. |
I assume that there might be an issue with the parmetis since this is when the code crashes.
|
I tried 3d example case as well, but the same error happens. I'm curious about where the error comes. Is the error from compilation with ParMETIS? |
I got the same error with Gnu compiler and OpenMPI |
Hi,
I am trying to run an example simulation after compilation.
It seems there is an issue with ParMETIS related to MPI segmentation.
I would greatly appreciate it if someone could guide me on how to resolve this issue.
I've attached the error message below.
ucns3d_p will run on 2 MPI tasks.
Authorization required, but no authorization protocol specified
Authorization required, but no authorization protocol specified
i read the bleed BC
RESTARTING 0 0.0000000000000000 0
[kucfd-System:909616] *** An error occurred in MPI_Comm_rank
[kucfd-System:909616] *** reported by process [1937178625,0]
[kucfd-System:909616] *** on communicator MPI_COMM_WORLD
[kucfd-System:909616] *** MPI_ERR_COMM: invalid communicator
[kucfd-System:909616] *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
[kucfd-System:909616] *** and potentially your MPI job)
[kucfd-System:909609] 1 more process has sent help message help-mpi-errors.txt / mpi_errors_are_fatal
[kucfd-System:909609] Set MCA parameter "orte_base_help_aggregate" to 0 to see all help / error messages
The text was updated successfully, but these errors were encountered: