I'm wrestling with the same issue and scenario at the moment, did you ever
work it out?
Going to try adding the following parameters to my nginx configuration
tomorrow:
uwsgi_param HTTP_X_CLIENT_DN $ssl_client_s_dn;
uwsgi_param HTTP_X_CLIENT_VERIFY $ssl_client_verify;
Den onsdagen den 25:e september 2013 kl. 16:49:41 UTC+2 skrev Roman:
>
> Hi,
>
> is anyone using the combination of uwsgi-plugin-rack-ruby with nginx and
> puppet? I had Nginx+Passenger running fine before, but now there seems to
> be a permissions-problem:
>
> Nginx is relaying everything to the uwsgi-process:
>
> /etc/nginx/sites-enabled/puppet:
> server {
> <---snip--->
>
> root /etc/puppet/rack/public;
>
> location ~ / {
> root "/etc/puppet/rack/public";
> include "uwsgi_params";
> uwsgi_modifier1 7;
> uwsgi_pass 127.0.0.1:3031;
> }
>
> }
>
> Running uwsgi with the following:
>
> uwsgi --plugins rack -s :3031 -M -p 4 -m --post-buffering 4096 --rack
> /etc/puppet/rack/config.ru
>
> and /etc/puppet/rack/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:
> # $LOAD_PATH.unshift('/opt/puppet/lib')
>
> $0 = "master"
>
> # if you want debugging:
> # ARGV << "--debug"
>
> ARGV << "--rack"
>
> ARGV << "--confdir" << "/etc/puppet"
> ARGV << "--vardir" << "/var/lib/puppet"
>
>
> require 'puppet/util/command_line'
> # we're usually running inside a Rack::Builder.new {} block,
> # therefore we need to call run *here*.
> run Puppet::Util::CommandLine.new.execute
>
>
> And the error i get is the following:
>
> root@vm013:/etc/nginx> puppet agent -t --tags ntp --noop
> Warning: Unable to fetch my node definition, but the agent run will
> continue:
> Warning: Error 403 on SERVER: Forbidden request: XXXX access to /node/XXXX
> [find] at :133
> Info: Retrieving plugin
> Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources
> using 'eval_generate: Error 403 on SERVER: Forbidden request: XXXX access
> to /file_metadata/plugins [search] at :133
> Error: /File[/var/lib/puppet/lib]: Could not evaluate: Error 403 on
> SERVER: Forbidden request: XXXX access to /file_metadata/plugins [find] at
> :133 Could not retrieve file metadata for puppet://puppetmaster/plugins:
> Error 403 on SERVER: Forbidden request:
> XXXX access to /file_metadata/plugins [find] at :133
> Info: Loading facts in
> /etc/puppet/modules/classify/lib/facter/system_role.rb
> Info: Loading facts in
> /etc/puppet/modules/classifiy/lib/facter/system_role.rb
> Info: Loading facts in
> /etc/puppet/modules/postgresql/lib/facter/postgres_default_version.rb
> Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb
> Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb
> Info: Loading facts in
> /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
> Info: Loading facts in
> /etc/puppet/modules/concat/lib/facter/concat_basedir.rb
> Info: Loading facts in
> /var/lib/puppet/lib/facter/postgres_default_version.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/system_role.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
