Actions
Bug #21858
closedCommand seq not found in crontab on AIX
Pull Request:
Severity:
UX impact:
I dislike using that feature
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Yes
Description
When we run this command: crontab -l | grep -i rudder
We have an error like :
sh: seq: not found * * * * /opt/rudder/bin/rudder agent check -q >> /var/log/rudder/agent-check/check.log 2>&1 # RUDDER CRON
We use seq to define que frequency of the run, but it doesn't exists on AIX OS
It is introduce by: https://issues.rudder.io/issues/16859
Updated by Nicolas CHARLES about 2 years ago
seq command can be replaced by
echo '0 59' | awk '{ for (i=$1;i<=$2;i=i+5) { printf "%s%s", sep, i; sep=","}} END{print ""}'
Updated by Nicolas CHARLES about 2 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1792
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 1002 to 7.1.7
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.1.7 to 7.1.8
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.1.8 to 7.1.9
Updated by Nicolas CHARLES almost 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|ff87cb70b4e7fdf7d2cd5eb4053405d1388026c5.
Updated by Alexis Mousset almost 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.1.9 and 7.2.3 which were released today.
Actions