FoamX configuration in Debian

The configuration of FoamX In Debian-the Linux Release Technology-Debian information. For details, refer to the following section. I am not very fond of the FoamX interface, and I am still used to directly edit the input file. Therefore, FoamX is not configured on my machine. After trying it out, there is indeed an error. Maybe you can configure it later as needed. I remember that I had encountered some problems during FoamX configuration in the past, mainly because some library files could not be identified (I remember the original practice was to link the target file to an existing library ), just now I found an article about this problem. I just transferred some text to it:

FoamInstallationTest passed! You can enter FoamX to enter the interface! I did think so before I had been suffering from various problems for more than half a month. Now I think a lot of problems are due to lack of understanding about Linux, which leads to many detours, as many problems cannot be reproduced, you can only briefly describe the possible obstacles as follows:

(1) libssl.0.9.7.so or other libraries cannot be found;
Most of these are caused by the new or old OpenFOAM version of Linux you use. For example, Versions later than Mandriva 2007 have integrated libssl.0.9.8, so FoamX is not recognized at all when running. If your version is earlier than 0.9.7, go to the Openssl website and install it. Here, pay attention to the Share Libary path required by OpenFOAM in/usr/lib, openssl may be installed with/usr/share/lib. Therefore, when a new or old version is installed, you should use the ln command for connection, this allows FoamX to search for the required database. The command is as follows:

Updated: Enter ln libssl.0.9.8.so libssl.0.9.so in/usr/lib.
Old: Enter ln/usr/share/lib/libssl.0.9.7.so libssl.0.9.7.so in/usr/lib

Note that the above operations may need to be completed as root, so it is best to enable a new Root Shell or use su command to convert the identity to run.

(2) localhost prompt;
This warning seems to be unavailable at the time, but I didn't prompt it on my current 2007, but on the machine in the lab, it prompts that the current running is under localhost, which may cause problems, and then it gets stuck, you can only press Ctrl + C to jump out. Fortunately, it is relatively simple to solve this problem. You only need to open a Root Shell or use what? Run the e method in the command line [~] Localhost XXXXX is enough. For example, after switching to the Root user in this example, go to [root @ localhost ~] Enter localhost coastlab at the prompt, and the prompt will be changed to [root @ coastlab].

(3) Shape
Starting NameServer with inet: linux: 1234...
Uncaught MICO exception: IDL: omg.org/CORBA/INITIALIZE:1.0 (0, not-completed)
/Home/coastlab/OpenFOAM/OpenFOAM-1.4/bin/runFoamXHB: line 127: 6862 Aborted nsd-ORBIIOPAddr $ myIOP -- ior $ FOAMX_USER_CONFIG/ns. ref
......

This is the most collapsed, cloud-ready, but miraculous solution. As can be summarized in (2), OpenFOAM tends to run in the form of host-client, similar to what Server of Ansys, therefore, when it fails to connect to the specified Server, it will strike. (2) The situation is described as a measure to avoid local operation. Here, when I find that the network is smooth, the error will be reported after a while, and the error will be reported immediately when the network is disconnected. There are many similar problems and solutions in OpenFOAM Message Board, but the most suitable one is to change the/etc/hosts settings. Open this file and check it, only 127.0.0.1 localhost has one line, and all we need to do is add 127.0.0.1 coastlab or select your external IP address, such as 192.168.0.5 coastlab.

After all this is done, if nothing happens, theoretically you should be able to see the FoamX Main Window drawn in the User Guide, waiting may be more complicated, but when a journey of just one thousand miles begins, do you still worry about not seeing the dawn of the road ahead? (Original Author: openfoam)