CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   STAR-CCM+ (https://www.cfd-online.com/Forums/star-ccm/)
-   -   Waiting for client to catch up (https://www.cfd-online.com/Forums/star-ccm/211209-waiting-client-catch-up.html)

Rinia November 13, 2018 19:27

Waiting for client to catch up
 
The output window shows "Waiting for client to catch up" and when I click "stop", it shows "waiting for current iteration to complete".Now I cannot stop and save the simulation.

Anyone encounter this trouble before?By the way,I use the version 11.02

Thanks a lot for your help.

me3840 November 13, 2018 21:32

The message "waiting for client to catch up" occurs when the queue for completing image rendering has grown long.

In that instance the server process will stop iterating until the client can finish all of its work.

This happens often when you are either (a) saving too many images too fast or (b) saving an image too complex for software rendering.

The obvious solutions are to (a) stop saving so many images or save them more infrequently and (b) use hardware rendering.

Rinia November 13, 2018 21:44

Thanks a lot for your answer.
This issue troubles me for a long time.I‘ll try your method.

LuckyTran November 16, 2018 11:07

Star-ccm was built from the start to have a client-server architecture and that influences some of its behavior. For example when you (on the client) presses the stop button, you send a message to the server to stop iterating. But the server doesn't respond this command until it finishes doing whatever it is currently doing and executes the stop task. This means if it is stuck doing some long calculation you can be stuck waiting for hours or days even though you can go to a task manager or job scheduler and terminate the job instantly (i.e. alt + ctrl + del in windows or some pkill in linux)

Rinia November 16, 2018 20:21

Quote:

Originally Posted by LuckyTran (Post 715887)
Star-ccm was built from the start to have a client-server architecture and that influences some of its behavior. For example when you (on the client) presses the stop button, you send a message to the server to stop iterating. But the server doesn't respond this command until it finishes doing whatever it is currently doing and executes the stop task. This means if it is stuck doing some long calculation you can be stuck waiting for hours or days even though you can go to a task manager or job scheduler and terminate the job instantly (i.e. alt + ctrl + del in windows or some pkill in linux)

Thanks a lot for your explanation.
It seems that all I can do is waiting.


All times are GMT -4. The time now is 13:02.