Project

General

Profile

Bug #10001

[Foreman] Rubygem-passenger 4.0.18

Added by Brandon Merjil over 5 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
RPMs
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Issue with Foreman frontend Web UI after system reboot.

I found an issue from the /usr/lib/tmpfiles.d/rubygem-pasenger.conf file and what mod_passenger is looking for to create the pid file based on an error message from httpd error_log:
"Cannot create server instance directory '/var/run/rubygem-passenger/passenger.1.0.{pid}': No such file or directory"

The /usr/lib/tmpfiles.d/rubygem-pasenger.conf file, from the rubygem-passenger RPM, is creating /var/run/passenger instead of /var/run/rubygem-passenger which causes the Foreman frontend web service to display Forbidden access to "/".

I changed the tmpfiles.d config to create the rubygem-passenger directory and have not had an issue with reboots since.


Related issues

Related to Packaging - Bug #8392: passenger-status broken on EL7Closed2014-11-13

Associated revisions

Revision 1ded206a (diff)
Added by Dominic Cleal over 5 years ago

fixes #10001 - create correct /var/run dir on boot for Passenger

History

#1 Updated by Dominic Cleal over 5 years ago

  • Assignee set to Dominic Cleal
  • Category set to RPMs
  • Status changed from New to Assigned
  • Legacy Backlogs Release (now unused) set to 28

#2 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #8392: passenger-status broken on EL7 added

#3 Updated by Dominic Cleal over 5 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF