Roslaunch not working

ROS 1 / ROS 2
1

ROS error running on ubuntu 16.04.
make px4_sitl_default gazebo works fine.
I am searching for this error for two days cant find the solution. Any help would be appreciated.
Terminal Output:
yuwenbin@yuwenbin-laptop:/home/nouman/Gazebo/Firmware$ roslaunch gazebo_ros empty_world.launch
… logging to /home/yuwenbin/.ros/log/f31b22ec-f597-11e9-b050-00215c20ee14/roslaunch-yuwenbin-laptop-5129.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://yuwenbin-laptop:34701/

SUMMARY

PARAMETERS

  • /rosdistro: kinetic
  • /rosversion: 1.12.14
  • /use_sim_time: True

NODES
/
gazebo (gazebo_ros/gzserver)
gazebo_gui (gazebo_ros/gzclient)

auto-starting new master
process[master]: started with pid [5139]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to f31b22ec-f597-11e9-b050-00215c20ee14
process[rosout-1]: started with pid [5152]
started core service [/rosout]
process[gazebo-2]: started with pid [5158]
process[gazebo_gui-3]: started with pid [5168]
terminate called after throwing an instance of ‘boost::filesystem::filesystem_error’
what(): boost::filesystem::status: Permission denied: “/home/yuwenbin/.gazebo/client-11345”
terminate called after throwing an instance of ‘boost::filesystem::filesystem_error’
what(): boost::filesystem::status: Permission denied: “/home/yuwenbin/.gazebo/server-11345”
Aborted (core dumped)
Aborted (core dumped)
[gazebo-2] process has died [pid 5158, exit code 134, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -e ode worlds/empty.world __name:=gazebo __log:=/home/yuwenbin/.ros/log/f31b22ec-f597-11e9-b050-00215c20ee14/gazebo-2.log].
log file: /home/yuwenbin/.ros/log/f31b22ec-f597-11e9-b050-00215c20ee14/gazebo-2*.log
[gazebo_gui-3] process has died [pid 5168, exit code 134, cmd /opt/ros/kinetic/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/yuwenbin/.ros/log/f31b22ec-f597-11e9-b050-00215c20ee14/gazebo_gui-3.log].
log file: /home/yuwenbin/.ros/log/f31b22ec-f597-11e9-b050-00215c20ee14/gazebo_gui-3*.log

2

@Nouman_Ashraf Can you explain what you are trying to do?

3

My task is to control a drone using off-board mode through a companion computer. I just followed the link below to setup my environment and to run some examples but i am stuck in this error. I am new to Gazebo and ROS and i have searched every where but didn’t find any solution to this problem.

At the end of this example my error is like this

setting /run_id to 66bce8dc-f5fe-11e9-b050-00215c20ee14
process[rosout-1]: started with pid [15552]
started core service [/rosout]
process[sitl-2]: started with pid [15577]
INFO [px4] Creating symlink /home/nouman/Gazebo/Firmware/ROMFS/px4fmu_common -> /home/yuwenbin/.ros/etc
ERROR [px4_daemon] error binding socket
0 WARNING: setRealtimeSched failed (not run as root?)

| ___ \ \ \ / / / |
| |/ / \ V / / /| |
| __/ / \ / /| |
| | / /^\ \ ___ |
_| / / |_/

px4 starting.

INFO [px4] Calling startup script: /bin/sh etc/init.d-posix/rcS 0
process[gazebo-3]: started with pid [15578]
ERROR [px4] Failed to communicate with daemon: Permission denied
process[gazebo_gui-4]: started with pid [15599]
ERROR [px4] Failed to communicate with daemon: Permission denied
ERROR [px4] Failed to communicate with daemon: Permission denied
ERROR [px4] Failed to communicate with daemon: Permission denied
ERROR [px4] Failed to communicate with daemon: Permission denied
ERROR [px4] Failed to communicate with daemon: Permission denied
process[vehicle_spawn_yuwenbin_laptop_15529_286625850023123580-5]: star

4

There is some permission issue on your machine!

what(): boost::filesystem::status: Permission denied: “/home/yuwenbin/.gazebo/server-11345”
Aborted (core dumped)

ERROR [px4] Failed to communicate with daemon: Permission denied

Have you messed with the users or permissions somehow?