Mark Christian
2011-Oct-14 01:22 UTC
[Puppet Users] I managed to break my Cent5 mongrel puppetmaster after upgrading from EPEL .25.5 to 2.6.6
CentOS release 5.7 (Final)
puppet-server-2.6.6-1.el5.noarch
ruby-1.8.5-19.el5_6.1.x86_64
rake, version 0.9.2
The upgrade from 25.5 to 2.6.6 had been working fine.
Not sure if this is relevant: I then attempted to get puppet-dashboard
working using this guide:
http://docs.puppetlabs.com/guides/installing_dashboard.html
I managed to upgrade rake, but never got this to work: rake
RAILS_ENV=production db:migrate , I then decided to restart the
puppetmaster and now I get this message:
Starting puppetmaster:
Port: 18140/usr/lib/ruby/site_ruby/1.8/puppet/network/http.rb:8:in
`server_class_by_type'': Mongrel is not installed on this platform
(ArgumentError)
from /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:157:in
`http_server_class_by_type''
from /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:137:in
`http_server_class''
from /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:58:in
`initialize''
from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:104:in
`new''
from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:104:in
`main''
from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:46:in
`run_command''
from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:304:in `run''
from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:410:in
`exit_on_fail''
from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:304:in `run''
from /usr/sbin/puppetmasterd:4
[FAILED]
Any help would be most appreciated. Thanks in advance.
$ cat /etc/puppet/puppet.conf
[main]
# Where Puppet stores dynamic and growing data.
# The default value is ''/var/puppet''.
vardir = /var/lib/puppet
# The Puppet log directory.
# The default value is ''$vardir/log''.
logdir = /var/log/puppet
# Where Puppet PID files are kept.
# The default value is ''$vardir/run''.
rundir = /var/run/puppet
# Where SSL certificates are kept.
# The default value is ''$confdir/ssl''.
ssldir = $vardir/ssl
[production]
modulepath=/etc/puppet/modules
manifest=/etc/puppet/manifests/site.pp
[development]
modulepath=/etc/puppet/environments/development/modules
manifest=/etc/puppet/environments/development/manifests/site.pp
trace=true
report=false
[agent]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is ''$confdir/classes.txt''.
classfile = $vardir/classes.txt
# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is ''$confdir/localconfig''.
localconfig = $vardir/localconfig
[master]
user = root
storeconfigs = false
dbadapter = mysql
dbuser = puppet
dbpassword dbserver = localhost
dbsocket = /var/lib/mysql/mysql.sock
modulepath = $confdir/modules
factsync = true
factpath = $vardir/facts
environments=production,development
# The list of reports to generate. All reports are looked for
# in puppet/reports/<name>.rb, and multiple report names should be
# comma-separated (whitespace is okay).
# The default value is ''store''.
reports = store, rrdgraph, tagmail
tagmap = /etc/puppet/tagmail.conf
# Whether RRD information should be graphed.
rrdgraph = true
# How often RRD should expect data.
# This should match how often the hosts report back to the server.
# The default value is ''$runinterval''.
rrdinterval = $runinterval
# The directory where RRD database files are stored.
# Directories for each reporting host will be created under
# this directory.
# The default value is ''$vardir/rrd''.
rrddir = $vardir/rrd
$ cat /etc/sysconfig/puppetmaster
# Location of the main manifest
#PUPPETMASTER_MANIFEST=/etc/puppet/manifests/site.pp
# Where to log general messages to.
# Specify syslog to send log messages to the system log.
#PUPPETMASTER_LOG=syslog
# You may specify an alternate port or an array of ports on which
# puppetmaster should listen. Default is: 8140
# If you specify more than one port, the puppetmaster ist
automatically
# started with the servertype set to mongrel. This might be
interesting
# if you''d like to run your puppetmaster in a loadbalanced cluster.
# Please note: this won''t setup nor start any loadbalancer.
# If you''d like to run puppetmaster with mongrel as servertype but
only
# on one (specified) port, you have to add --servertype=mongrel to
# PUPPETMASTER_EXTRA_OPTS.
# Default: Empty (Puppetmaster isn''t started with mongrel, nor on a
# specific port)
#
# Please note: Due to reduced options in the rc-functions lib in RHEL/
Centos
# versions prior to 5, this feature won''t work. Fedora versions >= 8
are
# known to work.
#PUPPETMASTER_PORTS=""
# Puppetmaster on a different port, run with standard webrick
servertype
#PUPPETMASTER_PORTS="8141"
# Example with multiple ports which will start puppetmaster with
mongrel
# as a servertype
PUPPETMASTER_PORTS=( 18140 18141 18142 18143 18144 18145 18146 18147)
$ cat /etc/httpd/conf.d/puppet.conf
Listen 8140
<Proxy balancer://puppetmaster>
BalancerMember http://127.0.0.1:18140
BalancerMember http://127.0.0.1:18141
BalancerMember http://127.0.0.1:18142
BalancerMember http://127.0.0.1:18143
BalancerMember http://127.0.0.1:18144
BalancerMember http://127.0.0.1:18145
BalancerMember http://127.0.0.1:18146
BalancerMember http://127.0.0.1:18147
BalancerMember http://127.0.0.1:18148
BalancerMember http://127.0.0.1:18149
</Proxy>
<VirtualHost *:8140>
SSLEngine On
SSLCipherSuite SSLv2:-LOW:-EXPORT:RC4+RSA
SSLCertificateFile /var/lib/puppet/ssl/certs/sj-
confman.altera.com.pem
SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/sj-
confman.altera.com.pem
SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem
SSLCACertificateFile /var/lib/puppet/ssl/ca/ca_crt.pem
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +StdEnvVars
RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e
<Location />
SetHandler balancer-manager
Order allow,deny
Allow from all
</Location>
ProxyPass / balancer://puppetmaster/
ProxyPassReverse / balancer://puppetmaster/
ProxyPreserveHost On
ErrorLog /var/log/httpd/balancer_error_log
CustomLog /var/log/httpd/balancer_access_log combined
</VirtualHost>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Mark Christian
2011-Oct-14 01:55 UTC
[Puppet Users] Re: I managed to break my Cent5 mongrel puppetmaster after upgrading from EPEL .25.5 to 2.6.6
I removed the rubygem-mongrel rpm and reinstalled it. That appears to have fixed my issue. On Oct 13, 6:22 pm, Mark Christian <mchri...@altera.com> wrote:> CentOS release 5.7 (Final) > puppet-server-2.6.6-1.el5.noarch > ruby-1.8.5-19.el5_6.1.x86_64 > rake, version 0.9.2 > > The upgrade from 25.5 to 2.6.6 had been working fine. > > Not sure if this is relevant: I then attempted to get puppet-dashboard > working using this guide:http://docs.puppetlabs.com/guides/installing_dashboard.html > I managed to upgrade rake, but never got this to work: rake > RAILS_ENV=production db:migrate , I then decided to restart the > puppetmaster and now I get this message: > > Starting puppetmaster: > Port: 18140/usr/lib/ruby/site_ruby/1.8/puppet/network/http.rb:8:in > `server_class_by_type'': Mongrel is not installed on this platform > (ArgumentError) > from /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:157:in > `http_server_class_by_type'' > from /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:137:in > `http_server_class'' > from /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:58:in > `initialize'' > from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:104:in > `new'' > from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:104:in > `main'' > from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:46:in > `run_command'' > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:304:in `run'' > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:410:in > `exit_on_fail'' > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:304:in `run'' > from /usr/sbin/puppetmasterd:4 > [FAILED] > > Any help would be most appreciated. Thanks in advance. > > $ cat /etc/puppet/puppet.conf > [main] > # Where Puppet stores dynamic and growing data. > # The default value is ''/var/puppet''. > vardir = /var/lib/puppet > > # The Puppet log directory. > # The default value is ''$vardir/log''. > logdir = /var/log/puppet > > # Where Puppet PID files are kept. > # The default value is ''$vardir/run''. > rundir = /var/run/puppet > > # Where SSL certificates are kept. > # The default value is ''$confdir/ssl''. > ssldir = $vardir/ssl > > [production] > modulepath=/etc/puppet/modules > manifest=/etc/puppet/manifests/site.pp > > [development] > modulepath=/etc/puppet/environments/development/modules > manifest=/etc/puppet/environments/development/manifests/site.pp > trace=true > report=false > > [agent] > # The file in which puppetd stores a list of the classes > # associated with the retrieved configuratiion. Can be loaded in > # the separate ``puppet`` executable using the ``--loadclasses`` > # option. > # The default value is ''$confdir/classes.txt''. > classfile = $vardir/classes.txt > > # Where puppetd caches the local configuration. An > # extension indicating the cache format is added automatically. > # The default value is ''$confdir/localconfig''. > localconfig = $vardir/localconfig > > [master] > user = root > storeconfigs = false > dbadapter = mysql > dbuser = puppet > dbpassword > dbserver = localhost > dbsocket = /var/lib/mysql/mysql.sock > > modulepath = $confdir/modules > > factsync = true > factpath = $vardir/facts > > environments=production,development > > # The list of reports to generate. All reports are looked for > # in puppet/reports/<name>.rb, and multiple report names should be > # comma-separated (whitespace is okay). > # The default value is ''store''. > reports = store, rrdgraph, tagmail > tagmap = /etc/puppet/tagmail.conf > > # Whether RRD information should be graphed. > rrdgraph = true > > # How often RRD should expect data. > # This should match how often the hosts report back to the server. > # The default value is ''$runinterval''. > rrdinterval = $runinterval > > # The directory where RRD database files are stored. > # Directories for each reporting host will be created under > # this directory. > # The default value is ''$vardir/rrd''. > rrddir = $vardir/rrd > > $ cat /etc/sysconfig/puppetmaster > # Location of the main manifest > #PUPPETMASTER_MANIFEST=/etc/puppet/manifests/site.pp > > # Where to log general messages to. > # Specify syslog to send log messages to the system log. > #PUPPETMASTER_LOG=syslog > > # You may specify an alternate port or an array of ports on which > # puppetmaster should listen. Default is: 8140 > # If you specify more than one port, the puppetmaster ist > automatically > # started with the servertype set to mongrel. This might be > interesting > # if you''d like to run your puppetmaster in a loadbalanced cluster. > # Please note: this won''t setup nor start any loadbalancer. > # If you''d like to run puppetmaster with mongrel as servertype but > only > # on one (specified) port, you have to add --servertype=mongrel to > # PUPPETMASTER_EXTRA_OPTS. > # Default: Empty (Puppetmaster isn''t started with mongrel, nor on a > # specific port) > # > # Please note: Due to reduced options in the rc-functions lib in RHEL/ > Centos > # versions prior to 5, this feature won''t work. Fedora versions >= 8 > are > # known to work. > #PUPPETMASTER_PORTS="" > # Puppetmaster on a different port, run with standard webrick > servertype > #PUPPETMASTER_PORTS="8141" > # Example with multiple ports which will start puppetmaster with > mongrel > # as a servertype > PUPPETMASTER_PORTS=( 18140 18141 18142 18143 18144 18145 18146 18147) > > $ cat /etc/httpd/conf.d/puppet.conf > Listen 8140 > > <Proxy balancer://puppetmaster> > BalancerMemberhttp://127.0.0.1:18140 > BalancerMemberhttp://127.0.0.1:18141 > BalancerMemberhttp://127.0.0.1:18142 > BalancerMemberhttp://127.0.0.1:18143 > BalancerMemberhttp://127.0.0.1:18144 > BalancerMemberhttp://127.0.0.1:18145 > BalancerMemberhttp://127.0.0.1:18146 > BalancerMemberhttp://127.0.0.1:18147 > BalancerMemberhttp://127.0.0.1:18148 > BalancerMemberhttp://127.0.0.1:18149 > </Proxy> > > <VirtualHost *:8140> > SSLEngine On > SSLCipherSuite SSLv2:-LOW:-EXPORT:RC4+RSA > SSLCertificateFile /var/lib/puppet/ssl/certs/sj- > confman.altera.com.pem > SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/sj- > confman.altera.com.pem > SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem > SSLCACertificateFile /var/lib/puppet/ssl/ca/ca_crt.pem > SSLVerifyClient optional > SSLVerifyDepth 1 > SSLOptions +StdEnvVars > > RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e > RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e > > <Location /> > SetHandler balancer-manager > Order allow,deny > Allow from all > </Location> > > ProxyPass / balancer://puppetmaster/ > ProxyPassReverse / balancer://puppetmaster/ > ProxyPreserveHost On > > ErrorLog /var/log/httpd/balancer_error_log > CustomLog /var/log/httpd/balancer_access_log combined > > </VirtualHost>-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.