Salome 4.1.4 Installation on Fedora 10 (x86_64)

23 Replies to “Salome 4.1.4 Installation on Fedora 10 (x86_64)”

1. Did you do any changes on your /etc/hosts file. I also use Fedora 10 x86_64 but, I get an “+++++++++Failed to narrow the root naming context” error. And editing of /etc/hosts described like here http://www.salome-platform.org/forum/?groupid=10&forumid=9&thread=1425 doesn’t help…

   tanks

2. Thanks for your comment.

   I haven’t meet this problem.

   Installation and running Salome don’t need any change in /etc/hosts, I think.

   Could you tell me more details about your Salome version and platform (64bit or not)? I used Salome 3.2.6 (32bit) on Fedora 10 x86_64, which worked well. Now, I work with Salome 4.1.4 (64bit).

3. Thanks for your answer.

   I also use a 64bit version of Fedora 10, and the InstallWizard_4.1.4_Debian_4.0_64bit.tar.gz file. In fact I’m able to launch Salome from the installation dialog, but not via ./runSalome command.
   The error I get have something to do with something called “omniNames”.
   I installed cppunit.x86_64 compat-libgfortran-41.x86_64 qscintilla.x86_64 from normal repo and not from rawhide. What are the patched you a referring to, because the Debian patches provided on the Salome Homepage seems to belong to Debian 3.1 (sarge) and not the 4.0 (etch) version.

4. Please try to run salome as this:

   $. /your_salome_root_directory/env_products.sh
   $/your_salome_root_directory/KERNEL_4.1.4/bin/salome/runSalome
   

   The first command is to set the environment variables.

   Patches don’t work, since their versions are different.

5. That also brings the same error as before. To me this is very strange since we both are using the same Linux and Salome version, and it also had been started successfuly before.
   here is my complete error log:
   [reini@sherwood salome_4.1.4]$ . /opt/salome_4.1.4/env_products.sh
[reini@sherwood salome_4.1.4]$ /opt/salome_4.1.4/KERNEL_4.1.4/bin/salome/runSalome
Configure parser: Warning : could not find user configuration file
runSalome running on sherwood
Configure parser: Warning : could not find user configuration file
Searching for a free port for naming service: 2810 - OK
Cannot open error log file: Searching Naming Service +/tmp/logs/reini/omniNameErrors.log

   usage: omniNames [-start []]
   [-logdir ]
   [-errlog ]
   [-ignoreport]
   [...]

   Use -start option to start omniNames for the first time.
   With no argument, the standard default of 2809 is used.

   Use -logdir option to specify the directory where the log/data files are kept.

   Use -errlog option to specify where standard error output is redirected.

   Use -ignoreport option to ignore the port specification.

   You can also set the environment variable OMNINAMES_LOGDIR to specify the
   directory where the log/data files are kept.

   +++++++++Failed to narrow the root naming context
   Traceback (most recent call last):
   File "/opt/salome_4.1.4/KERNEL_4.1.4/bin/salome/runSalome.py", line 638, in useSalome
   clt = startSalome(args, modules_list, modules_root_dir)
   File "/opt/salome_4.1.4/KERNEL_4.1.4/bin/salome/runSalome.py", line 419, in startSalome
   clt=orbmodule.client(args)
   File "/opt/salome_4.1.4/KERNEL_4.1.4/bin/salome/orbmodule.py", line 42, in __init__
   self.initNS(args or {})
   File "/opt/salome_4.1.4/KERNEL_4.1.4/bin/salome/orbmodule.py", line 75, in initNS
   sys.exit(1)
   SystemExit: 1

   --- Error during Salome launch ---
   Thanks for your time anyway!

6. Hi, Microsponge,

   I guess that your user account reini has no permission to write in your temporary folder /tmp/logs/reini/. So change your writing permission of the directory and that of files in the directory, and try again.

7. Great!

   Thanks, that was it, now it’s running.

8. Hi Martin,

   My case is similar to that of microsponge. I am running Fedora 10 64 bit and used InstallWizard_4.1.4_Debian_4.0_64bit.tar.gz file.

   I ran into the following issues:

   1. The following libraries were not installed:

   libBLSurf.so ….yum could not find this
   libg2c.so.0 ….yum installed this
   libcppunit-1.12.so.0 ….yum could not find this
   libqscintilla.so.6 …yum could not find this

   I have installed cppunit.x86_64 compat-libgfortran-41.x86_64 qscintilla.x86_64 before starting the installation.

   2. When I run ./runSalome, I get the following message:

   [root@sslap salome]# ./runSalome
   Traceback (most recent call last):
   File “/bin/salome/envSalome.py”, line 25, in
   import setenv
   ImportError: No module named setenv

   The file envSalome.py was not created during install. I installed Salome in /usr/local/bin/Salome and manually created the directory /bin/salome and copied envSalome.py from /usr/local/bin/Salome/KERNEL_4.1.4/bin/salome to /bin/salome.

   Thanks.

9. Hi Sudheer,

   try:

   $. /opt/salome_4.1.4/env_products.sh
   $/opt/salome_4.1.4/KERNEL_4.1.4/bin/salome/runSalome
   

10. Hi Martin,

    My /opt is empty. Please advice.

    Thanks.

11. Hi Sudheer,

    The folder /opt/salome_4.1.4/ is your salome 4.1.4 installation directory.

    Try to find the file env_products.sh in your salome 4.1.4 folder, and run it as:

    $. env_products.sh
    

    This file is to set the environment variables. Don’t forget the dot in the front of the command line. Then you can execute the runSalome.

12. Hi Martin,

    Thank you very much. Salome now opens. The mistake I did was to not put the dot before env_products.sh. I am a newbie to Linux and Salome as well!

    I have a few more issues relating to the libraries:

    1. When I try to open ‘Mesh’ in the drop down menu, I get the message:
    Can not load library libSMESH.so. libg2c.so.0: cannot open shared object file: No such file or directory.

    2. Similarly for the ‘Post-Pro’ menu item:
    Can not load library libVISU.so. libg2c.so.0: cannot open shared object file: No such file or directory.

    3. Similarly for the ‘YACS’ menu item:
    Can not load library libYACS.so. libqscintilla.so.6: cannot open shared object file: No such file or directory.

    The other menu items (Geometry, Med, Supervisor) open up.

    Thanks.

13. Hi Sudheer,

    try to install compat-libf2c-34.x86_64 and qscintilla.x86_64

14. Hi Martin,

    Thank you very much. I installed compat-libf2c-34.x86_64 and now the mesh and post-pro menus are working.

    I installed the latest qscintilla.x86_64 from rawhide which is: qscintilla.x86_64 0:2.3.2-2.fc11. Previously I had the one from fedora.repo, not the rawhide. Either way, the YACS menu item still says: “Can not load library libYACS.so. libqscintilla.so.6: cannot open shared object file: No such file or directory.”. Any thoughts?

    Thanks,
    Sudheer

15. Hi Sudheer,

    Try to google qscintilla-1.6-3.fc4.x86_64.rpm, and download it.

    Install it in this way:

    $ sudo rpm -ivh qscintilla-1.6-3.fc4.x86_64.rpm 
    

    It should work.

16. Hi Martin,

    Thank you very much! Everything works now. I replaced qscintilla.x86_64 0:2.3.2-2.fc11 with qscintilla-1.6-3.fc4.x86_64.rpm which is an older package and then YACS worked!. Great job, Martin. Thanks again so much.

    Best,
    Sudheer

17. You are Welcome.

18. Hi, I have problem with run Salome 5.1.4 as below:

    bash-3.1$ ./env_products.sh
    bash-3.1$ cd KERNEL_5.1.4/bin/salome/
    bash-3.1$ ./runSalome.py -g
    Traceback (most recent call last):
    File “./runSalome.py”, line 30, in
    import orbmodule
    File “/home/mac/salome_5.1.4/KERNEL_5.1.4/bin/salome/orbmodule.py”, line 31, i
    n
    from omniORB import CORBA
    ImportError: No module named omniORB
    export PYTHONPATH=”/home/mac/salome_5.1.4/omniORB-4.1.4/lib/python2.4/site-packa
    ges/”

    bash-3.1$ ./runSalome.py -g
    runSalome running on mac
    Configure parser: Warning : could not find user configuration file
    Searching for a free port for naming service: 2810 – OK
    (omniNames) launch failed: 2 (No such file or directory)
    Searching Naming Service ++++++++++Failed to narrow the root naming context
    Traceback (most recent call last):
    File “./runSalome.py”, line 617, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
    File “./runSalome.py”, line 417, in startSalome
    clt=orbmodule.client(args)
    File “/home/mac/salome_5.1.4/KERNEL_5.1.4/bin/salome/orbmodule.py”, line 49, i
    n __init__
    self.initNS(args or {})
    File “/home/mac/salome_5.1.4/KERNEL_5.1.4/bin/salome/orbmodule.py”, line 82, i
    n initNS
    sys.exit(1)
    SystemExit: 1

    — Error during Salome launch —

    Do you have any idea waht`s wrong here ?

    I`m very glad for every help …

19. Hi, Mac,

    Please try to give me more details about your system: do you use Fedora? or others? what version?

    your problem is the starting script cannot find module omniORB. I think you set your environment path with errors.

    please try

    $. ./env_products.sh
    $cd KERNEL_5.1.4/bin/salome/
    $./runSalome
    

    Please don’t miss the dot in the front of your command to setting the environment variable.

20. Hi Martin,

    thank you for reply!

    My previuos problem has been solved by putting dot in head of env_products.sh.

    I`am working on Linux Slackware 13.0 with 2.6.36 kernel.

    But now have another problem as below:

    bash-4.1# . ./env_products.sh
    bash-4.1# cd KERNEL_5.1.4/bin/salome/
    bash-4.1# ./runSalome
    runSalome running on proton
    Searching for a free port for naming service: 2810 – OK
    Searching Naming Service +++ found in 0.3 seconds
    Searching /Containers/proton/FactoryServerPy in Naming Service ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ found in 33.0 seconds
    Searching /Kernel/Session in Naming Service +++++++++++++++++++++++Traceback (most recent call last):
    File “/home/mac/salome_5.1.4/KERNEL_5.1.4/bin/salome/runSalome.py”, line 617, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
    File “/home/mac/salome_5.1.4/KERNEL_5.1.4/bin/salome/runSalome.py”, line 566, in startSalome
    session=clt.waitNSPID(“/Kernel/Session”,mySessionServ.PID,SALOME.Session)
    File “/home/mac/salome_5.1.4/KERNEL_5.1.4/bin/salome/orbmodule.py”, line 164, in waitNSPID
    raise RuntimeError, “Process %d for %s not found” % (thePID,theName)
    RuntimeError: Process 18652 for /Kernel/Session not found

    — Error during Salome launch —

    As I understood he cannot find PID of some process ???

21. Hi again,

    I found something interesting in /var/log/messages:

    Nov 14 23:28:49 localhost kernel: [19917.960026] SALOME_Launcher[30679]: segfault at 1c4f ip b6c4acf7 sp bfe874a8 error 4 in libc-2.12.1.so[b6bd1000+15b000]
    Nov 14 23:29:21 localhost kernel: [19949.385345] SALOME_Session_[30772]: segfault at 1c4f ip b5677cf7 sp b2a2ecd8 error 4 in libc-2.12.1.so[b55fe000+15b000]

    It looks like glibc 2.12.1 cause Segmentation Fault in Salome 5.1.4 (???)

22. Hi, Mac,

    I think you can try as http://www.idurun.com/?p=550

23. Problem has been solved. Since that time when this problem has been found I had changed computer to 64 bit machine

    bash-4.1$ uname -a
    Linux granit 2.6.38 #3 Sat Mar 19 19:39:42 CET 2011 x86_64 Intel(R) Celeron(R) M CPU 520 @ 1.60GHz GenuineIntel GNU/Linux

    After few days of searching I found this post:

    http://tech–help.blogspot.com/2011/02/ubuntu-solved-segfault-at-address-error.html?showComment=1300719209478#c9154781491171579820

    then I’ve downgraded zlib from latest 1.2.5 to 1.2.3 version, then Salome 5.1.5 starts to work!

This site uses Akismet to reduce spam. Learn how your comment data is processed.