Bug #732
config option 'masterport' seems to take precedence over cmd line option --masterport
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
I just upgraded my puppetmaster box to use 0.23.0.
I run two puppetmasterd instances: mongrel on port 8000 (proxied by apache), and webrick on 8141
I have “masterport 8000” in puppet.conf and I start the webrick puppetd with “puppetmasterd —masterport 8141”
When I run puppetmasterd —masterport 8141, I see an error about binding to a port already in use.
This is low priority because it’s easy enough to work around. When I comment out the masterport option in puppet.conf, I’m able to specify —masterport for each puppetmaster instance.
This problem seems to occur specifically with —masterport, I tried it with a few other options to see if the config file takes precendence over the command line and it doesn’t.
History
Updated by ben potts almost 5 years ago
- Status changed from 1 to Closed
- 7 set to invalid