Erreur au lancement de Salome sur Madriva2006
-
J'ai le message suivant au lancement de Salome.
Pouvez-vous me guider pour en trouver la cause.
[bruno@mercau salome]$ runSalome
Searching for a free port for naming service: 2810 2811 2812 - Ok
Configure parser: processing /opt/salome_3.2.1/GUI_3.2.1/share/salome/resources/gui/SalomeApp.xml ...
Configure parser: Warning : could not find configuration file /opt/salome_3.2.1/GUI_3.2.1/share/salome/reso
urces/SalomeApp.xml
Configure parser: Warning : could not find user configuration file
GEOM OCAF Resources
GEOM Shape Healing Resources
startSalome {u'portkill': 0, u'file': 0, u'embedded': [u'SalomeAppEngine', u'study', u'cppContainer', u're
gistry', u'moduleCatalog'], u'killall': 0, 'appname': 'SalomeApp', u'modules': [u'GEOM', u'SMESH', u'VISU',
u'SUPERV', u'MED', u'COMPONENT', u'PYCALCULATOR'], u'gui': 1, u'xterm': 0, u'interp': 0, u'pyModules': u''
, 'port': 2812, u'splash': 1, u'SMESH_plugins': [u'NETGENPlugin', u'GHS3DPlugin'], u'key': [u'no'], 'plugin
s': [], 'containers': [], u'logger': 0, u'noexcepthandler': 0, u'standalone': [u'pyContainer', u'supervCont
ainer', 'superv']}
Lancement du Naming Service runNS.sh > /tmp/logs/bruno/salomeNS.log 2>&1
Searching Naming Service ++++++++++Failed to narrow the root naming context
Traceback (most recent call last):
File "/opt/salome_3.2.1/KERNEL_3.2.1/bin/salome/runSalome.py", line 767, in useSalome
clt = startSalome(args, modules_list, modules_root_dir)
File "/opt/salome_3.2.1/KERNEL_3.2.1/bin/salome/runSalome.py", line 593, in startSalome
clt=orbmodule.client()
File "/opt/salome_3.2.1/KERNEL_3.2.1/bin/salome/orbmodule.py", line 60, in __init__
self.initNS()
File "/opt/salome_3.2.1/KERNEL_3.2.1/bin/salome/orbmodule.py", line 93, in initNS
sys.exit(1)
SystemExit: 1
--- erreur au lancement Salome ----
Hello,
1) The problem seems to be caused by incorrect work of omniORB on your PC.
To check this you can try to build and run omniORB examples (for that you will probably need to build the omniORB manually; you can find omniORB sources package on the SALOME installation CD).
The problem with omniORB (in first turn with the Naming Service) can be caused by wrong settings for network card driver or other network settings.
2) The mentioned problem may also occur on slow PCs. You can try to solve this by setting environment variable CSF_RepeatServerRequest (number of attempts to connect Naming service) to the big anough value, e.g. 1000000, or set environment variable CSF_DelayServerRequest (time delay between requests in microseconds) to something like 1000000 or more.
This also may help in some situations.
Regards,
Vadim.
-
-
Hi to all, me as well, I tried to install salome 3.2.2 on a debian sarge 3.1 with no success - I seriously passed all known issues I found in the forums in the last 2 days. At first I tried to install all that omniorb4 and python stuff available in the debian release. Further on I tried to export the variables export CSF_DelayServerRequest="100000" export CSF_RepeatServerRequest="1000000" and especially I installed omniorb 4.1.0 from scratch - unfortunately nothing changed: when try to start salome I get the following message: / source salome.sh / bin/salome/runSalome Searching for a free port for naming service: 2810 2811 2812 2813 2814 2815 - Ok Configure parser: processing /usr/local/salome/GUI_3.2.2/share/salome/resources/gui/SalomeApp.xml ... Configure parser: Warning : could not find user configuration file GEOM OCAF Resources GEOM Shape Healing Resources startSalome {u'portkill': 0, 'pyscript': [], u'file': 0, u'embedded': [u'SalomeAppEngine', u'study', u'cppContainer', u'registry', u'moduleCatalog'], u'killall': 0, 'appname': 'SalomeApp', u'modules': [u'GEOM', u'SMESH', u'VISU', u'SUPERV', u'MED', u'COMPONENT', u'PYCALCULATOR'], u'gui': 1, u'xterm': 0, u'interp': 0, u'pyModules': u'', 'port': 2815, u'splash': 1, u'SMESH_plugins': [u'NETGENPlugin', u'GHS3DPlugin'], u'key': [u'no'], 'plugins': [], 'containers': [], u'logger': 0, u'noexcepthandler': 0, u'standalone': [u'pyContainer', u'supervContainer', 'superv']} Lancement du Naming Service runNS.sh > /tmp/logs/master/salomeNS.log 2>&1 Searching Naming Service ++++++++++Failed to narrow the root naming context Traceback (most recent call last): File "/usr/local/salome/KERNEL_3.2.2/bin/salome/runSalome.py", line 780, in useSalome clt = startSalome(args, modules_list, modules_root_dir) File "/usr/local/salome/KERNEL_3.2.2/bin/salome/runSalome.py", line 606, in startSalome clt=orbmodule.client() File "/usr/local/salome/KERNEL_3.2.2/bin/salome/orbmodule.py", line 60, in __init__ self.initNS() File "/usr/local/salome/KERNEL_3.2.2/bin/salome/orbmodule.py", line 93, in initNS sys.exit(1) SystemExit: 1 --- erreur au lancement Salome --- Saving of the dictionary of Salome processes in /home/homes/master/master_(none)_2815_SALOME_pidict To kill SALOME processes from a console (kill all sessions from all ports): python killSalome.py To kill SALOME from the present interpreter, if it is not closed : killLocalPort() --> kill this session (use CORBA port from args of runSalome) givenPortKill(port) --> kill a specific session with given CORBA port killAllPorts() --> kill all sessions runSalome, with --killall option, starts with killing the processes resulting from the previous execution. now I'm lacking ideas to go any further - are there perhaps any suggestions on the debian install procedure I haven't found yet ? please help - thanks in advance Kai Henning Koch PS. If you need any further information please let me know so that I can provide them
-
Hi to all, me as well, I tried to install salome 3.2.2 on a debian sarge 3.1 with no success - I seriously passed all known issues I found in the forums in the last 2 days. At first I tried to install all that omniorb4 and python stuff available in the debian release. Further on I tried to export the variables export CSF_DelayServerRequest="100000" export CSF_RepeatServerRequest="1000000" and especially I installed omniorb 4.1.0 from scratch - unfortunately nothing changed: when try to start salome I get the following message: / source salome.sh / bin/salome/runSalome Searching for a free port for naming service: 2810 2811 2812 2813 2814 2815 - Ok Configure parser: processing /usr/local/salome/GUI_3.2.2/share/salome/resources/gui/SalomeApp.xml ... Configure parser: Warning : could not find user configuration file GEOM OCAF Resources GEOM Shape Healing Resources startSalome {u'portkill': 0, 'pyscript': [], u'file': 0, u'embedded': [u'SalomeAppEngine', u'study', u'cppContainer', u'registry', u'moduleCatalog'], u'killall': 0, 'appname': 'SalomeApp', u'modules': [u'GEOM', u'SMESH', u'VISU', u'SUPERV', u'MED', u'COMPONENT', u'PYCALCULATOR'], u'gui': 1, u'xterm': 0, u'interp': 0, u'pyModules': u'', 'port': 2815, u'splash': 1, u'SMESH_plugins': [u'NETGENPlugin', u'GHS3DPlugin'], u'key': [u'no'], 'plugins': [], 'containers': [], u'logger': 0, u'noexcepthandler': 0, u'standalone': [u'pyContainer', u'supervContainer', 'superv']} Lancement du Naming Service runNS.sh > /tmp/logs/master/salomeNS.log 2>&1 Searching Naming Service ++++++++++Failed to narrow the root naming context Traceback (most recent call last): File "/usr/local/salome/KERNEL_3.2.2/bin/salome/runSalome.py", line 780, in useSalome clt = startSalome(args, modules_list, modules_root_dir) File "/usr/local/salome/KERNEL_3.2.2/bin/salome/runSalome.py", line 606, in startSalome clt=orbmodule.client() File "/usr/local/salome/KERNEL_3.2.2/bin/salome/orbmodule.py", line 60, in __init__ self.initNS() File "/usr/local/salome/KERNEL_3.2.2/bin/salome/orbmodule.py", line 93, in initNS sys.exit(1) SystemExit: 1 --- erreur au lancement Salome --- Saving of the dictionary of Salome processes in /home/homes/master/master_(none)_2815_SALOME_pidict To kill SALOME processes from a console (kill all sessions from all ports): python killSalome.py To kill SALOME from the present interpreter, if it is not closed : killLocalPort() --> kill this session (use CORBA port from args of runSalome) givenPortKill(port) --> kill a specific session with given CORBA port killAllPorts() --> kill all sessions runSalome, with --killall option, starts with killing the processes resulting from the previous execution. now I'm lacking ideas to go any further - are there perhaps any suggestions on the debian install procedure I haven't found yet ? please help - thanks in advance Kai Henning Koch PS. If you need any further information please let me know so that I can provide them
-
-
-
Powered by
Ploneboard
