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

Apt installation dependant on ros enviroment configuration #3

Open
RSLamont opened this issue Jul 26, 2023 · 0 comments
Open

Apt installation dependant on ros enviroment configuration #3

RSLamont opened this issue Jul 26, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@RSLamont
Copy link

When apt installing the qcr-services package the installation will fail if the qcr-env file has been misconfiguration for the current state of the system. This has occurred in testing where roscore can't be run causing the start ros-watchdog.service to fail due to "Start request repeated too quickly". This failure causes the entire installation to fail.
The error messaging reported doesn't clearly articulate the source of the issue, a number of layers of the systemctl status messages are needed to identify the source of the issue which is not presented as an error for the roscore but as a warning regarding a missing file.
See photo series below:
apt-install_qcr-service-failure
systemctl-status-watchdog-service
systemctl-status-roscore

Suggest a few options to resolve:

  1. decoupling the success of starting the installed service with the success of installing the package.
  2. Adding checks for presence of ros installation and the validity of ros environment installation either prior to installation or as a separate tool/script either as a part of this package or qcr-tools in conjunction with suggestion 1.
  3. Adding the restart_after flag to each service with a value of a couple of seconds or increase the allowable values of StartLimitIntervalSec= or StartLimitBurst= in the service file in order to avoid a "start request repeated too quickly" error.
@RSLamont RSLamont added the bug Something isn't working label Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant