为了这个问题的目的，我需要区分我的制作木偶大师和我的发展木偶大师。 无论哪种情况，我的/etc/puppet/puppet.conf是：
[main] ssldir=$vardir/ssl [master] certname=puppet 开发木偶大师正在运行：
# puppetmasterd --debug --no-daemonize
生产木偶大师是一个瘦/ nginx的事情。 相关的nginxconfiguration文件：
# /etc/nginx/sites-enabled/default upstream puppet-production { server unix:/var/run/puppet/master.00.sock; server unix:/var/run/puppet/master.01.sock; server unix:/var/run/puppet/master.02.sock; } server { listen puppet:8140; include conf.d/puppet_ssl.conf; include conf.d/puppet_proxy_set_header.conf; default_type application/x-raw; location /production/file_content/ { rewrite ^/production/file_content/([^/]+)/(.*) /$1/files/$2; break; root /etc/puppet/modules/; } location / { proxy_pass http://puppet-production; } }
和
# /etc/nginx/conf.d/puppet_proxy_set_header.conf proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Client-Verify $ssl_client_verify; proxy_set_header X-Client-Verify SUCCESS; proxy_set_header X-Client-DN $ssl_client_s_dn; proxy_set_header X-SSL-Subject $ssl_client_s_dn; proxy_set_header X-SSL-Issuer $ssl_client_i_dn;
和
# /etc/nginx/conf.d/puppet_ssl.conf ssl on; ssl_certificate /var/lib/puppet/ssl/certs/puppet.pem; ssl_certificate_key /var/lib/puppet/ssl/private_keys/puppet.pem; ssl_ciphers ALL:-ADH:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP; ssl_client_certificate /var/lib/puppet/ssl/ca/ca_crt.pem; ssl_verify_client on;
相关的瘦configuration文件：
#/etc/puppet/config.ru # a config.ru, for use with every rack-compatible webserver. # SSL needs to be handled outside this, though. # if puppet is not in your RUBYLIB: # $:.unshift('/opt/puppet/lib') $0 = "master" # if you want debugging: # ARGV << "--debug" ARGV << "--rack" require 'puppet/application/master' # we're usually running inside a Rack::Builder.new {} block, # therefore we need to call run *here*. run Puppet::Application[:master].run
和
# /etc/supervisor/conf.d/puppetmaster.conf # This file is autogenerated by Puppet. Manual changes will be overwritten! [program:puppetmaster] command=/usr/bin/thin start -e development --socket /var/run/puppet/master.%(process_num)02d.sock --user puppet --group puppet --chdir /etc/puppet -R /etc/puppet/config.ru process_name=%(program_name)s_%(process_num)02d numprocs=3 priority=999 autostart=true autorestart=unexpected startsecs=3 startretries=3 exitcodes=0,2 stopsignal=TERM stopwaitsecs=10 redirect_stderr=false stdout_logfile=/var/log/supervisor/puppetmaster/puppetmaster.out stdout_logfile_maxbytes=250MB stdout_logfile_backups=10 stderr_logfile=/var/log/supervisor/puppetmaster/puppetmaster.err stderr_logfile_maxbytes=250MB stderr_logfile_backups=10
使用puppet-module-supervisor我发现manifests/init.pp中的源代码行path在生产模式下运行时会导致404：
'/etc/logrotate.d/supervisor': source => 'puppet:///modules/supervisor/logrotate', require => Package[$supervisor::params::package];
但如果我修改的path是简单的puppet:///supervisor/logrotate一切都很好。 第一种和第二种forms在开发模式下成功。 这是我的理解，第一种forms是正确的 ，我的生产模式应该没有问题。
运行puppet agent --test在生产模式下configuration主服务器时testing会导致：
# puppet agent --test info: Caching catalog for puppet.troutwine.us info: Applying configuration version '1327957286' err: /Stage[main]/Supervisor/File[/etc/logrotate.d/supervisor]/ensure: change from absent to file failed: Could not set 'file on ensure: Error 404 on SERVER: <html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <hr><center>nginx/1.1.8</center> </body> </html> at /etc/puppet/modules/supervisor/manifests/init.pp:32 notice: Finished catalog run in 1.65 seconds
和来自/var/log/nginx/access.log的日志
# cat /var/log/nginx/{access,error}.log 127.0.1.1 - - [30/Jan/2012:20:50:58 +0000] "POST /production/catalog/puppet.troutwine.us HTTP/1.1" 200 13290 "-" "Ruby" 127.0.1.1 - - [30/Jan/2012:20:51:00 +0000] "GET /production/file_metadata/modules/supervisor/logrotate? HTTP/1.1" 200 308 "-" "Ruby" 127.0.1.1 - - [30/Jan/2012:20:51:00 +0000] "GET /production/file_content/modules/supervisor/logrotate HTTP/1.1" 404 168 "-" "Ruby" 127.0.1.1 - - [30/Jan/2012:20:51:01 +0000] "PUT /production/report/puppet.troutwine.us HTTP/1.1" 200 14 "-" "Ruby" 2012/01/30 20:51:00 [error] 10716#0: *222 open() "/etc/puppet/modules/modules/files/supervisor/logrotate" failed (2: No such file or directory), client: 127.0.1.1, server: , request: "GET /production/file_content/modules/supervisor/logrotate HTTP/1.1", host: "puppet:8140"
有关我的环境的详情：
# puppet --version 2.7.9 # cat /etc/debian_version 6.0.3 # ruby -v ruby 1.9.2p0 (2010-08-18 revision 29036) [i486-linux]
任何人都有一个错误的错误？
客户机节点正在请求的path是：
/production/file_content/modules/supervisor/logrotate
虽然写的nginxconfiguration似乎期待：
/production/file_content/supervisor/logrotate
所以， modules被第一次捕获捕获， supervisor/logrotate被第二次捕获捕获; 需要在模块名称和文件名称之间的文件不在正确的地方， modules得到加倍：
"/etc/puppet/modules/modules/files/supervisor/logrotate" failed (2: No such file or directory)
好像你可以改变你的重写规则：
rewrite ^/production/file_content/modules/([^/]+)/(.*) /$1/files/$2;