> Apologies for taking so long to get back about this, more pressing > matters took precedence. So, back on this, I think I must be doing > something really daft then, as I've made that change to my auth.conf > file and still get the same forbidden errors.
Indeed, I was doing something really daft. I'd added the changes to the bottom of auth.conf. 2 things were wrong in doing that: a) Adding anything below the 'path /' stanza isn't going to be picked up, I don't think (I noticed this when trying to get 'puppet kick' to work and got similar 403 errors when trying to access /run) b) There's already a 'path ~ ^/catalog/([^/]+)$' stanza in the default auth.conf file, so the settings there were being hit before my new stanza at the bottom of the file. By adding 'allow master.domain.com' and 'auth any' to the default stanza the 403s have disappeared. Now though, is my next problem. puppet-load works fine with concurrency set to 1. As soon as I increase that number though, I get the following error: undefined method `>' for ["2.7.14", "2.7.14"]:Array on node master.domain.com Is this an issue with my Ruby version (1.8.7.299-7), or is it a bug in the code? Cheers, Matt. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
