Dear sirs,
I have a fresh install of orocos-toolchain it was installed on gnulinux on UBUNTU 10.04 32 bit the installation was done issuing the following commands
mkdir orocos-toolchain cd orocos-toolchain wget http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.1/bootstrap.sh sh bootstrap.sh source env.sh
Corba support was enabled with default option OMNIORB.
before installing orocos-toolchain I installed CORBA as suggested in "The OROCOS Real-Time Toolkit Installation Guide" using the following command
sudo aptitude install libtao-orbsvcs-dev tao-idl gperf-ace tao-naming
After that I used the example NAME.orogen that can be found in
/usr/src/orocos-toolchain/orogen/misc/new_project
I run the following commands to create the runnable program
orogen --target=gnulinux -v NAME.orogen mkdir build cd build cmake -G "Unix Makefiles" ../ make
after this I execute the command omniNames -start &
and then I ran the program with the command
./NAME_test
and I got the following errors 0.004 [ Warning][Thread] Forcing priority (1) of thread with SCHED_OTHER policy to 0. 0.007 [ Warning][TaskContextServer()] CTaskContext 'NAME' could not find CORBA Naming Service. 0.007 [ Warning][TaskContextServer()] Writing IOR to 'std::cerr' and file 'NAME.ior' IOR:010000001f00000049444c3a5254542f636f7262612f435461736b436f6e746578743a312e300000010000000000000064000000010102000d0000003139322e3136382e322e313100006fb40e000000fea69dce4c00000750000000000000000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
I even tryed the other solutions showed in
http://orocos.org/wiki/rtt/frequently-asked-questions-faq/using-corba
but I always got the same errors?
What am I doing wrong or missing?
Thank you for your support.
Gianpaolo Rizzi
CTaskContext 'NAME' could not find CORBA Naming Service - orogen
On 11/01/2010 01:20 PM, gprizzi [..] ... wrote:
> sudo aptitude install libtao-orbsvcs-dev tao-idl gperf-ace tao-naming
If you are using OmniORB, you do not need to do that. Actually,
installing tao-naming might be harmful as tao-naming and omniNames might
clash.
> After that I used the example NAME.orogen that can be found in
>
> /usr/src/orocos-toolchain/orogen/misc/new_project
>
> I run the following commands to create the runnable program
>
> orogen --target=gnulinux -v NAME.orogen
> mkdir build
> cd build
> cmake -G "Unix Makefiles" ../
> make
>
> after this I execute the command
> omniNames -start&
>
> and then I ran the program with the command
>
> ./NAME_test
>
> and I got the following errors
> 0.004 [ Warning][Thread] Forcing priority (1) of thread with SCHED_OTHER policy to 0.
> 0.007 [ Warning][TaskContextServer()] CTaskContext 'NAME' could not find CORBA Naming Service.
> 0.007 [ Warning][TaskContextServer()] Writing IOR to 'std::cerr' and file 'NAME.ior'
> IOR:010000001f00000049444c3a5254542f636f7262612f435461736b436f6e746578743a312e300000010000000000000064000000010102000d0000003139322e3136382e322e313100006fb40e000000fea69dce4c00000750000000000000000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
Try editing /etc/omniORB.cfg and add a line
InitRef = NameService=corbaname::localhost
Then try again.
CTaskContext 'NAME' could not find CORBA Naming Service - orogen
On Nov 1, 2010, at 09:20 , Sylvain Joyeux wrote:
> On 11/01/2010 01:20 PM, gprizzi [..] ... wrote:
>> sudo aptitude install libtao-orbsvcs-dev tao-idl gperf-ace tao-naming
> If you are using OmniORB, you do not need to do that. Actually,
> installing tao-naming might be harmful as tao-naming and omniNames might
> clash.
>
>> After that I used the example NAME.orogen that can be found in
>>
>> /usr/src/orocos-toolchain/orogen/misc/new_project
>>
>> I run the following commands to create the runnable program
>>
>> orogen --target=gnulinux -v NAME.orogen
>> mkdir build
>> cd build
>> cmake -G "Unix Makefiles" ../
>> make
>>
>> after this I execute the command
>> omniNames -start&
>>
>> and then I ran the program with the command
>>
>> ./NAME_test
>>
>> and I got the following errors
>> 0.004 [ Warning][Thread] Forcing priority (1) of thread with SCHED_OTHER policy to 0.
>> 0.007 [ Warning][TaskContextServer()] CTaskContext 'NAME' could not find CORBA Naming Service.
>> 0.007 [ Warning][TaskContextServer()] Writing IOR to 'std::cerr' and file 'NAME.ior'
>> IOR:010000001f00000049444c3a5254542f636f7262612f435461736b436f6e746578743a312e300000010000000000000064000000010102000d0000003139322e3136382e322e313100006fb40e000000fea69dce4c00000750000000000000000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
>
> Try editing /etc/omniORB.cfg and add a line
>
> InitRef = NameService=corbaname::localhost
>
> Then try again.
Does this work for you in Ubuntu 10.04, Sylvain? Specifying localhost on the command line as part of a "--ORBInitRef" doesn't work. If localhost doesn't work, specify an IP address directly.
Also, I wouldn't start omniNames directly. Just restart the service - "sudo /etc/init.d/omninames restart" (might be something slightly different than "omninames")
S
CTaskContext 'NAME' could not find CORBA Naming Service - orogen
On 11/01/2010 02:26 PM, S Roderick wrote:
> On Nov 1, 2010, at 09:20 , Sylvain Joyeux wrote:
>
>> On 11/01/2010 01:20 PM, gprizzi [..] ... wrote:
>>> sudo aptitude install libtao-orbsvcs-dev tao-idl gperf-ace tao-naming
>> If you are using OmniORB, you do not need to do that. Actually,
>> installing tao-naming might be harmful as tao-naming and omniNames might
>> clash.
>>
>>> After that I used the example NAME.orogen that can be found in
>>>
>>> /usr/src/orocos-toolchain/orogen/misc/new_project
>>>
>>> I run the following commands to create the runnable program
>>>
>>> orogen --target=gnulinux -v NAME.orogen
>>> mkdir build
>>> cd build
>>> cmake -G "Unix Makefiles" ../
>>> make
>>>
>>> after this I execute the command
>>> omniNames -start&
>>>
>>> and then I ran the program with the command
>>>
>>> ./NAME_test
>>>
>>> and I got the following errors
>>> 0.004 [ Warning][Thread] Forcing priority (1) of thread with SCHED_OTHER policy to 0.
>>> 0.007 [ Warning][TaskContextServer()] CTaskContext 'NAME' could not find CORBA Naming Service.
>>> 0.007 [ Warning][TaskContextServer()] Writing IOR to 'std::cerr' and file 'NAME.ior'
>>> IOR:010000001f00000049444c3a5254542f636f7262612f435461736b436f6e746578743a312e300000010000000000000064000000010102000d0000003139322e3136382e322e313100006fb40e000000fea69dce4c00000750000000000000000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
>> Try editing /etc/omniORB.cfg and add a line
>>
>> InitRef = NameService=corbaname::localhost
>>
>> Then try again.
>
> Does this work for you in Ubuntu 10.04, Sylvain? Specifying localhost on the command line as part of a "--ORBInitRef" doesn't work. If localhost doesn't work, specify an IP address directly.
The way that I *know* works is to export the ORBInitRef environment
variable to the same value. That's what orocos.rb does behind the scenes
and I had no complaints at DFKI since I made it do that.
I.e.
export ORBInitRef="NameService=corbaname::localhost"
For orogen-generated deployments, --ORBInitRef does not work since, as
far as I remember, the arguments don't get passed to the ORB
initialization function.
> Also, I wouldn't start omniNames directly. Just restart the service - "sudo /etc/init.d/omninames restart" (might be something slightly different than "omninames")
+1. The script is
/etc/init.d/omniorb4-nameserver
Another important test is to check if omniNames is listening with
sudo netstat -tlpn
CTaskContext 'NAME' could not find CORBA Naming Service - orogen
On Nov 1, 2010, at 09:32 , Sylvain Joyeux wrote:
> On 11/01/2010 02:26 PM, S Roderick wrote:
>> On Nov 1, 2010, at 09:20 , Sylvain Joyeux wrote:
>>
>>> On 11/01/2010 01:20 PM, gprizzi [..] ... wrote:
>>>> sudo aptitude install libtao-orbsvcs-dev tao-idl gperf-ace tao-naming
>>> If you are using OmniORB, you do not need to do that. Actually,
>>> installing tao-naming might be harmful as tao-naming and omniNames might
>>> clash.
>>>
>>>> After that I used the example NAME.orogen that can be found in
>>>>
>>>> /usr/src/orocos-toolchain/orogen/misc/new_project
>>>>
>>>> I run the following commands to create the runnable program
>>>>
>>>> orogen --target=gnulinux -v NAME.orogen
>>>> mkdir build
>>>> cd build
>>>> cmake -G "Unix Makefiles" ../
>>>> make
>>>>
>>>> after this I execute the command
>>>> omniNames -start&
>>>>
>>>> and then I ran the program with the command
>>>>
>>>> ./NAME_test
>>>>
>>>> and I got the following errors
>>>> 0.004 [ Warning][Thread] Forcing priority (1) of thread with SCHED_OTHER policy to 0.
>>>> 0.007 [ Warning][TaskContextServer()] CTaskContext 'NAME' could not find CORBA Naming Service.
>>>> 0.007 [ Warning][TaskContextServer()] Writing IOR to 'std::cerr' and file 'NAME.ior'
>>>> IOR:010000001f00000049444c3a5254542f636f7262612f435461736b436f6e746578743a312e300000010000000000000064000000010102000d0000003139322e3136382e322e313100006fb40e000000fea69dce4c00000750000000000000000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
>>> Try editing /etc/omniORB.cfg and add a line
>>>
>>> InitRef = NameService=corbaname::localhost
>>>
>>> Then try again.
>>
>> Does this work for you in Ubuntu 10.04, Sylvain? Specifying localhost on the command line as part of a "--ORBInitRef" doesn't work. If localhost doesn't work, specify an IP address directly.
> The way that I *know* works is to export the ORBInitRef environment variable to the same value. That's what orocos.rb does behind the scenes and I had no complaints at DFKI since I made it do that.
>
> I.e.
>
> export ORBInitRef="NameService=corbaname::localhost"
>
> For orogen-generated deployments, --ORBInitRef does not work since, as far as I remember, the arguments don't get passed to the ORB initialization function.
Interesting, so it might be that omniORB gets confused between the ORBInitRef value (env or cmd-line option) and what is in the config file. Worth investigating ... interesting thing is, passing ORBInitRef w/ localhost works fine on the Mac.
CTaskContext 'NAME' could not find CORBA Naming Service - orogen
On 11/01/2010 01:20 PM, gprizzi [..] ... wrote:
> Dear sirs,
>
> I have a fresh install of orocos-toolchain
> it was installed on gnulinux on UBUNTU 10.04 32 bit
> the installation was done issuing the following commands
>
> mkdir orocos-toolchain
> cd orocos-toolchain
> wget http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.1/boot...
> sh bootstrap.sh
> source env.sh
>
> Corba support was enabled with default option OMNIORB.
>
> before installing orocos-toolchain I installed CORBA as suggested in
> "The OROCOS Real-Time Toolkit Installation Guide"
> using the following command
>
> sudo aptitude install libtao-orbsvcs-dev tao-idl gperf-ace tao-naming
>
> After that I used the example NAME.orogen that can be found in
>
> /usr/src/orocos-toolchain/orogen/misc/new_project
>
> I run the following commands to create the runnable program
I unfortunately realize that I forgot to mention that in the documentation.
You can create a new orogen project with
orogen create project_name
for instance
orogen create test
which will create a test/ directory including a test.orogen file.
CTaskContext 'NAME' could not find CORBA Naming Service - orogen
Dear sirs,
I have a fresh install of orocos-toolchain
it was installed on gnulinux on UBUNTU 10.04 32 bit
the installation was done issuing the following commands
mkdir orocos-toolchain
cd orocos-toolchain
wget http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.1/boot...
sh bootstrap.sh
source env.sh
Corba support was enabled with default option OMNIORB.
before installing orocos-toolchain I installed CORBA as suggested in
"The OROCOS Real-Time Toolkit Installation Guide"
using the following command
sudo aptitude install libtao-orbsvcs-dev tao-idl gperf-ace tao-naming
After that I used the example NAME.orogen that can be found in
/usr/src/orocos-toolchain/orogen/misc/new_project
I run the following commands to create the runnable program
orogen --target=gnulinux -v NAME.orogen
mkdir build
cd build
cmake -G "Unix Makefiles" ../
make
after this I execute the command
omniNames -start &
and then I ran the program with the command
./NAME_test
and I got the following errors
0.004 [ Warning][Thread] Forcing priority (1) of thread with SCHED_OTHER policy to 0.
0.007 [ Warning][TaskContextServer()] CTaskContext 'NAME' could not find CORBA Naming Service.
0.007 [ Warning][TaskContextServer()] Writing IOR to 'std::cerr' and file 'NAME.ior'
IOR:010000001f00000049444c3a5254542f636f7262612f435461736b436f6e746578743a312e300000010000000000000064000000010102000d0000003139322e3136382e322e313100006fb40e000000fea69dce4c00000750000000000000000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
I even tryed the other solutions showed in
http://orocos.org/wiki/rtt/frequently-asked-questions-faq/using-corba
but I always got the same errors?
What am I doing wrong or missing?
Thank you for your support.
Gianpaolo Rizzi