[Puppet Users] Re: Error 400 on SERVER: Permission denied - /var/lib/puppet/yaml/facts/server.example.com.yaml
On Jan 6, 4:04 pm, David Chin wrote: > Hello, > > I'm new to puppet, and am working through the Pro Puppet book > (Turnbull & McCune). After a bit of struggling, I managed to get > puppet + passenger + apache mostly working: a simple connect to the > server on https port 8140 gives "The environment must be purely > alphanumeric, not ''" > > Here is what I have running: > - RedHat Enterprise Linux 6 > - httpd 2.2.15-15.el6 > - puppet 2.7.9-1.el6 > - puppet-server 2.7.9-1.el6 > - mod_passenger 3.0.11-1.el6 > - rubygem-rack 1.1.0-2.el6 > - facter 1.6.4-1.el6 > I just ran into this with Puppet Enterprise on CentOS 6.2. This may be related to a known bug, but it seems slightly different: http://projects.puppetlabs.com/issues/11807 Maybe someone with more experience can offer their view. ~David Klann -- 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.
Re: [Puppet Users] problem with rack versions and puppet-dashboard
On Tue, 24 May 2011 10:40:03 -0500, you said: > I get this error > can't activate rack (~> 1.0.1), already activated rack-1.2.2 > > It appears that puppet-dashboard uses rack 1.0.1 but passenger 3.0.7 > needs to use rack1.2.2 > > Is there a way around this or make dashboard use rack 1.2.2? > Don't know if it's the "supported" way to do it, but I simply removed the "embedded" version of rack that ships with puppet-dashboard: cd git clone git://github.com/puppetlabs/puppet-dashboard.git rm -r vendor/gems/rack-1.0.1 sed -i -e 's,~> 1.0.1,~> 1.2.2,' vendor/rails/actionpack/lib/action_controller.rb cp /config.ru . sudo service httpd start (or however you start apache/nginx). Is there a recommended way to resolve this conflict? ~David Klann signature.asc Description: PGP signature
[Puppet Users] Puppet 2.6.8 -- Thanks
I'm not sure exactly which bug was fixed, but 2.6.8 has corrected the operation of my "users" module, which I've been struggling with for several days. I'm new to puppet, and I've been trying to get a small installation running. I was having trouble with SSH authorized_keys. The puppet agent running on a remote server was trying to create an "authorized_keys" file for a user different than the one specified in the manifest. I upgraded to 2.6.8 and restarted the agent daemon and all seems to be working as I expect. It may have simply been the daemon restart that corrected the behaviour, but in any event it is now working as I would expect. Thanks for all your on-going work to improve and extend Puppet! ~dklann signature.asc Description: PGP signature
