Revision history [back]

on Kinetic Ubuntu through BASH on Windows 10

I think this is what is causing you issues: ROS on WSL is not an officially supported setup, and while it can be made to work somewhat (see #q238646), the network stack of WSL is not mature enough (in my opinion) to support the same kind of applications as a regular Ubuntu/other Linux install would be able to.

ARCONTROLLER_Network_GetAvailableSocketPort:125 - Failed to set socket option SO_REUSEADDR: error=22 (Invalid argument)

This is the kind of errors I've seen quite a lot with WSL, and they point to (remaining) issues with the network stack.

I cannot say conclusively that WSL is the real cause here, but I would test whether this works on a 'native' Ubuntu Xenial-ROS Kinetic install. If it does, then it would seem WSL's network stack is missing something the software you're trying to run needs.

on Kinetic Ubuntu through BASH on Windows 10

I think this is what is causing you issues: ROS on WSL is not an officially supported setup, and while it can be made to work somewhat (see #q238646), the network stack of WSL is not mature enough (in my opinion) opinion and according to quite some reporters on the wsl issue tracker) to support the same kind of applications as a regular Ubuntu/other Linux install would be able to.

ARCONTROLLER_Network_GetAvailableSocketPort:125 - Failed to set socket option SO_REUSEADDR: error=22 (Invalid argument)

This is the kind of errors I've seen quite a lot with WSL, and they point to (remaining) issues with the network stack.

I cannot say conclusively that WSL is the real cause here, but I would test whether this works on a 'native' Ubuntu Xenial-ROS Kinetic install. If it does, then it would seem WSL's network stack is missing something the software you're trying to run needs.