Actions
Bug #3600
closed
On a new installation of Rudder, the user root got mail containing error about execution of cron
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
-
Target version:
-
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Without definition of Rule, the Rudder server try to launch some commands with cron but with none expanded values:
From root@sles11sp1.vagrant.internal Fri May 17 11:00:01 2013
Return-Path: <root@sles11sp1.vagrant.internal>
X-Original-To: root
Delivered-To: root@sles11sp1.vagrant.internal
Received: by sles11sp1.vagrant.internal (Postfix, from userid 0)
id 43AF3A329; Fri, 17 May 2013 11:00:01 -0700 (PDT)
From: root@sles11sp1.vagrant.internal
To: root@sles11sp1.vagrant.internal
Subject: Cron <root@server> if [ ! -e ${g.rudder_base}/etc/disable-agent -a `ps -efww | grep -E "(cf-execd|cf-agent)" | grep -E "${sys.workdir}/bin/(cf-execd|cf-agent)" | grep -v grep | wc -l` -eq 0 ]; then ${sys.workdir}/bin/cf-agent -f failsafe.cf \&\& ${sys.workdir}/bin/cf-agent; fi
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Message-Id: <20130517180001.43AF3A329@sles11sp1.vagrant.internal>
Date: Fri, 17 May 2013 11:00:01 -0700 (PDT)
/bin/sh: ${g.rudder_base}/etc/disable-agent: bad substitution
Updated by Nicolas PERRON over 10 years ago
- Status changed from New to Rejected
I reject this issue since similar informations are added into #3654
Updated by Jonathan CLARKE over 10 years ago
Actions