Project

General

Profile

Actions

Bug #7420

closed

cf-execd is running twice after a reboot or after running rudder-agent twice

Added by Dennis Cabooter about 9 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
1 (highest)
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

cf-execd is running twice after a reboot or after running rudder-agent twice.

# ps wwwuax|grep cf- |grep -v grep
root      2960  0.0  0.5  44028  5836 ?        Ss   11:49   0:00 /var/rudder/cfengine-community/bin/cf-serverd
root      3137  0.0  0.3 107860  3880 ?        Ss   11:49   0:00 /var/rudder/cfengine-community/bin/cf-execd
root      3504  0.0  0.3 107868  3880 ?        Ss   11:49   0:00 /var/rudder/cfengine-community/bin/cf-execd

All I can do now is stop rudder-agent, kill the left cf-execd process and start rudder-agent again.

# /etc/init.d/rudder-agent stop
rudder-agent[8821]: [INFO] Using /etc/default/rudder-agent for configuration
rudder-agent[8824]: [INFO] Using /var/rudder/cfengine-community for CFEngine workdir
rudder-agent[8825]: [INFO] Halting CFEngine Community cf-serverd...
rudder-agent[8833]: [OK] CFEngine Community cf-serverd stopped after 2 seconds
rudder-agent[8834]: [INFO] Halting CFEngine Community cf-execd...
rudder-agent[8913]: [OK] CFEngine Community cf-execd stopped after 2 seconds
# ps wwwuax|grep cf- |grep -v grep
root      3137  0.0  0.3 107860  3880 ?        Ss   11:49   0:00 /var/rudder/cfengine-community/bin/cf-execd
# kill 3137
# /etc/init.d/rudder-agent start
rudder-agent[10066]: [INFO] Using /etc/default/rudder-agent for configuration
rudder-agent[10069]: [INFO] Using /var/rudder/cfengine-community for CFEngine workdir
rudder-agent[10070]: [INFO] Launching CFEngine Community cf-serverd...
rudder-agent[10245]: [OK] CFEngine Community cf-serverd started after 1 seconds
rudder-agent[10246]: [INFO] Launching CFEngine Community cf-execd...
rudder-agent[10422]: [OK] CFEngine Community cf-execd started after 1 seconds
# ps wwwuax|grep cf- |grep -v grep
root     10242  0.0  0.5  44032  5764 ?        Ss   13:11   0:00 /var/rudder/cfengine-community/bin/cf-serverd
root     10419  0.0  0.2  40276  2860 ?        Ss   13:11   0:00 /var/rudder/cfengine-community/bin/cf-execd

And now everything is fine again, untill the next time, which is annoying.


Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #7537: /etc/init.d/rudder-agent start starts cf-execd even if it is running, resulting in 2 cf-execd running, and big problemsRejectedBenoît PECCATTE2015-12-03Actions
Actions #1

Updated by Nicolas CHARLES about 9 years ago

Dennis,

Just to be sure: it happens if you run twice /etc/init.d/rudder-agent start ; or is it another condition ?
Which version of the agent are you using ?
Which OS and version of the OS are you using?

Thank you !

Actions #2

Updated by Dennis Cabooter about 9 years ago

Nicolas,

As far as I know it happens always after a reboot and it happens when I start rudder-agent twice. To be honest it doesn't make much sense to start rudder-agent twice, but sometimes it happens accidently.

I use rudder-agent 3.1.4 on Ubuntu Trusty 14.04.1 LTS.

Regards,

Dennis

Actions #3

Updated by Nicolas CHARLES about 9 years ago

  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE

Ok, so this is clearly a problem in the init script to detect if the agent is running or not
Benoit, could you have a look at that please ?

Actions #4

Updated by Jonathan CLARKE almost 9 years ago

  • Has duplicate Bug #7537: /etc/init.d/rudder-agent start starts cf-execd even if it is running, resulting in 2 cf-execd running, and big problems added
Actions #5

Updated by Nicolas CHARLES almost 9 years ago

  • Priority changed from 3 to 1 (highest)
Actions #6

Updated by Benoît PECCATTE almost 9 years ago

  • Target version changed from 3.1.5 to 2.11.17
Actions #7

Updated by Benoît PECCATTE almost 9 years ago

  • Status changed from New to In progress
Actions #8

Updated by Benoît PECCATTE almost 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/826
Actions #9

Updated by Benoît PECCATTE almost 9 years ago

  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
Actions #10

Updated by Benoît PECCATTE almost 9 years ago

  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE
Actions #11

Updated by Benoît PECCATTE almost 9 years ago

  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
Actions #12

Updated by Benoît PECCATTE almost 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #13

Updated by Jonathan CLARKE almost 9 years ago

Actions #14

Updated by Vincent MEMBRÉ almost 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.17, 3.0.12 and 3.1.5 which were released today.

Actions

Also available in: Atom PDF