SALOME failed to start

Bug #783186 reported by Norbert
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
salome (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: salome

Installed SALOME from Natty package salome (and salome-common).

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: salome 5.1.3-12ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CheckboxSubmission: a3c9de473bf7a483a92609c6b20d2aee
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
Date: Mon May 16 00:28:32 2011
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: salome
UpgradeStatus: Upgraded to natty on 2011-05-01 (13 days ago)

Revision history for this message
Norbert (nrbrtx) wrote :
Revision history for this message
Norbert (nrbrtx) wrote :
Revision history for this message
Norbert (nrbrtx) wrote :

Tried with and without omniorb package. In both cases I got the same error (see log below).
My /etc/hosts is in attachment.

runSalome running on norbert-vaio
Configure parser: Warning : could not find user configuration file
Searching for a free port for naming service: 2810 2811 2812 2813 2814 2815 - OK
Searching Naming Service ++++++++++Failed to narrow the root naming context
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/salome/runSalome.py", line 617, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
  File "/usr/lib/python2.7/dist-packages/salome/runSalome.py", line 417, in startSalome
    clt=orbmodule.client(args)
  File "/usr/share/pyshared/salome/orbmodule.py", line 49, in __init__
    self.initNS(args or {})
  File "/usr/share/pyshared/salome/orbmodule.py", line 82, in initNS
    sys.exit(1)
SystemExit: 1

--- Error during Salome launch ---

Revision history for this message
Rubendebruin (rubendebruin) wrote :

Exactly the same error here, runnning Ubuntu 11.04 (upgraded from 10.10) , all upgrades installed may 18, 2011

Revision history for this message
tobin (nadlerto) wrote :

I also get this error on Kubuntu 11.04, May 28

Revision history for this message
Evert van Vliet (evertvanvliet) wrote :

I've got the same error, runnning Ubuntu 11.04 (upgraded from 10.10) , all upgrades installed may 29, 2011

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

It fails to start in Ubuntu Oneiric (11.10) as well, but I get a slightly different error message:

$ runSalome --gui
Configure parser: Warning : could not find user configuration file
runSalome running on ubuntu
Configure parser: Warning : could not find user configuration file
Searching for a free port for naming service: 2810 2811 2812 2813 - OK
Searching Naming Service + found in 0.1 seconds
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/salome/runSalome.py", line 617, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
  File "/usr/lib/python2.7/dist-packages/salome/runSalome.py", line 446, in startSalome
    myServer=NotifyServer(args,modules_root_dir)
  File "/usr/lib/python2.7/dist-packages/salome/runSalome.py", line 383, in __init__
    myLogName = os.environ["LOGNAME"]
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'LOGNAME'

--- Error during Salome launch ---

Changed in salome (Ubuntu):
status: New → Confirmed
tags: added: oneiric
Revision history for this message
Norbert (nrbrtx) wrote :

With --gui flag I got:

$ runSalome --gui
Configure parser: Warning : could not find user configuration file
runSalome running on norbert-vaio
Configure parser: Warning : could not find user configuration file
Searching for a free port for naming service: 2810 - OK
Searching Naming Service ++++++++++Failed to narrow the root naming context
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/salome/runSalome.py", line 617, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
  File "/usr/lib/python2.7/dist-packages/salome/runSalome.py", line 417, in startSalome
    clt=orbmodule.client(args)
  File "/usr/share/pyshared/salome/orbmodule.py", line 49, in __init__
    self.initNS(args or {})
  File "/usr/share/pyshared/salome/orbmodule.py", line 82, in initNS
    sys.exit(1)
SystemExit: 1

--- Error during Salome launch ---
>>>

What did you do to avoid 'Failed to narrow the root naming context' message? :)

Revision history for this message
Christoph Buchner (bilderbuchi) wrote :

maybe it would be worthwhile to package the new salome release (6.3) into a PPA? Many bugs have been fixed. http://www.salome-platform.org/news/11-jun-2011-salome-version-6.3.0
Does anyone have the skills for that?

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

>What did you do to avoid 'Failed to narrow the root naming context' message?
Norbert: I am afraid I don't think I will be of much help there. I am mainly checking bug reports and see if I can reproduce issues so all I have done is basically installed and attempted to run the program.

Revision history for this message
Norbert (nrbrtx) wrote :

@Hans
OK. Let's wait for solution from others.

Revision history for this message
Andreas Moog (ampelbein) wrote :

The "Failed to narrow the root naming context" is an error displayed when there is no entry in /etc/hosts corresponding to your hostname. So, you need (using Norbert's hostname):

127.0.0.2 norbert-vaio

in /etc/hosts.

Changed in salome (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Norbert (nrbrtx) wrote :

@Andreas Moog (amoog)
Thank you.
Now in /etc/hosts I have:

127.0.0.1 localhost norbert-vaio
127.0.0.2 norbert-vaio
::1 norbert-vaio localhost6.localdomain6 localhost6
#127.0.1.1 norbert-vaio

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

What am I doing wrong?

Revision history for this message
GreatBunzinni (greatbunzinni) wrote :

I've just tried to install salome and my installation also failed to run. I'm running Kubuntu 10.04.

Revision history for this message
Theo (theo-virtual) wrote :

The error is due to a missing definition of the LOGNAME variable within the environment. It has to point to your user name, so you can use the USER variable to define it (in case you have more than one user in the box). Finally, you can either export it by hand or add it at the end of .bashrc

By hand:
export LOGNAME=$USER

Added to your local .bashrc:
(be sure to be at the root of your home directory)
echo "export LOGNAME=\$USER" >> .bashrc

If its for all the users in the box:
echo "export LOGNAME=\$USER" >> /etc/bash.bashrc

C-u around!
Theo

Revision history for this message
tobin (nadlerto) wrote :

I just tried this without success (same error as before):

export LOGNAME=$USER
runSalome -g
(it does not matter, whether -g is appended or not)

Revision history for this message
Norbert (nrbrtx) wrote :

I got the same result as in #16.

Revision history for this message
tobin (nadlerto) wrote :

On my system, Salome starts successfully after an dist-upgrade to 11.10, though it is not part of 11.10 any more (i.e. I am using salome package of Ubuntu 11.04 in Ubuntu 11.10).

Revision history for this message
Norbert (nrbrtx) wrote :

I solved the problem under 11.04. I disabled IPv6 records in /etc/hosts:
cat /etc/hosts
127.0.0.1 localhost norbert-vaio
127.0.0.2 norbert-vaio
#::1 norbert-vaio localhost6.localdomain6 localhost6
#127.0.1.1 norbert-vaio

# The following lines are desirable for IPv6 capable hosts
#::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Thanks to [http://powerpan.blogspot.com/2009/11/installing-salome-platfrom-on-fedora-12.html] and Russian guys from LOR [http://www.linux.org.ru/forum/desktop/6241867].

Norbert (nrbrtx)
tags: removed: natty oneiric
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.