This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using
. See the following page for information on filing tickets with JIRA:
Remove support for running embedded mongrel server
|Assignee:||Patrick Carlisle||% Done:|
|Affected Puppet version:||
Possible to do as a ‘hard’ deprecation.
- Status changed from Needs Decision to Accepted
- Assignee changed from eric sorenson to Anonymous
- Priority changed from Normal to High
- Target version changed from 3.x to 3.0.0
- Assignee changed from Anonymous to Anonymous
- Assignee deleted (
We’re taking this right now to mean we’re dropping mongrel support. Keeping the built-in webrick but converting it to work via rack is transparent to the users, and we can put that part off for now.
- Subject changed from Deprecate running puppet master under non-rack setups to Remove support for running embedded mongrel server
- Status changed from Accepted to In Topic Branch Pending Review
- Assignee set to Patrick Carlisle
- Branch set to https://github.com/puppetlabs/puppet/pull/1110
- Status changed from In Topic Branch Pending Review to Merged - Pending Release
So what is the work around to loosing mongrel? I’m using apache/mongrel to handle the load of about 12 nodes. I can’t run passenger due to its inability to run inside SELinux Enforcing mode (it goes crazy inside /proc)
Hi Curtis, not sure what OS platform you’re running on, but there has been recent work in RHEL6 specifically to fix puppet running under passenger:
Another option would be to run a non-passenger Rack server such as Unicorn or thin.
I finally got it working after much frustration. I’m now stuck on passenger and dashboard… 403 forbidden from apache, no logs anywhere, but ssl cert authentication works fine in puppet master’s passenger config.
- Status changed from Merged - Pending Release to Closed
Released in Puppet 3.0.0-rc6
Also available in: Atom