Fix client not terminating correctly while doing a reboot as part of an update
Description
For unknown reasons, the client does not terminate when it is told to by systemd at reboot time, and one has to wait the entire 1m30s or 3m (depending on setup) interval for it to use kill -9. It doesn't misbehave, but it causes all updates to take much longer.
I saw the issue on the feature-client_auth_api branch, but @Manuel Zedel said that he also saw it on master.
@Peter Grzybowski No. As I said in the comment below, it is unlikely (but theoretically possible). Feel free to re-test.
Peter GrzybowskiMarch 6, 2025 at 4:50 PM
have we checked that this one is fixed in the new clients?
Lluis CamposMarch 4, 2025 at 3:45 PM
Client 2.x is long EOL and has since been rewritten in a different programming language. It is unlikely that this bug is still present. Rejecting the report.
Lluis CamposJanuary 20, 2021 at 9:42 AM
Removed Fix Version 2.6.0 for this bug, if any we'll target a 2.6.1
Kristian AmlieJanuary 15, 2021 at 3:08 PM
Are you sure this is not because of MEN-4276? Keep in mind, that when killing mender-client, it also kills mender-connect, because it depends on mender-client.
For unknown reasons, the client does not terminate when it is told to by systemd at reboot time, and one has to wait the entire 1m30s or 3m (depending on setup) interval for it to use kill -9. It doesn't misbehave, but it causes all updates to take much longer.
I saw the issue on the
feature-client_auth_apibranch, but @Manuel Zedel said that he also saw it on master.