RuntimeError: Process XXX for /Registry not found

Good evening,

I'm using SALOME together with an optimisation software called Nimrod/O (this software launches different cases with different values for certain variables).

The work i'm doing with SALOME is creating a rectangle in CAD (using a python script in which I read the values from Nimrod/O), meshing it and produce a UNV file. Everything works OK, but sometimes the following message appears (I'll copy the full trace received by SALOME):

Traceback (most recent call last):

  File "/home/javi/Thesis/Salome/Salome-V5_1_5_32bit/SALOME5/V5_1_5/KERNEL_V5_1_5/bin/salome/runSalome.py", line 608, in useSalome

    clt = startSalome(args, modules_list, modules_root_dir)

  File "/home/javi/Thesis/Salome/Salome-V5_1_5_32bit/SALOME5/V5_1_5/KERNEL_V5_1_5/bin/salome/runSalome.py", line 459, in startSalome

    clt.waitNSPID("/Registry",myServer.PID)

  File "/home/javi/Thesis/Salome/Salome-V5_1_5_32bit/SALOME5/V5_1_5/KERNEL_V5_1_5/bin/salome/orbmodule.py", line 164, in waitNSPID

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

RuntimeError: Process 11874 for /Registry not found

I receive this error randomly (sometimes after a few executions, 5 or 6, sometimes after computing around 15 or 16 times), and I don't have any idea about why it is happening. I'm launching SALOME like this (( ./runSalome -t -u file.py -k & )) and if I redirect the output of this call to a logfile, I get the following message:

ROOT_SALOME: /home/javi/Thesis/Salome/Salome-V5_1_5_32bit/SALOME5/V5_1_5

Loading environnement for python 2.4

CHECK /home/javi

Searching for free port for the SALOME Naming Service: 2810 - Ok

runSalome running on javi-XXX-XXX

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

Searching /Registry in Naming Service +

--- Error during Salome launch ---

Thank you for your time.

Kind regards,

Hi

I use Dakota to do some optimization.

In my script for running Salome i need to run it like so

xterm -e /share/apps/salome-6.5.0/appli_V6_5_0p1/runAppli -t -u dump.py --shutdown-servers=1

The reason for using xterm -e is that if I run multiple optimization points at the same time Salome will crash because it cant handle launching more than one instance in one terminal window. So xterm -e will launch a terminal window and run the commands. After the commands are done it will gracefully exit and run the next step in the optimization script.

Hope this helps.