Personal tools
You are here: Home Forum Install & build 5.1.3 stalling at launch on openSuse 11.2

5.1.3 stalling at launch on openSuse 11.2

Up to Install & build

5.1.3 stalling at launch on openSuse 11.2

Posted by Dave McDaniel at March 11. 2010

I am trying to use the universal binary on a brand new installation of opensuse 11.2.

The launch script just stalls out at the following juncture:

Searching for free port for the SALOME Naming Service: 2810; 2811 - Ok
Configure parser: Warning : could not find user configuration file
runSalome running on opteron
Configure parser: Warning : could not find user configuration file
Searching for a free port for naming service: 2810 2811 - OK
++++Searching Naming Service +

Any ideas?  Perhaps a firewall port issue?

 

Thanks, Dave

 

 

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by DAVID Gilles at March 12. 2010

Previously Dave McDaniel wrote:

I am trying to use the universal binary on a brand new installation of opensuse 11.2.

The launch script just stalls out at the following juncture:

Searching for free port for the SALOME Naming Service: 2810; 2811 - Ok
Configure parser: Warning : could not find user configuration file
runSalome running on opteron
Configure parser: Warning : could not find user configuration file
Searching for a free port for naming service: 2810 2811 - OK
++++Searching Naming Service +

Any ideas?  Perhaps a firewall port issue?

 

Thanks, Dave

 

 

Hello Dave,

 

I just installed OpenSuse 11.2 64 bits in a new virtual box machine (host is windows 7).

I ran successfully Salome from the 64 bits universal package.

I didn't tweak the distribution, it is a "fresh" installation.

 

Regards,

Gilles

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Dave McDaniel at March 12. 2010

Interesting, this too is a fresh install.  I wonder if it has something to do with the graphics capability on this machine.  I remember having issues running Abaqus CAE on this machine.  Its mainly a server/number cruncher with fairly mediocre graphics.  I could get CAE to run with -vesa option.  Is there a more verbose way to launch Salome so I can see what is going on?  Doesn't seem to have a "-v" option.

Thanks, Dave

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by DAVID Gilles at March 12. 2010

Yes the graphic card can be an issue.

I have an ATI HD 4970 and it works fine.

Old graphic cards (maybe more than 5-6 years) are not advised.

 

Gilles

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Tamás Baksa at March 12. 2010

Dave,

Sorry for the stupid question:

 

Did you wait enough? During the first run I had to wait ~3mins at that point.

 

regards,

Tamás

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Dave McDaniel at March 13. 2010

I did wait quite a while.  I am seeing this message at the end of the runSalome -h option:

Cannot find or open SALOME PIDs file for port 2812

Could that message be indicative of my problem?

 

I now doubt that it is a gpu issue as I am running a desktop sharing program (nxserver) in order to remotely login.  My interest is primarily setting up models remotely so i am not constantly transfering large input decks to the server across town.  I plan to use the python TUI interface to built scripts that I can run to build the input decks on the server itself, for this I assume I don't need good graphics capability?

 

Thanks again,

Dave

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Dave McDaniel at March 13. 2010

Here's an update,  if I wait for 15 or so minutes this is what I get:

Searching for free port for the SALOME Naming Service: 2810; 2811; 2812 - Ok
Configure parser: Warning : could not find user configuration file
runSalome running on opteron
Configure parser: Warning : could not find user configuration file
Searching for a free port for naming service: 2810 2811 2812 - OK
Searching Naming Service ++++++++++Failed to narrow the root naming context
Traceback (most recent call last):
  File "/home/dmcdaniel/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/runSalome.py", line 617, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
  File "/home/dmcdaniel/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/runSalome.py", line 417, in startSalome
    clt=orbmodule.client(args)
  File "/home/dmcdaniel/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/orbmodule.py", line 49, in __init__
    self.initNS(args or {})
  File "/home/dmcdaniel/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/orbmodule.py", line 82, in initNS
    sys.exit(1)
SystemExit: 1


--- Error during Salome launch ---

there is at least a python prompt at the end of the message.

 

any ideas?

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by DAVID Gilles at March 13. 2010

Try to execute the command: ./runSalome -k -t

This will launch Salome in batch mode, i.e without GUI.

At the end if launch is successful you will have a python prompt (without error).

This mode allows you at least to execute python scripts.

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Dave McDaniel at March 15. 2010

i get the same error message as my most previous post when trying those options.

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Dave McDaniel at March 18. 2010

okay, found the issue.  looks like my /etc/hosts file had the original hostname given during install.  this was the first thing i changed via Yast settings, looks like it did not update the 127.0.0.2 loopback.  once i manually corrected this file it worked!

david, looks like my install wasn't quite as "fresh" as yours afterall!

thanks guys, dave

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by DAVID Gilles at March 18. 2010

Good news !

Happy Salome now ;)

Gilles

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Nelson Faria at March 26. 2010

hello ppl,

I'm newbi to Linux I installed Salome 5.1.3 in opensuse 11.2 and I'm having exactly the same problem as Dave McDanie.  I see that you have found the solution but its a bit "increpted" could you please put in plain steps of how to fix it?

 

Best Regards,

Nelson

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Dave McDaniel at March 26. 2010

hey nelson, check to make sure that the command "hostname" returns the same value as what is listed in the /etc/hosts file for ip address 127.0.0.2

have you changed your hostname since install for any reason?

dave

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Nelson Faria at March 26. 2010

The host name looks the same:

 

nelsonfaria@linux-yerp:/etc> more hosts

#

# hosts         This file describes a number of hostname-to-address

#               mappings for the TCP/IP subsystem.  It is mostly

#               used at boot time, when no name servers are running.

#               On small systems, this file can be used instead of a

#               "named" name server.

# Syntax:

#

# IP-Address  Full-Qualified-Hostname  Short-Hostname

#

 

127.0.0.1       localhost

 

# special IPv6 addresses

::1             localhost ipv6-localhost ipv6-loopback

 

fe00::0         ipv6-localnet

 

ff00::0         ipv6-mcastprefix

ff02::1         ipv6-allnodes

ff02::2         ipv6-allrouters

ff02::3         ipv6-allhosts

 

127.0.0.2       linux-yerp.site linux-yerp

nelsonfaria@linux-yerp:/etc>

 

the hostname is the same

 

nelsonfaria@linux-yerp:~> hostname

linux-yerp

 

What you think it can be?

 

Nelson

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Dave McDaniel at March 26. 2010

no idea.  please post your error message, as it is now clear it is not the same issue.  how long are you waiting for it to start?

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Nelson Faria at March 26. 2010

Hi,

iIt does not take long to start. But I noticed that if I run it under su it goes further and appears the splash screen with the loading bar loading near up to 100%. It crashes requesting with the following "Python container is not found".

I have python installed... Any ideas??

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Dave McDaniel at March 26. 2010

please copy and paste the traceback for this error.  that is strange it goes further in su.  what are the permissions in the folder you installed it to?

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Nelson Faria at March 26. 2010

nelsonfaria@linux-yerp:~> runSalome                            

Configure parser: Warning : could not find user configuration file

runSalome running on linux-yerp                                   

Configure parser: Warning : could not find user configuration file

Searching for a free port for naming service: 2810 - OK           

Searching Naming Service + found in 0.1 seconds                   

(notifd) launch failed: 2 (No such file or directory)             

Searching /Containers/linux-yerp/FactoryServerPy in Naming Service ++++Traceback (most recent call last):

  File "/usr/bin/salome/SALOME_ContainerPy.py", line 38, in <module>                                     

    from SALOME_ComponentPy import *                                                                     

  File "/usr/bin/salome/SALOME_ComponentPy.py", line 45, in <module>                                     

    from libNOTIFICATION import *                                                                        

  File "/usr/lib/python2.6/site-packages/salome/libNOTIFICATION.py", line 7, in <module>                 

    import _libNOTIFICATION                                                                              

ImportError: No module named _libNOTIFICATION                                                            

th. 140401598511008 - Trace SALOME_Session_Server.cxx [97] : Debug: File cannot be opened                

th. 140401598511008 - Trace SALOME_Session_Server.cxx [97] : Debug: QtxResourceMgr: Could not load resource file "/home/nelsonfaria/.SalomeApprc"

th. 140401598511008 - Trace SALOME_Session_Server.cxx [97] : Debug: File '/usr/share/salome/resources/gui/SalomeApp.xml' is loaded successfully  

th. 140401598511008 - Trace SALOME_Session_Server.cxx [97] : Debug: File '/usr/share/salome/resources/gui/SalomeApp.xml' is loaded successfully  

th. 140401598511008 - Trace SALOME_Session_Server.cxx [100] : Warning: QPainter::begin: Cannot paint on a null pixmap                            

th. 140401598511008 - Trace SALOME_Session_Server.cxx [100] : Warning: QPainter::initFrom: Painter not active, aborted                           

Traceback (most recent call last):                                                                                                               

  File "/usr/bin/salome/runSalome.py", line 617, in useSalome                                                                                    

    clt = startSalome(args, modules_list, modules_root_dir)                                                                                      

  File "/usr/bin/salome/runSalome.py", line 550, in startSalome                                                                                  

    clt.waitNSPID("/Containers/" + theComputer + "/FactoryServerPy",myServer.PID)                                                                

  File "/usr/bin/salome/orbmodule.py", line 164, in waitNSPID                                                                                    

    raise RuntimeError, "Process %d for %s not found" % (thePID,theName)                                                                         

RuntimeError: Process 25578 for /Containers/linux-yerp/FactoryServerPy not found                                                                 

 

 

--- Error during Salome launch ---

nelsonfaria@linux-yerp:~> th. 140401598511008 - Trace SALOME_Session_Server.cxx [423] : pman->activate()

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=0                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=SALOME_Session_Server        

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=1                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=--with                       

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=2                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=Registry                     

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=3                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=(                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=4                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=--salome_session             

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=5                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=theSession                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=6                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=)                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [160] : server : Registry                        

th. 140401236109584 - Trace Session_ServerLauncher.cxx [162] :   arg : --salome_session                 

th. 140401236109584 - Trace Session_ServerLauncher.cxx [162] :   arg : theSession                       

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=7                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=--with                       

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=8                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=ModuleCatalog                

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=9                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=(                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=10                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=-common                      

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=11                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]="/usr/share/salome/resources/kernel/KERNELCatalog.xml"

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=12                                                           

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=-personal                                             

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=13                                                           

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=/home/nelsonfaria/Salome/resources/CatalogModulePersonnel.xml

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=14                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=)                                                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [160] : server : ModuleCatalog                                                   

th. 140401236109584 - Trace Session_ServerLauncher.cxx [162] :   arg : -common                                                          

th. 140401236109584 - Trace Session_ServerLauncher.cxx [162] :   arg : "/usr/share/salome/resources/kernel/KERNELCatalog.xml"           

th. 140401236109584 - Trace Session_ServerLauncher.cxx [162] :   arg : -personal                                                        

th. 140401236109584 - Trace Session_ServerLauncher.cxx [162] :   arg : /home/nelsonfaria/Salome/resources/CatalogModulePersonnel.xml    

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=15                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=--with                                                       

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=16                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=SALOMEDS                                                     

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=17                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=(                                                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=18                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=)                                                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [160] : server : SALOMEDS                                                        

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=19                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=--with                                                       

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=20                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=Container                                                    

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=21                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=(                                                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=22                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=FactoryServer                                                

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=23                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=)                                                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [160] : server : Container                                                       

th. 140401236109584 - Trace Session_ServerLauncher.cxx [162] :   arg : FactoryServer                                                    

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=24                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=--with                                                       

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=25                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=SalomeAppEngine                                              

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=26                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=(                                                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=27                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=)                                                            

th. 140401236109584 - Trace Session_ServerLauncher.cxx [160] : server : SalomeAppEngine                                                 

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=28                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=CPP                                                          

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=29                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=PY                                                           

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=30                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=GUI                                                          

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=31                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=SPLASH                                                       

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=32                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=--resources=                                                 

th. 140401236109584 - Trace Session_ServerLauncher.cxx [116] : iarg=33                                                                  

th. 140401236109584 - Trace Session_ServerLauncher.cxx [117] : _argv[iarg]=--modules (GEOM:SMESH:VISU:MED:YACS)                         

th. 140401236109584 - Trace Session_ServerLauncher.cxx [200] : *** activating [3] : Registry                                            

th. 140401236109584 - Trace Session_ServerThread.cxx [115] : Session_ServerThread::Init Registry                                        

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=Registry                                                          

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=--salome_session                                                  

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=theSession                                                        

th. 140401236109584 - Trace Session_ServerThread.cxx [123] : Server Thread type : Registry                                              

th. 140401236109584 - Trace Session_ServerThread.cxx [248] : Registry thread started                                                    

th. 140401236109584 - Trace Session_ServerThread.cxx [249] : argc=3                                                                     

th. 140401236109584 - Trace Session_ServerLauncher.cxx [200] : *** activating [5] : ModuleCatalog                                       

th. 140401236109584 - Trace Session_ServerThread.cxx [115] : Session_ServerThread::Init ModuleCatalog                                   

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=ModuleCatalog                                                     

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=-common                                                           

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]="/usr/share/salome/resources/kernel/KERNELCatalog.xml"            

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=-personal                                                         

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=/home/nelsonfaria/Salome/resources/CatalogModulePersonnel.xml     

th. 140401236109584 - Trace Session_ServerThread.cxx [123] : Server Thread type : ModuleCatalog                                         

th. 140401236109584 - Trace Session_ServerThread.cxx [186] : ModuleCatalog thread started                                               

th. 140401236109584 - Trace Session_ServerLauncher.cxx [200] : *** activating [1] : SALOMEDS                                            

th. 140401236109584 - Trace Session_ServerThread.cxx [115] : Session_ServerThread::Init SALOMEDS                                        

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=SALOMEDS                                                          

th. 140401236109584 - Trace Session_ServerThread.cxx [123] : Server Thread type : SALOMEDS                                              

th. 140401236109584 - Trace Session_ServerThread.cxx [221] : SALOMEDS thread started                                                    

th. 140401236109584 - Trace Session_ServerLauncher.cxx [200] : *** activating [2] : Container                                           

th. 140401236109584 - Trace Session_ServerThread.cxx [115] : Session_ServerThread::Init Container                                       

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=Container                                                         

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=FactoryServer                                                     

th. 140401236109584 - Trace Session_ServerThread.cxx [123] : Server Thread type : Container                                             

th. 140401236109584 - Trace Session_ServerThread.cxx [323] : Container thread started                                                   

th. 140401236109584 - Trace Session_ServerThread.cxx [333] : factory_poa does not exists, create...                                     

th. 140401236109584 - Trace Session_ServerThread.cxx [365] : pmanfac->activate()                                                        

Traceback (most recent call last):                                                                                                      

  File "<string>", line 1, in <module>                                                                                                  

  File "/usr/lib/python2.6/site-packages/salome/import_hook.py", line 160, in import_hook                                               

    module= original_import(name, globals, locals, fromlist, *args)                                                                     

  File "/usr/bin/salome/SALOME_Container.py", line 43, in <module>                                                                      

    from SALOME_ComponentPy import *                                                                                                    

  File "/usr/lib/python2.6/site-packages/salome/import_hook.py", line 160, in import_hook                                               

    module= original_import(name, globals, locals, fromlist, *args)                                                                     

  File "/usr/bin/salome/SALOME_ComponentPy.py", line 45, in <module>                                                                    

    from libNOTIFICATION import *                                                                                                       

  File "/usr/lib/python2.6/site-packages/salome/import_hook.py", line 160, in import_hook                                               

    module= original_import(name, globals, locals, fromlist, *args)                                                                     

  File "/usr/lib/python2.6/site-packages/salome/libNOTIFICATION.py", line 7, in <module>                                                

    import _libNOTIFICATION                                                                                                             

  File "/usr/lib/python2.6/site-packages/salome/import_hook.py", line 160, in import_hook                                               

    module= original_import(name, globals, locals, fromlist, *args)                                                                     

ImportError: No module named _libNOTIFICATION

Traceback (most recent call last):

  File "<string>", line 1, in <module>

NameError: name 'SALOME_Container' is not defined

th. 140401236109584 - Trace Session_ServerLauncher.cxx [200] : *** activating [1] : SalomeAppEngine

th. 140401236109584 - Trace Session_ServerThread.cxx [115] : Session_ServerThread::Init SalomeAppEngine

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=SalomeAppEngine

th. 140401236109584 - Trace Session_ServerThread.cxx [123] : Server Thread type : SalomeAppEngine

th. 140401236109584 - Trace Session_ServerThread.cxx [396] : SalomeApp_Engine thread started

th. 140401236109584 - Trace Session_ServerThread.cxx [399] : poa->activate_object( SalomeApp_Engine )

th. 140401236109584 - Trace Session_ServerLauncher.cxx [212] : *** activating [ SESSION ]

th. 140401236109584 - Trace Session_ServerThread.cxx [115] : Session_ServerThread::Init Session

th. 140401236109584 - Trace Session_ServerThread.cxx [118] : _argv[i]=Session

th. 140401236109584 - Trace Session_ServerThread.cxx [123] : Server Thread type : Session

th. 140401236109584 - Trace Session_ServerThread.cxx [448] : Session thread started

th. 140401236109584 - Trace Session_ServerThread.cxx [453] : poa->activate_object(mySALOME_Session)

th. 140401227716880 - Trace Session_ServerCheck.cxx [299] : /Registry is found

th. 140401227716880 - Trace Session_ServerCheck.cxx [301] : Registry was activated

th. 140401227716880 - Trace Session_ServerCheck.cxx [347] : /myStudyManager is found

th. 140401227716880 - Trace Session_ServerCheck.cxx [349] : StudyManager was activated

th. 140401227716880 - Trace Session_ServerCheck.cxx [395] : /Kernel/ModulCatalog is found

th. 140401227716880 - Trace Session_ServerCheck.cxx [397] : ModuleCatalog was activated

th. 140401227716880 - Trace Session_ServerCheck.cxx [443] : /Kernel/Session is found

th. 140401227716880 - Trace Session_ServerCheck.cxx [445] : SALOME_Session was activated

th. 140401227716880 - Trace Session_ServerCheck.cxx [493] : /Containers/linux-yerp/FactoryServer is found

th. 140401227716880 - Trace Session_ServerCheck.cxx [495] : FactoryServer container was activated

th. 140401598511008 - Trace Session_ServerLauncher.cxx [229] : Session_ServerLauncher::KillAll()

th. 140401598511008 - Trace SALOME_Session_Server.cxx [607] : Salome_Session_Server:endofserver

th. 140401598511008 end of trace

 

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Nelson Faria at March 26. 2010

Modefied the .bashrc to stop an error that openFOAM is doing with kde. Now I can run as normal user nut still crashes requesting for python container...

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by DAVID Gilles at March 26. 2010

It seems that you are launching Salome with the wrong version of Python.

I see: /usr/lib/python2.6/...

But if you use the universal binary package, it should be: [SALOME_INSTALL_DIR]/SALOME5/Prerequis/Python2.4/...

 

What binary did you download ?

launching SALOME gui on OpenSuse 11.2 x86_64

Posted by J. Wolf at April 11. 2010
After installing SALOME from /repositories/Education:/Salome:/Factory/openSUSE_11.2/x86_64 I did the following as root: ln -s /usr/lib64/python2.6/site-packages/salome/* /usr/lib/python2.6/site-packages/salome/ ln -s /usr/lib64/salome /usr/lib/salome ln -s /usr/lib64/libTKOpenGl* /usr/lib/ Then runSalome starts on my OpenSuse 11.2 x86_64 It seems to be some confusion about library path within the salome packages.

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Alex at October 16. 2011
Hi, I have some news about this issue... after sourcing the proper files, i try to launch salome, and get : alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ ./runSalome CHECK /home/alex Searching for free port for the SALOME Naming Service: 2810 - Ok runSalome running on iskandhar Searching for a free port for naming service: 2810 - OK Searching Naming Service + found in 0.1 seconds Searching /Containers/iskandhar/FactoryServerPy in Naming Service +FactBatchManager of type 'eSGE' inserted into catalog FactBatchManager of type 'ePBS' inserted into catalog FactBatchManager of type 'SH' inserted into catalog FactBatchManager of type 'RSH' inserted into catalog FactBatchManager of type 'SSH' inserted into catalog FactBatchManager of type 'eSGE' inserted into catalog FactBatchManager of type 'ePBS' inserted into catalog FactBatchManager of type 'SH' inserted into catalog FactBatchManager of type 'RSH' inserted into catalog FactBatchManager of type 'SSH' inserted into catalog + found in 1.0 seconds Traceback (most recent call last): File "/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/runSalome.py", line 617, in useSalome clt = startSalome(args, modules_list, modules_root_dir) File "/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/runSalome.py", line 566, in startSalome session=clt.waitNSPID("/Kernel/Session",mySessionServ.PID,SALOME.Session) File "/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/orbmodule.py", line 164, in waitNSPID raise RuntimeError, "Process %d for %s not found" % (thePID,theName) RuntimeError: Process 18000 for /Kernel/Session not found Searching /Kernel/Session in Naming Service --- Error during Salome launch --- >>> But... if i source the environment for Code Aster, which i have in ~/.bashrc : ########################################################## #### My Stuff ########################################################## export PATH=$PATH:/usr/brlcad/bin:/opt/MbDyn/bin:/usr/local/dakota/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/brlcad/lib:/opt/MbDyn/lib:/usr/local/dakota/lib alias OF15="source $HOME/OpenFOAM/OpenFOAM-1.5-dev/etc/bashrc" alias OF17="source /opt/openfoam171/etc/bashrc" alias OF20="source $HOME/OpenFOAM/OpenFOAM-2.0.1/etc/bashrc" alias OF16="source $HOME/OpenFOAM/OpenFOAM-1.6/etc/bashrc" alias work="cd /home/alex/work" alias ccxwork="cd /home/alex/work/Calculix" alias OFWork="cd /home/alex/work/OF" alias BRLWork="cd /home/alex/work/brlcad" ##. /opt/openfoam201/etc/bashrc ##. $HOME/OpenFOAM/OpenFOAM-2.0.1/etc/bashrc ##. $HOME/OpenFOAM/OpenFOAM-1.5-dev/etc/bashrc . /opt/intel/bin/compilervars.sh intel64 . /opt/syrthes3.4.2/bin/syrthes.profile ##. /opt/aster/etc/codeaster/profile.sh and run the launching script of salome, the application starts with no problem... alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ ./runSalome CHECK /home/alex Searching for free port for the SALOME Naming Service: 2810 - Ok runSalome running on iskandhar Searching for a free port for naming service: 2810 - OK Searching Naming Service + found in 0.1 seconds Searching /Containers/iskandhar/FactoryServerPy in Naming Service +FactBatchManager of type 'eSGE' inserted into catalog FactBatchManager of type 'ePBS' inserted into catalog FactBatchManager of type 'SH' inserted into catalog FactBatchManager of type 'RSH' inserted into catalog FactBatchManager of type 'SSH' inserted into catalog FactBatchManager of type 'eSGE' inserted into catalog FactBatchManager of type 'ePBS' inserted into catalog FactBatchManager of type 'SH' inserted into catalog FactBatchManager of type 'RSH' inserted into catalog FactBatchManager of type 'SSH' inserted into catalog + found in 1.0 seconds Searching /Kernel/Session in Naming Service found in 0.0 seconds Start SALOME, elapsed time : 43.1 seconds additional external python interpreters: 0 >>> **************************************************************** * Warning: DSCCODE GUI resources are not found. * DSCCODE GUI will not be available. **************************************************************** But only after sourcing the script /opt/aster/etc/codeaster/profile.sh which has nothing to do with salome universal binaries fro version 5.1.3 How can this be...? the environment files of salome are next, along with my /etc/hosts file : alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ nano SALOME5/V5_1_3/prerequis-V5_1_3.sh INSTALLROOT="/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/Prerequis/" ....................................................................... alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ nano SALOME5/V5_1_3/envSalome-V5_1_3.sh # On d�finit ici l'emplacement d'installation des MODULES de SALOME5. INSTALLROOT=/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/V5_1_3 tag="V5_1_3" .......................................................................... alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ cat /etc/hosts 127.0.0.1 localhost localhost iskandhar 192.168.100.10 iskandhar # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters 127.0.0.2 iskandhar iskandhar alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ Code aster works allright with my settings, and so does Salome 6.3.1 Debian Squeeze installer. I am running this in debian squeeze, and trying to build Salome-Saturne under squeeze, so i would need a working Salome 5.1.3 Why does Salome 5.1.3 only runs after having the Code Aster environment sourced...? BRGDS Alex .....................................................

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Alex at October 16. 2011
Hi, I have some news about this issue... after sourcing the proper files, i try to launch salome, and get : [CODE]alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ ./runSalome CHECK /home/alex Searching for free port for the SALOME Naming Service: 2810 - Ok runSalome running on iskandhar Searching for a free port for naming service: 2810 - OK Searching Naming Service + found in 0.1 seconds Searching /Containers/iskandhar/FactoryServerPy in Naming Service +FactBatchManager of type 'eSGE' inserted into catalog FactBatchManager of type 'ePBS' inserted into catalog FactBatchManager of type 'SH' inserted into catalog FactBatchManager of type 'RSH' inserted into catalog FactBatchManager of type 'SSH' inserted into catalog FactBatchManager of type 'eSGE' inserted into catalog FactBatchManager of type 'ePBS' inserted into catalog FactBatchManager of type 'SH' inserted into catalog FactBatchManager of type 'RSH' inserted into catalog FactBatchManager of type 'SSH' inserted into catalog + found in 1.0 seconds Traceback (most recent call last): File "/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/runSalome.py", line 617, in useSalome clt = startSalome(args, modules_list, modules_root_dir) File "/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/runSalome.py", line 566, in startSalome session=clt.waitNSPID("/Kernel/Session",mySessionServ.PID,SALOME.Session) File "/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/V5_1_3/KERNEL_V5_1_3/bin/salome/orbmodule.py", line 164, in waitNSPID raise RuntimeError, "Process %d for %s not found" % (thePID,theName) RuntimeError: Process 18000 for /Kernel/Session not found Searching /Kernel/Session in Naming Service --- Error during Salome launch --- >>> [/CODE] But... if i source the environment for Code Aster, which i have in ~/.bashrc : [CODE] ########################################################## #### My Stuff ########################################################## export PATH=$PATH:/usr/brlcad/bin:/opt/MbDyn/bin:/usr/local/dakota/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/brlcad/lib:/opt/MbDyn/lib:/usr/local/dakota/lib alias OF15="source $HOME/OpenFOAM/OpenFOAM-1.5-dev/etc/bashrc" alias OF17="source /opt/openfoam171/etc/bashrc" alias OF20="source $HOME/OpenFOAM/OpenFOAM-2.0.1/etc/bashrc" alias OF16="source $HOME/OpenFOAM/OpenFOAM-1.6/etc/bashrc" alias work="cd /home/alex/work" alias ccxwork="cd /home/alex/work/Calculix" alias OFWork="cd /home/alex/work/OF" alias BRLWork="cd /home/alex/work/brlcad" ##. /opt/openfoam201/etc/bashrc ##. $HOME/OpenFOAM/OpenFOAM-2.0.1/etc/bashrc ##. $HOME/OpenFOAM/OpenFOAM-1.5-dev/etc/bashrc . /opt/intel/bin/compilervars.sh intel64 . /opt/syrthes3.4.2/bin/syrthes.profile ##. /opt/aster/etc/codeaster/profile.sh [/CODE] and run the launching script of salome, the application starts with no problem... [CODE] alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ ./runSalome CHECK /home/alex Searching for free port for the SALOME Naming Service: 2810 - Ok runSalome running on iskandhar Searching for a free port for naming service: 2810 - OK Searching Naming Service + found in 0.1 seconds Searching /Containers/iskandhar/FactoryServerPy in Naming Service +FactBatchManager of type 'eSGE' inserted into catalog FactBatchManager of type 'ePBS' inserted into catalog FactBatchManager of type 'SH' inserted into catalog FactBatchManager of type 'RSH' inserted into catalog FactBatchManager of type 'SSH' inserted into catalog FactBatchManager of type 'eSGE' inserted into catalog FactBatchManager of type 'ePBS' inserted into catalog FactBatchManager of type 'SH' inserted into catalog FactBatchManager of type 'RSH' inserted into catalog FactBatchManager of type 'SSH' inserted into catalog + found in 1.0 seconds Searching /Kernel/Session in Naming Service found in 0.0 seconds Start SALOME, elapsed time : 43.1 seconds additional external python interpreters: 0 >>> **************************************************************** * Warning: DSCCODE GUI resources are not found. * DSCCODE GUI will not be available. **************************************************************** [/CODE] But only after sourcing the script /opt/aster/etc/codeaster/profile.sh which has nothing to do with salome universal binaries fro version 5.1.3 How can this be...? the environment files of salome are next, along with my /etc/hosts file : [CODE] alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ nano SALOME5/V5_1_3/prerequis-V5_1_3.sh INSTALLROOT="/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/Prerequis/" ....................................................................... alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ nano SALOME5/V5_1_3/envSalome-V5_1_3.sh # On d�finit ici l'emplacement d'installation des MODULES de SALOME5. INSTALLROOT=/home/alex/pkgs/SPlat/Salome_5.1.3/SALOME5/V5_1_3 tag="V5_1_3" .......................................................................... alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ cat /etc/hosts 127.0.0.1 localhost localhost iskandhar 192.168.100.10 iskandhar # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters 127.0.0.2 iskandhar iskandhar alex@iskandhar:~/pkgs/SPlat/Salome_5.1.3$ [/CODE] Code aster works allright with my settings, and so does Salome 6.3.1 Debian Squeeze installer. I am running this in debian squeeze, and trying to build Salome-Saturne under squeeze, so i would need a working Salome 5.1.3 Why does Salome 5.1.3 only runs after having the Code Aster environment sourced...? BRGDS Alex .....................................................

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by Alex at October 16. 2011
What shoud i do to post my message into a human readable form... ??!! :( BRGDS Alex

Re: 5.1.3 stalling at launch on openSuse 11.2

Posted by DAVID Gilles at October 16. 2011

Hello Alex,

Please next time try to post a new thread since this a different problem than the original one.

Concerning your problem, please see this thread: http://www.salome-platform.org/forum/forum_9/322811199

Regards,

Gilles

Powered by Ploneboard
Document Actions