Bug 10728 - Rubygem-passenger doesn't work and suggests to use Yum
Summary: Rubygem-passenger doesn't work and suggests to use Yum
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Funda Wang
QA Contact:
Depends on:
Reported: 2013-07-07 14:26 CEST by claire robinson
Modified: 2015-03-31 16:06 CEST (History)
1 user (show)

See Also:
Source RPM: rubygem-passenger
Status comment:


Description claire robinson 2013-07-07 14:26:56 CEST
This bug is created to allow a broken security update to be pushed.

Please refer to bug 10497 for all the details.


Steps to Reproduce:
Comment 1 José Jorge 2013-10-15 08:47:55 CEST
I think I have the same bug according to apache error log: 

[passenger:error] [pid 19615] *** Passenger could not be initialized because of this error: Unable to start the Phusion Passenger watchdog because its executable (/usr/lib/phusion-passenger/agents/PassengerWatchdog) does not exist. This probably means that your Phusion Passenger installation is broken or incomplete, or that your 'PassengerRoot' directive is set to the wrong value. Please reinstall Phusion Passenger or fix your 'PassengerRoot' directive, whichever is applicable.

I worked around it with the following link, but I don't know enough of Ruby to know where to fix the package.

sudo ln -s /usr/lib/ruby/site_ruby /usr/lib/phusion-passenger

CC: (none) => lists.jjorge

Comment 2 Marja Van Waes 2015-03-31 16:06:24 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

The Mageia Bugsquad

Resolution: (none) => OLD

Note You need to log in before you can comment on or make changes to this bug.