Project

General

Profile

Actions
Copy link

User story #5018

closed

Add logs of package install actions

User story #5018: Add logs of package install actions

Added by Jonathan CLARKE about 12 years ago. Updated about 12 years ago.

Status:
Released
Priority:
3
Assignee:
Jonathan CLARKE
Category:
System integration
Target version:
2.11.0~beta1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Currently, many actions in our packages post install scripts are redirected to /dev/null, to avoid spewing useless messages on the user's screen. This is nice, but...

This makes it very hard to analyze a problem. Usually, commands that fail are good enough to say why (or at least try) on the stdout or stderr, but we throw this information away.

I would like to implement a mechanism whereby each package's post-install script outputs any such information to /var/log/rudder/install/<package name>.log

Subtasks 1 (0 open — 1 closed)

User story #5019: Add logs of package install actions to ease debugging - rudder-agentReleasedNicolas CHARLESActions

Updated by Vincent MEMBRÉ about 12 years ago Actions
Copy link
 #1

  • Target version changed from 2.11.0~beta1 to 2.11.0~beta2

Updated by Vincent MEMBRÉ about 12 years ago Actions
Copy link
 #2

  • Status changed from 13 to Pending release
  • Target version changed from 2.11.0~beta2 to 2.11.0~beta1

Updated by Vincent MEMBRÉ about 12 years ago Actions
Copy link
 #3

  • Subject changed from Add logs of package install actions to ease debugging to Add logs of package install actions

Updated by Vincent MEMBRÉ about 12 years ago Actions
Copy link
 #4

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.0~beta1 that was released yesterday.

Actions
Copy link

Also available in: PDF Atom