Foreman_proxy "Could not evaluate: 404"

Hey folks,

I've got a few issues with installing foreman and was hoping someone might
have some ideas on how to approach this.
I've done a fair bit of googling about the errors I have.

System:

  • Type of System = VMware Virtual Platform

  • OS Version = CentOS release 6.5 (Final)

things seem to be going ok, but then it errors out:

[ INFO 2014-08-31 00:36:33 verbose]
/usr/lib/ruby/gems/1.8/gems/puppet-3.6.2/lib/puppet/util/command_line.rb:137:in
`run'

[ INFO 2014-08-31 00:36:33 verbose]
/usr/lib/ruby/gems/1.8/gems/puppet-3.6.2/lib/puppet/util/command_line.rb:91:in
`execute'

[ INFO 2014-08-31 00:36:33 verbose]
/usr/lib/ruby/gems/1.8/gems/puppet-3.6.2/bin/puppet:8

[ INFO 2014-08-31 00:36:33 verbose] /usr/bin/puppet:20:in `load'

[ INFO 2014-08-31 00:36:33 verbose] /usr/bin/puppet:20

[ WARN 2014-08-31 00:36:33 verbose] Finished catalog run in 4.55 seconds

[ INFO 2014-08-31 00:36:34 verbose] Puppet has finished, bye!

[ INFO 2014-08-31 00:36:34 verbose] Executing hooks in group post

[ INFO 2014-08-31 00:36:34 verbose] All hooks in group post finished

[ERROR 2014-08-31 00:36:34 verbose] Repeating errors encountered during run:

[ERROR 2014-08-31 00:36:34 verbose]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[localhostname_redacted]:
Could not evaluate: 404 Resource Not Found: <!DOCTYPE HTML PUBLIC
"-//IETF//DTD HTML 2.0//EN">

Something went wrong! Check the log for ERROR-level output

The full log is at /var/log/foreman-installer/foreman-installer.log

I did install ruby 193 from SCL but I'm not exactly sure how to force the
installer to try using that or if that would help.

I don't get any errors starting or stopping foreman-proxy.

I thought maybe it installed anyway so I checked the https logs - which I
suspect may be a different problem:

[Sat Aug 30 23:39:21 2014] [notice] caught SIGTERM, shutting down

[Sat Aug 30 23:39:23 2014] [error] *** Passenger could not be initialized
because of this error: The 'PassengerRoot' configuration option is not
specified. This option is required, so please specify it. TIP: The correct
value for this option was given to you by
'passenger-install-apache2-module'.

[Sat Aug 30 23:39:23 2014] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)

[Sat Aug 30 23:39:23 2014] [notice] Digest: generating secret for digest
authentication …

[Sat Aug 30 23:39:23 2014] [notice] Digest: done

[Sat Aug 30 23:39:23 2014] [error] *** Passenger could not be initialized
because of this error: The 'PassengerRoot' configuration option is not
specified. This option is required, so please specify it. TIP: The correct
value for this option was given to you by
'passenger-install-apache2-module'.

[Sat Aug 30 23:39:23 2014] [notice] Apache/2.2.15 (Unix) DAV/2
Phusion_Passenger/3.0.21 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured –
resuming normal operations

If I attempt to access the foreman server through the browser I get:

Forbidden

You don't have permission to access / on this server.

I did try creating a /etc/httpd/conf.d/foreman.conf but it didn't work,
and besides I see there are other files put there for foreman.

Any help appreciated.

-mike

The logs below say Passenger 3.0.21's installed, though we require/ship
version 4.0.18 in our repos, so I guess you have another repo configured
that's overriding this. (Either epochs or yum priorities.)

Try an "rpm -qa *passenger*" and check you have seven RPMs (three
ruby193*, three rubygem* and one mod_passenger) all version 4.0.18 from
our repo.

If it's epochs, you can try a "yum downgrade rubygem-passenger-4.0.18
rubygem-passenger-native-4.0.18 rubygem-passenger-native-libs-4.0.18
mod_passenger-4.0.18".

··· -- Dominic Cleal Red Hat Engineering

On 31/08/14 01:50, Michael Maher wrote:

Hey folks,

I’ve got a few issues with installing foreman and was hoping someone
might have some ideas on how to approach this.
I’ve done a fair bit of googling about the errors I have.

System:

  • Type of System = VMware Virtual Platform

  • OS Version = CentOS release 6.5 (Final)

things seem to be going ok, but then it errors out:

[ INFO 2014-08-31 00:36:33 verbose]
/usr/lib/ruby/gems/1.8/gems/puppet-3.6.2/lib/puppet/util/command_line.rb:137:in
`run’

[ INFO 2014-08-31 00:36:33 verbose]
/usr/lib/ruby/gems/1.8/gems/puppet-3.6.2/lib/puppet/util/command_line.rb:91:in
`execute’

[ INFO 2014-08-31 00:36:33 verbose]
/usr/lib/ruby/gems/1.8/gems/puppet-3.6.2/bin/puppet:8

[ INFO 2014-08-31 00:36:33 verbose] /usr/bin/puppet:20:in `load’

[ INFO 2014-08-31 00:36:33 verbose] /usr/bin/puppet:20

[ WARN 2014-08-31 00:36:33 verbose] Finished catalog run in 4.55 seconds

[ INFO 2014-08-31 00:36:34 verbose] Puppet has finished, bye!

[ INFO 2014-08-31 00:36:34 verbose] Executing hooks in group post

[ INFO 2014-08-31 00:36:34 verbose] All hooks in group post finished

[ERROR 2014-08-31 00:36:34 verbose] Repeating errors encountered during run:

[ERROR 2014-08-31 00:36:34 verbose]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[localhostname_redacted]:
Could not evaluate: 404 Resource Not Found:

Something went wrong! Check the log for ERROR-level output

The full log is at /var/log/foreman-installer/foreman-installer.log

I did install ruby 193 from SCL but I’m not exactly sure how to force
the installer to try using that or if that would help.

I don’t get any errors starting or stopping foreman-proxy.

I thought maybe it installed anyway so I checked the https logs - which
I suspect may be a different problem:

[Sat Aug 30 23:39:21 2014] [notice] caught SIGTERM, shutting down

[Sat Aug 30 23:39:23 2014] [error] *** Passenger could not be
initialized because of this error: The ‘PassengerRoot’ configuration
option is not specified. This option is required, so please specify it.
TIP: The correct value for this option was given to you by
‘passenger-install-apache2-module’.

[Sat Aug 30 23:39:23 2014] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)

[Sat Aug 30 23:39:23 2014] [notice] Digest: generating secret for digest
authentication …

[Sat Aug 30 23:39:23 2014] [notice] Digest: done

[Sat Aug 30 23:39:23 2014] [error] *** Passenger could not be
initialized because of this error: The ‘PassengerRoot’ configuration
option is not specified. This option is required, so please specify it.
TIP: The correct value for this option was given to you by
‘passenger-install-apache2-module’.

[Sat Aug 30 23:39:23 2014] [notice] Apache/2.2.15 (Unix) DAV/2
Phusion_Passenger/3.0.21 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured
– resuming normal operations

If I attempt to access the foreman server through the browser I get:

Forbidden

You don’t have permission to access / on this server.

I did try creating a /etc/httpd/conf.d/foreman.conf but it didn’t
work, and besides I see there are other files put there for foreman.

Any help appreciated.

-mike


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 foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.