Skip to main content

Buildout recipes to configure the pound load balancer

Project description

Pound buildout recipe

This package provides buildout_recipes for the configuration of pound. This is a more fully featured recipe than others we’ve found on PyPI, and supports things like 500 error pages, emergency servers and configurable affinity.

We use the system pound, so this recipe will not install pound for you. If you wish to install pound, use zc.recipe.cmmi perhaps.

An example of a standard setup:

recipe = isotoma.recipe.pound
address =
port = 8080
session = COOKIE:_ZopeID:3600
err500 = /var/www/emergency/index.html
emergency =
backends =

If you use pound or another loadbalancer, you might find isotoma.recipe.portmap useful too.

Mandatory parameters


The address on which to listen for connections


The port on which to listen for connections


A list of backends, supplied as address:port pairs, separated by whitespace

Optional parameters


The path to the pound binary. Defaults to /usr/sbin/pound.


The path to the poundctl binary. Defaults to /usr/sbin/poundctl.


The user to run pound as. Defaults to www-data.


The group to run pound as. Defaults to www-data.


The syslog facility to which to send log output. Defaults to local0.


The logging level. Defaults to ‘2’.


The number of seconds between checks for aliveness of previously dead backends. Defaults to ‘30’.


The timeout for HTTP requests to a backend. Defaults to ‘60’.


Which verbs are accepted. See the pound manual for more details. Defaults to ‘0’ (accept only standard verbs).


The full path to the configuration file template, if you want to customise further. Defaults to pound.cfg template in this package.


If you wish to have session affinity, provide the configuration here as type:id:TTL.


If you use an emergency server, provide the configuration here as address:port.


If you wish to provide an error 500 page, provide the full path here.


If you wish to provide an error 503 page, provide the full path here.

Emergency Servers

Recipes are also included to help construct emergency pages. Pound’s support for emergency serving is pretty rudimentary, so it needs some help to provide a decent service. The emergency recipe:

  • provides an apache configuration suitable for use in this situation

  • processes the index page of the emergency content with a simple string substitution, so the image and css resources can be located

The index page of the emergency server is suitable for using in the err500 directive as well.

To use this, you should first create a directory containing an index.html page, and whatever resources are needed to serve this page from apache. In the template, refer to all resouces using $baseurl. For example, if we have:


then in index.html put:

        <img src="$baseurl/images/logo.png" />

Then provide a recipe like:

recipe = isotoma.recipe.pound:emergency
path = /path/to/htdocs
interfaces =
listen = yes
public =
access_log = /var/log/apache2/
error_log = /var/log/apache2/
substitute = index.html

$baseurl will be replaced with the value of public.

This might seem like an overly convoluted way of setting up something relatively simple, but if you want valid and testable configurations in continuous integration, staging and production environments this is worth the effort.


0.1.13 (2013-01-28)

  • Nothing changed yet.

0.1.12 (2013-01-21)

  • Make sure the cycle script is run as run and only when there is a pound socket.

0.1.11 (2012-10-25)

  • Don’t invoke poundctl when working out which backends to use. This avoids the whole issue of crappy pound XML that python2.4 can’t parse.

0.1.10 (2012-10-14)

  • Refactor resuable cycle logic into a Backend class.

  • Ensure the listen address is in correct state before moving onto next backend.

  • You can optionally poke URL’s on the backend to ensure it has started.

0.1.9 (2012-10-01)

  • Add a default emergency page.

0.1.8 (2012-07-03)

  • No changes - release to fix version sync weirdness?

0.1.7 (2012-07-03)

  • Restore python2.4 compatibility

0.1.6 (2012-02-03)

  • Better handling of migrations to ${buildout:run-directory}

0.1.5 (2011-08-26)

  • If there is a ${buildout:run-directory}, put pid file in there

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution (21.0 kB view hashes)

Uploaded source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page