Actions
User story #5018
closed
Add logs of package install actions
Status:
Released
Priority:
3
Assignee:
Jonathan CLARKE
Category:
System integration
Target version:
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
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.11.0~beta1 to 2.11.0~beta2
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from 13 to Pending release
- Target version changed from 2.11.0~beta2 to 2.11.0~beta1
Updated by Vincent MEMBRÉ over 10 years ago
- Subject changed from Add logs of package install actions to ease debugging to Add logs of package install actions
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.0~beta1 that was released yesterday.
- announcement
- changelog
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions