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] > <javascript:>> 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.18/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/bin/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/share/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.18/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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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 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.
