Hello a newbie here. The situation is that: 2 machine one master one client Puppet 0.24.5 This my configuration: Client: /etc/puppet/puppetd.conf [puppetd] server = Asus-Vista-Box logdir = /var/log/puppet vardir = /var/lib/puppet rundir = /var/run master /etc/puppet/manifests/classes/sudo.pp class sudo { file { "/etc/sudoers": owner => "root", group => "root", mode => 440, } } /etc/puppet/manifests/site.pp import "classes/*" node default { include sudo } I make puppetca --list debian.lokku.net and puppetca --sign debian.lokku.net Signed debian.lokku.net But even I restart both client and master 100 times if I do: ls -l /etc/sudoers -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers What I did wrong? --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi, What happens when you run ''puppetd --test'' on the client? Best Julian. 2009/10/20 Renato Tuveri <renato.tuveri@gmail.com>:> > Hello a newbie here. > > The situation is that: > > 2 machine one master one client > Puppet 0.24.5 > > This my configuration: > > Client: > > /etc/puppet/puppetd.conf > > [puppetd] > server = Asus-Vista-Box > logdir = /var/log/puppet > vardir = /var/lib/puppet > rundir = /var/run > > > master > > /etc/puppet/manifests/classes/sudo.pp > > class sudo { > file { "/etc/sudoers": > owner => "root", > group => "root", > mode => 440, > } > } > > > > /etc/puppet/manifests/site.pp > > import "classes/*" > > node default { > include sudo > } > > > I make > > puppetca --list > debian.lokku.net > > and > > puppetca --sign debian.lokku.net > Signed debian.lokku.net > > But even I restart both client and master 100 times if I do: > > ls -l /etc/sudoers > -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers > > What I did wrong? > > > >-- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
If you run puppetd with the "--test" and "--debug" options you should be able to see that resource being applied (Or not). It could be that an error in one of these files will be obvious with the output from running it manually with these options. On Oct 20, 11:24 am, Renato Tuveri <renato.tuv...@gmail.com> wrote:> Hello a newbie here. > > The situation is that: > > 2 machine one master one client > Puppet 0.24.5 > > This my configuration: > > Client: > > /etc/puppet/puppetd.conf > > [puppetd] > server = Asus-Vista-Box > logdir = /var/log/puppet > vardir = /var/lib/puppet > rundir = /var/run > > master > > /etc/puppet/manifests/classes/sudo.pp > > class sudo { > file { "/etc/sudoers": > owner => "root", > group => "root", > mode => 440, > } > > } > > /etc/puppet/manifests/site.pp > > import "classes/*" > > node default { > include sudo > > } > > I make > > puppetca --list > debian.lokku.net > > and > > puppetca --sign debian.lokku.net > Signed debian.lokku.net > > But even I restart both client and master 100 times if I do: > > ls -l /etc/sudoers > -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers > > What I did wrong?--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi, thanks for the reply. reno# puppetd --test warning: Certificate validation failed; considering using the certname configuration option err: Could not retrieve catalog: Certificates were not trusted: hostname was not match with the server certificate warning: Not using cache on failed catalog On Oct 20, 10:39 pm, nothings_absolute <soren.mor...@gmail.com> wrote:> If you run puppetd with the "--test" and "--debug" options you > should be able to see that resource being applied (Or not). It could > be that an error in one of these files will be obvious with the output > from running it manually with these options. > > On Oct 20, 11:24 am, Renato Tuveri <renato.tuv...@gmail.com> wrote: > > > Hello a newbie here. > > > The situation is that: > > > 2 machine one master one client > > Puppet 0.24.5 > > > This my configuration: > > > Client: > > > /etc/puppet/puppetd.conf > > > [puppetd] > > server = Asus-Vista-Box > > logdir = /var/log/puppet > > vardir = /var/lib/puppet > > rundir = /var/run > > > master > > > /etc/puppet/manifests/classes/sudo.pp > > > class sudo { > > file { "/etc/sudoers": > > owner => "root", > > group => "root", > > mode => 440, > > } > > > } > > > /etc/puppet/manifests/site.pp > > > import "classes/*" > > > node default { > > include sudo > > > } > > > I make > > > puppetca --list > > debian.lokku.net > > > and > > > puppetca --sign debian.lokku.net > > Signed debian.lokku.net > > > But even I restart both client and master 100 times if I do: > > > ls -l /etc/sudoers > > -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers > > > What I did wrong?--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi Reno, in puppet.conf on the client you have: server = Asus-Vista-Box this should be an host you can find (via hosts or dns) AND the hostname of your server, otherwise you run into certificates problems. I suggest to use "puppet" as servername (the default) or change things in the followring way: - Take the hostname of the server - Make it reacheable from the client (eventually editind /etc/hosts) - Remove the old client certificates. On the client: rm -rf /var/lib/ puppet/ssl - Clean the client certificate on the server: puppetca --clean debian.lokku.net - Relunch puppetd -t on the client, sign the new certificate on the server, relaunch puppetd -t Good luck Al On Oct 21, 12:21 pm, Reno <renato.tuv...@gmail.com> wrote:> Hi, thanks for the reply. > > reno# puppetd --test > warning: Certificate validation failed; considering using the certname > configuration option > err: Could not retrieve catalog: Certificates were not trusted: > hostname was not match with the server certificate > warning: Not using cache on failed catalog > > On Oct 20, 10:39 pm, nothings_absolute <soren.mor...@gmail.com> wrote: > > > If you run puppetd with the "--test" and "--debug" options you > > should be able to see that resource being applied (Or not). It could > > be that an error in one of these files will be obvious with the output > > from running it manually with these options. > > > On Oct 20, 11:24 am, Renato Tuveri <renato.tuv...@gmail.com> wrote: > > > > Hello a newbie here. > > > > The situation is that: > > > > 2 machine one master one client > > > Puppet 0.24.5 > > > > This my configuration: > > > > Client: > > > > /etc/puppet/puppetd.conf > > > > [puppetd] > > > server = Asus-Vista-Box > > > logdir = /var/log/puppet > > > vardir = /var/lib/puppet > > > rundir = /var/run > > > > master > > > > /etc/puppet/manifests/classes/sudo.pp > > > > class sudo { > > > file { "/etc/sudoers": > > > owner => "root", > > > group => "root", > > > mode => 440, > > > } > > > > } > > > > /etc/puppet/manifests/site.pp > > > > import "classes/*" > > > > node default { > > > include sudo > > > > } > > > > I make > > > > puppetca --list > > > debian.lokku.net > > > > and > > > > puppetca --sign debian.lokku.net > > > Signed debian.lokku.net > > > > But even I restart both client and master 100 times if I do: > > > > ls -l /etc/sudoers > > > -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers > > > > What I did wrong?--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi, I really do not get it. the host name of the server is Asus-Vista-Box This is my /etc/host in the server 127.0.0.1 localhost 127.0.1.1 Asus-Vista-Box.lokku.net Asus-Vista-Box and this in the clent: 127.0.0.1 localhost 127.0.1.1 puppetclient.lokku.net puppetclient 192.168.56.1 Asus-Vista-Box what is wrong? On Oct 21, 11:53 am, "Al @ Lab42" <lab42...@gmail.com> wrote:> Hi Reno, > in puppet.conf on the client you have: > server = Asus-Vista-Box > this should be an host you can find (via hosts or dns) AND the > hostname of your server, otherwise you run into certificates problems. > > I suggest to use "puppet" as servername (the default) or change things > in the followring way: > - Take the hostname of the server > - Make it reacheable from the client (eventually editind /etc/hosts) > - Remove the old client certificates. On the client: rm -rf /var/lib/ > puppet/ssl > - Clean the client certificate on the server: puppetca --clean > debian.lokku.net > - Relunch puppetd -t on the client, sign the new certificate on the > server, relaunch puppetd -t > > Good luck > Al > > On Oct 21, 12:21 pm, Reno <renato.tuv...@gmail.com> wrote: > > > Hi, thanks for the reply. > > > reno# puppetd --test > > warning: Certificate validation failed; considering using the certname > > configuration option > > err: Could not retrieve catalog: Certificates were not trusted: > > hostname was not match with the server certificate > > warning: Not using cache on failed catalog > > > On Oct 20, 10:39 pm, nothings_absolute <soren.mor...@gmail.com> wrote: > > > > If you run puppetd with the "--test" and "--debug" options you > > > should be able to see that resource being applied (Or not). It could > > > be that an error in one of these files will be obvious with the output > > > from running it manually with these options. > > > > On Oct 20, 11:24 am, Renato Tuveri <renato.tuv...@gmail.com> wrote: > > > > > Hello a newbie here. > > > > > The situation is that: > > > > > 2 machine one master one client > > > > Puppet 0.24.5 > > > > > This my configuration: > > > > > Client: > > > > > /etc/puppet/puppetd.conf > > > > > [puppetd] > > > > server = Asus-Vista-Box > > > > logdir = /var/log/puppet > > > > vardir = /var/lib/puppet > > > > rundir = /var/run > > > > > master > > > > > /etc/puppet/manifests/classes/sudo.pp > > > > > class sudo { > > > > file { "/etc/sudoers": > > > > owner => "root", > > > > group => "root", > > > > mode => 440, > > > > } > > > > > } > > > > > /etc/puppet/manifests/site.pp > > > > > import "classes/*" > > > > > node default { > > > > include sudo > > > > > } > > > > > I make > > > > > puppetca --list > > > > debian.lokku.net > > > > > and > > > > > puppetca --sign debian.lokku.net > > > > Signed debian.lokku.net > > > > > But even I restart both client and master 100 times if I do: > > > > > ls -l /etc/sudoers > > > > -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers > > > > > What I did wrong?--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
ok I fix that just putting Asus-Vista-Box.lokku.net instead of Asus- Vista-Box as client config but: puppetd --test info: Retrieving plugins err: Could not retrieve plugins: execution expired but no rules are apply On Oct 21, 1:07 pm, Reno <renato.tuv...@gmail.com> wrote:> Hi, > I really do not get it. > the host name of the server is Asus-Vista-Box > > This is my /etc/host in the server > > 127.0.0.1 localhost > 127.0.1.1 Asus-Vista-Box.lokku.net Asus-Vista-Box > > and this in the clent: > > 127.0.0.1 localhost > 127.0.1.1 puppetclient.lokku.net puppetclient > 192.168.56.1 Asus-Vista-Box > > what is wrong? > > On Oct 21, 11:53 am, "Al @ Lab42" <lab42...@gmail.com> wrote: > > > Hi Reno, > > in puppet.conf on the client you have: > > server = Asus-Vista-Box > > this should be an host you can find (via hosts or dns) AND the > > hostname of your server, otherwise you run into certificates problems. > > > I suggest to use "puppet" as servername (the default) or change things > > in the followring way: > > - Take the hostname of the server > > - Make it reacheable from the client (eventually editind /etc/hosts) > > - Remove the old client certificates. On the client: rm -rf /var/lib/ > > puppet/ssl > > - Clean the client certificate on the server: puppetca --clean > > debian.lokku.net > > - Relunch puppetd -t on the client, sign the new certificate on the > > server, relaunch puppetd -t > > > Good luck > > Al > > > On Oct 21, 12:21 pm, Reno <renato.tuv...@gmail.com> wrote: > > > > Hi, thanks for the reply. > > > > reno# puppetd --test > > > warning: Certificate validation failed; considering using the certname > > > configuration option > > > err: Could not retrieve catalog: Certificates were not trusted: > > > hostname was not match with the server certificate > > > warning: Not using cache on failed catalog > > > > On Oct 20, 10:39 pm, nothings_absolute <soren.mor...@gmail.com> wrote: > > > > > If you run puppetd with the "--test" and "--debug" options you > > > > should be able to see that resource being applied (Or not). It could > > > > be that an error in one of these files will be obvious with the output > > > > from running it manually with these options. > > > > > On Oct 20, 11:24 am, Renato Tuveri <renato.tuv...@gmail.com> wrote: > > > > > > Hello a newbie here. > > > > > > The situation is that: > > > > > > 2 machine one master one client > > > > > Puppet 0.24.5 > > > > > > This my configuration: > > > > > > Client: > > > > > > /etc/puppet/puppetd.conf > > > > > > [puppetd] > > > > > server = Asus-Vista-Box > > > > > logdir = /var/log/puppet > > > > > vardir = /var/lib/puppet > > > > > rundir = /var/run > > > > > > master > > > > > > /etc/puppet/manifests/classes/sudo.pp > > > > > > class sudo { > > > > > file { "/etc/sudoers": > > > > > owner => "root", > > > > > group => "root", > > > > > mode => 440, > > > > > } > > > > > > } > > > > > > /etc/puppet/manifests/site.pp > > > > > > import "classes/*" > > > > > > node default { > > > > > include sudo > > > > > > } > > > > > > I make > > > > > > puppetca --list > > > > > debian.lokku.net > > > > > > and > > > > > > puppetca --sign debian.lokku.net > > > > > Signed debian.lokku.net > > > > > > But even I restart both client and master 100 times if I do: > > > > > > ls -l /etc/sudoers > > > > > -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers > > > > > > What I did wrong?--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Ok now, seems that all is working....almost.....but: class aptsetup { file { "/etc/apt/sources.list": owner => root, group => root, mode => 644, source => "puppet://asus-vista-box.lokku.net/files/etc/ apt/sources.list } } exec { subscribe-echo: command => "/usr/bin/apt-get -q -q update", logoutput => false, refreshonly => true, subscribe => file["/etc/apt/sources.list"] } err: Could not retrieve catalog: Could not parse for environment production: Could not match ''/usr/bin/apt-get'' at /etc/puppet/ manifests/classes/source.list.pp:7 On Oct 21, 2:44 pm, Reno <renato.tuv...@gmail.com> wrote:> ok I fix that just putting Asus-Vista-Box.lokku.net instead of Asus- > Vista-Box as client config but: > > puppetd --test > info: Retrieving plugins > err: Could not retrieve plugins: execution expired > > but no rules are apply > > On Oct 21, 1:07 pm, Reno <renato.tuv...@gmail.com> wrote: > > > Hi, > > I really do not get it. > > the host name of the server is Asus-Vista-Box > > > This is my /etc/host in the server > > > 127.0.0.1 localhost > > 127.0.1.1 Asus-Vista-Box.lokku.net Asus-Vista-Box > > > and this in the clent: > > > 127.0.0.1 localhost > > 127.0.1.1 puppetclient.lokku.net puppetclient > > 192.168.56.1 Asus-Vista-Box > > > what is wrong? > > > On Oct 21, 11:53 am, "Al @ Lab42" <lab42...@gmail.com> wrote: > > > > Hi Reno, > > > in puppet.conf on the client you have: > > > server = Asus-Vista-Box > > > this should be an host you can find (via hosts or dns) AND the > > > hostname of your server, otherwise you run into certificates problems. > > > > I suggest to use "puppet" as servername (the default) or change things > > > in the followring way: > > > - Take the hostname of the server > > > - Make it reacheable from the client (eventually editind /etc/hosts) > > > - Remove the old client certificates. On the client: rm -rf /var/lib/ > > > puppet/ssl > > > - Clean the client certificate on the server: puppetca --clean > > > debian.lokku.net > > > - Relunch puppetd -t on the client, sign the new certificate on the > > > server, relaunch puppetd -t > > > > Good luck > > > Al > > > > On Oct 21, 12:21 pm, Reno <renato.tuv...@gmail.com> wrote: > > > > > Hi, thanks for the reply. > > > > > reno# puppetd --test > > > > warning: Certificate validation failed; considering using the certname > > > > configuration option > > > > err: Could not retrieve catalog: Certificates were not trusted: > > > > hostname was not match with the server certificate > > > > warning: Not using cache on failed catalog > > > > > On Oct 20, 10:39 pm, nothings_absolute <soren.mor...@gmail.com> wrote: > > > > > > If you run puppetd with the "--test" and "--debug" options you > > > > > should be able to see that resource being applied (Or not). It could > > > > > be that an error in one of these files will be obvious with the output > > > > > from running it manually with these options. > > > > > > On Oct 20, 11:24 am, Renato Tuveri <renato.tuv...@gmail.com> wrote: > > > > > > > Hello a newbie here. > > > > > > > The situation is that: > > > > > > > 2 machine one master one client > > > > > > Puppet 0.24.5 > > > > > > > This my configuration: > > > > > > > Client: > > > > > > > /etc/puppet/puppetd.conf > > > > > > > [puppetd] > > > > > > server = Asus-Vista-Box > > > > > > logdir = /var/log/puppet > > > > > > vardir = /var/lib/puppet > > > > > > rundir = /var/run > > > > > > > master > > > > > > > /etc/puppet/manifests/classes/sudo.pp > > > > > > > class sudo { > > > > > > file { "/etc/sudoers": > > > > > > owner => "root", > > > > > > group => "root", > > > > > > mode => 440, > > > > > > } > > > > > > > } > > > > > > > /etc/puppet/manifests/site.pp > > > > > > > import "classes/*" > > > > > > > node default { > > > > > > include sudo > > > > > > > } > > > > > > > I make > > > > > > > puppetca --list > > > > > > debian.lokku.net > > > > > > > and > > > > > > > puppetca --sign debian.lokku.net > > > > > > Signed debian.lokku.net > > > > > > > But even I restart both client and master 100 times if I do: > > > > > > > ls -l /etc/sudoers > > > > > > -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers > > > > > > > What I did wrong?--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
It looks like you are missing the closing " at the end of the source line. -Adam On Oct 21, 2009, at 7:27 AM, Reno <renato.tuveri@gmail.com> wrote:> > Ok now, seems that all is working....almost.....but: > > > class aptsetup { > > file { "/etc/apt/sources.list": > owner => root, > group => root, > mode => 644, > source => "puppet://asus-vista-box.lokku.net/files/etc/ > apt/sources.list > } > } > exec { subscribe-echo: > command => "/usr/bin/apt-get -q -q update", > logoutput => false, > refreshonly => true, > subscribe => file["/etc/apt/sources.list"] > } > > > err: Could not retrieve catalog: Could not parse for environment > production: Could not match ''/usr/bin/apt-get'' at /etc/puppet/ > manifests/classes/source.list.pp:7 > > > > On Oct 21, 2:44 pm, Reno <renato.tuv...@gmail.com> wrote: >> ok I fix that just putting Asus-Vista-Box.lokku.net instead of >> Asus- >> Vista-Box as client config but: >> >> puppetd --test >> info: Retrieving plugins >> err: Could not retrieve plugins: execution expired >> >> but no rules are apply >> >> On Oct 21, 1:07 pm, Reno <renato.tuv...@gmail.com> wrote: >> >>> Hi, >>> I really do not get it. >>> the host name of the server is Asus-Vista-Box >> >>> This is my /etc/host in the server >> >>> 127.0.0.1 localhost >>> 127.0.1.1 Asus-Vista-Box.lokku.net Asus-Vista-Box >> >>> and this in the clent: >> >>> 127.0.0.1 localhost >>> 127.0.1.1 puppetclient.lokku.net puppetclient >>> 192.168.56.1 Asus-Vista-Box >> >>> what is wrong? >> >>> On Oct 21, 11:53 am, "Al @ Lab42" <lab42...@gmail.com> wrote: >> >>>> Hi Reno, >>>> in puppet.conf on the client you have: >>>> server = Asus-Vista-Box >>>> this should be an host you can find (via hosts or dns) AND the >>>> hostname of your server, otherwise you run into certificates >>>> problems. >> >>>> I suggest to use "puppet" as servername (the default) or change >>>> things >>>> in the followring way: >>>> - Take the hostname of the server >>>> - Make it reacheable from the client (eventually editind /etc/ >>>> hosts) >>>> - Remove the old client certificates. On the client: rm -rf /var/ >>>> lib/ >>>> puppet/ssl >>>> - Clean the client certificate on the server: puppetca --clean >>>> debian.lokku.net >>>> - Relunch puppetd -t on the client, sign the new certificate on the >>>> server, relaunch puppetd -t >> >>>> Good luck >>>> Al >> >>>> On Oct 21, 12:21 pm, Reno <renato.tuv...@gmail.com> wrote: >> >>>>> Hi, thanks for the reply. >> >>>>> reno# puppetd --test >>>>> warning: Certificate validation failed; considering using the >>>>> certname >>>>> configuration option >>>>> err: Could not retrieve catalog: Certificates were not trusted: >>>>> hostname was not match with the server certificate >>>>> warning: Not using cache on failed catalog >> >>>>> On Oct 20, 10:39 pm, nothings_absolute <soren.mor...@gmail.com> >>>>> wrote: >> >>>>>> If you run puppetd with the "--test" and "--debug" options you >>>>>> should be able to see that resource being applied (Or not). It >>>>>> could >>>>>> be that an error in one of these files will be obvious with the >>>>>> output >>>>>> from running it manually with these options. >> >>>>>> On Oct 20, 11:24 am, Renato Tuveri <renato.tuv...@gmail.com> >>>>>> wrote: >> >>>>>>> Hello a newbie here. >> >>>>>>> The situation is that: >> >>>>>>> 2 machine one master one client >>>>>>> Puppet 0.24.5 >> >>>>>>> This my configuration: >> >>>>>>> Client: >> >>>>>>> /etc/puppet/puppetd.conf >> >>>>>>> [puppetd] >>>>>>> server = Asus-Vista-Box >>>>>>> logdir = /var/log/puppet >>>>>>> vardir = /var/lib/puppet >>>>>>> rundir = /var/run >> >>>>>>> master >> >>>>>>> /etc/puppet/manifests/classes/sudo.pp >> >>>>>>> class sudo { >>>>>>> file { "/etc/sudoers": >>>>>>> owner => "root", >>>>>>> group => "root", >>>>>>> mode => 440, >>>>>>> } >> >>>>>>> } >> >>>>>>> /etc/puppet/manifests/site.pp >> >>>>>>> import "classes/*" >> >>>>>>> node default { >>>>>>> include sudo >> >>>>>>> } >> >>>>>>> I make >> >>>>>>> puppetca --list >>>>>>> debian.lokku.net >> >>>>>>> and >> >>>>>>> puppetca --sign debian.lokku.net >>>>>>> Signed debian.lokku.net >> >>>>>>> But even I restart both client and master 100 times if I do: >> >>>>>>> ls -l /etc/sudoers >>>>>>> -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers >> >>>>>>> What I did wrong? > >--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
sorry just a copy and past error ;-) btw I found the problem, stupid like the previsious one...I forgot to copy the source.list in /etc/ puppet/files :-/ thnks for the repply btw ;-) On Oct 21, 3:32 pm, Adam Crews <adam.cr...@gmail.com> wrote:> It looks like you are missing the closing " at the end of the source > line. > > -Adam > > On Oct 21, 2009, at 7:27 AM, Reno <renato.tuv...@gmail.com> wrote: > > > > > Ok now, seems that all is working....almost.....but: > > > class aptsetup { > > > file { "/etc/apt/sources.list": > > owner => root, > > group => root, > > mode => 644, > > source => "puppet://asus-vista-box.lokku.net/files/etc/ > > apt/sources.list > > } > > } > > exec { subscribe-echo: > > command => "/usr/bin/apt-get -q -q update", > > logoutput => false, > > refreshonly => true, > > subscribe => file["/etc/apt/sources.list"] > > } > > > err: Could not retrieve catalog: Could not parse for environment > > production: Could not match ''/usr/bin/apt-get'' at /etc/puppet/ > > manifests/classes/source.list.pp:7 > > > On Oct 21, 2:44 pm, Reno <renato.tuv...@gmail.com> wrote: > >> ok I fix that just putting Asus-Vista-Box.lokku.net instead of > >> Asus- > >> Vista-Box as client config but: > > >> puppetd --test > >> info: Retrieving plugins > >> err: Could not retrieve plugins: execution expired > > >> but no rules are apply > > >> On Oct 21, 1:07 pm, Reno <renato.tuv...@gmail.com> wrote: > > >>> Hi, > >>> I really do not get it. > >>> the host name of the server is Asus-Vista-Box > > >>> This is my /etc/host in the server > > >>> 127.0.0.1 localhost > >>> 127.0.1.1 Asus-Vista-Box.lokku.net Asus-Vista-Box > > >>> and this in the clent: > > >>> 127.0.0.1 localhost > >>> 127.0.1.1 puppetclient.lokku.net puppetclient > >>> 192.168.56.1 Asus-Vista-Box > > >>> what is wrong? > > >>> On Oct 21, 11:53 am, "Al @ Lab42" <lab42...@gmail.com> wrote: > > >>>> Hi Reno, > >>>> in puppet.conf on the client you have: > >>>> server = Asus-Vista-Box > >>>> this should be an host you can find (via hosts or dns) AND the > >>>> hostname of your server, otherwise you run into certificates > >>>> problems. > > >>>> I suggest to use "puppet" as servername (the default) or change > >>>> things > >>>> in the followring way: > >>>> - Take the hostname of the server > >>>> - Make it reacheable from the client (eventually editind /etc/ > >>>> hosts) > >>>> - Remove the old client certificates. On the client: rm -rf /var/ > >>>> lib/ > >>>> puppet/ssl > >>>> - Clean the client certificate on the server: puppetca --clean > >>>> debian.lokku.net > >>>> - Relunch puppetd -t on the client, sign the new certificate on the > >>>> server, relaunch puppetd -t > > >>>> Good luck > >>>> Al > > >>>> On Oct 21, 12:21 pm, Reno <renato.tuv...@gmail.com> wrote: > > >>>>> Hi, thanks for the reply. > > >>>>> reno# puppetd --test > >>>>> warning: Certificate validation failed; considering using the > >>>>> certname > >>>>> configuration option > >>>>> err: Could not retrieve catalog: Certificates were not trusted: > >>>>> hostname was not match with the server certificate > >>>>> warning: Not using cache on failed catalog > > >>>>> On Oct 20, 10:39 pm, nothings_absolute <soren.mor...@gmail.com> > >>>>> wrote: > > >>>>>> If you run puppetd with the "--test" and "--debug" options you > >>>>>> should be able to see that resource being applied (Or not). It > >>>>>> could > >>>>>> be that an error in one of these files will be obvious with the > >>>>>> output > >>>>>> from running it manually with these options. > > >>>>>> On Oct 20, 11:24 am, Renato Tuveri <renato.tuv...@gmail.com> > >>>>>> wrote: > > >>>>>>> Hello a newbie here. > > >>>>>>> The situation is that: > > >>>>>>> 2 machine one master one client > >>>>>>> Puppet 0.24.5 > > >>>>>>> This my configuration: > > >>>>>>> Client: > > >>>>>>> /etc/puppet/puppetd.conf > > >>>>>>> [puppetd] > >>>>>>> server = Asus-Vista-Box > >>>>>>> logdir = /var/log/puppet > >>>>>>> vardir = /var/lib/puppet > >>>>>>> rundir = /var/run > > >>>>>>> master > > >>>>>>> /etc/puppet/manifests/classes/sudo.pp > > >>>>>>> class sudo { > >>>>>>> file { "/etc/sudoers": > >>>>>>> owner => "root", > >>>>>>> group => "root", > >>>>>>> mode => 440, > >>>>>>> } > > >>>>>>> } > > >>>>>>> /etc/puppet/manifests/site.pp > > >>>>>>> import "classes/*" > > >>>>>>> node default { > >>>>>>> include sudo > > >>>>>>> } > > >>>>>>> I make > > >>>>>>> puppetca --list > >>>>>>> debian.lokku.net > > >>>>>>> and > > >>>>>>> puppetca --sign debian.lokku.net > >>>>>>> Signed debian.lokku.net > > >>>>>>> But even I restart both client and master 100 times if I do: > > >>>>>>> ls -l /etc/sudoers > >>>>>>> -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers > > >>>>>>> What I did wrong?--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
hi Reno, I read your post but I am really sorry I cannot help you out because i am facing the same problem here. It was working before but now it stops working. Did you found any solution of this intriguing problem? if yes, please share it with me.. regards On Oct 21, 4:27 pm, Reno <renato.tuv...@gmail.com> wrote:> Ok now, seems that all is working....almost.....but: > > class aptsetup { > > file { "/etc/apt/sources.list": > owner => root, > group => root, > mode => 644, > source => "puppet://asus-vista-box.lokku.net/files/etc/ > apt/sources.list > } > } > exec { subscribe-echo: > command => "/usr/bin/apt-get -q -q update", > logoutput => false, > refreshonly => true, > subscribe => file["/etc/apt/sources.list"] > } > > err: Could not retrieve catalog: Could not parse for environment > production: Could not match ''/usr/bin/apt-get'' at /etc/puppet/ > manifests/classes/source.list.pp:7 > > On Oct 21, 2:44 pm, Reno <renato.tuv...@gmail.com> wrote:> ok I fix that just putting Asus-Vista-Box.lokku.net instead of Asus- > > Vista-Box as client config but: > > > puppetd --test > > info: Retrieving plugins > > err: Could not retrieve plugins: execution expired > > > but no rules are apply > > > On Oct 21, 1:07 pm, Reno <renato.tuv...@gmail.com> wrote: > > > > Hi, > > > I really do not get it. > > > the host name of the server is Asus-Vista-Box > > > > This is my /etc/host in the server > > > > 127.0.0.1 localhost > > > 127.0.1.1 Asus-Vista-Box.lokku.net Asus-Vista-Box > > > > and this in the clent: > > > > 127.0.0.1 localhost > > > 127.0.1.1 puppetclient.lokku.net puppetclient > > > 192.168.56.1 Asus-Vista-Box > > > > what is wrong? > > > > On Oct 21, 11:53 am, "Al @ Lab42" <lab42...@gmail.com> wrote: > > > > > Hi Reno, > > > > in puppet.conf on the client you have: > > > > server = Asus-Vista-Box > > > > this should be an host you can find (via hosts or dns) AND the > > > > hostname of your server, otherwise you run into certificates problems. > > > > > I suggest to use "puppet" as servername (the default) or change things > > > > in the followring way: > > > > - Take the hostname of the server > > > > - Make it reacheable from the client (eventually editind /etc/hosts) > > > > - Remove the old client certificates. On the client: rm -rf /var/lib/ > > > > puppet/ssl > > > > - Clean the client certificate on the server: puppetca --clean > > > > debian.lokku.net > > > > - Relunch puppetd -t on the client, sign the new certificate on the > > > > server, relaunch puppetd -t > > > > > Good luck > > > > Al > > > > > On Oct 21, 12:21 pm, Reno <renato.tuv...@gmail.com> wrote: > > > > > > Hi, thanks for the reply. > > > > > > reno# puppetd --test > > > > > warning: Certificate validation failed; considering using the certname > > > > > configuration option > > > > > err: Could not retrieve catalog: Certificates were not trusted: > > > > > hostname was not match with the server certificate > > > > > warning: Not using cache on failed catalog > > > > > > On Oct 20, 10:39 pm, nothings_absolute <soren.mor...@gmail.com> wrote: > > > > > > > If you run puppetd with the "--test" and "--debug" options you > > > > > > should be able to see that resource being applied (Or not). It could > > > > > > be that an error in one of these files will be obvious with the output > > > > > > from running it manually with these options. > > > > > > > On Oct 20, 11:24 am, Renato Tuveri <renato.tuv...@gmail.com> wrote: > > > > > > > > Hello a newbie here. > > > > > > > > The situation is that: > > > > > > > > 2 machine one master one client > > > > > > > Puppet 0.24.5 > > > > > > > > This my configuration: > > > > > > > > Client: > > > > > > > > /etc/puppet/puppetd.conf > > > > > > > > [puppetd] > > > > > > > server = Asus-Vista-Box > > > > > > > logdir = /var/log/puppet > > > > > > > vardir = /var/lib/puppet > > > > > > > rundir = /var/run > > > > > > > > master > > > > > > > > /etc/puppet/manifests/classes/sudo.pp > > > > > > > > class sudo { > > > > > > > file { "/etc/sudoers": > > > > > > > owner => "root", > > > > > > > group => "root", > > > > > > > mode => 440, > > > > > > > } > > > > > > > > } > > > > > > > > /etc/puppet/manifests/site.pp > > > > > > > > import "classes/*" > > > > > > > > node default { > > > > > > > include sudo > > > > > > > > } > > > > > > > > I make > > > > > > > > puppetca --list > > > > > > > debian.lokku.net > > > > > > > > and > > > > > > > > puppetca --sign debian.lokku.net > > > > > > > Signed debian.lokku.net > > > > > > > > But even I restart both client and master 100 times if I do: > > > > > > > > ls -l /etc/sudoers > > > > > > > -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers > > > > > > > > What I did wrong?--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
You might consider spelling the «subscribe => file["/etc/apt/ sources.list"]» with the capital letter, i.e.: «subscribe => File["/ etc/apt/sources.list"]». --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---