[wmplcfd]

Does anyone encounter this error in CFX-Solver? I encountered this error prompt in a transient simulation of a cylinder moving in water. The details of this error is posted as follows,
+--------------------------------------------------------------------+
| ERROR #001100288 has occurred in subroutine CTRL_MESG_HANDLER. |
| Message: |
| The following message handling error occurred: |
| Unable to start message handler. |
| Hostname: node3 |
| Port number: 0 |
| |
| Messages will now be handled using a less robust method, |
| with a greater risk of parallel deadlocks.


Thank you very much for your advice!

[ghorrocks]

Sounds like your network had a glitch and it interfered with a parallel simulation. I would check your network is reliable and able to handle a heavy workload. A big parallel simulation pumps a lot of data through the network so you need plenty of bandwidth to handle it.

[wmplcfd]

Thank you for your advice. I would check the parallel environment of MPI. Thank you again for your reply !

[evcelica]

I get a similar message a lot:


+--------------------------------------------------------------------+
| ERROR #001100288 has occurred in subroutine MESG_SEND. |
| Message: |
| The following message handling error occurred: |
| Failed to contact the message handler. |
| Hostname: Node1 |
| Port number: 12345 |
| |
| Messages will now be handled using a less robust method, |
| with a greater risk of parallel deadlocks. |
+--------------------------------------------------------------------+


I have always just ignored it, and have not noticed any problems from it.
I'm using 20gbps infiniband. Infinihost 3 cards and switch. I'm upgrading to connectX as soon as I get time to install the cards.

[Mazze[ITA]]

I am leaving you the suggestions from ANSYS:

If this occurs, please check:

-Network settings in /etc/hosts
-Password-less ssh login
-Check the default path (if the default path points to a gateway that is not reachable, password-less ssh and parallel simulations are possible, but the message handler is still unable to start and a less robust messaging method is used.