Project

General

Profile

Actions
Copy link

Bug #14171

closed

'rudder-cf-execd' and 'rudder-cf-serverd' in status 'inactive (dead)'

Added by Krzysztof Pogłodziński over 5 years ago. Updated almost 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Packaging
Target version:
5.0.11
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
94
Name check:
Fix check:
Regression:

Description

Nodes with fresh install of Ubuntu 18.04. Rudder in 5.0.3 (same issue occurs on 5.0.4)

Installation process:
--- cut here ---
apt-get install rudder-agent
echo '[...server_address...]' > /var/rudder/cfengine-community/policy_server.dat
rudder agent start
rudder agent inventory
rudder agent run
--- cut here ---

Problem:
After reboot services 'rudder-cf-execd' and 'rudder-cf-serverd' are in status 'inactive (dead)'.

agent-check on every run is generating:
WARNING: No disable file detected and no agent executor process either. Restarting agent service...ok: stop service rudder-agent succeeded
ok: start service rudder-agent succeeded

Temporary solution:
systemctl enable rudder-agent rudder-cf-execd rudder-cf-serverd

Sugested permanent solution:
agent-check should check if required services are up, and if not, should bring them up.

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #14692: Rudder agent check does not repair policies if they are broken ReleasedNicolas CHARLESActions
Actions
Copy link
 #1

Updated by François ARMAND about 5 years ago

  • Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Effort required set to Very Small
  • Priority changed from 0 to 96
Actions
Copy link
 #2

Updated by François ARMAND about 5 years ago

  • Category changed from Agent to Packaging
  • Assignee set to Félix DALLIDET
  • Target version set to 5.0.9
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.9 to 5.0.10
Actions
Copy link
 #4

Updated by François ARMAND about 5 years ago

  • Assignee changed from Félix DALLIDET to Nicolas CHARLES
  • Priority changed from 96 to 95

We weren't able to reproduce it, but we had several concording reports about that problem. So perhaps the problem is on "rudder agent check".

Actions
Copy link
 #5

Updated by Nicolas CHARLES about 5 years ago

  • Related to Bug #14692: Rudder agent check does not repair policies if they are broken added
Actions
Copy link
 #6

Updated by Nicolas CHARLES about 5 years ago

I cannot reproduce the issue - even with specified version of Rudder and Ubuntu
Could you paste the complet output of the systemctl status rudder-cf-execd ?

Actions
Copy link
 #7

Updated by Nicolas CHARLES about 5 years ago

even if i volontarly break the policies, after reboot I have

root@agent1:/home/vagrant# systemctl status rudder-cf-execd
● rudder-cf-execd.service - CFEngine Execution Scheduler
   Loaded: loaded (/lib/systemd/system/rudder-cf-execd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2019-04-19 12:49:31 UTC; 1s ago
  Process: 2408 ExecStart=/var/rudder/cfengine-community/bin/cf-execd --no-fork (code=exited, status=1/FAILURE)
 Main PID: 2408 (code=exited, status=1/FAILURE)

Apr 19 12:49:31 agent1 systemd[1]: rudder-cf-execd.service: Main process exited, code=exited, status=1/FAILURE
Apr 19 12:49:31 agent1 systemd[1]: rudder-cf-execd.service: Failed with result 'exit-code'.

Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
  • Priority changed from 95 to 94
Actions
Copy link
 #9

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from New to Rejected

We couldn't reproduce, and it seemed to be related to broken policies
Since #14692 fixed this point, i'm closing this ticket - if it happens again, please reopen this ticket, with as many details you can include

Thank you!

Actions
Copy link

Also available in: Atom PDF