Deployer problem

Submitted by pierre on Tue, 2010-07-06 08:44

Orocos-users

Hi,

we have a problem when we use the deployer of our package.
See the error message. The library files exist but seems to be "not valid
component library".

We have tried "make wipe on ocl" and "rosmake" but it is the same problem.

root@lias-desktop:/home/lias/kul-ros-pkg/soem_ethercat_drivers# rosrun
ocl_2.0 deployer-gnulinux -s soem_master.xml
[rosrun] You have chosen a non-unique executable, please pick one of the
following:
1) /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
2) /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer-gnulinux
#? 1
0.604 [ ERROR ][DeploymentComponent::configure] Unloading
/home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3:
not a valid component library:
0.604 [ ERROR ][DeploymentComponent::configure]
/home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3:
undefined symbol
0.741 [ Warning][DeploymentComponent::configure] Component type name
OCL::HelloWorld already used: overriding.
0.787 [ ERROR ][DeploymentComponent::configure] Unloading
/home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3:
not a valid component library:
0.792 [ ERROR ][DeploymentComponent::configure] component library:
0.823 [ Warning][DeploymentComponent::configure] Component type name
soem_ethercat_drivers::SoemMasterComponent already used: overriding.
0.835 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition:
Part 'size' of type int is not changeable.
0.838 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition:
Part 'capacity' of type int is not changeable.
0.844 [ Warning][DeploymentComponent::loadComponents] Forcing priority (0)
of thread with !SCHED_OTHER policy to 1.
Switched to : Deployer

Deployer problem

Submitted by peter on Tue, 2010-07-06 19:48.

On Tue, Jul 6, 2010 at 10:40 AM, Pierre ANDRE <pierre [..] ...> wrote:
>
> Hi,
>
> we have a problem when we use the deployer of our package.
> See the error message. The library files exist but seems to be "not valid
> component library".
>
> We have tried "make wipe on ocl" and "rosmake" but it is the same problem.
>
>
> root@lias-desktop:/home/lias/kul-ros-pkg/soem_ethercat_drivers# rosrun
> ocl_2.0 deployer-gnulinux -s soem_master.xml
> [rosrun] You have chosen a non-unique executable, please pick one of the
> following:
> 1) /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
> 2) /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer-gnulinux
> #? 1
> 0.604 [ ERROR ][DeploymentComponent::configure] Unloading
> /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3:
> not a valid component library:
> 0.604 [ ERROR ][DeploymentComponent::configure]
> /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3:
> undefined symbol

Is the error message cut off ? Can you attach the orocos.log file
(which also contains the info messages) ?

Peter
--
Orocos-Users mailing list
Orocos-Users [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

Deployer problem

Submitted by Pierre ANDRE on Wed, 2010-07-07 06:56.

Le 06/07/2010 21:44, Peter Soetens a écrit :
> On Tue, Jul 6, 2010 at 10:40 AM, Pierre ANDRE<pierre [..] ...> wrote:
>
>> Hi,
>>
>> we have a problem when we use the deployer of our package.
>> See the error message. The library files exist but seems to be "not valid
>> component library".
>>
>> We have tried "make wipe on ocl" and "rosmake" but it is the same problem.
>>
>>
>> root@lias-desktop:/home/lias/kul-ros-pkg/soem_ethercat_drivers# rosrun
>> ocl_2.0 deployer-gnulinux -s soem_master.xml
>> [rosrun] You have chosen a non-unique executable, please pick one of the
>> following:
>> 1) /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
>> 2) /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer-gnulinux
>> #? 1
>> 0.604 [ ERROR ][DeploymentComponent::configure] Unloading
>> /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3:
>> not a valid component library:
>> 0.604 [ ERROR ][DeploymentComponent::configure]
>> /home/lias/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3:
>> undefined symbol
>>
> Is the error message cut off ? Can you attach the orocos.log file
> (which also contains the info messages) ?
>
> Peter
Here is the orocos.log form another computer with the same problem.

Pierre

Deployer problem

Submitted by sferris on Wed, 2010-07-07 21:04.

Hi,

After the update of the deployer a new problem has appeared :

root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_drivers# rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml
[rosrun] You have chosen a non-unique executable, please pick one of the following:
1) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
2) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer-gnulinux
#? 1
0.158 [ ERROR ][DeploymentComponent::configure] Unloading /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: not a valid component library:
0.158 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol: createComponent
0.158 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol: getComponentType
0.199 [ ERROR ][DeploymentComponent::configure] Unloading /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3: not a valid component library:
0.199 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3: undefined symbol: createComponent
0.199 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3: undefined symbol: getComponentType
0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'size' of type int is not changeable.
0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'capacity' of type int is not changeable.
0.222 [ ERROR ][DeploymentComponent::loadComponent] Unable to create Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown component type.
0.222 [ Warning][DeploymentComponent::loadComponents] Could not configure 'SoemMaster': No such peer.
0.222 [ ERROR ][Logger] Failed to load a component: aborting kick-start.
Switched to : Deployer

Here is the orocos.log form another computer with the same problem

Thank you in advance.

Pierre & Sebastien

Deployer problem

Submitted by sferris on Wed, 2010-07-07 15:50.

Hi,

After the update of the deployer a new problem has appeared :

0.158 [ ERROR ][DeploymentComponent::configure] Unloading /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: not a valid component library: 0.158 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol: createComponent 0.158 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol: getComponentType 0.199 [ ERROR ][DeploymentComponent::configure] Unloading /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3: not a valid component library: 0.199 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3: undefined symbol: createComponent 0.199 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3: undefined symbol: getComponentType 0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'size' of type int is not changeable. 0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'capacity' of type int is not changeable. 0.222 [ ERROR ][DeploymentComponent::loadComponent] Unable to create Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown component type. 0.222 [ Warning][DeploymentComponent::loadComponents] Could not configure 'SoemMaster': No such peer. 0.222 [ ERROR ][Logger] Failed to load a component: aborting kick-start.

   Switched to : Deployer

Here is the orocos.log form another computer with the same problem

Thank you in advance.

Pierre & Sebastien

Deployer problem

Submitted by sferris on Fri, 2010-07-09 07:52.

Hello,

We have update rtt and ocl, however there is still errors and the
deployer is blocked. We have tried to test the deployer on the
original files of SOEM.
PS : The component library is not a symlink.

Could we try to reload an old version of ocl_2.0 which worked
(temporarly) with the git reset to be able to test our files?
The p

root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_drivers#
rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml
[rosrun] You have chosen a non-unique executable, please pick one of
the following:
1) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
2) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer-gnulinux
#? 1
0.158 [ ERROR ][DeploymentComponent::configure] Unloading
/home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3:
not a valid component library:
0.158 [ ERROR ][DeploymentComponent::configure]
/home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3:
undefined symbol: createComponent
0.158 [ ERROR ][DeploymentComponent::configure]
/home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3:
undefined symbol: getComponentType
0.198 [ ERROR ][DeploymentComponent::configure] Unloading
/home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3:
not a valid component library:
0.198 [ ERROR ][DeploymentComponent::configure]
/home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3:
undefined symbol: createComponent
0.198 [ ERROR ][DeploymentComponent::configure]
/home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-gnulinux.so.1.99.3:
undefined symbol: getComponentType
0.220 [ ERROR ][DeploymentComponent::loadComponent] Unable to create
Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown
component type.
0.220 [ Warning][DeploymentComponent::loadComponents] Could not
configure 'SoemMaster': No such peer.
0.220 [ ERROR ][Logger] Failed to load a component: aborting kick-start.
Switched to : Deployer

Thank you for your help.

Sebastien & Pierre

In Task Deployer[X]
(type 'ls' for context info) :

2010/7/9 Peter Soetens <peter [..] ...>:
> On Thu, Jul 8, 2010 at 8:11 AM, seb ferris <seb [dot] ferris [..] ...> wrote:
>> Hi, you will find enclosed the orocos log created after the setting.
>
> The soem library is found, but it is ignored by the component loader.
> A component library or plugin library must be a regular file, and not
> a symlink. I've updated the repository with 'Debug' messages that
> explain why a certain file is skipped.
>
> I also removed the Warning you got about PropertyDecomposition.
>
> Functionally nothing changed, so you have to change something on your
> side. In case your library *is* a regular file and not a symlink,
> we've got a problem with the boost filesystem library.
>
> Peter
>
>>
>>
>> Regards
>>
>> Sebastien
>>
>> 2010/7/7 Peter Soetens <peter [..] ...>:
>>> Thanks for reporting,
>>>
>>> On Wed, Jul 7, 2010 at 5:50 PM, <seb [dot] ferris [..] ...> wrote:
>>>> Hi,
>>>>
>>>> After the update of the deployer a new problem has appeared :
>>>>
>>>> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_drivers# rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml
>>>> [rosrun] You have chosen a non-unique executable, please pick one of the following:
>>>> 1) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
>>>> 2) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer-gnulinux
>>>> #? 1
>>>> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: not a valid component library:
>>>> 0.158 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol: createComponent
>>>
>>> These are harmless and you'll have to ignore them for know. What they
>>> tell us is that the deployement components' libraries do not contain
>>> loadable Orocos components. Which is true. These should be moved to
>>> the 'lib' directory or get a component macro. I'm not sure which would
>>> be actually best.
>>>
>>>
>>>> 0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'size' of type int is not changeable.
>>>> 0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'capacity' of type int is not changeable.
>>>
>>> I still need to find out why you are getting these warnings. They must
>>> eventually disappear.
>>>
>>>> 0.222 [ ERROR ][DeploymentComponent::loadComponent] Unable to create Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown component type.
>>>> 0.222 [ Warning][DeploymentComponent::loadComponents] Could not configure 'SoemMaster': No such peer.
>>>> 0.222 [ ERROR ][Logger] Failed to load a component: aborting kick-start.
>>>> Switched to : Deployer
>>>>
>>>> Here is the orocos.log form another computer with the same problem
>>>
>>> I didn't see any attachment. Can you send it again ? Can you run the
>>> app with the env variable: export ORO_LOGLEVEL=7
>>> set, and send the orocos.log created from that ?
>>>
>>> Thanks,
>>> Peter
>>>
>>
>

Deployer problem

Submitted by Ruben Smits on Fri, 2010-07-09 08:16.

On Friday 09 July 2010 09:50:11 seb ferris wrote:
> Hello,
>
> We have update rtt and ocl, however there is still errors and the
> deployer is blocked. We have tried to test the deployer on the
> original files of SOEM.
> PS : The component library is not a symlink.
>
> Could we try to reload an old version of ocl_2.0 which worked
> (temporarly) with the git reset to be able to test our files?
> The p
>
> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_drivers#
> rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml
> [rosrun] You have chosen a non-unique executable, please pick one of
> the following:
> 1)
> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinu
> x 2)
> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer
> -gnulinux #? 1
> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading
> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
> borocos-deployment-corba-gnulinux.so.1.99.3: not a valid component library:
> 0.158 [ ERROR ][DeploymentComponent::configure]
> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
> borocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
> createComponent
> 0.158 [ ERROR ][DeploymentComponent::configure]
> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
> borocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
> getComponentType
> 0.198 [ ERROR ][DeploymentComponent::configure] Unloading
> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
> borocos-deployment-gnulinux.so.1.99.3: not a valid component library:
> 0.198 [ ERROR ][DeploymentComponent::configure]
> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
> borocos-deployment-gnulinux.so.1.99.3: undefined symbol: createComponent
> 0.198 [ ERROR ][DeploymentComponent::configure]
> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
> borocos-deployment-gnulinux.so.1.99.3: undefined symbol: getComponentType
> 0.220 [ ERROR ][DeploymentComponent::loadComponent] Unable to create
> Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown
> component type.
> 0.220 [ Warning][DeploymentComponent::loadComponents] Could not
> configure 'SoemMaster': No such peer.
> 0.220 [ ERROR ][Logger] Failed to load a component: aborting kick-start.
> Switched to : Deployer

Can you rerun the deployer with -ldebug or with the OROCOS_LOG_LEVEL env
variable set to 7. It looks like the the component library that contains the
SoemMasterComponent is not loaded?

Ruben

> Thank you for your help.
>
> Sebastien & Pierre
>
>
>
> In Task Deployer[X]
> (type 'ls' for context info) :
>
> 2010/7/9 Peter Soetens <peter [..] ...>:
> > On Thu, Jul 8, 2010 at 8:11 AM, seb ferris <seb [dot] ferris [..] ...> wrote:
> >> Hi, you will find enclosed the orocos log created after the setting.
> >
> > The soem library is found, but it is ignored by the component loader.
> > A component library or plugin library must be a regular file, and not
> > a symlink. I've updated the repository with 'Debug' messages that
> > explain why a certain file is skipped.
> >
> > I also removed the Warning you got about PropertyDecomposition.
> >
> > Functionally nothing changed, so you have to change something on your
> > side. In case your library *is* a regular file and not a symlink,
> > we've got a problem with the boost filesystem library.
> >
> > Peter
> >
> >> Regards
> >>
> >> Sebastien
> >>
> >> 2010/7/7 Peter Soetens <peter [..] ...>:
> >>> Thanks for reporting,
> >>>
> >>> On Wed, Jul 7, 2010 at 5:50 PM, <seb [dot] ferris [..] ...> wrote:
> >>>> Hi,
> >>>>
> >>>> After the update of the deployer a new problem has appeared :
> >>>>
> >>>> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_dri
> >>>> vers# rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml [rosrun] You
> >>>> have chosen a non-unique executable, please pick one of the
> >>>> following: 1)
> >>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gn
> >>>> ulinux 2)
> >>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/dep
> >>>> loyer-gnulinux #? 1
> >>>> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading
> >>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/oro
> >>>> cos/liborocos-deployment-corba-gnulinux.so.1.99.3: not a valid
> >>>> component library: 0.158 [ ERROR ][DeploymentComponent::configure]
> >>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/or
> >>>> ocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
> >>>> createComponent
> >>>
> >>> These are harmless and you'll have to ignore them for know. What they
> >>> tell us is that the deployement components' libraries do not contain
> >>> loadable Orocos components. Which is true. These should be moved to
> >>> the 'lib' directory or get a component macro. I'm not sure which would
> >>> be actually best.
> >>>
> >>>> 0.222 [ Warning][DeploymentComponent::loadComponents]
> >>>> propertyDecomposition: Part 'size' of type int is not changeable.
> >>>> 0.222 [ Warning][DeploymentComponent::loadComponents]
> >>>> propertyDecomposition: Part 'capacity' of type int is not changeable.
> >>>
> >>> I still need to find out why you are getting these warnings. They must
> >>> eventually disappear.
> >>>
> >>>> 0.222 [ ERROR ][DeploymentComponent::loadComponent] Unable to create
> >>>> Orocos Component 'soem_ethercat_drivers::SoemMasterComponent':
> >>>> unknown component type. 0.222 [
> >>>> Warning][DeploymentComponent::loadComponents] Could not configure
> >>>> 'SoemMaster': No such peer. 0.222 [ ERROR ][Logger] Failed to load a
> >>>> component: aborting kick-start. Switched to : Deployer
> >>>>
> >>>> Here is the orocos.log form another computer with the same problem
> >>>
> >>> I didn't see any attachment. Can you send it again ? Can you run the
> >>> app with the env variable: export ORO_LOGLEVEL=7
> >>> set, and send the orocos.log created from that ?
> >>>
> >>> Thanks,
> >>> Peter

Deployer problem

Submitted by Pierre ANDRE on Fri, 2010-07-09 08:20.

Hi,

This is the file from my computer with -ldebug.

Le 09/07/2010 10:11, Ruben Smits a écrit :
> On Friday 09 July 2010 09:50:11 seb ferris wrote:
>
>> Hello,
>>
>> We have update rtt and ocl, however there is still errors and the
>> deployer is blocked. We have tried to test the deployer on the
>> original files of SOEM.
>> PS : The component library is not a symlink.
>>
>> Could we try to reload an old version of ocl_2.0 which worked
>> (temporarly) with the git reset to be able to test our files?
>> The p
>>
>> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_drivers#
>> rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml
>> [rosrun] You have chosen a non-unique executable, please pick one of
>> the following:
>> 1)
>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinu
>> x 2)
>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer
>> -gnulinux #? 1
>> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading
>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>> borocos-deployment-corba-gnulinux.so.1.99.3: not a valid component library:
>> 0.158 [ ERROR ][DeploymentComponent::configure]
>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>> borocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
>> createComponent
>> 0.158 [ ERROR ][DeploymentComponent::configure]
>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>> borocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
>> getComponentType
>> 0.198 [ ERROR ][DeploymentComponent::configure] Unloading
>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>> borocos-deployment-gnulinux.so.1.99.3: not a valid component library:
>> 0.198 [ ERROR ][DeploymentComponent::configure]
>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>> borocos-deployment-gnulinux.so.1.99.3: undefined symbol: createComponent
>> 0.198 [ ERROR ][DeploymentComponent::configure]
>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>> borocos-deployment-gnulinux.so.1.99.3: undefined symbol: getComponentType
>> 0.220 [ ERROR ][DeploymentComponent::loadComponent] Unable to create
>> Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown
>> component type.
>> 0.220 [ Warning][DeploymentComponent::loadComponents] Could not
>> configure 'SoemMaster': No such peer.
>> 0.220 [ ERROR ][Logger] Failed to load a component: aborting kick-start.
>> Switched to : Deployer
>>
> Can you rerun the deployer with -ldebug or with the OROCOS_LOG_LEVEL env
> variable set to 7. It looks like the the component library that contains the
> SoemMasterComponent is not loaded?
>
> Ruben
>
>
>> Thank you for your help.
>>
>> Sebastien& Pierre
>>
>>
>>
>> In Task Deployer[X]
>> (type 'ls' for context info) :
>>
>> 2010/7/9 Peter Soetens<peter [..] ...>:
>>
>>> On Thu, Jul 8, 2010 at 8:11 AM, seb ferris<seb [dot] ferris [..] ...> wrote:
>>>
>>>> Hi, you will find enclosed the orocos log created after the setting.
>>>>
>>> The soem library is found, but it is ignored by the component loader.
>>> A component library or plugin library must be a regular file, and not
>>> a symlink. I've updated the repository with 'Debug' messages that
>>> explain why a certain file is skipped.
>>>
>>> I also removed the Warning you got about PropertyDecomposition.
>>>
>>> Functionally nothing changed, so you have to change something on your
>>> side. In case your library *is* a regular file and not a symlink,
>>> we've got a problem with the boost filesystem library.
>>>
>>> Peter
>>>
>>>
>>>> Regards
>>>>
>>>> Sebastien
>>>>
>>>> 2010/7/7 Peter Soetens<peter [..] ...>:
>>>>
>>>>> Thanks for reporting,
>>>>>
>>>>> On Wed, Jul 7, 2010 at 5:50 PM,<seb [dot] ferris [..] ...> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> After the update of the deployer a new problem has appeared :
>>>>>>
>>>>>> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_dri
>>>>>> vers# rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml [rosrun] You
>>>>>> have chosen a non-unique executable, please pick one of the
>>>>>> following: 1)
>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gn
>>>>>> ulinux 2)
>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/dep
>>>>>> loyer-gnulinux #? 1
>>>>>> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading
>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/oro
>>>>>> cos/liborocos-deployment-corba-gnulinux.so.1.99.3: not a valid
>>>>>> component library: 0.158 [ ERROR ][DeploymentComponent::configure]
>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/or
>>>>>> ocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
>>>>>> createComponent
>>>>>>
>>>>> These are harmless and you'll have to ignore them for know. What they
>>>>> tell us is that the deployement components' libraries do not contain
>>>>> loadable Orocos components. Which is true. These should be moved to
>>>>> the 'lib' directory or get a component macro. I'm not sure which would
>>>>> be actually best.
>>>>>
>>>>>
>>>>>> 0.222 [ Warning][DeploymentComponent::loadComponents]
>>>>>> propertyDecomposition: Part 'size' of type int is not changeable.
>>>>>> 0.222 [ Warning][DeploymentComponent::loadComponents]
>>>>>> propertyDecomposition: Part 'capacity' of type int is not changeable.
>>>>>>
>>>>> I still need to find out why you are getting these warnings. They must
>>>>> eventually disappear.
>>>>>
>>>>>
>>>>>> 0.222 [ ERROR ][DeploymentComponent::loadComponent] Unable to create
>>>>>> Orocos Component 'soem_ethercat_drivers::SoemMasterComponent':
>>>>>> unknown component type. 0.222 [
>>>>>> Warning][DeploymentComponent::loadComponents] Could not configure
>>>>>> 'SoemMaster': No such peer. 0.222 [ ERROR ][Logger] Failed to load a
>>>>>> component: aborting kick-start. Switched to : Deployer
>>>>>>
>>>>>> Here is the orocos.log form another computer with the same problem
>>>>>>
>>>>> I didn't see any attachment. Can you send it again ? Can you run the
>>>>> app with the env variable: export ORO_LOGLEVEL=7
>>>>> set, and send the orocos.log created from that ?
>>>>>
>>>>> Thanks,
>>>>> Peter
>>>>>

Deployer problem

Submitted by peter on Fri, 2010-07-09 09:48.

On Fri, Jul 9, 2010 at 10:18 AM, Pierre ANDRE <pierre [dot] j [dot] andre [..] ...> wrote:
> Hi,
>
> This is the file from my computer with -ldebug.

The bug is in loadComponents() function. Something throws, I have no
idea what yet. Can you send the xml file that causes this ?

Peter

>
> Le 09/07/2010 10:11, Ruben Smits a écrit :
>>
>> On Friday 09 July 2010 09:50:11 seb ferris wrote:
>>
>>>
>>> Hello,
>>>
>>> We have update rtt and ocl, however there is still errors and the
>>> deployer is blocked. We have tried to test the deployer on the
>>> original files of SOEM.
>>> PS : The component library is not a symlink.
>>>
>>> Could we try to reload an old version of ocl_2.0 which worked
>>> (temporarly) with the git reset to be able to test our files?
>>> The p
>>>
>>>
>>> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_drivers#
>>> rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml
>>> [rosrun] You have chosen a non-unique executable, please pick one of
>>> the following:
>>> 1)
>>>
>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinu
>>> x 2)
>>>
>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer
>>> -gnulinux #? 1
>>> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading
>>>
>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>> borocos-deployment-corba-gnulinux.so.1.99.3: not a valid component
>>> library:
>>> 0.158 [ ERROR ][DeploymentComponent::configure]
>>>
>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>> borocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
>>> createComponent
>>> 0.158 [ ERROR ][DeploymentComponent::configure]
>>>
>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>> borocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
>>> getComponentType
>>> 0.198 [ ERROR ][DeploymentComponent::configure] Unloading
>>>
>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>> borocos-deployment-gnulinux.so.1.99.3: not a valid component library:
>>> 0.198 [ ERROR ][DeploymentComponent::configure]
>>>
>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>> borocos-deployment-gnulinux.so.1.99.3: undefined symbol: createComponent
>>> 0.198 [ ERROR ][DeploymentComponent::configure]
>>>
>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>> borocos-deployment-gnulinux.so.1.99.3: undefined symbol: getComponentType
>>> 0.220 [ ERROR ][DeploymentComponent::loadComponent] Unable to create
>>> Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown
>>> component type.
>>> 0.220 [ Warning][DeploymentComponent::loadComponents] Could not
>>> configure 'SoemMaster': No such peer.
>>> 0.220 [ ERROR ][Logger] Failed to load a component: aborting kick-start.
>>> Switched to : Deployer
>>>
>>
>> Can you rerun the deployer with -ldebug or with the OROCOS_LOG_LEVEL env
>> variable set to 7. It looks like the the component library that contains
>> the
>> SoemMasterComponent is not loaded?
>>
>> Ruben
>>
>>
>>>
>>> Thank you for your help.
>>>
>>> Sebastien& Pierre
>>>
>>>
>>>
>>> In Task Deployer[X]
>>> (type 'ls' for context info) :
>>>
>>> 2010/7/9 Peter Soetens<peter [..] ...>:
>>>
>>>>
>>>> On Thu, Jul 8, 2010 at 8:11 AM, seb ferris<seb [dot] ferris [..] ...> wrote:
>>>>
>>>>>
>>>>> Hi, you will find enclosed the orocos log created after the setting.
>>>>>
>>>>
>>>> The soem library is found, but it is ignored by the component loader.
>>>> A component library or plugin library must be a regular file, and not
>>>> a symlink. I've updated the repository with 'Debug' messages that
>>>> explain why a certain file is skipped.
>>>>
>>>> I also removed the Warning you got about PropertyDecomposition.
>>>>
>>>> Functionally nothing changed, so you have to change something on your
>>>> side. In case your library *is* a regular file and not a symlink,
>>>> we've got a problem with the boost filesystem library.
>>>>
>>>> Peter
>>>>
>>>>
>>>>>
>>>>> Regards
>>>>>
>>>>> Sebastien
>>>>>
>>>>> 2010/7/7 Peter Soetens<peter [..] ...>:
>>>>>
>>>>>>
>>>>>> Thanks for reporting,
>>>>>>
>>>>>> On Wed, Jul 7, 2010 at 5:50 PM,<seb [dot] ferris [..] ...> wrote:
>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> After the update of the deployer a new problem has appeared :
>>>>>>>
>>>>>>>
>>>>>>> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_dri
>>>>>>> vers# rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml [rosrun]
>>>>>>> You
>>>>>>> have chosen a non-unique executable, please pick one of the
>>>>>>> following: 1)
>>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gn
>>>>>>> ulinux 2)
>>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/dep
>>>>>>> loyer-gnulinux #? 1
>>>>>>> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading
>>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/oro
>>>>>>> cos/liborocos-deployment-corba-gnulinux.so.1.99.3: not a valid
>>>>>>> component library: 0.158 [ ERROR ][DeploymentComponent::configure]
>>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/or
>>>>>>> ocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
>>>>>>> createComponent
>>>>>>>
>>>>>>
>>>>>> These are harmless and you'll have to ignore them for know. What they
>>>>>> tell us is that the deployement components' libraries do not contain
>>>>>> loadable Orocos components. Which is true. These should be moved to
>>>>>> the 'lib' directory or get a component macro. I'm not sure which would
>>>>>> be actually best.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> 0.222 [ Warning][DeploymentComponent::loadComponents]
>>>>>>> propertyDecomposition: Part 'size' of type int is not changeable.
>>>>>>> 0.222 [ Warning][DeploymentComponent::loadComponents]
>>>>>>> propertyDecomposition: Part 'capacity' of type int is not changeable.
>>>>>>>
>>>>>>
>>>>>> I still need to find out why you are getting these warnings. They must
>>>>>> eventually disappear.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> 0.222 [ ERROR ][DeploymentComponent::loadComponent] Unable to create
>>>>>>> Orocos Component 'soem_ethercat_drivers::SoemMasterComponent':
>>>>>>> unknown component type. 0.222 [
>>>>>>> Warning][DeploymentComponent::loadComponents] Could not configure
>>>>>>> 'SoemMaster': No such peer. 0.222 [ ERROR ][Logger] Failed to load a
>>>>>>> component: aborting kick-start. Switched to : Deployer
>>>>>>>
>>>>>>> Here is the orocos.log form another computer with the same problem
>>>>>>>
>>>>>>
>>>>>> I didn't see any attachment. Can you send it again ? Can you run the
>>>>>> app with the env variable: export ORO_LOGLEVEL=7
>>>>>> set, and send the orocos.log created from that ?
>>>>>>
>>>>>> Thanks,
>>>>>> Peter
>>>>>>
>
>
> --
> Pierre ANDRE
> pierre [dot] j [dot] andre [..] ...
>
>
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
--
Orocos-Users mailing list
Orocos-Users [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

Deployer problem

Submitted by peter on Wed, 2010-07-07 21:12.

Thanks for reporting,

On Wed, Jul 7, 2010 at 5:50 PM, <seb [dot] ferris [..] ...> wrote:
> Hi,
>
> After the update of the deployer a new problem has appeared :
>
> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_drivers# rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml
> [rosrun] You have chosen a non-unique executable, please pick one of the following:
> 1) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
> 2) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer-gnulinux
> #? 1
> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: not a valid component library:
> 0.158 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol: createComponent

These are harmless and you'll have to ignore them for know. What they
tell us is that the deployement components' libraries do not contain
loadable Orocos components. Which is true. These should be moved to
the 'lib' directory or get a component macro. I'm not sure which would
be actually best.

> 0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'size' of type int is not changeable.
> 0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'capacity' of type int is not changeable.

I still need to find out why you are getting these warnings. They must
eventually disappear.

> 0.222 [ ERROR ][DeploymentComponent::loadComponent] Unable to create Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown component type.
> 0.222 [ Warning][DeploymentComponent::loadComponents] Could not configure 'SoemMaster': No such peer.
> 0.222 [ ERROR ][Logger] Failed to load a component: aborting kick-start.
> Switched to : Deployer
>
> Here is the orocos.log form another computer with the same problem

I didn't see any attachment. Can you send it again ? Can you run the
app with the env variable: export ORO_LOGLEVEL=7
set, and send the orocos.log created from that ?

Thanks,
Peter
--
Orocos-Users mailing list
Orocos-Users [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

Deployer problem

Submitted by sferris on Thu, 2010-07-08 08:12.

Hi, you will find enclosed the orocos log created after the setting.

Regards

Sebastien

2010/7/7 Peter Soetens <peter [..] ...>:
> Thanks for reporting,
>
> On Wed, Jul 7, 2010 at 5:50 PM, <seb [dot] ferris [..] ...> wrote:
>> Hi,
>>
>> After the update of the deployer a new problem has appeared :
>>
>> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_drivers# rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml
>> [rosrun] You have chosen a non-unique executable, please pick one of the following:
>> 1) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
>> 2) /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer-gnulinux
>> #? 1
>> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: not a valid component library:
>> 0.158 [ ERROR ][DeploymentComponent::configure] /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol: createComponent
>
> These are harmless and you'll have to ignore them for know. What they
> tell us is that the deployement components' libraries do not contain
> loadable Orocos components. Which is true. These should be moved to
> the 'lib' directory or get a component macro. I'm not sure which would
> be actually best.
>
>
>> 0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'size' of type int is not changeable.
>> 0.222 [ Warning][DeploymentComponent::loadComponents] propertyDecomposition: Part 'capacity' of type int is not changeable.
>
> I still need to find out why you are getting these warnings. They must
> eventually disappear.
>
>> 0.222 [ ERROR ][DeploymentComponent::loadComponent] Unable to create Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown component type.
>> 0.222 [ Warning][DeploymentComponent::loadComponents] Could not configure 'SoemMaster': No such peer.
>> 0.222 [ ERROR ][Logger] Failed to load a component: aborting kick-start.
>> Switched to : Deployer
>>
>> Here is the orocos.log form another computer with the same problem
>
> I didn't see any attachment. Can you send it again ? Can you run the
> app with the env variable: export ORO_LOGLEVEL=7
> set, and send the orocos.log created from that ?
>
> Thanks,
> Peter
>

Deployer problem

Submitted by Pierre ANDRE on Wed, 2010-07-07 06:56.

Hi,

we have a problem when we use the deployer of our package.
See the error message. The library files exist but seems to be "not valid
component library".

We have tried "make wipe on ocl" and "rosmake" but it is the same problem.

Deployer problem

Submitted by peter on Fri, 2010-07-09 10:48.

I hope we can soon forget about this week... Check out the latest git
ocl 2.0 version please...

Peter

2010/7/9 Pierre ANDRE <pierre [..] ...>:
> Le 09/07/2010 11:43, Peter Soetens a écrit :
>>
>> On Fri, Jul 9, 2010 at 10:18 AM, Pierre ANDRE<pierre [dot] j [dot] andre [..] ...>
>> wrote:
>>
>>>
>>> Hi,
>>>
>>> This is the file from my computer with -ldebug.
>>>
>>
>> The bug is in loadComponents() function. Something throws, I have no
>> idea what yet. Can you send the xml file that causes this ?
>>
>> Peter
>>
>>
>>>
>>> Le 09/07/2010 10:11, Ruben Smits a écrit :
>>>
>>>>
>>>> On Friday 09 July 2010 09:50:11 seb ferris wrote:
>>>>
>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> We have update rtt and ocl, however there is still errors and the
>>>>> deployer is blocked. We have tried to test the deployer on the
>>>>> original files of SOEM.
>>>>> PS : The component library is not a symlink.
>>>>>
>>>>> Could we try to reload an old version of ocl_2.0 which worked
>>>>> (temporarly) with the git reset to be able to test our files?
>>>>> The p
>>>>>
>>>>>
>>>>>
>>>>> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_drivers#
>>>>> rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml
>>>>> [rosrun] You have chosen a non-unique executable, please pick one of
>>>>> the following:
>>>>> 1)
>>>>>
>>>>>
>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinu
>>>>> x 2)
>>>>>
>>>>>
>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/deployer
>>>>> -gnulinux #? 1
>>>>> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading
>>>>>
>>>>>
>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>>>> borocos-deployment-corba-gnulinux.so.1.99.3: not a valid component
>>>>> library:
>>>>> 0.158 [ ERROR ][DeploymentComponent::configure]
>>>>>
>>>>>
>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>>>> borocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
>>>>> createComponent
>>>>> 0.158 [ ERROR ][DeploymentComponent::configure]
>>>>>
>>>>>
>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>>>> borocos-deployment-corba-gnulinux.so.1.99.3: undefined symbol:
>>>>> getComponentType
>>>>> 0.198 [ ERROR ][DeploymentComponent::configure] Unloading
>>>>>
>>>>>
>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>>>> borocos-deployment-gnulinux.so.1.99.3: not a valid component library:
>>>>> 0.198 [ ERROR ][DeploymentComponent::configure]
>>>>>
>>>>>
>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>>>> borocos-deployment-gnulinux.so.1.99.3: undefined symbol:
>>>>> createComponent
>>>>> 0.198 [ ERROR ][DeploymentComponent::configure]
>>>>>
>>>>>
>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/li
>>>>> borocos-deployment-gnulinux.so.1.99.3: undefined symbol:
>>>>> getComponentType
>>>>> 0.220 [ ERROR ][DeploymentComponent::loadComponent] Unable to create
>>>>> Orocos Component 'soem_ethercat_drivers::SoemMasterComponent': unknown
>>>>> component type.
>>>>> 0.220 [ Warning][DeploymentComponent::loadComponents] Could not
>>>>> configure 'SoemMaster': No such peer.
>>>>> 0.220 [ ERROR ][Logger] Failed to load a component: aborting
>>>>> kick-start.
>>>>> Switched to : Deployer
>>>>>
>>>>>
>>>>
>>>> Can you rerun the deployer with -ldebug or with the OROCOS_LOG_LEVEL env
>>>> variable set to 7. It looks like the the component library that contains
>>>> the
>>>> SoemMasterComponent is not loaded?
>>>>
>>>> Ruben
>>>>
>>>>
>>>>
>>>>>
>>>>> Thank you for your help.
>>>>>
>>>>> Sebastien& Pierre
>>>>>
>>>>>
>>>>>
>>>>> In Task Deployer[X]
>>>>> (type 'ls' for context info) :
>>>>>
>>>>> 2010/7/9 Peter Soetens<peter [..] ...>:
>>>>>
>>>>>
>>>>>>
>>>>>> On Thu, Jul 8, 2010 at 8:11 AM, seb ferris<seb [dot] ferris [..] ...>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Hi, you will find enclosed the orocos log created after the setting.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> The soem library is found, but it is ignored by the component loader.
>>>>>> A component library or plugin library must be a regular file, and not
>>>>>> a symlink. I've updated the repository with 'Debug' messages that
>>>>>> explain why a certain file is skipped.
>>>>>>
>>>>>> I also removed the Warning you got about PropertyDecomposition.
>>>>>>
>>>>>> Functionally nothing changed, so you have to change something on your
>>>>>> side. In case your library *is* a regular file and not a symlink,
>>>>>> we've got a problem with the boost filesystem library.
>>>>>>
>>>>>> Peter
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Sebastien
>>>>>>>
>>>>>>> 2010/7/7 Peter Soetens<peter [..] ...>:
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks for reporting,
>>>>>>>>
>>>>>>>> On Wed, Jul 7, 2010 at 5:50 PM,<seb [dot] ferris [..] ...> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> After the update of the deployer a new problem has appeared :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> root@hp-sebastien:/home/sebastien/orocos/kul-ros-pkg/soem_ethercat_dri
>>>>>>>>> vers# rosrun ocl_2.0 deployer-gnulinux -s soem_master.xml [rosrun]
>>>>>>>>> You
>>>>>>>>> have chosen a non-unique executable, please pick one of the
>>>>>>>>> following: 1)
>>>>>>>>>
>>>>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gn
>>>>>>>>> ulinux 2)
>>>>>>>>>
>>>>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/bin/dep
>>>>>>>>> loyer-gnulinux #? 1
>>>>>>>>> 0.158 [ ERROR ][DeploymentComponent::configure] Unloading
>>>>>>>>>
>>>>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/oro
>>>>>>>>> cos/liborocos-deployment-corba-gnulinux.so.1.99.3: not a valid
>>>>>>>>> component library: 0.158 [ ERROR ][DeploymentComponent::configure]
>>>>>>>>>
>>>>>>>>> /home/sebastien/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/or
>>>>>>>>> ocos/liborocos-deployment-corba-gnulinux.so.1.99.3: undefined
>>>>>>>>> symbol:
>>>>>>>>> createComponent
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> These are harmless and you'll have to ignore them for know. What
>>>>>>>> they
>>>>>>>> tell us is that the deployement components' libraries do not contain
>>>>>>>> loadable Orocos components. Which is true. These should be moved to
>>>>>>>> the 'lib' directory or get a component macro. I'm not sure which
>>>>>>>> would
>>>>>>>> be actually best.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> 0.222 [ Warning][DeploymentComponent::loadComponents]
>>>>>>>>> propertyDecomposition: Part 'size' of type int is not changeable.
>>>>>>>>> 0.222 [ Warning][DeploymentComponent::loadComponents]
>>>>>>>>> propertyDecomposition: Part 'capacity' of type int is not
>>>>>>>>> changeable.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> I still need to find out why you are getting these warnings. They
>>>>>>>> must
>>>>>>>> eventually disappear.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> 0.222 [ ERROR ][DeploymentComponent::loadComponent] Unable to
>>>>>>>>> create
>>>>>>>>> Orocos Component 'soem_ethercat_drivers::SoemMasterComponent':
>>>>>>>>> unknown component type. 0.222 [
>>>>>>>>> Warning][DeploymentComponent::loadComponents] Could not configure
>>>>>>>>> 'SoemMaster': No such peer. 0.222 [ ERROR ][Logger] Failed to load
>>>>>>>>> a
>>>>>>>>> component: aborting kick-start. Switched to : Deployer
>>>>>>>>>
>>>>>>>>> Here is the orocos.log form another computer with the same problem
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> I didn't see any attachment. Can you send it again ? Can you run the
>>>>>>>> app with the env variable: export ORO_LOGLEVEL=7
>>>>>>>> set, and send the orocos.log created from that ?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Peter
>>>>>>>>
>>>>>>>>
>>>
>>> --
>>> Pierre ANDRE
>>> pierre [dot] j [dot] andre [..] ...
>>>
>>>
>>> --
>>> Orocos-Users mailing list
>>> Orocos-Users [..] ...
>>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>>
>>>
>>>
>
>
> --
> Pierre ANDRE
>
> 06 76 59 34 92
> pierre [..] ...
>
> Le Belvédère
> 46700 Puy l'Évêque
>
> Appt 2 Bat D
> 50 Avenue de Lespinet
> 31400 Toulouse
>
>
--
Orocos-Users mailing list
Orocos-Users [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

Deployer problem

Submitted by pierre on Fri, 2010-07-09 11:40.

Now with the new update, we could lunch the deployer and acces to the
soem master component.
But we have several error messages.
You could find these message in the orocos logfile.

When we stop the program, we have these errors:

*** glibc detected ***
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux: double
free or corruption (!prev): 0x0000000001e4c020 ***
======= Backtrace: =========
/lib/libc.so.6(+0x775b6)[0x7f464f2f85b6]
/lib/libc.so.6(cfree+0x73)[0x7f464f2fee53]
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/lib/liborocos-taskbrowser-gnulinux.so.1.99(_ZN9__gnu_cxx13new_allocatorIPN3RTT11TaskContextEE10deallocateEPS3_m+0x20)[0x7f465375b676]
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/lib/liborocos-taskbrowser-gnulinux.so.1.99(_ZNSt11_Deque_baseIPN3RTT11TaskContextESaIS2_EE18_M_deallocate_nodeEPS2_+0x30)[0x7f4653758acc]
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/lib/liborocos-taskbrowser-gnulinux.so.1.99(_ZNSt11_Deque_baseIPN3RTT11TaskContextESaIS2_EE16_M_destroy_nodesEPPS2_S6_+0x34)[0x7f46537588a8]
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/lib/liborocos-taskbrowser-gnulinux.so.1.99(_ZNSt11_Deque_baseIPN3RTT11TaskContextESaIS2_EED2Ev+0x3e)[0x7f46537558da]
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/lib/liborocos-taskbrowser-gnulinux.so.1.99(_ZNSt5dequeIPN3RTT11TaskContextESaIS2_EED1Ev+0x6a)[0x7f4653752aa6]
/lib/libc.so.6(__cxa_finalize+0xa0)[0x7f464f2ba630]
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/lib/liborocos-taskbrowser-gnulinux.so.1.99(+0x4f766)[0x7f465373d766]
======= Memory map: ========
00400000-00427000 r-xp 00000000 08:04 2169266
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
00627000-00628000 r--p 00027000 08:04 2169266
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
00628000-00629000 rw-p 00028000 08:04 2169266
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux
01ddd000-01e85000 rw-p 00000000 00:00 0
[heap]
7f463c000000-7f463c021000 rw-p 00000000 00:00 0
7f463c021000-7f4640000000 ---p 00000000 00:00 0
7f4643b91000-7f4643b92000 ---p 00000000 00:00 0
7f4643b92000-7f4644392000 rw-p 00000000 00:00 0
7f4644392000-7f4644393000 ---p 00000000 00:00 0
7f4644393000-7f4644b93000 rw-p 00000000 00:00 0
7f4644b93000-7f4644bae000 r-xp 00000000 08:04 2003687
/home/pierre/orocos/kul-ros-pkg/soem_ethercat_drivers/lib/orocos/libsoem_master_component.so
7f4644bae000-7f4644dad000 ---p 0001b000 08:04 2003687
/home/pierre/orocos/kul-ros-pkg/soem_ethercat_drivers/lib/orocos/libsoem_master_component.so
7f4644dad000-7f4644daf000 r--p 0001a000 08:04 2003687
/home/pierre/orocos/kul-ros-pkg/soem_ethercat_drivers/lib/orocos/libsoem_master_component.so
7f4644daf000-7f4644db0000 rw-p 0001c000 08:04 2003687
/home/pierre/orocos/kul-ros-pkg/soem_ethercat_drivers/lib/orocos/libsoem_master_component.so
7f4644db0000-7f4645457000 r-xp 00000000 08:04 2143770
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-ocl-common-gnulinux.so.1.99.3
7f4645457000-7f4645657000 ---p 006a7000 08:04 2143770
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-ocl-common-gnulinux.so.1.99.3
7f4645657000-7f4645684000 r--p 006a7000 08:04 2143770
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-ocl-common-gnulinux.so.1.99.3
7f4645684000-7f464569e000 rw-p 006d4000 08:04 2143770
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-ocl-common-gnulinux.so.1.99.3
7f464569e000-7f4645954000 r-xp 00000000 08:04 2143781
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-timer-gnulinux.so.1.99.3
7f4645954000-7f4645b53000 ---p 002b6000 08:04 2143781
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-timer-gnulinux.so.1.99.3
7f4645b53000-7f4645b66000 r--p 002b5000 08:04 2143781
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-timer-gnulinux.so.1.99.3
7f4645b66000-7f4645b72000 rw-p 002c8000 08:04 2143781
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-timer-gnulinux.so.1.99.3
7f4645b72000-7f4645d2a000 r-xp 00000000 08:04 2143788
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-reporting-gnulinux.so.1.99.3
7f4645d2a000-7f4645f2a000 ---p 001b8000 08:04 2143788
/home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/install/lib/orocos/liborocos-reporting-gnulinux.so.1.99.3/opt/ros/cturtle/ros/bin/rosrun:
line 35: 26120 Abandon $exepath "$@"

Thanks.

Sebastien and Pierre

Le 09/07/2010 12:43, Peter Soetens a écrit :
> I hope we can soon forget about this week... Check out the latest git
> ocl 2.0 version please...
>
> Peter
>

Deployer problem

Submitted by peter on Fri, 2010-07-09 13:32.

On Fri, Jul 9, 2010 at 1:36 PM, Pierre ANDRE <pierre [..] ...> wrote:
> Now with the new update, we could lunch the deployer and acces to the soem
> master component.
> But we have several error messages.
> You could find these message in the orocos logfile.
>

A message is only an error if it says 'ERROR' in front of it. I didn't
see any such except for the exception, which has been solved.

> When we stop the program, we have these errors:
>
> *** glibc detected ***
> /home/pierre/orocos/kul-ros-pkg/orocos/ocl/ocl_2.0/bin/deployer-gnulinux:
> double free or corruption (!prev): 0x0000000001e4c020 ***
> ======= Backtrace: =========

I can not reproduce this. It may be due to loading mixed libraries of
older/newer versions.

Peter