Free Courses Fluids Structures Electronics 3D Design Optics Photonics Materials Installation Python Optimization Safety & Cybersecurity Embedded Software MBSE Digital Mission Engineering STEM NVH Student Teams Semiconductors Indo Kursus Partner Courses My Courses

[FAQ]

Summary: Socket Disconnection Issue This is primarily a Windows issue. If running Fluent with -t1 or higher number of processes and leave the session for an extended period of time (2-20 hours), it receives the following message in the console: The fl process could not be started. No other information about what timed out is provided, and only the cortex process is left running. This issue becomes more significant in light of the switch from serial to -t1. IP interfaces on the machine. The problem seems to occur with the PPP Adapter Umbrella doing some periodic disconnections. We do not see connection disruptions between the cortex and host process which are connected through Local loopback: 127.0.0.1 Resolution: Windows Type: ipconfig /all in a Command Prompt window If you see the PPP Adapter Umbrella connected disable it if possible. You can also enforce the use of local loopback in the Fluent Launcher, Environment tab by entering this value: FLUENT_HOST_IP=-127.0.0.1 If using command line job submission add this value to your command line when launching FLUENT or modify the FLUENT Launcher, Environment tab as noted above This issue will be addressed in future releases of Fluent.