Foreman 1.4

Cristian_Falcas · January 29, 2014, 7:45am

Hello,

I can't seem to be able to successfully install latest foreman. Maybe
someone else has the same problem and can help me with some advice.

I'm trying to set up a smart proxy using the following command:

foreman-installer --verbose --no-enable-foreman
–enable-foreman-proxy --enable-puppet --puppet-configtimeout=600
–puppet-server-ca=false
–puppet-ca-server=https://puppet.company.net
–puppet-server-foreman-url=https://puppet.company.net
–puppet-server-reports=foreman,log,store
–puppet-server-report-api=v2
–puppet-server-dynamic-environments=true
–foreman-proxy-oauth-consumer-key=some_key
–foreman-proxy-oauth-consumer-secret=some_secret
–foreman-proxy-foreman-base-url=https://puppet.company.net
–foreman-proxy-register-in-foreman=true
–foreman-proxy-puppetca=false --foreman-proxy-tftp=false
–foreman-proxy-puppetrun-provider=mcollective

Errors are:

[ERROR 2014-01-29 09:37:52 verbose]
/Stage[main]/Apache::Service/Service[httpd]/ensure: change from
stopped to running failed: Could not start Service[httpd]: Execution
of '/sbin/service httpd start' returned 1: at
/usr/share/foreman-installer/modules/apache/manifests/service.pp:34

[ERROR 2014-01-29 09:38:07 verbose]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[v-is-puppet-02.synygy.net]:
Could not evaluate: undefined method `[]' for nil:NilClass

Trying to start the httpd server manually:

service httpd restart
Stopping httpd: [FAILED]
Starting httpd: Syntax error on line 20 of /etc/httpd/conf.d/25-puppet.conf:
Invalid command 'PassengerEnabled', perhaps misspelled or defined by a
module not included in the server configuration
[FAILED]

I think that it messes up the httpd configuration. Those are the files
in /etc/httpd/conf.d/ after the install:

15-default.conf
25-puppet.conf
actions.load
alias.conf
alias.load
auth_basic.load
auth_digest.load
authn_alias.load
authn_anon.load
authn_dbm.load
authn_default.load
authn_file.load
authz_dbm.load
authz_default.load
authz_groupfile.load
authz_host.load
authz_owner.load
authz_user.load
autoindex.conf
autoindex.load
cache.load
cgi.load
dav_fs.conf
dav_fs.load
dav.load
deflate.conf
deflate.load
dir.conf
dir.load
env.load
expires.load
ext_filter.load
headers.load
include.load
log_config.load
logio.load
mime.conf
mime.load
mime_magic.conf
mime_magic.load
negotiation.conf
negotiation.load
prefork.conf
rewrite.load
setenvif.conf
setenvif.load
speling.load
ssl.conf
ssl.load
substitute.load
suexec.load
usertrack.load
version.load
vhost_alias.load

Installed foreman versions:

foreman-installer-1.4.0-0.2.RC2.el6.noarch
foreman-proxy-1.4.0-0.2.RC2.el6.noarch

Best regards,
Cristian Falcas

Dominic_Cleal1 · January 29, 2014, 8:33am

Yes, you're missing passenger.conf from this list. It's because you've
disabled Foreman from the install and are doing a standalone Puppet
master installation, and our "puppet" module didn't include passenger so
it wasn't installed.

This patch to our "puppet" module fixes the issue, and will be in 1.4.0:
https://github.com/theforeman/puppet-puppet/commit/488e069c1

You can either apply that to
/usr/share/foreman-installer/modules/puppet/, or just doing "yum install
mod_passenger" should be sufficient.

Regards,

···

On 29/01/14 07:45, Cristian Falcas wrote: > Hello, > > I can't seem to be able to successfully install latest foreman. Maybe > someone else has the same problem and can help me with some advice. > > I'm trying to set up a smart proxy using the following command: > > foreman-installer --verbose --no-enable-foreman > --enable-foreman-proxy --enable-puppet --puppet-configtimeout=600 > --puppet-server-ca=false > --puppet-ca-server=https://puppet.company.net > --puppet-server-foreman-url=https://puppet.company.net > --puppet-server-reports=foreman,log,store > --puppet-server-report-api=v2 > --puppet-server-dynamic-environments=true > --foreman-proxy-oauth-consumer-key=some_key > --foreman-proxy-oauth-consumer-secret=some_secret > --foreman-proxy-foreman-base-url=https://puppet.company.net > --foreman-proxy-register-in-foreman=true > --foreman-proxy-puppetca=false --foreman-proxy-tftp=false > --foreman-proxy-puppetrun-provider=mcollective > > Errors are: > > [ERROR 2014-01-29 09:37:52 verbose] > /Stage[main]/Apache::Service/Service[httpd]/ensure: change from > stopped to running failed: Could not start Service[httpd]: Execution > of '/sbin/service httpd start' returned 1: at > /usr/share/foreman-installer/modules/apache/manifests/service.pp:34 > > [ERROR 2014-01-29 09:38:07 verbose] > /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[v-is-puppet-02.synygy.net]: > Could not evaluate: undefined method `[]' for nil:NilClass > > Trying to start the httpd server manually: > > service httpd restart > Stopping httpd: [FAILED] > Starting httpd: Syntax error on line 20 of /etc/httpd/conf.d/25-puppet.conf: > Invalid command 'PassengerEnabled', perhaps misspelled or defined by a > module not included in the server configuration > [FAILED] > > > > I think that it messes up the httpd configuration. Those are the files > in /etc/httpd/conf.d/ after the install:

–
Dominic Cleal
Red Hat Engineering

Cristian_Falcas · January 29, 2014, 12:44pm

Hi,

This solved my issue, thank you.

But when trying to upgrade the foreman installation, I get this error
when trying to install foreman-postgresql:

Transaction Check Error:
file /usr/bin/ruby193-ruby conflicts between attempted installs of
ruby193-ruby-wrapper-0.0.2-4.el6.noarch and
ruby193-ruby-1.9.3.327-27.el6.x86_64

ruby193-ruby-wrapper noarch
0.0.2-4.el6 foreman 5.0 k
ruby193-ruby x86_64
1.9.3.327-27.el6 scl_ruby193 58 k

I'm using thye scl_ruby from http://people.redhat.com/bkabrda/ruby193-rhel-6/

Best regards,
Cristian Falcas

···

On Wed, Jan 29, 2014 at 10:33 AM, Dominic Cleal wrote: > On 29/01/14 07:45, Cristian Falcas wrote: >> Hello, >> >> I can't seem to be able to successfully install latest foreman. Maybe >> someone else has the same problem and can help me with some advice. >> >> I'm trying to set up a smart proxy using the following command: >> >> foreman-installer --verbose --no-enable-foreman >> --enable-foreman-proxy --enable-puppet --puppet-configtimeout=600 >> --puppet-server-ca=false >> --puppet-ca-server=https://puppet.company.net >> --puppet-server-foreman-url=https://puppet.company.net >> --puppet-server-reports=foreman,log,store >> --puppet-server-report-api=v2 >> --puppet-server-dynamic-environments=true >> --foreman-proxy-oauth-consumer-key=some_key >> --foreman-proxy-oauth-consumer-secret=some_secret >> --foreman-proxy-foreman-base-url=https://puppet.company.net >> --foreman-proxy-register-in-foreman=true >> --foreman-proxy-puppetca=false --foreman-proxy-tftp=false >> --foreman-proxy-puppetrun-provider=mcollective >> >> Errors are: >> >> [ERROR 2014-01-29 09:37:52 verbose] >> /Stage[main]/Apache::Service/Service[httpd]/ensure: change from >> stopped to running failed: Could not start Service[httpd]: Execution >> of '/sbin/service httpd start' returned 1: at >> /usr/share/foreman-installer/modules/apache/manifests/service.pp:34 >> >> [ERROR 2014-01-29 09:38:07 verbose] >> /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[v-is-puppet-02.synygy.net]: >> Could not evaluate: undefined method `[]' for nil:NilClass >> >> Trying to start the httpd server manually: >> >> service httpd restart >> Stopping httpd: [FAILED] >> Starting httpd: Syntax error on line 20 of /etc/httpd/conf.d/25-puppet.conf: >> Invalid command 'PassengerEnabled', perhaps misspelled or defined by a >> module not included in the server configuration >> [FAILED] >> >> >> >> I think that it messes up the httpd configuration. Those are the files >> in /etc/httpd/conf.d/ after the install: > > Yes, you're missing passenger.conf from this list. It's because you've > disabled Foreman from the install and are doing a standalone Puppet > master installation, and our "puppet" module didn't include passenger so > it wasn't installed. > > This patch to our "puppet" module fixes the issue, and will be in 1.4.0: > https://github.com/theforeman/puppet-puppet/commit/488e069c1 > > You can either apply that to > /usr/share/foreman-installer/modules/puppet/, or just doing "yum install > mod_passenger" should be sufficient. > > Regards, > > -- > Dominic Cleal > 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 foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/groups/opt_out.

Cristian_Falcas · January 29, 2014, 1:03pm

So it seems to work with packages from

http://ftp.scientificlinux.org/linux/scientific/6.5/x86_64/external_products/softwarecollections/

Sorry for bothering you

···

On Wed, Jan 29, 2014 at 2:44 PM, Cristian Falcas wrote: > Hi, > > This solved my issue, thank you. > > But when trying to upgrade the foreman installation, I get this error > when trying to install foreman-postgresql: > > Transaction Check Error: > file /usr/bin/ruby193-ruby conflicts between attempted installs of > ruby193-ruby-wrapper-0.0.2-4.el6.noarch and > ruby193-ruby-1.9.3.327-27.el6.x86_64 > > ruby193-ruby-wrapper noarch > 0.0.2-4.el6 foreman 5.0 k > ruby193-ruby x86_64 > 1.9.3.327-27.el6 scl_ruby193 58 k > > > > I'm using thye scl_ruby from http://people.redhat.com/bkabrda/ruby193-rhel-6/ > > > Best regards, > Cristian Falcas > > On Wed, Jan 29, 2014 at 10:33 AM, Dominic Cleal wrote: >> On 29/01/14 07:45, Cristian Falcas wrote: >>> Hello, >>> >>> I can't seem to be able to successfully install latest foreman. Maybe >>> someone else has the same problem and can help me with some advice. >>> >>> I'm trying to set up a smart proxy using the following command: >>> >>> foreman-installer --verbose --no-enable-foreman >>> --enable-foreman-proxy --enable-puppet --puppet-configtimeout=600 >>> --puppet-server-ca=false >>> --puppet-ca-server=https://puppet.company.net >>> --puppet-server-foreman-url=https://puppet.company.net >>> --puppet-server-reports=foreman,log,store >>> --puppet-server-report-api=v2 >>> --puppet-server-dynamic-environments=true >>> --foreman-proxy-oauth-consumer-key=some_key >>> --foreman-proxy-oauth-consumer-secret=some_secret >>> --foreman-proxy-foreman-base-url=https://puppet.company.net >>> --foreman-proxy-register-in-foreman=true >>> --foreman-proxy-puppetca=false --foreman-proxy-tftp=false >>> --foreman-proxy-puppetrun-provider=mcollective >>> >>> Errors are: >>> >>> [ERROR 2014-01-29 09:37:52 verbose] >>> /Stage[main]/Apache::Service/Service[httpd]/ensure: change from >>> stopped to running failed: Could not start Service[httpd]: Execution >>> of '/sbin/service httpd start' returned 1: at >>> /usr/share/foreman-installer/modules/apache/manifests/service.pp:34 >>> >>> [ERROR 2014-01-29 09:38:07 verbose] >>> /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[v-is-puppet-02.synygy.net]: >>> Could not evaluate: undefined method `[]' for nil:NilClass >>> >>> Trying to start the httpd server manually: >>> >>> service httpd restart >>> Stopping httpd: [FAILED] >>> Starting httpd: Syntax error on line 20 of /etc/httpd/conf.d/25-puppet.conf: >>> Invalid command 'PassengerEnabled', perhaps misspelled or defined by a >>> module not included in the server configuration >>> [FAILED] >>> >>> >>> >>> I think that it messes up the httpd configuration. Those are the files >>> in /etc/httpd/conf.d/ after the install: >> >> Yes, you're missing passenger.conf from this list. It's because you've >> disabled Foreman from the install and are doing a standalone Puppet >> master installation, and our "puppet" module didn't include passenger so >> it wasn't installed. >> >> This patch to our "puppet" module fixes the issue, and will be in 1.4.0: >> https://github.com/theforeman/puppet-puppet/commit/488e069c1 >> >> You can either apply that to >> /usr/share/foreman-installer/modules/puppet/, or just doing "yum install >> mod_passenger" should be sufficient. >> >> Regards, >> >> -- >> Dominic Cleal >> 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 foreman-users+unsubscribe@googlegroups.com. >> To post to this group, send email to foreman-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out.