Skip to content
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

Pool run_batch error #3532

Closed
AnsysDeveloper opened this issue Oct 31, 2024 · 1 comment
Closed

Pool run_batch error #3532

AnsysDeveloper opened this issue Oct 31, 2024 · 1 comment

Comments

@AnsysDeveloper
Copy link

I am using MapdlPool and the command run_batch.
The code is launching properly and the pool is created.
Randomly, the computation fails and I receive the following error

%-------------------------------------
raise MapdlExitedError(
ansys.mapdl.core.errors.MapdlExitedError: MAPDL server connection terminated with the following error
<_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "Connection reset"
debug_error_string = "UNKNOWN:Error received from peer ipv4:.... {grpc_message:"Connection reset", grpc_status:14, created_time:"......"}"
%-------------------------------------

In some cases the mapdl session reboots and the computation continues (although it takes some time for the rebooting)
In other cases, I get

%-------------------------------------
PyMAPDL is taking longer than expected to connect to an MAPDL session.
Checking if there are any available licenses...
%-------------------------------------

and the computation stops completely.

Do you know how to prevent such issues?
I have tried running the pool with a lower number of instances as well. To no avail.


Community Forum: https://discuss.ansys.com/discussion/4497/mapdl-pool-run-batch-error

@germa89
Copy link
Collaborator

germa89 commented Oct 31, 2024

This is related to #3313 ... We are working on that already.

I'm going to close it as duplicate since it does not provide code to replicate the issue just the message.

Future visitors should refer to #3313

@germa89 germa89 closed this as completed Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants