I'll give it ago in the morning, fingers crossed :-) On Aug 23, 5:26 pm, Patrick <[email protected]> wrote: > On Aug 23, 2010, at 2:10 AM, matonb wrote: > > > Hi Patrick, > > > The client and server are both version 2.6.0 > > I am running puppetrun as root on the puppet master server. > > And yes, a test run completes successfully.... > > > Thanks for your help, > > Brett > > Puppet.conf had it's section names changed in 2.6.0 (see below). I'm > wondering if the namespaceauth.conf could have had it's section names changed > in 2.6.0. You might want to add a section for "kick" and test it. This is > just a shot in the dark though because I'm running out of ideas. > > On Jul 18, 2010, at 8:31 PM, James Turnbull wrote: > > > > > Single Binary > > > Puppet is now available as a single binary with sub-arguments for the > > functions previously provided by the seperate binaries (the existing > > binaries remain for backwards compatibility). This includes renaming > > several Puppet functions to better fit an overall model. > > > List of binary changes > > > puppetmasterd –> puppet master > > puppetd –> puppet agent > > puppet –> puppet apply > > puppetca –> puppet cert > > ralsh –> puppet resource > > puppetrun –> puppet kick > > puppetqd –> puppet queue > > filebucket –> puppet filebucket > > puppetdoc –> puppet doc > > pi –> puppet describe > > > This also results in a change in the puppet.conf configuration file. > > The sections, previously things like [puppetd], now should be renamed to > > match the new binary names. So [puppetd] becomes [agent]. You will be > > prompted to do this when you start Puppet with a log message for each > > section that needs to be renamed. This is merely a warning - existing > > configuration file will work unchanged. > > > On Aug 23, 9:31 am, Patrick <[email protected]> wrote: > >> Here are a couple more things: > >> What version is your client? > >> What version is your server? > >> Make sure you're running puppetrun as root. > >> Make sure that running "puppetd --test --verbose" as root on the client > >> actually works. > > >> On Aug 23, 2010, at 12:53 AM, matonb wrote: > > >>> Didn't help unfortunaltely. Still getting the same error(s)! > > >>> On Aug 20, 4:07 pm, Patrick <[email protected]> wrote: > >>>> On Aug 20, 2010, at 6:05 AM, matonb wrote: > > >>>>> I'm trying to push client configurations from the puppetmaster instead > >>>>> of having scheduled runs on each client. > >>>>> I think puppetrun is what I'm after but I can't get it to work! > > >>>> Try replacing the line in puppetrunner with "allow *" and work back from > >>>> there. If that doesn't work, try replacing every line with "allow *". > > > -- > > 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 > > athttp://groups.google.com/group/puppet-users?hl=en.
-- 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.
