Bug #10244

Mongrel server fails to start even though mongrel is installed

Added by Nick Lewis 7 months ago. Updated 6 months ago.

Status:Closed Start date:10/24/2011
Priority:Normal Due date:
Assignee:Michael Stahnke % Done:

0%

Category:-
Target version:2.6.13
Affected Puppet version: Branch:
Keywords:
Votes: 1

Description

debug: Failed to load library 'puppet/network/http_server/mongrel' for feature 'mongrel'
Could not run: Mongrel is not installed on this platform

History

Updated by Jacob Helwig 7 months ago

This affects both 2.6.12 and 2.7.6.

Updated by yasuhiro yoshida 7 months ago

puppet 2.6.11 source 3files copy

puppet/network/http_server.rb puppet/network/http_server/mongrel.rb puppet/network/http_server/webrick.rb

mongrel pupeptmaster running OK

Updated by Jacob Helwig 7 months ago

  • Status changed from Accepted to Merged - Pending Release
  • Assignee set to Michael Stahnke
  • Target version set to 2.6.x

This has been fixed in the 2.6.x, and 2.7.x branches.

  • 2.6.x: As of commit:7514d325c01ee105c04e3dda8d248d3023a07b2f
  • 2.7.x: As of commit:eab5965329cbfe7593c3c6e36bb547f6cdac193a

Updated by Michael Stahnke 7 months ago

The mongrel patch is being carried in the Puppet Labs packages on yum.puppetlabs.com

Just a note in case some wanders here.

Updated by micah - 7 months ago

  • Status changed from Merged - Pending Release to Code Insufficient

I applied the 2.7.x patch in eab5965329cbfe7593c3c6e36bb547f6cdac193a but I am still seeing this when I attempt to start puppetmaster:

Could not run: Mongrel is not installed on this platform

and the daemon doesn’t start.

However, I do have mongrel installed.

Updated by micah - 7 months ago

I’ve tried both using the debian mongrel package, and also the gem, but neither configuration worked.

Updated by Michael Stahnke 7 months ago

Micah, sounds like you got fixed from Jacob. Can we move this back to closed?

Updated by micah - 7 months ago

Yeah, it appears the referenced commit (ab5965329cbfe7593c3c6e36bb547f6cdac193a) were just the test fixes, the actual fixes were in 397a5064892cb1d581594c110907fa3f2b83af36 (for 2.6.x) and 614526a for 2.7.

I can’t change the status back to “Merged – Pending Release” because I do not have access, but whoever can do that should go ahead.

Updated by Nick Lewis 7 months ago

  • Status changed from Code Insufficient to Merged - Pending Release

Updated by Matthaus Litteken 6 months ago

  • Target version changed from 2.6.x to 2.6.13

released in 2.6.13rc1

Updated by Matthaus Litteken 6 months ago

  • Status changed from Merged - Pending Release to Closed

also released in 2.7.7

Also available in: Atom PDF