The patch from the issue designed to fix this ( https://github.com/theforeman/foreman-packaging/blob/rpm/develop/rubygem-passenger/rubygem-passenger-4.0.18-tmpdir.patch) is still present so you can't entirely judge the versioning as to whats available as a fix. What is the error you see?
On Mon, Aug 21, 2017 at 11:51 AM, Charlie Derwent < [email protected]> wrote: > Apologies for resurrecting an old thread but this looks like this bug > http://projects.theforeman.org/issues/8392 and it is still a problem in > 1.15.3. It appears it was fixed in satellite https://access.redhat.com/ > errata/RHBA-2015:1911 (BZ - 1163380 - passenger-status broken on sat6 on > rhel7) which is using ruby193-rubygem-passenger-4.0.18-20.el7sat.src.rpm > while foreman is still running tfm-rubygem-passenger-4.0.18- > 9.11.el7.x86_64.rpm. > > Apologies if i'm misreading the scl versioning. > > Thanks > Charlie > > On Thursday, 6 October 2016 15:59:14 UTC+1, Edson Manners wrote: >> >> Unfortunately no. As I think you've seen in the forums someone gave me >> some hints but they never helped either. It's still an issue for us as we >> seem to regularly overrun katello's ability to process puppet requests and >> need this to tune the Apache webserver. I'd be very interested in whatever >> you found. >> >> On 10/6/2016 2:24 AM, Matthew Wilmott wrote: >> >> Did this ever get fixed? >> >> We use telegraf to monitor passenger-status and send to influx/grafana >> >> We have the same issue, regardless of how we call the passenger-status we >> insists passenger isnt running... >> >> On Thursday, July 14, 2016 at 6:01:56 AM UTC+10, Edson Manners wrote: >>> >>> Thanks for the replies Eric. I tried those commands on both the current >>> production server and a newly rebuilt test server using only the commands >>> from the katello install page and got the following output: >>> >>> [root@katello ~]# scl enable tfm '/opt/theforeman/tfm/root/usr/ >>> bin/passenger-status' >>> ERROR: Phusion Passenger doesn't seem to be running. >>> [root@katello-test ~]# scl enable tfm '/opt/theforeman/tfm/root/usr/ >>> bin/passenger-status' >>> ERROR: Phusion Passenger doesn't seem to be running. >>> >>> [root@katello ~]# /usr/sbin/passenger-status >>> ERROR: Phusion Passenger doesn't seem to be running. >>> [root@katello-test ~]# /usr/sbin/passenger-status >>> ERROR: Phusion Passenger doesn't seem to be running. >>> >>> If you look closely you'll see that one machine is katello and the other >>> is katello-test and they both behave the same. >>> >>> >>> >>> On Thursday, July 7, 2016 at 3:21:52 PM UTC-4, Eric Helms wrote: >>>> >>>> >>>> >>>> On Tue, Jul 5, 2016 at 10:55 AM, Edson Manners <[email protected]> >>>> wrote: >>>> >>>>> I've been struggling with this issue for a while and finally feel the >>>>> need to seek external help. >>>>> >>>>> We used to run Foreman 1.9.3 on RHEL 7.2. the passenger-status command >>>>> was used to tune the puppetmaster when the server got overwhelmed. >>>>> >>>>> [root@foreman ~]# cat /etc/redhat-release >>>>> Red Hat Enterprise Linux Server release 7.2 (Maipo) >>>>> [root@foreman ~]# which passenger-status >>>>> /usr/bin/passenger-status >>>>> [root@foreman ~]# rpm -q --whatprovides /usr/bin/passenger-status >>>>> rubygem-passenger-4.0.18-9.8.el7.x86_64 >>>>> [root@foreman ~]# /usr/bin/passenger-status >>>>> Version : 4.0.18 >>>>> Date : 2016-07-05 10:44:15 -0400 >>>>> Instance: 3376 >>>>> ----------- General information ----------- >>>>> Max pool size : 48 >>>>> Processes : 3 >>>>> Requests in top-level queue : 0 >>>>> >>>>> ----------- Application groups ----------- >>>>> /usr/share/foreman#default: >>>>> App root: /usr/share/foreman >>>>> Requests in queue: 0 >>>>> * PID: 18170 Sessions: 0 Processed: 622 Uptime: 4h 24m >>>>> 28s >>>>> CPU: 0% Memory : 232M Last used: 6s ago >>>>> .... >>>>> ... >>>>> >>>>> >>>>> We've moved to katello 2.4 on CentOS 7.2 and now passenger-status no >>>>> longer works out of the box. >>>>> >>>>> [root@katello-test emanners]# cat /etc/redhat-release >>>>> CentOS Linux release 7.2.1511 (Core) >>>>> [root@katello-test emanners]# which passenger-status >>>>> /sbin/passenger-status >>>>> [root@katello-test emanners]# rpm -q --whatprovides >>>>> /usr/sbin/passenger-status >>>>> passenger-4.0.53-4.el7.x86_64 >>>>> [root@katello-test emanners]# /usr/sbin/passenger-status >>>>> ERROR: Phusion Passenger doesn't seem to be running. >>>>> >>>>> I've managed to find a few posts on Google (not Katello related) that >>>>> suggest the reason is multiple copies of passenger on the host. >>>>> [root@katello-test ~]# locate passenger-status >>>>> /opt/theforeman/tfm/root/usr/bin/passenger-status >>>>> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.1 >>>>> 8/bin/passenger-status >>>>> /opt/theforeman/tfm/root/usr/share/man/man8/passenger-status.8.gz >>>>> >>>> >>>> This set of passenger libraries are used for running the Foreman web >>>> application under Apache within the SCL. To run the passenger-status >>>> command for the SCL, you'd need to enable the SCL and run it: >>>> >>>> scl enable tfm '/opt/theforeman/tfm/root/usr/bin/passenger-status' >>>> >>>> >>>>> /usr/sbin/passenger-status >>>>> /usr/share/man/man8/passenger-status.8.gz >>>>> >>>> >>>> This set of passenger libraries are used for running the puppetmaster >>>> that is installed on the server by default which is running outside the SC >>>> and should work like normal (barring a bug in newer passenger). >>>> >>>> >>>>> [root@katello-test ~]# /opt/theforeman/tfm/root/usr/b >>>>> in/passenger-status >>>>> /opt/rh/ruby193/root/usr/bin/ruby: error while loading shared >>>>> libraries: libruby.so.1.9: cannot open shared object file: No such file or >>>>> directory >>>>> [root@katello-test ~]# /opt/theforeman/tfm/root/usr/s >>>>> hare/gems/gems/passenger-4.0.18/bin/passenger-status >>>>> *** Phusion Passenger: no passenger_native_support.so found for the >>>>> current Ruby interpreter. Compiling one (set >>>>> PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0 >>>>> to disable)... >>>>> # mkdir -p /root/.passenger/native_support/4.0.18/ruby-2.0.0-x86_64- >>>>> linux >>>>> # cd /root/.passenger/native_support/4.0.18/ruby-2.0.0-x86_64-linux >>>>> # /usr/bin/ruby '/opt/theforeman/tfm/root/usr/ >>>>> share/gems/gems/passenger-4.0.18/ruby_extension_source/extconf.rb' >>>>> /usr/bin/ruby: No such file or directory -- >>>>> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.1 >>>>> 8/ruby_extension_source/extconf.rb (LoadError) >>>>> Compilation failed. >>>>> ------------------------------- >>>>> Ruby native_support extension not loaded. Continuing without >>>>> native_support. >>>>> ERROR: Phusion Passenger doesn't seem to be running. >>>>> >>>>> >>>>> So the question is which ones does Katello really need since they were >>>>> both installed during the installer and how do I get this command working >>>>> again without breaking the underlying app? >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Foreman users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at https://groups.google.com/group/foreman-users. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> >>>> -- >>>> Eric D. Helms >>>> Red Hat Engineering >>>> Ph.D. Student - North Carolina State University >>>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/foreman-users/rWnFdRzy3Zg/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
