[Rock-dev] roby shell

Chris Müller ruunhb at googlemail.com
Fri Jan 6 06:19:39 CET 2012 

Hi Allan,

i've tried something which results maybe in an interesting hint about 
that problem. If we try to start it from a complete
NEXT flavor, you get your error message instantly.

I've simple changed now the branch for tools/roby to MASTER in order to 
observe the behaviour. It takes some seconds and
results in another error message (of course due to some incompabilities 
between next / master).

$ ./scripts/shell
05:51:17.422 (Robot) turning ON MQueue usage
/home/chris/repos/avalon_next/tools/utilrb/lib/utilrb/module/const_defined_here_p.rb:9:in 
`const_defined?': nil is not a symbol (TypeError)
     from 
/home/chris/repos/avalon_next/tools/utilrb/lib/utilrb/module/const_defined_here_p.rb:9:in 
`const_defined_here?'
     from 
/home/chris/repos/avalon_next/tools/utilrb/lib/utilrb/module/define_or_reuse.rb:13:in 
`define_or_reuse'
     from 
/home/chris/repos/avalon_next/tools/roby/lib/roby/interface.rb:146:in 
`reconnect'

I think it's very interesting to see it is processing some seconds in 
the background and outputs a simple message from the robot logger.
In that case i've a feeling it already accomplish the drb 
initialization, which would be hint for: a patch for the shell is only 
included on the master branch.

That's of course very uncertain and it would be better to test it 
directly with a complete master flavor. Unfortunately switching and rebuild
to MASTER and back to NEXT is very time consuming :/. But i can already 
confirm the shell is working on MASTER on our autoproj setup for
RIMRES.

Are we actually the first project, who is using Rock completely on Next? :]

We could maybe test it on AVALON itself; I didn't delete there our old 
master flavor ...

Chris


On 05.01.2012 12:19, Allan E. Conquest wrote:
> Hi, could anyone please suggest how to cope with this problem?
>
> Thanks.
>
> Am 24.12.2011 21:00, schrieb Allan E. Conquest:
>> Hi,
>>
>> i have a new bootstrapped system with NEXT flavor. If I run MARS by
>> supervision and try to connect with the shell (both on my local
>> machine), I get this error message:
>>
>>
>> allan at XYZ:~/dev/AVALON/supervision$ scripts/shell
>>
>> = Address already in use - bind(2) (Errno::EADDRINUSE)
>> |   /usr/lib/ruby/1.8/drb/drb.rb:846:in `initialize',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:846:in `open',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:846:in `open_server_inaddr_any',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:859:in `open_server',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:759:in `open_server',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:757:in `each',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:757:in `open_server',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:1342:in `initialize',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:1630:in `new',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:1630:in `start_service',
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/app.rb:748:in
>> `setup_drb_server',
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/app.rb:696:in `setup',
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/app/scripts/shell.rb:23,
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/exceptions.rb:336:in
>> `display_exception',
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/app/scripts/shell.rb:22,
>> |   /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in
>> `gem_original_require',
>> |   /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require',
>> |   scripts/shell:3
>> = Backtrace
>> | /usr/lib/ruby/1.8/drb/drb.rb:846:in `initialize',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:846:in `open',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:846:in `open_server_inaddr_any',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:859:in `open_server',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:759:in `open_server',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:757:in `each',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:757:in `open_server',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:1342:in `initialize',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:1630:in `new',
>> |   /usr/lib/ruby/1.8/drb/drb.rb:1630:in `start_service',
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/app.rb:748:in
>> `setup_drb_server',
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/app.rb:696:in `setup',
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/app/scripts/shell.rb:23,
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/exceptions.rb:336:in
>> `display_exception',
>> |   /home/allan/dev/AVALON/tools/roby/lib/roby/app/scripts/shell.rb:22,
>> |   /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in
>> `gem_original_require',
>> |   /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require',
>> |   scripts/shell:3
>> =
>>
>>
>> Then, I tried using tools/roby on master by editing
>> autoproj/overrides.yml followed by update and build. Now, I get a
>> different error message:
>>
>> allan at XYZ:~/dev/AVALON/supervision$ scripts/shell
>> 20:47:43.949 (Robot) turning ON MQueue usage
>> /home/allan/dev/AVALON/tools/utilrb/lib/utilrb/module/const_defined_here_p.rb:9:in
>> `const_defined?': nil is not a symbol (TypeError)
>>      from
>> /home/allan/dev/AVALON/tools/utilrb/lib/utilrb/module/const_defined_here_p.rb:9:in
>> `const_defined_here?'
>>      from
>> /home/allan/dev/AVALON/tools/utilrb/lib/utilrb/module/define_or_reuse.rb:13:in
>> `define_or_reuse'
>>      from /home/allan/dev/AVALON/tools/roby/lib/roby/interface.rb:146:in
>> `reconnect'
>>      from /home/allan/dev/AVALON/tools/roby/lib/roby/interface.rb:133:in
>> `each'
>>      from /home/allan/dev/AVALON/tools/roby/lib/roby/interface.rb:133:in
>> `reconnect'
>>      from /home/allan/dev/AVALON/tools/roby/lib/roby/interface.rb:109:in
>> `initialize'
>>      from
>> /home/allan/dev/AVALON/tools/roby/lib/roby/app/scripts/shell.rb:60:in `new'
>>      from /home/allan/dev/AVALON/tools/roby/lib/roby/app/scripts/shell.rb:60
>>      from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in
>> `gem_original_require'
>>      from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
>>      from scripts/shell:3
>>
>>
>> I also tried to use tools/* on master before with the same result. Any
>> ideas?
>>
>>
>> Am 12.12.2011 15:52, schrieb Sylvain Joyeux:
>>> On 12/12/2011 03:25 PM, Chris Mueller wrote:
>>>> Hi,
>>>>
>>>> I have only two questions about the roby shell provided by each
>>>> supervision (./scripts/shell):
>>>>
>>>> 1) For some weeks ago the shell couldn't be used because of some changes
>>>> in orocos.rb.
>>>> Is it currently fixed in our latest version on branch: master? If i try
>>>> to start it, i always
>>>> get an error message shown in the end of this mail. (We also override
>>>> our droby ports and
>>>> local process server in our setup, but i removed it temporarely in order
>>>> test the shell).
>>> I've pushed a fix for it. Please test and report.
>>>
>>>> 2) Does anyone currently know the commands for reloading all properties
>>>> and deployments at runtime in the supervision
>>>> usable via the shell? If it's not currently implemented, it would be
>>>> also great to provide a help command
>>>> in the shell for showing all current utility methods :] or some hints on
>>>> the website.
>>> Yeah. The documentation of the whole rock/roby stuff sucks big time.
>>>
>>> There's some info in the (recently added) system management tutorials:
>>>
>>> http://rock-robotics.org/documentation/system_management_tutorials/500_config_files.html
>>>
>>> Feel free to implement an extensible command documentation system for
>>> the Roby shell ;-)
>> _______________________________________________
>> Rock-dev mailing list
>> Rock-dev at dfki.de
>> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
> _______________________________________________
> Rock-dev mailing list
> Rock-dev at dfki.de
> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev

More information about the Rock-dev mailing list