Actions
Bug #3681
closedDouble cron job for Rudder agent when upgrading from 2.5 to 2.6
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
After upgrading from 2.5 to 2.6 a new cron file is created. However, the old cron entry is not cleaned up. This happens on either Ubuntu (12.04 LTS) and Red Hat (RHEL 5).
# tail -1 /etc/crontab 0,5,10,15,20,25,30,35,40,45,50,55 * * * * root if [ ! -e /opt/rudder/etc/disable-agent -a `ps -efww | grep -E "(cf-execd|cf-agent)" | grep -E "/var/rudder/cfengine-community/bin/(cf-execd|cf-agent)" | grep -v grep | wc -l` -eq 0 ]; then /var/rudder/cfengine-community/bin/cf-agent -f failsafe.cf \&\& /var/rudder/cfengine-community/bin/cf-agent; fi
# tail -1 /etc/cron.d/rudder-agent 0,5,10,15,20,25,30,35,40,45,50,55 * * * * root if [ ! -e /opt/rudder/etc/disable-agent -a `ps -efww | grep -E "(cf-execd|cf-agent)" | grep -E "/var/rudder/cfengine-community/bin/(cf-execd|cf-agent)" | grep -v grep | wc -l` -eq 0 ]; then /var/rudder/cfengine-community/bin/cf-agent -f failsafe.cf && /var/rudder/cfengine-community/bin/cf-agent; fi
Updated by Nicolas CHARLES almost 12 years ago
- Assignee set to Nicolas PERRON
- Priority changed from N/A to 2
- Target version set to 2.5.5
Updated by Nicolas PERRON almost 12 years ago
- Status changed from New to Pending technical review
- Assignee changed from Nicolas PERRON to Nicolas CHARLES
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/142
Updated by Nicolas PERRON almost 12 years ago
- Status changed from Pending technical review to Pending release
Updated by Nicolas PERRON over 11 years ago
- Subject changed from Double cron job when upgrading from 2.5 to 2.6 to Double cron job for Rudder agent when upgrading from 2.5 to 2.6
Updated by Benoît PECCATTE about 10 years ago
- Project changed from 24 to Rudder
- Category changed from Techniques to Techniques
Actions