Personal tools
You are here: Home Forum Use Clean salome ports

Clean salome ports

Up to Use

Clean salome ports

Posted by alexandre at June 24. 2015

Hi,

this post continue my previous post here

As I said in my previous post, I had a message error when during a mesh generation without GUI: salome can't kill local port a the end of the script:

Terminating SALOME on port 2897...
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/home/choco/salome_7.5.1/Python-2.7.3/lib/python2.7/threading.py", line 551, in __bootstrap_inner
    self.run()
  File "/home/choco/salome_7.5.1/Python-2.7.3/lib/python2.7/threading.py", line 504, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/home/choco/salome_7.5.1/KERNEL_7.5.1/bin/salome/killSalomeWithPort.py", line 192, in shutdownMyPort
    **kwargs)
  File "/home/choco/salome_7.5.1/KERNEL_7.5.1/bin/salome/salome_utils.py", line 272, in generateFileName
    from launchConfigureParser import verbose
ImportError: No module named launchConfigureParser

problem in killLocalPort()

Now, there is no free port avaliable!! Even after a computer reboot...

I can launch Salome with GUI (currently on port 2820), but I can't without GUI

I tried :

./runAppli -k

./runAppli -p

./runAppli --ns-port-log=salomePortLog.txt

and I have alwayse the same message: 

Can't find a free port to launch omniNames

Try to kill the running servers and then launch SALOME again.

It seems that there is no avaliable port for the without GUI mode.

 

Is a way exists to clean salome port ?

 

I saw this

post but I hope there is another solution but reinstall salome 7.5.1...

 

Thanks,

 

Alex.

 

 

 

Re: Clean salome ports

Posted by Vadim SANDLER at June 24. 2015

Hello Alex,

This seems to be a bug of a SALOME launcher - we'll check that.

Meantime, removal of .omniORB_PortManager.cfg file from your home directory should solve the problem.

Regards,
Vadim.

Re: Clean salome ports

Posted by alexandre at June 24. 2015

Helo Vadim, 

I tried either removing tne .omniORP_PortManager.cfg and all .omniORB* files in my home but it doesn't work.

I solved my problem adding "busy_ports = []" after the  "busy_ports = config["busy_ports"]" (line 129 in salome_7.5.1/salome_appli_7.5.1/bin/salome/Portanager.py).

It's not the cleanest solution but it works!!

It seams salome not update properly the list of free ports.

Regards.

Alex.

 

Re: Clean salome ports

Posted by Vadim SANDLER at June 24. 2015

Hello Alex,

Yes,exactly - as I said, there's a bug in SALOME launcher, namely in a port manager. It is to be analyzed.

Regarding your case, I have forgotten that in case of using application skeleton scripts, i.e. runAppli, runSession etc the .omniORP_PortManager.cfg is created not in the home directory but in the USERS subfolder of your application skeleton directory. I.e. if you installed SALOME 7.5.1 from universal binaries, see appli_V7_5_1/USERS directory.

Regards,
Vadim.

Re: Clean salome ports

Posted by MZX at September 25. 2015

Hi Vadim and Alex,

I have pretty much the same problem but under Windows 7 (see here).

Removing .omniORP_PortManager.cfg located in \TMP did not help. I did not find any other file with same name in other folders.

Modifying \SALOME-7.5.1-WIN64\MODULES\KERNEL\bin\salome\PortManager.py did not help either.

I appreciate your advice.

Thanks,

MZ 

Re: Clean salome ports

Posted by Saint Michael at September 25. 2015

Hi

I did not find any other file with same name in other folders.

Have you checked TEMP directory within SALOME installation for *.cfg files?

You need to find files named like .omniORB_*_2810.cfg.

St.Michael

Re: Clean salome ports

Posted by MZX at September 25. 2015

in D:\SALOME-7.5.1-WIN64\TMP I have three .cfg files:

.omniORB_ana_anastex_2811.cfg

.omniORB_ana_last.cfg

.omniORB_PortManager.cfg

I deleted all and nothing happened.

 

Re: Clean salome ports

Posted by MZX at September 25. 2015

I don't know if this would help or not but I have different versions of Salome on my PC: 7.3, 7.4, 7.5, 7.6. I just tested the other versions and I should say that 7.3 and 7.4 work fine but both 7.5 and 7.6 have this issue.

Powered by Ploneboard
Document Actions