Salome freeze "checking naming service"
- Eric
- Topic Author
- Visitor
-
19 years 5 months ago #42
by Eric
Replied by Eric on topic Re:Salome freeze "checking naming service"
Hi,
/opt/salome/Salome.sh
Searching for a free port for naming service: 2810 - Ok
Launch configuration file does not exist. Create default: /root/.salome_2.2.2/salome.launch
source= []
opts= {}
args= {u'portkill': 1, 'file': 0, u'killall': 0, 'embedded': , 'standalone': , 'appname': 'salome', 'modules': , u'gui': 1, u'xterm': 0, 'SMESH_plugins': , 'key': [], u'logger': 0, 'interp': 0, 'port': 2810, 'containers': []}
le fichier /tmp/root_2810_SALOME_pidict des process SALOME n'est pas accessible
startSalome {u'portkill': 1, 'file': 0, u'killall': 0, 'embedded': , 'standalone': , 'appname': 'salome', 'modules': , u'gui': 1, u'xterm': 0, 'SMESH_plugins': , 'key': [], u'logger': 0, 'interp': 0, 'port': 2810, 'containers': []}
Lancement du Naming Service runNS.sh > /tmp/logs/root/salomeNS.log 2>&1
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Searching Naming Service ++++++++++Failed to narrow the root naming context
Traceback (most recent call last):
File \"/opt/salome/KERNEL_2.2.2/bin/salome/runSalome.py\", line 667, in useSalome
clt = startSalome(args, modules_list, modules_root_dir)
File \"/opt/salome/KERNEL_2.2.2/bin/salome/runSalome.py\", line 490, in startSalome
clt=orbmodule.client()
File \"/opt/salome/KERNEL_2.2.2/bin/salome/orbmodule.py\", line 40, in __init__
self.initNS()
File \"/opt/salome/KERNEL_2.2.2/bin/salome/orbmodule.py\", line 73, in initNS
sys.exit(1)
SystemExit: 1
--- erreur au lancement Salome ---
Saving of the dictionary of Salome processes in /tmp/root_2810_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.
[root@dhcppc1 root]#
Good luck.
Eric
/opt/salome/Salome.sh
Searching for a free port for naming service: 2810 - Ok
Launch configuration file does not exist. Create default: /root/.salome_2.2.2/salome.launch
source= []
opts= {}
args= {u'portkill': 1, 'file': 0, u'killall': 0, 'embedded': , 'standalone': , 'appname': 'salome', 'modules': , u'gui': 1, u'xterm': 0, 'SMESH_plugins': , 'key': [], u'logger': 0, 'interp': 0, 'port': 2810, 'containers': []}
le fichier /tmp/root_2810_SALOME_pidict des process SALOME n'est pas accessible
startSalome {u'portkill': 1, 'file': 0, u'killall': 0, 'embedded': , 'standalone': , 'appname': 'salome', 'modules': , u'gui': 1, u'xterm': 0, 'SMESH_plugins': , 'key': [], u'logger': 0, 'interp': 0, 'port': 2810, 'containers': []}
Lancement du Naming Service runNS.sh > /tmp/logs/root/salomeNS.log 2>&1
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Searching Naming Service ++++++++++Failed to narrow the root naming context
Traceback (most recent call last):
File \"/opt/salome/KERNEL_2.2.2/bin/salome/runSalome.py\", line 667, in useSalome
clt = startSalome(args, modules_list, modules_root_dir)
File \"/opt/salome/KERNEL_2.2.2/bin/salome/runSalome.py\", line 490, in startSalome
clt=orbmodule.client()
File \"/opt/salome/KERNEL_2.2.2/bin/salome/orbmodule.py\", line 40, in __init__
self.initNS()
File \"/opt/salome/KERNEL_2.2.2/bin/salome/orbmodule.py\", line 73, in initNS
sys.exit(1)
SystemExit: 1
--- erreur au lancement Salome ---
Saving of the dictionary of Salome processes in /tmp/root_2810_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.
[root@dhcppc1 root]#
Good luck.
Eric
- admin
- Topic Author
- Visitor
-
19 years 5 months ago #43
by admin
Replied by admin on topic Re:Salome freeze "checking naming service"
Hello,
thank you for these details. After SALOME hangs, could you please copy and send me the file /tmp/logs/root/salomeNS.log
I think that this problem could come from a misleading DNS search: I think your router has a DNS relay/server but maybe dhcppc1 is not in the DNS records of your router and/or the Linux resolv.conf does prevent the resolution of local DNS names like dhcppc1. I have to test these hypothesis but it seems to be the most probable reason.
Lancement du Naming Service runNS.sh > /tmp/logs/root/salomeNS.log 2>&1
thank you for these details. After SALOME hangs, could you please copy and send me the file /tmp/logs/root/salomeNS.log
I think that this problem could come from a misleading DNS search: I think your router has a DNS relay/server but maybe dhcppc1 is not in the DNS records of your router and/or the Linux resolv.conf does prevent the resolution of local DNS names like dhcppc1. I have to test these hypothesis but it seems to be the most probable reason.
- Eric
- Topic Author
- Visitor
-
19 years 5 months ago #48
by Eric
Replied by Eric on topic Re:Salome freeze "checking naming service"
Hi,
Sorry, but the directory is empty !?
[root@dhcppc1 root]# cd /
[root@dhcppc1 /]# cd /tmp/logs/root
[root@dhcppc1 root]# ls -al
total 0
drwxrwxrwx 2 root root 40 Nov 24 22:03 ./
drwxrwxrwx 3 root root 60 Nov 24 22:03 ../
Eric
Sorry, but the directory is empty !?
[root@dhcppc1 root]# cd /
[root@dhcppc1 /]# cd /tmp/logs/root
[root@dhcppc1 root]# ls -al
total 0
drwxrwxrwx 2 root root 40 Nov 24 22:03 ./
drwxrwxrwx 3 root root 60 Nov 24 22:03 ../
Eric
- admin
- Topic Author
- Visitor
-
19 years 5 months ago #73
by admin
Replied by admin on topic Re:Salome freeze "checking naming service"
Sorry Eric,
but I didn't had time to try to reproduce your problem for the moment. But I will try to do it as soon as I can find some time...
but I didn't had time to try to reproduce your problem for the moment. But I will try to do it as soon as I can find some time...
- Olivier
- Topic Author
- Visitor
-
19 years 5 months ago #85
by Olivier
Replied by Olivier on topic Re:Salome freeze "checking naming service"
Hi,
I have the same problem. Salome freeze.
I wait, and as soon as it's possible, I close the Salome window (using the \"close\" in the toolbar).
Then I restart Salome and it works.
Reggards,
Olivier.
Thanks for this livecd.
I have the same problem. Salome freeze.
I wait, and as soon as it's possible, I close the Salome window (using the \"close\" in the toolbar).
Then I restart Salome and it works.

Reggards,
Olivier.
Thanks for this livecd.
- dmetzler
- Topic Author
- Visitor
-
19 years 5 months ago #86
by dmetzler
Replied by dmetzler on topic Re:Salome freeze "checking naming service"
Try setting your hostname to \"localhost\" and see if Salome runs. I had to do this on my system. From the looks of your ifconfig output, I'd say you're behind a ZyXEL DSL router.
Moderators: catux
Time to create page: 0.172 seconds