TimeoutError #1317
Replies: 3 comments
-
Let me transfer this issue to PyAnsys Geometry and answer you there =) |
Beta Was this translation helpful? Give feedback.
-
Hi @JulienAlpha521 - thanks for raising this issue. Let me try to explain it the best way I can :) So, what you are trying to do (currently) is connect to an existing "Modeler" session, may it be with Ansys SpaceClaim, Ansys Discovery or Ansys Geometry Service. It won't be enough that you just have any of these services up and running... it is also necessary that you launch the so called "APIServer" plugin with them. Otherwise it won't work. However, there are some convenience functions that will allow you to both launch the services as needed and instantiate a Modeler object so that you can get yourself started. You can see an example here: https://github.com/ansys/pyansys-geometry?tab=readme-ov-file#basic-usage - search for the Once you have your Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
Closing due to lack of activity |
Beta Was this translation helpful? Give feedback.
-
Hello everyone,
I hope this message finds you well.
I am encountering an issue with pyAnsys that I would like to submit for your assistance. Specifically, I am trying to use the pyAnsys geometry module, but when I launch the modeler, the script cannot connect to the Ansys server.
Script:
from ansys.geometry.core import Modeler modeler = Modeler()
Output:
CRITICAL - - logger - handle_exception - Uncaught exception y\core\modeler.py", line 106, in __init__ self._client = GrpcClient( ^^^^^^^^^^^ File "<@beartype(ansys.geometry.core.connection.client.GrpcClient.__init__) at 0x2235a316de0>", line 244, in __init__ File "C:\Users\lac\Documents\pyansys_tst\.venv\Lib\site-packages\ansys\geometry\core\connection\client.py", line 159, in __init__ wait_until_healthy(self._channel, timeout) File "C:\Users\lac\Documents\pyansys_tst\.venv\Lib\site-packages\ansys\geometry\core\connection\client.py", line 80, in wait_until_healthy raise TimeoutError( TimeoutError: Channel health check to target 'dns:///160.103.238.66:1055' timed out after 120 seconds.
However, if I ping the server via the terminal, it responds successfully:
`ping wansys
Pinging wansys [160.103.238.66] with 32 bytes of data:
Reply from 160.103.238.66: bytes=32 time=3ms TTL=125
Reply from 160.103.238.66: bytes=32 time=4ms TTL=125
Reply from 160.103.238.66: bytes=32 time=2ms TTL=125
Reply from 160.103.238.66: bytes=32 time=2ms TTL=125
Ping statistics for 160.103.238.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milliseconds:
Minimum = 2ms, Maximum = 4ms, Average = 2ms`
If you have any ideas on how I could resolve this issue, it would be greatly appreciated.
Best regards,
Julien
Beta Was this translation helpful? Give feedback.
All reactions