Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR [px4] Startup script returned with return value: 256 #496

Closed
yousef337 opened this issue Oct 11, 2023 · 12 comments
Closed

ERROR [px4] Startup script returned with return value: 256 #496

yousef337 opened this issue Oct 11, 2023 · 12 comments

Comments

@yousef337
Copy link

I have been following the documentation at
https://github.com/CopterExpress/clover/blob/master/docs/en/simulation_native.md for running the simulation in ROS Noetic and have faced the following error

Error: no autostart file found (**********/init.d-posix/airframes/4500_clover)
ERROR [px4] Startup script returned with return value: 256

during running roslaunch clover_simulation simulator.launch

@okalachev
Copy link
Member

What virtual machine to you use, and were there any errors during the installation?

Also, can you please provide the full output log of this command, maybe it can help to investigate the reason of this error.

@yousef337
Copy link
Author

yousef337 commented Oct 12, 2023

I am not using a virtual machine, I am running EndeavourOS that contains an apptainer container running Ubuntu, which I use to run the whole process. The only error that occures was #495, the current error occurs when I remove aruco_pose in order to make the catkin_make run successfully.

@okalachev
Copy link
Member

Are you sure you have symlinked simulated Clover airframe to PX4 sources as required in this step?

@yousef337
Copy link
Author

Yes, and checked manually, the file is there

@yousef337
Copy link
Author

yousef337 commented Oct 14, 2023

After resolving #495, the error stack is the same,

Error: no autostart file found (****/init.d-posix/airframes/4500_clover)
ERROR [px4] Startup script returned with return value: 256
================================================================================REQUIRED process [sitl_0-3] has died!
process has died [pid 558325, exit code 255, cmd ***/devel/lib/px4/px4 ***/src/PX4-Autopilot/ROMFS/px4fmu_common -s etc/init.d-posix/rcS -i 0 __name:=sitl_0 __log:=****/.ros/log/f7aa0c6e-691b-11ee-87cf-84fdd1142c15/sitl_0-3.log].
log file: *****/.ros/log/f7aa0c6e-691b-11ee-87cf-84fdd1142c15/sitl_0-3*.log
Initiating shutdown!
================================================================================
RLException: cannot add process [vpe_publisher-8] after process monitor has been shut down
The traceback for the exception was written to the log file

@yousef337
Copy link
Author

Sometimes, if running the launch file again, gazeboo does open with the empty world, along with the error messages. However, running topics-related command doesn't seem to function properly.

For example, running rostopic echo /mavros/local_position/pose would result in WARNING: no messages received and simulated time is active.
Is /clock being published?

@okalachev
Copy link
Member

I don't get why px4 binary can't find the 4500_clover airframe file, if you say, that you have symlinked it as in the manual.

Please, check, if there is a following file: ~/.ros/etc/init.d-posix/airframes/4500_clover.

@yousef337
Copy link
Author

It is, were you able to replicate the issue? Can you go through the setup docs?

@MagicWinnie
Copy link
Contributor

Fixed same issue by manually creating a symlink:
ln -sf ~/catkin_ws/src/clover/clover_simulation/airframes/* ~/.ros/etc/init.d-posix/airframes/
I guess I have made a mistake while creating a symlink per instructions in docs.

@yousef337
Copy link
Author

Unfortunately it didn't resolve the issue

@yousef337
Copy link
Author

When ls ~/.ros/etc/init.d-posix/airframes/, I would still get 4500_clover. When ls -la, it would yield .ros/etc/init.d-posix/airframes/4500_clover -> src/clover/clover_simulation/airframes/4500_clover

@okalachev
Copy link
Member

Closed as stale.

@okalachev okalachev closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants