Project

General

Profile

Actions

Bug #9858

closed

When upgrading Rudder, we get mails from cron saying "ok: Rudder agent check ran without errors."

Added by Nicolas CHARLES almost 8 years ago. Updated almost 8 years ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When we upgrade rudder-agent, the file /etc/cron.d/rudder-agent-uuid is created (see http://www.rudder-project.org/redmine/issues/3930 and http://www.rudder-project.org/redmine/issues/3925 )
This file now calls check_rudder_agent, and it became verbose in 4.0

So during upgrade, we create this cron file ( https://github.com/Normation/rudder-packages/blob/master/rudder-agent/SOURCES/rudder-agent-postinst ) without the > /dev/null, and the file is deleted afterward by techniques

We should probably:
  • in 4.0 redirect to > /dev/null in the cron
  • remove this cron in version 4.1 (cause of the file was in 2.7.2 ...)

Related issues 2 (0 open2 closed)

Related to Rudder - Architecture #3930: Rudder-agent cron file now use check-rudder-agent script (/opt/rudder/bin/check-rudder-agent)ReleasedMatthieu CERDA2013-09-17Actions
Related to Rudder - Bug #7911: Add an output to all Rudder commandsReleasedBenoît PECCATTE2016-05-20Actions
Actions

Also available in: Atom PDF