Bug #6168
`puppet master` should not daemonize before checking that it can startup
| Status: | Accepted | Start date: | 02/04/2011 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 2.7.x | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
| Votes: | 1 |
Description
If there are problems that would cause the puppet master to fail to start up (missing directories, permissions errors, etc, etc), these are not reported when running the master via the command line (puppet master --daemonize). Puppet should check for proper directories, and permissions before daemonizing so it can output initialization errors, and return non-zero, rather than giving the appearance of success, when it actually has silently failed.
Related issues
History
Updated by Jacob Helwig over 1 year ago
- Subject changed from `puppet master` daemonizes before checking that it can startup to `puppet master` should not daemonize before checking that it can startup
Updated by James Turnbull over 1 year ago
- Status changed from Unreviewed to Accepted
Updated by Nigel Kersten about 1 year ago
- Assignee deleted (
Nigel Kersten) - Priority changed from Normal to High
- Target version set to 2.7.x
Hell yes.