Personal tools
You are here: Home Forum Install & build SuSE 10.1 - problems

SuSE 10.1 - problems

Up to Install & build
  • SuSE 10.1 - problems

    Posted by José Santos at April 14. 2006
    Hello I've successfully installed Salome 2.2.8 on SuSE 10.1, but I am not able to run it. The error message is the following: Searching for a free port for naming service: 2810 2811 2812 2813 2814 2815 - Ok Can not read launch configuration file /home/jose/.salome_2.2.8/salome.launch source= [] opts= {} args= {'portkill': 0, 'key': [], 'embedded': [], 'standalone': [], 'appname': 'salome', 'interp': 0, 'killall': 0, 'xterm': 0, 'modules': [], 'port': 2815, 'file': 0, 'logger': 0, 'gui': 0, 'containers': []} startSalome {'portkill': 0, 'key': [], 'embedded': [], 'standalone': [], 'appname': 'salome', 'interp': 0, 'killall': 0, 'xterm': 0, 'modules': [], 'port': 2815, 'file': 0, 'logger': 0, 'gui': 0, 'containers': []} Lancement du Naming Service runNS.sh > /tmp/logs/root/salomeNS.log 2>&1 Searching Naming Service found in 0.0 seconds Notify Server to launch Searching /Registry in Naming Service +th. 3078080176 COMPILED with /vsr/salome_2.2.8/KERNEL_SRC_2.2.8/src/Registry/SALOME_Registry_Server.cxx [59] : g++, Jan 10 2006 at 16:04:10 th. 3078080176 - Trace /vsr/salome_2.2.8/KERNEL_SRC_2.2.8/src/NamingService/SALOME_NamingService.cxx [337] : Resolve() : Registry (object) not found found in 0.5 seconds KERNELCatalog.xml Searching /Kernel/ModulCatalog in Naming Service +th. 3068012208 - Trace /vsr/salome_2.2.8/KERNEL_SRC_2.2.8/src/ModuleCatalog/SALOME_ModuleCatalog_Server.cxx [97] : Module Catalog Server: Naming Service was found found in 0.5 seconds Searching /myStudyManager in Naming Service ++ found in 1.0 seconds KERNELCatalog.xml KERNELCatalog.xml Searching /Kernel/Session in Naming Service +This is the end of document +++th. 2995017392 - Trace /vsr/salome_2.2.8/KERNEL_SRC_2.2.8/src/Session/SALOME_Session_Server.cxx [123] : pman->activate() th. 2961419168 - Trace /vsr/salome_2.2.8/KERNEL_SRC_2.2.8/src/NamingService/SALOME_NamingService.cxx [337] : Resolve() : Containers (dir) not found +th. 2961419168 - Trace /vsr/salome_2.2.8/KERNEL_SRC_2.2.8/src/NamingService/NamingService_WaitForServerReadiness.cxx [94] : Server /Containers/portatil/FactoryServer not found, abort... +Traceback (most recent call last): File "/usr/local/bin/salome/KERNEL_2.2.8/bin/salome/runSalome.py", line 670, in useSalome clt = startSalome(args, modules_list, modules_root_dir) File "/usr/local/bin/salome/KERNEL_2.2.8/bin/salome/runSalome.py", line 585, in startSalome session=clt.waitNSPID("/Kernel/Session",mySessionServ.PID,SALOME.Session) File "/usr/local/bin/salome/KERNEL_2.2.8/bin/salome/orbmodule.py", line 153, in waitNSPID raise "Impossible de trouver %s" % theName Impossible de trouver /Kernel/Session --- erreur au lancement Salome --- Saving of the dictionary of Salome processes in /root/root_portatil_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. Does anyone have any ideia on how to fix this? Thanks! José Santos
Powered by Ploneboard
Document Actions