yarprun --log broken

Created on 18 Apr 2017  路  14Comments  路  Source: robotology/yarp

yarpmanager cannot launch modules on different machines (for instance: if you are working on the icub21, it cannot launch modules on icub22 and icub-cuda) if the Log is enabled on those machines.
I managed to launch the modules on icub22 and icub-cuda, disabling the their Log from the icub-cluster.py.

Tool - yarprun YARP v2.3.70 Bug Fixed Major

Most helpful comment

Ok, found the problem, I couldn't find it on my systems since for some reason I was building with SKIP_ACE on both of them, and I had issues with the PATH variable...
Anyway, it should be fixed now...

All 14 comments

Some recent changes to yarprun have broken the --log option.

@giuliavezzani :

  • on icub22 yarprun does not work because on that machine the new version of yarprun is running.
  • on icub21 yarprun works because an old version of yarprun is running (ps aux shows that it has been not restarted since Apr 06th)

@drdanz
Maybe https://github.com/robotology/yarp/commit/3c1882dfb8a217b4e3a83962b49aeba417c9aee1 ?

The error message displayed by yarprun:

ABORTED: server=/icub22 alias=test cmd=stdout
Can't execute stdout because Operation not supported

In the previous version, yarprun was displaying the name of the executable to run instead of stdout

Hi,
Do you already have an update on this? We were just running into this issue. Anything I can help with to resolve this?

Best, Tobias

Hi @Tobias-Fischer, afaik there is not a fix yet, but is on the go 馃槃
Thanks for the patience!

After some debugging, I think there was some change on debian/ubuntu that break it

my test was:

yarp server

```bash
yarprun --server /foo --log

```bash
yarprun --on /foo --as bar --cmd /bin/true

Result:

  • Works on windows 10
  • Broken on 2 different debian testing (one recently updated and one updated a few weeks ago)
  • Broken on ubuntu xenial
  • Works on ubuntu trusty

I bisected it and apparently the first broken commit was the one where the --log option was added

Can anyone test it on more (or even the same) operating systems?

macOS 10.12.4

makas-pro:build makaveli$ yarprun --server /foo --log
STARTED: server=/foo alias=bar cmd=stdout pid=65483
ABORTED: server=/foo alias=bar cmd=stdout
Can't execute stdout because Operation not supported
ABORTED: server=/foo alias=bar cmd=stdout
Can't execute stdout because Operation not supported
ABORTED: server=/foo alias=bar cmd=/bin/true
Can't execute command because No such file or directory
makas-pro:build makaveli$ yarprun --on /foo --as bar --cmd /bin/true
yarp: Port /tmp/port/1 active at tcp://10.255.36.7:10003/
yarp: Sending output from /tmp/port/1 to /foo using tcp
yarp: Removing output from /tmp/port/1 to /foo
RESPONSE:
=========
-1
ABORTED: server=/foo alias=bar cmd=stdout
Can't execute stdout because Operation not supported
ABORTED: server=/foo alias=bar cmd=/bin/true
Can't execute command because No such file or directory

(/bin/true does not exist on macOS, but even with an existing command the result is the same)

Great debugging @drdanz 馃憤
However, I can certainly tell that the --log option was running ok on xenial in the past, just because we have introduced xenial in our system since quite long by now.

If I may add, on macOS using master branch everything works perfectly.

makas-pro:build makaveli$ yarprun --server /foo --log
STARTED: server=/foo alias=bar cmd=stdout pid=67235
STARTED: server=/foo alias=bar cmd=/bin/ls pid=67236
yarprun --on /foo --as bar --cmd /bin/ls
yarp: Port /tmp/port/1 active at tcp://10.255.36.7:10003/
yarp: Sending output from /tmp/port/1 to /foo using tcp
yarp: Removing output from /tmp/port/1 to /foo
RESPONSE:
=========
67236
STARTED: server=/foo alias=bar cmd=/bin/ls pid=67236

It is broken also on Linux 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 GNU/Linux running on my laptop.

Ok, found the problem, I couldn't find it on my systems since for some reason I was building with SKIP_ACE on both of them, and I had issues with the PATH variable...
Anyway, it should be fixed now...

Please everyone test and report...

@drdanz tested on macOS and the issue is solved.

@gabrielenava is testing it now on iCubGenova04 , I will update this issue.

@drdanz Updated and tested on iCubGenova03. Everything running smoothly :) Thanks!

Was this page helpful?
0 / 5 - 0 ratings