You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Suggest a few options to resolve:
decoupling the success of starting the installed service with the success of installing the package.
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.
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.
The text was updated successfully, but these errors were encountered:
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:
Suggest a few options to resolve:
The text was updated successfully, but these errors were encountered: