Project

General

Profile

Actions
Copy link

Bug #15697

closed

Command not found when running "rudder agent enable -s"

Added by Philip Seeger about 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Agent
Target version:
5.0.14
Pull Request:
https://github.com/Normation/rudder-a...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

Rudder fails to re-enable and start the agent in some cases.

# rudder agent enable -s
/opt/rudder/share/commands/../lib/common.sh: line 44: service: command not found

Bug #1: The systemd detection fails:

# systemctl list-units --type service --all ${service}.service 2>&1 | grep -q "^${service}.service"; echo $?
1
# systemctl list-units --type service --all ${service}.service 2>&1 
  UNIT           LOAD   ACTIVE SUB    DESCRIPTION
● rudder.service loaded failed failed LSB: Rudder server

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

Bug #2: The "service" compatibility wrapper is detected but not executed.

Actions
Copy link

Also available in: Atom PDF