Project

General

Profile

Actions

Bug #5894

closed

Passenger apache configuration doesn't get generated/updated

Added by Derrick Hammer almost 10 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
foreman-installer script
Target version:
-
Difficulty:
medium
Triaged:
Fixed in Releases:
Found in Releases:

Description

I recently upgraded to v1.5. I ran foreman-installer after. It seems there was an error introduced with the passenger conf. I renamed the file and re-ran the installer. The file wasn't re-created.

I had to install ruby193-mod_passenger and copy its passenger.conf to get the panel functional.

Actions #1

Updated by Dominic Cleal almost 10 years ago

  • Status changed from New to Rejected
  • translation missing: en.field_release deleted (16)

We're not able to generate this really from the installer as its contents are very platform-specific, so we have to rely on what's in the OS package (as it may refer to specific paths and varies across distributions & versions). Instead, the puppetlabs-apache module excludes the file from being purged, but if it's renamed then this will indeed be deleted by Puppet.

Sorry, I'm not sure there's anything we can do to fix this. I'd recommend using "yum reinstall mod_passenger" to restore it if you lose the original.

Actions

Also available in: Atom PDF