Objects matching the expression 'server'

• #906 Mongrel Server working with Pound Proxy (mongrel, pound, puppetmaster, server)
• #1040 Exceptions when compiling should include node name (exceptions, server)
• ReportsAndReporting Puppet clients can be configured to send reports at the end of every configuration run. Because the Transaction class is responsible for creating and sending the reports, these are called transaction reports. Currently, these reports include all of the log messages generated during the configuration run, along with some basic metrics of what happened on that run. Reports are sent as Puppet::Transaction::Report instances, serialized with YAML. Logs ---- The bulk of the report is every log message generated during the transaction. This is a simple way to send almost all client logs to the Puppet server; you can use the log report to send all of these client logs to syslog on the server. Metrics ------- The rest of the report is some basic metrics describing what happened in the transaction. There are three types of metrics in each report, and each type of metric has one or more values: - **Time**: Keeps track of how long things took. - *Total*: Total time for the configuration run - *File*: - *Exec*: - *User*: - *Group*: - *Config Retrieval*: How long the configuration took to retrieve - *Service*: - *Package*: - **Resources**: Keeps track of the following stats: - *Total*: The total number of resources being managed - *Skipped*: How many resources were skipped, because of either tagging or scheduling restrictions - *Scheduled*: How many resources met any scheduling restrictions - *Out of Sync*: How many resources were out of sync - *Applied*: How many resources were attempted to be fixed - *Failed*: How many resources were not successfully fixed - *Restarted*: How many resources were restarted because their dependencies changed - *Failed Restarts*: How many resources could not be restarted - **Changes**: The total number of changes in the transaction. Setting Up Reporting (client, documentation, reports, server)
• UsingMongrel Alternatively, see: UsingMongrelOnDebian_ UsingMongrelPound_ UsingMongrelNginx_ .. _UsingMongrelOnDebian: Using Mongrel OnDebian .. _UsingMongrelPound: Using Mongrel Pound .. _UsingMongrelNginx: Using Mongrel Nginx Puppet daemons default to using WEBrick for http serving, but puppetmasterd can be used with Mongrel instead. This requires setting up a web proxy in front of Mongrel to handle the SSL connections, and then you can start as many puppetmasterd instances as you need. Note that Puppet uses Mongrel differently than most -- usually, you would have a mongrel_cluster command that managed multiple Mongrel instances. I planned to implement it this way, but it ended up being easier in the short term to stick with puppetmasterd. Please contact me (Luke) if you want to work on getting mongrel_cluster to work with Puppet, as it could be used to manage multiple Mongrel instances at once. See the following diagram which shows how it works: http://reductivelabs.com/trac/puppet/attachment/wiki/UsingMongrel/puppetmaster-mongrel.png Version 0.23.1 or higher of puppetmasterd is required. (Earlier versions couldn't do certificate signing because they didn't support the X-Client-Verify header.) This document only describes setting up Apache as a proxy in front of Mongrel. Any other http proxy should work, as long as it supports validating client certificates. Why You'd Do This ----------------- Mongrel scales much better than WEBrick, at least partially because it allows you to run multiple processes serving the same pool of clients on the same host. WEBrick only uses Ruby's threading, which does not scale beyond one processor, and it appears that WEBrick starts dropping connections beyond about 2 concurrent connections. If you're getting connection-reset or End-of-file errors, you should try Mongrel. As more people try it and it proves to be stable, it will eventually become the preferred serving platform for the master. Apache Configuration -------------------- Here is a complete apache configuration, intended for use only with puppet:: # Jeff Mc Cune? <mccune@math.ohio-state.edu> # 2007-09-14 # # Minimal Apache Configuration for Apache+Mongrel+Puppetmaster # # Host System Setup and Configuration: # - Add puppet/puppet user/group # - Use the following configuration file. # - /Library/Puppet/Generated/Server is owned by puppet/puppet # # - If you have a system which doens't provide Apache 2.2.X packages: # Apache may be built with: # # ./configure --enable-so \ # --enable-ssl (http, mongrel, puppet, puppetmasterd, server)
• UsingMongrelOnDebian This is a complete step-by-step configuration for using Mongrel instead of Webrick on Debian Etch. It uses the Debian Apache2 recipe_ and creates a stand-alone apache server on port 8140 for puppetmaster. You need: 1. The mongrel and libdaemons-ruby1.8 packages from etch-backports_ 2. A stand-alone apache2 configuration for puppetmaster only: Apache Configuration_ 3. An init script for stand-alone apache: Apache init script_ 4. A puppetmaster init script, which starts 10 mongrel processes: Puppetmasterd init script_ 5. And finally, a module called puppet to tie this all together. The module's init.pp file is listed below:: class puppetmaster inherits apache2 { $certname (debian, http, mongrel, puppet, puppetmasterd, recipe, server)