On Fri, Aug 5, 2011 at 11:24 AM, Claude <claude.duroc...@gmail.com> wrote:

> I finally made it working by modifying auth.conf like this :
>
> path /facts
> auth any
> method find, search
> allow *
>
> path /file_bucket_file/md5
> auth no
> method find, save
> allow *
>

That's going to allow everyone, and you really should lock it down to just
the dashboard itself.


>
> On 5 août, 09:31, Nigel Kersten <ni...@puppetlabs.com> wrote:
> > On Fri, Aug 5, 2011 at 5:14 AM, Claude <claude.duroc...@gmail.com>
> wrote:
> > > Here's what the log shows :
> >
> > > Processing FilesController#show (for 10.10.10.1 at 2011-08-05
> > > 08:11:17) [GET]
> > >  Parameters: {"action"=>"show", "controller"=>"files",
> > > "file"=>"70c1c6de6d4b1a02ec32b463e4d255b0"}
> >
> > > Net::HTTPServerException (403 "Forbidden"):
> >
> > Ahah. You're missing this step.
> >
> > http://docs.puppetlabs.com/dashboard/manual/1.2/configuring.html
> >
> > Once the puppet master is properly configured with a database-backed
> > inventory, edit your puppet master’s
> > auth.conf<http://docs.puppetlabs.com/guides/rest_auth_conf.html> file
> > to grant Dashboard find and search access to /facts:
> >
> > path /facts
> > auth yes
> > method find, search
> > allow dashboard
> >
> > (change the allow line to reference your certificate identity you
> generated)
> >
> >  /usr/lib64/ruby/1.8/net/http.rb:2105:in `error!'
> >
> >
> >
> > >  lib/puppet_https.rb:34:in `get'
> > >  app/controllers/files_controller.rb:23:in `show'
> > >  sass (3.1.2) [v] rails/./lib/sass/plugin/rack.rb:54:in `call'
> > >  passenger (3.0.7) lib/phusion_passenger/rack/request_handler.rb:
> > > 96:in `process_request'
> > >  passenger (3.0.7) lib/phusion_passenger/abstract_request_handler.rb:
> > > 513:in `accept_and_process_next_request'
> > >  passenger (3.0.7) lib/phusion_passenger/abstract_request_handler.rb:
> > > 274:in `main_loop'
> > >  passenger (3.0.7) lib/phusion_passenger/classic_rails/
> > > application_spawner.rb:321:in `start_request_handler'
> > >  passenger (3.0.7) lib/phusion_passenger/classic_rails/
> > > application_spawner.rb:275:in `send'
> > >  passenger (3.0.7) lib/phusion_passenger/classic_rails/
> > > application_spawner.rb:275:in `handle_spawn_application'
> > >  passenger (3.0.7) lib/phusion_passenger/utils.rb:479:in `safe_fork'
> > >  passenger (3.0.7) lib/phusion_passenger/classic_rails/
> > > application_spawner.rb:270:in `handle_spawn_application'
> > >  passenger (3.0.7) lib/phusion_passenger/abstract_server.rb:357:in
> > > `__send__'
> > >  passenger (3.0.7) lib/phusion_passenger/abstract_server.rb:357:in
> > > `server_main_loop'
> > >  passenger (3.0.7) lib/phusion_passenger/abstract_server.rb:206:in
> > > `start_synchronously'
> > >  passenger (3.0.7) lib/phusion_passenger/abstract_server.rb:180:in
> > > `start'
> > >  passenger (3.0.7) lib/phusion_passenger/classic_rails/
> > > application_spawner.rb:149:in `start'
> > >  passenger (3.0.7) lib/phusion_passenger/spawn_manager.rb:219:in
> > > `spawn_rails_application'
> > >  passenger (3.0.7) lib/phusion_passenger/
> > > abstract_server_collection.rb:132:in `lookup_or_add'
> > >  passenger (3.0.7) lib/phusion_passenger/spawn_manager.rb:214:in
> > > `spawn_rails_application'
> > >  passenger (3.0.7) lib/phusion_passenger/
> > > abstract_server_collection.rb:82:in `synchronize'
> > >  passenger (3.0.7) lib/phusion_passenger/
> > > abstract_server_collection.rb:79:in `synchronize'
> > >  passenger (3.0.7) lib/phusion_passenger/spawn_manager.rb:213:in
> > > `spawn_rails_application'
> > >  passenger (3.0.7) lib/phusion_passenger/spawn_manager.rb:132:in
> > > `spawn_application'
> > >  passenger (3.0.7) lib/phusion_passenger/spawn_manager.rb:275:in
> > > `handle_spawn_application'
> > >  passenger (3.0.7) lib/phusion_passenger/abstract_server.rb:357:in
> > > `__send__'
> > >  passenger (3.0.7) lib/phusion_passenger/abstract_server.rb:357:in
> > > `server_main_loop'
> > >  passenger (3.0.7) lib/phusion_passenger/abstract_server.rb:206:in
> > > `start_synchronously'
> > >  passenger (3.0.7) helper-scripts/passenger-spawn-server:99
> >
> > > The Dashboard and the master are running under passenger.
> >
> > > On 5 août, 01:46, Nigel Kersten <ni...@puppetlabs.com> wrote:
> > > > On Thu, Aug 4, 2011 at 8:14 PM, Claude <claude.duroc...@gmail.com>
> > > wrote:
> > > > > Using Puppet-DashBoard 1.2Rc3 with Puppet master 2.7.1 on the same
> > > > > server.
> >
> > > > > When trying to display bucketed file in the Dashboard, I get the
> > > > > following error message (after clicking on the link '{md5}...) :
> >
> > > > > We're sorry, but something went wrong. We've been notified about
> this
> > > > > issue and we'll take a look at it shortly.
> >
> > > > Ugh. I hate that error message.
> > >https://projects.puppetlabs.com/issues/8796
> >
> > > > Have a look at log/production.log and see what's going on.
> >
> > > > Can you try it against a puppet master in debug mode?
> >
> > > > > Here's how I did the config :
> >
> > > > > -puppet cert generate dashboard
> >
> > > > > -Edit config/settings.yml :
> > > > > cn_name: 'dashboard'
> > > > > ca_crl_path: '/var/lib/puppet/ssl/ca/ca_crl.pem'
> > > > > ca_certificate_path: '/var/lib/puppet/ssl/ca/ca_crt.pem'
> > > > > certificate_path: '/var/lib/puppet/ssl/certs/dashboard.pem'
> > > > > private_key_path: '/var/lib/puppet/ssl/private_keys/dashboard.pem'
> > > > > public_key_path: '/var/lib/puppet/ssl/public_keys/dashboard.pem'
> >
> > > > > -Edit site.pp :
> > > > > filebucket { "main":
> > > > >  server => "puppet.myorg.internal",
> > > > >  path => false,
> > > > > }
> > > > > File { backup => "main" }
> >
> > > > Try adding: path => "false"  ?
> >
> > > > > -Restart PuppetDashboard
> >
> > > > > -Generate a file update on a node.
> >
> > > > > I've located bucketed files on the master so the problem seems to
> be
> > > > > between the dashboard and the master. How do I debug this?
> >
> > > > > --
> > > > > 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+unsubscr...@googlegroups.com.
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/puppet-users?hl=en.
> >
> > > > --
> > > > Nigel Kersten
> > > > Product Manager, Puppet Labs
> >
> > > > *Join us for **PuppetConf *
> > > > <http://www.bit.ly/puppetconfsig>
> > > > Sept 22/23 Portland, Oregon, USA.
> > > > *
> > > > *
> >
> > > --
> > > 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+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/puppet-users?hl=en.
> >
> > --
> > Nigel Kersten
> > Product Manager, Puppet Labs
> >
> > *Join us for **PuppetConf *
> > <http://www.bit.ly/puppetconfsig>
> > Sept 22/23 Portland, Oregon, USA.
> > *
> > *
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
Nigel Kersten
Product Manager, Puppet Labs

*Join us for **PuppetConf *
<http://www.bit.ly/puppetconfsig>
Sept 22/23 Portland, Oregon, USA.
*
*

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to