[Puppet Users] Puppetserver error
Hello everyone, I am new to puppet. I have installed on redhat Enterprise 5and seems to be working fine. Couple days ago I was testing some permissions on / etc folder and applied 600 /etc and sub folders. Although I have reverted the permission but I am having issues on puppetmaster. Currently I have these permission on etc 755 and puppet folder: my /etc folder is 755 and puppet folder with tese permsions: -rw-r--r-- 1 root root 2346 May 8 2010 auth.conf -rw-r--r-- 1 root root 419 May 19 2010 fileserver.conf drwxr-xr-x 3 root root 4096 Dec 23 10:48 manifests drwxr-xr-x 21 root root 4096 Oct 22 2010 modules -rw-r--r-- 1 root root 980 May 27 2010 puppet.conf -rw-r--r-- 1 root root 855 May 17 2010 puppet.conf.rpmnew I am getting these error in the log: puppet-master[3519]: Could not parse for environment production: Permission denied - /etc/puppet/manifests/classes/sysctl.pp at /etc/ puppet/manifests/site.pp:3 on node client1 Dec 27 14:25:46 server puppet-master[3519]: Could not parse for environment production: Permission denied - /etc/puppet/manifests/ classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client2 Dec 27 14:27:15 server puppet-master[3519]: Could not parse for environment production: Permission denied - /etc/puppet/manifests/ classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client3 Dec 27 14:27:15 server puppet-master[3519]: Could not parse for environment production: Permission denied - /etc/puppet/manifests/ classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client4 Dec 27 14:27:15 server puppet-agent[10407]: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Permission denied - /etc/puppet/manifests/ classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node server Any Help will be greatly appreciated. -- 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.
[Puppet Users] Re: Puppetserver error
Hello Khan, I'm fairly new to Puppet as well. I'm assuming that `manifests/classes/sysctl.pp` is being referenced by the line 3 of `manifests/site.pp` from the error msgs. My first thing would be to double check the permissions on `manifests/ classes/sysctl.pp` After that I would check the content and files being referenced by sysctl.pp and see if it's a permission issue at a lower level and Puppet is errorring at an unhelpfully high level. If that doesn't help, what the users/groups for the manifests and files being created by the manifests? Are you using filebucket? - Justin On Dec 29, 8:36 am, Khan wrote: > Hello everyone, > I am new to puppet. I have installed on redhat Enterprise 5and seems > to be working fine. Couple days ago I was testing some permissions on / > etc folder and applied 600 /etc and sub folders. Although I have > reverted the permission but I am having issues on puppetmaster. > Currently I have these permission on etc 755 and puppet folder: > my /etc folder is 755 and puppet folder with tese permsions: > > -rw-r--r-- 1 root root 2346 May 8 2010 auth.conf > -rw-r--r-- 1 root root 419 May 19 2010 fileserver.conf > drwxr-xr-x 3 root root 4096 Dec 23 10:48 manifests > drwxr-xr-x 21 root root 4096 Oct 22 2010 modules > -rw-r--r-- 1 root root 980 May 27 2010 puppet.conf > -rw-r--r-- 1 root root 855 May 17 2010 puppet.conf.rpmnew > > I am getting these error in the log: > > puppet-master[3519]: Could not parse for environment production: > Permission denied - /etc/puppet/manifests/classes/sysctl.pp at /etc/ > puppet/manifests/site.pp:3 on node client1 > > Dec 27 14:25:46 server puppet-master[3519]: Could not parse for > environment production: Permission denied - /etc/puppet/manifests/ > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client2 > > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for > environment production: Permission denied - /etc/puppet/manifests/ > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client3 > > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for > environment production: Permission denied - /etc/puppet/manifests/ > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client4 > > Dec 27 14:27:15 server puppet-agent[10407]: Could not retrieve catalog > from remote server: Error 400 on SERVER: Could not parse for > environment production: Permission denied - /etc/puppet/manifests/ > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node server > Any Help will be greatly appreciated. -- 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.
[Puppet Users] Might someone out there repair some busted links ?
Lots of the links on this page: http://projects.puppetlabs.com/projects/1/wiki/Patterns are busted. one specific example: http://projects.puppetlabs.com/trac/puppet/wiki/Recipes/Tripwire "The page you were trying to access doesn't exist or has been removed." Would it be possible to either fix them or remove them ? Thanks. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) -- 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] Re: Puppetserver error
Run puppet --genconfig for an example. On Thu, Dec 29, 2011 at 11:12 AM, Mohammad Khan wrote: > same results after changes , what should i add into master section? > > > On Thu, Dec 29, 2011 at 2:08 PM, Aaron Grewell > wrote: >> >> You'll want to change [puppetd] to [agent], as well as adding a >> [master] section with appropriate contents. >> >> On Thu, Dec 29, 2011 at 10:57 AM, Mohammad Khan >> wrote: >> > [main] >> > # Where Puppet stores dynamic and growing data. >> > # The default value is '/var/puppet'. >> > vardir = /var/lib/puppet >> > >> > # The Puppet log directory. >> > # The default value is '$vardir/log'. >> > logdir = /var/log/puppet >> > >> > # Where Puppet PID files are kept. >> > # The default value is '$vardir/run'. >> > rundir = /var/run/puppet >> > >> > # Where SSL certificates are kept. >> > # The default value is '$confdir/ssl'. >> > ssldir = $vardir/ssl >> > >> > [puppetd] >> > # The file in which puppetd stores a list of the classes >> > # associated with the retrieved configuratiion. Can be loaded in >> > # the separate ``puppet`` executable using the ``--loadclasses`` >> > # option. >> > # The default value is '$confdir/classes.txt'. >> > classfile = $vardir/classes.txt >> > >> > # Where puppetd caches the local configuration. An >> > # extension indicating the cache format is added automatically. >> > # The default value is '$confdir/localconfig'. >> > localconfig = $vardir/localconfig >> > >> > >> > >> > On Thu, Dec 29, 2011 at 1:43 PM, Aaron Grewell >> > wrote: >> >> >> >> Can you post your config? It sounds like there may be an error in it. >> >> >> >> On Thu, Dec 29, 2011 at 10:35 AM, Mohammad Khan >> >> wrote: >> >> > Thanks for your response. >> >> > I have cahnge the permission to 655 on manifests and still the same >> >> > thing. >> >> > My puppetmaster was not even starting then and now. The user/group is >> >> > root >> >> > for this folder. Every time when I try to start puppetmaster is get >> >> > this >> >> > error message: >> >> > >> >> > server puppet-master[20965]: Starting Puppet master version 2.6.12 >> >> > Dec 29 13:29:26 server puppet-master[20982]: You have configuration >> >> > parameter $classfile specified in [puppetd], which is a deprecated >> >> > section. >> >> > I'm assuming you meant [agent] >> >> > Dec 29 13:29:26 server puppet-master[20982]: You have configuration >> >> > parameter $localconfig specified in [puppetd], which is a deprecated >> >> > section. I'm assuming you meant [agent] >> >> > Dec 29 13:29:27 server puppet-master[21035]: Reopening log files >> >> > Dec 29 13:29:27 server puppet-master[21035]: Starting Puppet master >> >> > version >> >> > 2.6.12 >> >> > >> >> > >> >> > >> >> > >> >> > On Thu, Dec 29, 2011 at 12:35 PM, Justin >> >> > wrote: >> >> >> >> >> >> Hello Khan, >> >> >> >> >> >> I'm fairly new to Puppet as well. >> >> >> I'm assuming that `manifests/classes/sysctl.pp` is being referenced >> >> >> by >> >> >> the line 3 of `manifests/site.pp` from the error msgs. >> >> >> My first thing would be to double check the permissions on >> >> >> `manifests/ >> >> >> classes/sysctl.pp` >> >> >> >> >> >> After that I would check the content and files being referenced by >> >> >> sysctl.pp and see if it's a permission issue at a lower level and >> >> >> Puppet is errorring at an unhelpfully high level. >> >> >> >> >> >> If that doesn't help, what the users/groups for the manifests and >> >> >> files being created by the manifests? Are you using filebucket? >> >> >> >> >> >> >> >> >> - Justin >> >> >> >> >> >> >> >> >> >> >> >> On Dec 29, 8:36 am, Khan wrote: >> >> >> > Hello everyone, >> >> >> > I am new to puppet. I have installed on redhat Enterprise 5and >> >> >> > seems >> >> >> > to be working fine. Couple days ago I was testing some permissions >> >> >> > on >> >> >> > / >> >> >> > etc folder and applied 600 /etc and sub folders. Although I have >> >> >> > reverted the permission but I am having issues on puppetmaster. >> >> >> > Currently I have these permission on etc 755 and puppet folder: >> >> >> > my /etc folder is 755 and puppet folder with tese permsions: >> >> >> > >> >> >> > -rw-r--r-- 1 root root 2346 May 8 2010 auth.conf >> >> >> > -rw-r--r-- 1 root root 419 May 19 2010 fileserver.conf >> >> >> > drwxr-xr-x 3 root root 4096 Dec 23 10:48 manifests >> >> >> > drwxr-xr-x 21 root root 4096 Oct 22 2010 modules >> >> >> > -rw-r--r-- 1 root root 980 May 27 2010 puppet.conf >> >> >> > -rw-r--r-- 1 root root 855 May 17 2010 puppet.conf.rpmnew >> >> >> > >> >> >> > I am getting these error in the log: >> >> >> > >> >> >> > puppet-master[3519]: Could not parse for environment production: >> >> >> > Permission denied - /etc/puppet/manifests/classes/sysctl.pp at >> >> >> > /etc/ >> >> >> > puppet/manifests/site.pp:3 on node client1 >> >> >> > >> >> >> > Dec 27 14:25:46 server puppet-master[3519]: Could not parse f
Re: [Puppet Users] Re: Puppetserver error
[main] # Where Puppet stores dynamic and growing data. # The default value is '/var/puppet'. vardir = /var/lib/puppet # The Puppet log directory. # The default value is '$vardir/log'. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is '$vardir/run'. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is '$confdir/ssl'. ssldir = $vardir/ssl [puppetd] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is '$confdir/classes.txt'. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is '$confdir/localconfig'. localconfig = $vardir/localconfig On Thu, Dec 29, 2011 at 1:43 PM, Aaron Grewell wrote: > Can you post your config? It sounds like there may be an error in it. > > On Thu, Dec 29, 2011 at 10:35 AM, Mohammad Khan > wrote: > > Thanks for your response. > > I have cahnge the permission to 655 on manifests and still the same > thing. > > My puppetmaster was not even starting then and now. The user/group is > root > > for this folder. Every time when I try to start puppetmaster is get this > > error message: > > > > server puppet-master[20965]: Starting Puppet master version 2.6.12 > > Dec 29 13:29:26 server puppet-master[20982]: You have configuration > > parameter $classfile specified in [puppetd], which is a deprecated > section. > > I'm assuming you meant [agent] > > Dec 29 13:29:26 server puppet-master[20982]: You have configuration > > parameter $localconfig specified in [puppetd], which is a deprecated > > section. I'm assuming you meant [agent] > > Dec 29 13:29:27 server puppet-master[21035]: Reopening log files > > Dec 29 13:29:27 server puppet-master[21035]: Starting Puppet master > version > > 2.6.12 > > > > > > > > > > On Thu, Dec 29, 2011 at 12:35 PM, Justin > wrote: > >> > >> Hello Khan, > >> > >> I'm fairly new to Puppet as well. > >> I'm assuming that `manifests/classes/sysctl.pp` is being referenced by > >> the line 3 of `manifests/site.pp` from the error msgs. > >> My first thing would be to double check the permissions on `manifests/ > >> classes/sysctl.pp` > >> > >> After that I would check the content and files being referenced by > >> sysctl.pp and see if it's a permission issue at a lower level and > >> Puppet is errorring at an unhelpfully high level. > >> > >> If that doesn't help, what the users/groups for the manifests and > >> files being created by the manifests? Are you using filebucket? > >> > >> > >> - Justin > >> > >> > >> > >> On Dec 29, 8:36 am, Khan wrote: > >> > Hello everyone, > >> > I am new to puppet. I have installed on redhat Enterprise 5and seems > >> > to be working fine. Couple days ago I was testing some permissions on > / > >> > etc folder and applied 600 /etc and sub folders. Although I have > >> > reverted the permission but I am having issues on puppetmaster. > >> > Currently I have these permission on etc 755 and puppet folder: > >> > my /etc folder is 755 and puppet folder with tese permsions: > >> > > >> > -rw-r--r-- 1 root root 2346 May 8 2010 auth.conf > >> > -rw-r--r-- 1 root root 419 May 19 2010 fileserver.conf > >> > drwxr-xr-x 3 root root 4096 Dec 23 10:48 manifests > >> > drwxr-xr-x 21 root root 4096 Oct 22 2010 modules > >> > -rw-r--r-- 1 root root 980 May 27 2010 puppet.conf > >> > -rw-r--r-- 1 root root 855 May 17 2010 puppet.conf.rpmnew > >> > > >> > I am getting these error in the log: > >> > > >> > puppet-master[3519]: Could not parse for environment production: > >> > Permission denied - /etc/puppet/manifests/classes/sysctl.pp at /etc/ > >> > puppet/manifests/site.pp:3 on node client1 > >> > > >> > Dec 27 14:25:46 server puppet-master[3519]: Could not parse for > >> > environment production: Permission denied - /etc/puppet/manifests/ > >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client2 > >> > > >> > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for > >> > environment production: Permission denied - /etc/puppet/manifests/ > >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client3 > >> > > >> > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for > >> > environment production: Permission denied - /etc/puppet/manifests/ > >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client4 > >> > > >> > Dec 27 14:27:15 server puppet-agent[10407]: Could not retrieve catalog > >> > from remote server: Error 400 on SERVER: Could not parse for > >> > environment production: Permission denied - /etc/puppet/manifests/ > >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node server > >> > Any Help will be greatly appreciated
[Puppet Users] Re: puppet.conf questions
Thank you! $clientcert works like a charm! I'm still unclear as to why I can't see any of the ec2 variables in my ec2 instance. Is it because I'm running an old version of puppet or something? Sean On Dec 29, 10:21 am, Nan Liu wrote: > On Wed, Dec 28, 2011 at 7:38 PM, seanm wrote: > > I'm testing puppet 2.6.2 (debian) in ec2. I had two questions- > > 2. I'm using certname=webserver01 in my puppet.conf /w an external > > node classifier to distinguish nodes. I don't seem to be able to use > > certname as a global scope variable: why doesn't this work out of the > > box? and how can I get it into my manifests? (is re-parroting the > > certname as a variable in my ENC script the only way?) > > This is available as > $clientcert:http://docs.puppetlabs.com/guides/faq.html#are-there-variables-availa... > > Thanks, > > Nan -- 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] Re: Puppetserver error
same results after changes , what should i add into master section? On Thu, Dec 29, 2011 at 2:08 PM, Aaron Grewell wrote: > You'll want to change [puppetd] to [agent], as well as adding a > [master] section with appropriate contents. > > On Thu, Dec 29, 2011 at 10:57 AM, Mohammad Khan > wrote: > > [main] > > # Where Puppet stores dynamic and growing data. > > # The default value is '/var/puppet'. > > vardir = /var/lib/puppet > > > > # The Puppet log directory. > > # The default value is '$vardir/log'. > > logdir = /var/log/puppet > > > > # Where Puppet PID files are kept. > > # The default value is '$vardir/run'. > > rundir = /var/run/puppet > > > > # Where SSL certificates are kept. > > # The default value is '$confdir/ssl'. > > ssldir = $vardir/ssl > > > > [puppetd] > > # The file in which puppetd stores a list of the classes > > # associated with the retrieved configuratiion. Can be loaded in > > # the separate ``puppet`` executable using the ``--loadclasses`` > > # option. > > # The default value is '$confdir/classes.txt'. > > classfile = $vardir/classes.txt > > > > # Where puppetd caches the local configuration. An > > # extension indicating the cache format is added automatically. > > # The default value is '$confdir/localconfig'. > > localconfig = $vardir/localconfig > > > > > > > > On Thu, Dec 29, 2011 at 1:43 PM, Aaron Grewell > > wrote: > >> > >> Can you post your config? It sounds like there may be an error in it. > >> > >> On Thu, Dec 29, 2011 at 10:35 AM, Mohammad Khan > >> wrote: > >> > Thanks for your response. > >> > I have cahnge the permission to 655 on manifests and still the same > >> > thing. > >> > My puppetmaster was not even starting then and now. The user/group is > >> > root > >> > for this folder. Every time when I try to start puppetmaster is get > this > >> > error message: > >> > > >> > server puppet-master[20965]: Starting Puppet master version 2.6.12 > >> > Dec 29 13:29:26 server puppet-master[20982]: You have configuration > >> > parameter $classfile specified in [puppetd], which is a deprecated > >> > section. > >> > I'm assuming you meant [agent] > >> > Dec 29 13:29:26 server puppet-master[20982]: You have configuration > >> > parameter $localconfig specified in [puppetd], which is a deprecated > >> > section. I'm assuming you meant [agent] > >> > Dec 29 13:29:27 server puppet-master[21035]: Reopening log files > >> > Dec 29 13:29:27 server puppet-master[21035]: Starting Puppet master > >> > version > >> > 2.6.12 > >> > > >> > > >> > > >> > > >> > On Thu, Dec 29, 2011 at 12:35 PM, Justin > >> > wrote: > >> >> > >> >> Hello Khan, > >> >> > >> >> I'm fairly new to Puppet as well. > >> >> I'm assuming that `manifests/classes/sysctl.pp` is being referenced > by > >> >> the line 3 of `manifests/site.pp` from the error msgs. > >> >> My first thing would be to double check the permissions on > `manifests/ > >> >> classes/sysctl.pp` > >> >> > >> >> After that I would check the content and files being referenced by > >> >> sysctl.pp and see if it's a permission issue at a lower level and > >> >> Puppet is errorring at an unhelpfully high level. > >> >> > >> >> If that doesn't help, what the users/groups for the manifests and > >> >> files being created by the manifests? Are you using filebucket? > >> >> > >> >> > >> >> - Justin > >> >> > >> >> > >> >> > >> >> On Dec 29, 8:36 am, Khan wrote: > >> >> > Hello everyone, > >> >> > I am new to puppet. I have installed on redhat Enterprise 5and > seems > >> >> > to be working fine. Couple days ago I was testing some permissions > on > >> >> > / > >> >> > etc folder and applied 600 /etc and sub folders. Although I have > >> >> > reverted the permission but I am having issues on puppetmaster. > >> >> > Currently I have these permission on etc 755 and puppet folder: > >> >> > my /etc folder is 755 and puppet folder with tese permsions: > >> >> > > >> >> > -rw-r--r-- 1 root root 2346 May 8 2010 auth.conf > >> >> > -rw-r--r-- 1 root root 419 May 19 2010 fileserver.conf > >> >> > drwxr-xr-x 3 root root 4096 Dec 23 10:48 manifests > >> >> > drwxr-xr-x 21 root root 4096 Oct 22 2010 modules > >> >> > -rw-r--r-- 1 root root 980 May 27 2010 puppet.conf > >> >> > -rw-r--r-- 1 root root 855 May 17 2010 puppet.conf.rpmnew > >> >> > > >> >> > I am getting these error in the log: > >> >> > > >> >> > puppet-master[3519]: Could not parse for environment production: > >> >> > Permission denied - /etc/puppet/manifests/classes/sysctl.pp at > /etc/ > >> >> > puppet/manifests/site.pp:3 on node client1 > >> >> > > >> >> > Dec 27 14:25:46 server puppet-master[3519]: Could not parse for > >> >> > environment production: Permission denied - /etc/puppet/manifests/ > >> >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node > client2 > >> >> > > >> >> > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for > >> >> > environment prod
Re: [Puppet Users] Re: Puppetserver error
You'll want to change [puppetd] to [agent], as well as adding a [master] section with appropriate contents. On Thu, Dec 29, 2011 at 10:57 AM, Mohammad Khan wrote: > [main] > # Where Puppet stores dynamic and growing data. > # The default value is '/var/puppet'. > vardir = /var/lib/puppet > > # The Puppet log directory. > # The default value is '$vardir/log'. > logdir = /var/log/puppet > > # Where Puppet PID files are kept. > # The default value is '$vardir/run'. > rundir = /var/run/puppet > > # Where SSL certificates are kept. > # The default value is '$confdir/ssl'. > ssldir = $vardir/ssl > > [puppetd] > # The file in which puppetd stores a list of the classes > # associated with the retrieved configuratiion. Can be loaded in > # the separate ``puppet`` executable using the ``--loadclasses`` > # option. > # The default value is '$confdir/classes.txt'. > classfile = $vardir/classes.txt > > # Where puppetd caches the local configuration. An > # extension indicating the cache format is added automatically. > # The default value is '$confdir/localconfig'. > localconfig = $vardir/localconfig > > > > On Thu, Dec 29, 2011 at 1:43 PM, Aaron Grewell > wrote: >> >> Can you post your config? It sounds like there may be an error in it. >> >> On Thu, Dec 29, 2011 at 10:35 AM, Mohammad Khan >> wrote: >> > Thanks for your response. >> > I have cahnge the permission to 655 on manifests and still the same >> > thing. >> > My puppetmaster was not even starting then and now. The user/group is >> > root >> > for this folder. Every time when I try to start puppetmaster is get this >> > error message: >> > >> > server puppet-master[20965]: Starting Puppet master version 2.6.12 >> > Dec 29 13:29:26 server puppet-master[20982]: You have configuration >> > parameter $classfile specified in [puppetd], which is a deprecated >> > section. >> > I'm assuming you meant [agent] >> > Dec 29 13:29:26 server puppet-master[20982]: You have configuration >> > parameter $localconfig specified in [puppetd], which is a deprecated >> > section. I'm assuming you meant [agent] >> > Dec 29 13:29:27 server puppet-master[21035]: Reopening log files >> > Dec 29 13:29:27 server puppet-master[21035]: Starting Puppet master >> > version >> > 2.6.12 >> > >> > >> > >> > >> > On Thu, Dec 29, 2011 at 12:35 PM, Justin >> > wrote: >> >> >> >> Hello Khan, >> >> >> >> I'm fairly new to Puppet as well. >> >> I'm assuming that `manifests/classes/sysctl.pp` is being referenced by >> >> the line 3 of `manifests/site.pp` from the error msgs. >> >> My first thing would be to double check the permissions on `manifests/ >> >> classes/sysctl.pp` >> >> >> >> After that I would check the content and files being referenced by >> >> sysctl.pp and see if it's a permission issue at a lower level and >> >> Puppet is errorring at an unhelpfully high level. >> >> >> >> If that doesn't help, what the users/groups for the manifests and >> >> files being created by the manifests? Are you using filebucket? >> >> >> >> >> >> - Justin >> >> >> >> >> >> >> >> On Dec 29, 8:36 am, Khan wrote: >> >> > Hello everyone, >> >> > I am new to puppet. I have installed on redhat Enterprise 5and seems >> >> > to be working fine. Couple days ago I was testing some permissions on >> >> > / >> >> > etc folder and applied 600 /etc and sub folders. Although I have >> >> > reverted the permission but I am having issues on puppetmaster. >> >> > Currently I have these permission on etc 755 and puppet folder: >> >> > my /etc folder is 755 and puppet folder with tese permsions: >> >> > >> >> > -rw-r--r-- 1 root root 2346 May 8 2010 auth.conf >> >> > -rw-r--r-- 1 root root 419 May 19 2010 fileserver.conf >> >> > drwxr-xr-x 3 root root 4096 Dec 23 10:48 manifests >> >> > drwxr-xr-x 21 root root 4096 Oct 22 2010 modules >> >> > -rw-r--r-- 1 root root 980 May 27 2010 puppet.conf >> >> > -rw-r--r-- 1 root root 855 May 17 2010 puppet.conf.rpmnew >> >> > >> >> > I am getting these error in the log: >> >> > >> >> > puppet-master[3519]: Could not parse for environment production: >> >> > Permission denied - /etc/puppet/manifests/classes/sysctl.pp at /etc/ >> >> > puppet/manifests/site.pp:3 on node client1 >> >> > >> >> > Dec 27 14:25:46 server puppet-master[3519]: Could not parse for >> >> > environment production: Permission denied - /etc/puppet/manifests/ >> >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client2 >> >> > >> >> > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for >> >> > environment production: Permission denied - /etc/puppet/manifests/ >> >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client3 >> >> > >> >> > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for >> >> > environment production: Permission denied - /etc/puppet/manifests/ >> >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client4 >> >> > >> >> >
Re: [Puppet Users] Might someone out there repair some busted links ?
On Thu, Dec 29, 2011 at 11:14, Dan White wrote: > Lots of the links on this page: > http://projects.puppetlabs.com/projects/1/wiki/Patterns > are busted. > > one specific example: > http://projects.puppetlabs.com/trac/puppet/wiki/Recipes/Tripwire > > "The page you were trying to access doesn't exist or has been removed." > > Would it be possible to either fix them or remove them ? I have asked the folks who maintain our web stuff to look into that; thanks for letting us know. :) Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
[Puppet Users] puppet.conf questions
I'm testing puppet 2.6.2 (debian) in ec2. I had two questions- 1. Does anyone know why I can't see any ec2 variables from facter in my instance? I'm running facter --puppet in my instance 2. I'm using certname=webserver01 in my puppet.conf /w an external node classifier to distinguish nodes. I don't seem to be able to use certname as a global scope variable: why doesn't this work out of the box? and how can I get it into my manifests? (is re-parroting the certname as a variable in my ENC script the only way?) Thanks! I'm really loving puppet so far. -- 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] Re: New variable scoping question regarding defines calling defines.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The issue is that, should you call that define more than once, there's no way
for Puppet to know which one to use unless it walks directly up the call
stack first.
Trevor
On 12/28/2011 09:16 PM, Ryan Coleman wrote:
>
>
> On Monday, December 26, 2011 5:56:26 AM UTC-8, Trevor Vaughan wrote:
>>
>> I just ran into an interesting scenario where I didn't know how to
>> scope my variables and I'd just like to share for the crowd.
>>
>> Suppose you have two modules 'foo' and 'bar'. You also have two
>> defines, 'foo::do_stuff' and 'bar::more_stuff'.
>>
>> define foo::do_stuff (
>> $var1 = 'a',
>> $var2 = 'b'
>> ) {
>> bar::more_stuff { 'test': }
>> }
>>
>> define bar::more_stuff (
>> $optional_var = 'ignore'
>> ) {
>> file { '/tmp/test':
>> content => template('bar/random.erb')
>> }
>>
>> +++ random.erb +++
>>
>> var1 = <%= var1 %>
>> var2 = <%= var2 %>
>>
> Have you tried this in your template?
>
> <%= scope.lookupvar('foo::do_stuff::var1') %>
>
> That should let you refer directly to the variable in that define, if I
> understand your setup correctly.
>
- --
Trevor Vaughan
Vice President, Onyx Point, Inc.
email: tvaug...@onyxpoint.com
phone: 410-541-ONYX (6699)
pgp: 0x6C701E94
- -- This account not approved for unencrypted sensitive information --
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJO/HDxAAoJECNCGV1OLcypqScIAIlaCSNBRncSh4/1zGXyuvX5
CA35+lpr4TaQ8JweGltLmY0Ceb3RQcLyiqXdna3pZ1+kLNiKnrlysaRk6/e91zO7
0ngbhMGbOJLK0TyHFPq+5m+VjB0DvEvCaNRYIabQZWOwVKRLCpQYaFOoQPLyZ3f2
JX3YsvdhqhreVxqFKv7SlStc1cLxSoh8+TjWTwxQsa9Sq6Ff9P+iY+zTyHbZU7IP
opBLbg1uIS1xIYSYILZKtkDvQjAVfY8oYvmslz0MXKyS6TTZMVYGs8F8zJUZSpC8
lO8LEAyLtXsPIAGKNevfKpka3KxZ2wQ7mM70ydK3ShPEYe77V9K/oXBGeg2dh7E=
=/Fg0
-END PGP SIGNATURE-
--
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] Re: Puppetserver error
Thanks for your response. I have cahnge the permission to 655 on manifests and still the same thing. My puppetmaster was not even starting then and now. The user/group is root for this folder. Every time when I try to start puppetmaster is get this error message: server puppet-master[20965]: Starting Puppet master version 2.6.12 Dec 29 13:29:26 server puppet-master[20982]: You have configuration parameter $classfile specified in [puppetd], which is a deprecated section. I'm assuming you meant [agent] Dec 29 13:29:26 server puppet-master[20982]: You have configuration parameter $localconfig specified in [puppetd], which is a deprecated section. I'm assuming you meant [agent] Dec 29 13:29:27 server puppet-master[21035]: Reopening log files Dec 29 13:29:27 server puppet-master[21035]: Starting Puppet master version 2.6.12 On Thu, Dec 29, 2011 at 12:35 PM, Justin wrote: > Hello Khan, > > I'm fairly new to Puppet as well. > I'm assuming that `manifests/classes/sysctl.pp` is being referenced by > the line 3 of `manifests/site.pp` from the error msgs. > My first thing would be to double check the permissions on `manifests/ > classes/sysctl.pp` > > After that I would check the content and files being referenced by > sysctl.pp and see if it's a permission issue at a lower level and > Puppet is errorring at an unhelpfully high level. > > If that doesn't help, what the users/groups for the manifests and > files being created by the manifests? Are you using filebucket? > > > - Justin > > > > On Dec 29, 8:36 am, Khan wrote: > > Hello everyone, > > I am new to puppet. I have installed on redhat Enterprise 5and seems > > to be working fine. Couple days ago I was testing some permissions on / > > etc folder and applied 600 /etc and sub folders. Although I have > > reverted the permission but I am having issues on puppetmaster. > > Currently I have these permission on etc 755 and puppet folder: > > my /etc folder is 755 and puppet folder with tese permsions: > > > > -rw-r--r-- 1 root root 2346 May 8 2010 auth.conf > > -rw-r--r-- 1 root root 419 May 19 2010 fileserver.conf > > drwxr-xr-x 3 root root 4096 Dec 23 10:48 manifests > > drwxr-xr-x 21 root root 4096 Oct 22 2010 modules > > -rw-r--r-- 1 root root 980 May 27 2010 puppet.conf > > -rw-r--r-- 1 root root 855 May 17 2010 puppet.conf.rpmnew > > > > I am getting these error in the log: > > > > puppet-master[3519]: Could not parse for environment production: > > Permission denied - /etc/puppet/manifests/classes/sysctl.pp at /etc/ > > puppet/manifests/site.pp:3 on node client1 > > > > Dec 27 14:25:46 server puppet-master[3519]: Could not parse for > > environment production: Permission denied - /etc/puppet/manifests/ > > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client2 > > > > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for > > environment production: Permission denied - /etc/puppet/manifests/ > > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client3 > > > > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for > > environment production: Permission denied - /etc/puppet/manifests/ > > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client4 > > > > Dec 27 14:27:15 server puppet-agent[10407]: Could not retrieve catalog > > from remote server: Error 400 on SERVER: Could not parse for > > environment production: Permission denied - /etc/puppet/manifests/ > > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node server > > Any Help will be greatly appreciated. > > -- > 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. > > -- Regards, Mohammad -- 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] Re: Puppetserver error
Can you post your config? It sounds like there may be an error in it. On Thu, Dec 29, 2011 at 10:35 AM, Mohammad Khan wrote: > Thanks for your response. > I have cahnge the permission to 655 on manifests and still the same thing. > My puppetmaster was not even starting then and now. The user/group is root > for this folder. Every time when I try to start puppetmaster is get this > error message: > > server puppet-master[20965]: Starting Puppet master version 2.6.12 > Dec 29 13:29:26 server puppet-master[20982]: You have configuration > parameter $classfile specified in [puppetd], which is a deprecated section. > I'm assuming you meant [agent] > Dec 29 13:29:26 server puppet-master[20982]: You have configuration > parameter $localconfig specified in [puppetd], which is a deprecated > section. I'm assuming you meant [agent] > Dec 29 13:29:27 server puppet-master[21035]: Reopening log files > Dec 29 13:29:27 server puppet-master[21035]: Starting Puppet master version > 2.6.12 > > > > > On Thu, Dec 29, 2011 at 12:35 PM, Justin wrote: >> >> Hello Khan, >> >> I'm fairly new to Puppet as well. >> I'm assuming that `manifests/classes/sysctl.pp` is being referenced by >> the line 3 of `manifests/site.pp` from the error msgs. >> My first thing would be to double check the permissions on `manifests/ >> classes/sysctl.pp` >> >> After that I would check the content and files being referenced by >> sysctl.pp and see if it's a permission issue at a lower level and >> Puppet is errorring at an unhelpfully high level. >> >> If that doesn't help, what the users/groups for the manifests and >> files being created by the manifests? Are you using filebucket? >> >> >> - Justin >> >> >> >> On Dec 29, 8:36 am, Khan wrote: >> > Hello everyone, >> > I am new to puppet. I have installed on redhat Enterprise 5and seems >> > to be working fine. Couple days ago I was testing some permissions on / >> > etc folder and applied 600 /etc and sub folders. Although I have >> > reverted the permission but I am having issues on puppetmaster. >> > Currently I have these permission on etc 755 and puppet folder: >> > my /etc folder is 755 and puppet folder with tese permsions: >> > >> > -rw-r--r-- 1 root root 2346 May 8 2010 auth.conf >> > -rw-r--r-- 1 root root 419 May 19 2010 fileserver.conf >> > drwxr-xr-x 3 root root 4096 Dec 23 10:48 manifests >> > drwxr-xr-x 21 root root 4096 Oct 22 2010 modules >> > -rw-r--r-- 1 root root 980 May 27 2010 puppet.conf >> > -rw-r--r-- 1 root root 855 May 17 2010 puppet.conf.rpmnew >> > >> > I am getting these error in the log: >> > >> > puppet-master[3519]: Could not parse for environment production: >> > Permission denied - /etc/puppet/manifests/classes/sysctl.pp at /etc/ >> > puppet/manifests/site.pp:3 on node client1 >> > >> > Dec 27 14:25:46 server puppet-master[3519]: Could not parse for >> > environment production: Permission denied - /etc/puppet/manifests/ >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client2 >> > >> > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for >> > environment production: Permission denied - /etc/puppet/manifests/ >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client3 >> > >> > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for >> > environment production: Permission denied - /etc/puppet/manifests/ >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client4 >> > >> > Dec 27 14:27:15 server puppet-agent[10407]: Could not retrieve catalog >> > from remote server: Error 400 on SERVER: Could not parse for >> > environment production: Permission denied - /etc/puppet/manifests/ >> > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node server >> > Any Help will be greatly appreciated. >> >> -- >> 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. >> > > > > -- > Regards, > Mohammad > > > -- > 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. -- 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] puppet.conf questions
On Wed, Dec 28, 2011 at 7:38 PM, seanm wrote: > I'm testing puppet 2.6.2 (debian) in ec2. I had two questions- > 2. I'm using certname=webserver01 in my puppet.conf /w an external > node classifier to distinguish nodes. I don't seem to be able to use > certname as a global scope variable: why doesn't this work out of the > box? and how can I get it into my manifests? (is re-parroting the > certname as a variable in my ENC script the only way?) This is available as $clientcert: http://docs.puppetlabs.com/guides/faq.html#are-there-variables-available-other-than-those-provided-by-facter Thanks, Nan -- 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.
[Puppet Users] user provider for AIX run error
run “puppet resource user” got the error blew, I tested at AIX 5.3 and AIX 6.1 ruby 1.8.7 puppet 2.7.9 /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/provider/aixobject.rb:291:in `instances': undefined method `list_all' for Puppet::Type::Group::ProviderAix:Class (NoMethodError) from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/type.rb:880:in `instances' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/type.rb:873:in `collect' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/type.rb:873:in `instances' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/indirector/resource/ral.rb:14:in `search' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/indirector/indirection.rb:249:in `search' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application/resource.rb:234:in `find_or_save_resources' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application/resource.rb:144:in `main' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:314:in `run_command' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:306:in `run' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:410:in `hook' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:306:in `run' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:401:in `exit_on_fail' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:306:in `run' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/util/command_line.rb:69:in `execute' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/bin/puppet:4 from /usr/local/bin/puppet:18:in `load' from /usr/local/bin/puppet:18 -- 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] user provider for AIX run error
Hi. Can you file this as a bug at http://projects.puppetlabs.com/projects/puppet/issues/new please? Daniel On Thu, Dec 29, 2011 at 06:48, Alpha wrote: > run “puppet resource user” got the error blew, I tested at AIX 5.3 and AIX > 6.1 ruby 1.8.7 puppet 2.7.9 > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/provider/aixobject.rb:291:in > `instances': undefined method `list_all' for > Puppet::Type::Group::ProviderAix:Class (NoMethodError) from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/type.rb:880:in > `instances' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/type.rb:873:in > `collect' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/type.rb:873:in > `instances' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/indirector/resource/ral.rb:14:in > `search' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/indirector/indirection.rb:249:in > `search' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application/resource.rb:234:in > `find_or_save_resources' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application/resource.rb:144:in > `main' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:314:in > `run_command' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:306:in > `run' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:410:in > `hook' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:306:in > `run' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:401:in > `exit_on_fail' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/application.rb:306:in > `run' from > /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/lib/puppet/util/command_line.rb:69:in > `execute' from /usr/local/lib/ruby/gems/1.8/gems/puppet-2.7.9/bin/puppet:4 > from /usr/local/bin/puppet:18:in `load' from /usr/local/bin/puppet:18 > > -- > 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. -- ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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] Re: Puppetserver error
I am getting these messages now at the puppetmaster start: Denying access: Forbidden request: server(ip) access to /catalog/ server.domain.co [find] at line 93 Dec 29 15:13:20 server puppet-master[3311]: Forbidden request: server (ip) access to /catalog/server.domain.co [find] at line 93 Dec 29 15:13:20 server puppet-agent[4382]: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: server (ip) access to /catalog/server.domain.co [find] at line 93 And also the same error: but on 17 line now. Which represent my ldap if i disable ldap line then the error moves to next line and so on. On Thu, Dec 29, 2011 at 2:22 PM, Aaron Grewell wrote: > Run puppet --genconfig for an example. > > > On Thu, Dec 29, 2011 at 11:12 AM, Mohammad Khan > wrote: > > same results after changes , what should i add into master section? > > > > > > On Thu, Dec 29, 2011 at 2:08 PM, Aaron Grewell > > wrote: > >> > >> You'll want to change [puppetd] to [agent], as well as adding a > >> [master] section with appropriate contents. > >> > >> On Thu, Dec 29, 2011 at 10:57 AM, Mohammad Khan > >> wrote: > >> > [main] > >> > # Where Puppet stores dynamic and growing data. > >> > # The default value is '/var/puppet'. > >> > vardir = /var/lib/puppet > >> > > >> > # The Puppet log directory. > >> > # The default value is '$vardir/log'. > >> > logdir = /var/log/puppet > >> > > >> > # Where Puppet PID files are kept. > >> > # The default value is '$vardir/run'. > >> > rundir = /var/run/puppet > >> > > >> > # Where SSL certificates are kept. > >> > # The default value is '$confdir/ssl'. > >> > ssldir = $vardir/ssl > >> > > >> > [puppetd] > >> > # The file in which puppetd stores a list of the classes > >> > # associated with the retrieved configuratiion. Can be loaded in > >> > # the separate ``puppet`` executable using the ``--loadclasses`` > >> > # option. > >> > # The default value is '$confdir/classes.txt'. > >> > classfile = $vardir/classes.txt > >> > > >> > # Where puppetd caches the local configuration. An > >> > # extension indicating the cache format is added automatically. > >> > # The default value is '$confdir/localconfig'. > >> > localconfig = $vardir/localconfig > >> > > >> > > >> > > >> > On Thu, Dec 29, 2011 at 1:43 PM, Aaron Grewell < > aaron.grew...@gmail.com> > >> > wrote: > >> >> > >> >> Can you post your config? It sounds like there may be an error in > it. > >> >> > >> >> On Thu, Dec 29, 2011 at 10:35 AM, Mohammad Khan > > >> >> wrote: > >> >> > Thanks for your response. > >> >> > I have cahnge the permission to 655 on manifests and still the same > >> >> > thing. > >> >> > My puppetmaster was not even starting then and now. The user/group > is > >> >> > root > >> >> > for this folder. Every time when I try to start puppetmaster is get > >> >> > this > >> >> > error message: > >> >> > > >> >> > server puppet-master[20965]: Starting Puppet master version 2.6.12 > >> >> > Dec 29 13:29:26 server puppet-master[20982]: You have > configuration > >> >> > parameter $classfile specified in [puppetd], which is a deprecated > >> >> > section. > >> >> > I'm assuming you meant [agent] > >> >> > Dec 29 13:29:26 server puppet-master[20982]: You have configuration > >> >> > parameter $localconfig specified in [puppetd], which is a > deprecated > >> >> > section. I'm assuming you meant [agent] > >> >> > Dec 29 13:29:27 server puppet-master[21035]: Reopening log files > >> >> > Dec 29 13:29:27 server puppet-master[21035]: Starting Puppet master > >> >> > version > >> >> > 2.6.12 > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > On Thu, Dec 29, 2011 at 12:35 PM, Justin > > >> >> > wrote: > >> >> >> > >> >> >> Hello Khan, > >> >> >> > >> >> >> I'm fairly new to Puppet as well. > >> >> >> I'm assuming that `manifests/classes/sysctl.pp` is being > referenced > >> >> >> by > >> >> >> the line 3 of `manifests/site.pp` from the error msgs. > >> >> >> My first thing would be to double check the permissions on > >> >> >> `manifests/ > >> >> >> classes/sysctl.pp` > >> >> >> > >> >> >> After that I would check the content and files being referenced by > >> >> >> sysctl.pp and see if it's a permission issue at a lower level and > >> >> >> Puppet is errorring at an unhelpfully high level. > >> >> >> > >> >> >> If that doesn't help, what the users/groups for the manifests and > >> >> >> files being created by the manifests? Are you using filebucket? > >> >> >> > >> >> >> > >> >> >> - Justin > >> >> >> > >> >> >> > >> >> >> > >> >> >> On Dec 29, 8:36 am, Khan wrote: > >> >> >> > Hello everyone, > >> >> >> > I am new to puppet. I have installed on redhat Enterprise 5and > >> >> >> > seems > >> >> >> > to be working fine. Couple days ago I was testing some > permissions > >> >> >> > on > >> >> >> > / > >> >> >> > etc folder and applied 600 /etc and sub folders. Although I have > >> >> >> > reverted the permission but I am havin
Re: [Puppet Users] Re: Puppetserver error
I've never integrated Puppet with LDAP so I can't help much there. On Thu, Dec 29, 2011 at 12:25 PM, Mohammad Khan wrote: > I am getting these messages now at the puppetmaster start: > > > Denying access: Forbidden request: server(ip) access to > /catalog/server.domain.co [find] at line 93 > Dec 29 15:13:20 server puppet-master[3311]: Forbidden request: server (ip) > access to /catalog/server.domain.co [find] at line 93 > Dec 29 15:13:20 server puppet-agent[4382]: Could not retrieve catalog from > remote server: Error 403 on SERVER: Forbidden request: server (ip) access to > /catalog/server.domain.co [find] at line 93 > And also the same error: but on 17 line now. Which represent my ldap if i > disable ldap line then the error moves to next line and so on. > > > On Thu, Dec 29, 2011 at 2:22 PM, Aaron Grewell > wrote: >> >> Run puppet --genconfig for an example. >> >> >> On Thu, Dec 29, 2011 at 11:12 AM, Mohammad Khan >> wrote: >> > same results after changes , what should i add into master section? >> > >> > >> > On Thu, Dec 29, 2011 at 2:08 PM, Aaron Grewell >> > wrote: >> >> >> >> You'll want to change [puppetd] to [agent], as well as adding a >> >> [master] section with appropriate contents. >> >> >> >> On Thu, Dec 29, 2011 at 10:57 AM, Mohammad Khan >> >> wrote: >> >> > [main] >> >> > # Where Puppet stores dynamic and growing data. >> >> > # The default value is '/var/puppet'. >> >> > vardir = /var/lib/puppet >> >> > >> >> > # The Puppet log directory. >> >> > # The default value is '$vardir/log'. >> >> > logdir = /var/log/puppet >> >> > >> >> > # Where Puppet PID files are kept. >> >> > # The default value is '$vardir/run'. >> >> > rundir = /var/run/puppet >> >> > >> >> > # Where SSL certificates are kept. >> >> > # The default value is '$confdir/ssl'. >> >> > ssldir = $vardir/ssl >> >> > >> >> > [puppetd] >> >> > # The file in which puppetd stores a list of the classes >> >> > # associated with the retrieved configuratiion. Can be loaded in >> >> > # the separate ``puppet`` executable using the ``--loadclasses`` >> >> > # option. >> >> > # The default value is '$confdir/classes.txt'. >> >> > classfile = $vardir/classes.txt >> >> > >> >> > # Where puppetd caches the local configuration. An >> >> > # extension indicating the cache format is added automatically. >> >> > # The default value is '$confdir/localconfig'. >> >> > localconfig = $vardir/localconfig >> >> > >> >> > >> >> > >> >> > On Thu, Dec 29, 2011 at 1:43 PM, Aaron Grewell >> >> > >> >> > wrote: >> >> >> >> >> >> Can you post your config? It sounds like there may be an error in >> >> >> it. >> >> >> >> >> >> On Thu, Dec 29, 2011 at 10:35 AM, Mohammad Khan >> >> >> >> >> >> wrote: >> >> >> > Thanks for your response. >> >> >> > I have cahnge the permission to 655 on manifests and still the >> >> >> > same >> >> >> > thing. >> >> >> > My puppetmaster was not even starting then and now. The user/group >> >> >> > is >> >> >> > root >> >> >> > for this folder. Every time when I try to start puppetmaster is >> >> >> > get >> >> >> > this >> >> >> > error message: >> >> >> > >> >> >> > server puppet-master[20965]: Starting Puppet master version 2.6.12 >> >> >> > Dec 29 13:29:26 server puppet-master[20982]: You have >> >> >> > configuration >> >> >> > parameter $classfile specified in [puppetd], which is a deprecated >> >> >> > section. >> >> >> > I'm assuming you meant [agent] >> >> >> > Dec 29 13:29:26 server puppet-master[20982]: You have >> >> >> > configuration >> >> >> > parameter $localconfig specified in [puppetd], which is a >> >> >> > deprecated >> >> >> > section. I'm assuming you meant [agent] >> >> >> > Dec 29 13:29:27 server puppet-master[21035]: Reopening log files >> >> >> > Dec 29 13:29:27 server puppet-master[21035]: Starting Puppet >> >> >> > master >> >> >> > version >> >> >> > 2.6.12 >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > On Thu, Dec 29, 2011 at 12:35 PM, Justin >> >> >> > >> >> >> > wrote: >> >> >> >> >> >> >> >> Hello Khan, >> >> >> >> >> >> >> >> I'm fairly new to Puppet as well. >> >> >> >> I'm assuming that `manifests/classes/sysctl.pp` is being >> >> >> >> referenced >> >> >> >> by >> >> >> >> the line 3 of `manifests/site.pp` from the error msgs. >> >> >> >> My first thing would be to double check the permissions on >> >> >> >> `manifests/ >> >> >> >> classes/sysctl.pp` >> >> >> >> >> >> >> >> After that I would check the content and files being referenced >> >> >> >> by >> >> >> >> sysctl.pp and see if it's a permission issue at a lower level and >> >> >> >> Puppet is errorring at an unhelpfully high level. >> >> >> >> >> >> >> >> If that doesn't help, what the users/groups for the manifests and >> >> >> >> files being created by the manifests? Are you using filebucket? >> >> >> >> >> >> >> >> >> >> >> >> - Justin >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Dec 29, 8:36 am, Khan wrote: >> >> >> >
Re: [Puppet Users] Might someone out there repair some busted links ?
Thanks. We Dans need to stick together :) “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) - Daniel Pittman wrote: > On Thu, Dec 29, 2011 at 11:14, Dan White wrote: > > Lots of the links on this page: > > http://projects.puppetlabs.com/projects/1/wiki/Patterns > > are busted. > > > > one specific example: > > http://projects.puppetlabs.com/trac/puppet/wiki/Recipes/Tripwire > > > > "The page you were trying to access doesn't exist or has been removed." > > > > Would it be possible to either fix them or remove them ? > > I have asked the folks who maintain our web stuff to look into that; > thanks for letting us know. :) > > Daniel > -- > ⎋ Puppet Labs Developer – http://puppetlabs.com > ♲ Made with 100 percent post-consumer electrons -- 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.
[Puppet Users] Windows Client DFS share Access
Does anybody know if it is possible to have a WIndows client access an existing DFS share. Based on what I have been able to determine so far. It appears that files can only be served to windows clients using nfs. Does anybody have any information on this? I've read through the wiki and didn't see anything mentioning this. Additionally, my other searches on this topic has come up with no useful information. Any help would be greatly appreciated. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/GOHcYLlFpbUJ. 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] Windows Client DFS share Access
Hi Jeff, On Thu, Dec 29, 2011 at 1:29 PM, jvandellen wrote: > Does anybody know if it is possible to have a WIndows client access an > existing DFS share. Based on what I have been able to determine so far. It > appears that files can only be served to windows clients using nfs. Does > anybody have any information on this? I've read through the wiki and didn't > see anything mentioning this. Additionally, my other searches on this > topic has come up with no useful information. > > Any help would be greatly appreciated. > I have not tried this, but most likely it doesn't work when referencing the share as a UNC path. See https://projects.puppetlabs.com/issues/8657. However, if you can map the share to a drive, e.g. net use z: \\server\share, then that should definitely work. Josh -- Josh Cooper Developer, Puppet Labs -- 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.
[Puppet Users] Help with some script
Hello So i used this guide http://itand.me/using-puppet-to-manage-users-passwords-and-ss to set it up similar. Now want to do small modification. What i want is to have all the users defined in a speciall file or a folder where all the users are created, and then import the users into the nodes. Any ideas how to manage that? -- 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] Re: puppet.conf questions
On Thu, Dec 29, 2011 at 10:59 AM, seanm wrote: > Thank you! $clientcert works like a charm! > > I'm still unclear as to why I can't see any of the ec2 variables in my > ec2 instance. Is it because I'm running an old version of puppet or > something? > If you're running Puppet 2.6.2, I imagine the version of Facter is also quite old. EC2 facts have had some work done to them in the last few releases of Facter. What's the version you are running? > Sean > > On Dec 29, 10:21 am, Nan Liu wrote: >> On Wed, Dec 28, 2011 at 7:38 PM, seanm wrote: >> > I'm testing puppet 2.6.2 (debian) in ec2. I had two questions- >> > 2. I'm using certname=webserver01 in my puppet.conf /w an external >> > node classifier to distinguish nodes. I don't seem to be able to use >> > certname as a global scope variable: why doesn't this work out of the >> > box? and how can I get it into my manifests? (is re-parroting the >> > certname as a variable in my ENC script the only way?) >> >> This is available as >> $clientcert:http://docs.puppetlabs.com/guides/faq.html#are-there-variables-availa... >> >> Thanks, >> >> Nan > > -- > 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. > -- 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] Windows Client DFS share Access
Awesome!! thank you so much for the information. I really appreciate it. On Thu, Dec 29, 2011 at 4:51 PM, Josh Cooper wrote: > Hi Jeff, > > On Thu, Dec 29, 2011 at 1:29 PM, jvandellen > wrote: >> >> Does anybody know if it is possible to have a WIndows client access an >> existing DFS share. Based on what I have been able to determine so far. It >> appears that files can only be served to windows clients using nfs. Does >> anybody have any information on this? I've read through the wiki and didn't >> see anything mentioning this. Additionally, my other searches on this topic >> has come up with no useful information. >> >> Any help would be greatly appreciated. > > > I have not tried this, but most likely it doesn't work when referencing the > share as a UNC path. See https://projects.puppetlabs.com/issues/8657. > > However, if you can map the share to a drive, e.g. net use z: > \\server\share, then that should definitely work. > > Josh > > -- > Josh Cooper > Developer, Puppet Labs > > -- > 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. -- 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.
[Puppet Users] Re: puppet.conf questions
facter --version is showing: 1.5.7 On Dec 29, 4:11 pm, Michael Stahnke wrote: > On Thu, Dec 29, 2011 at 10:59 AM, seanm wrote: > > Thank you! $clientcert works like a charm! > > > I'm still unclear as to why I can't see any of the ec2 variables in my > > ec2 instance. Is it because I'm running an old version of puppet or > > something? > > If you're running Puppet 2.6.2, I imagine the version of Facter is > also quite old. EC2 facts have had some work done to them in the last > few releases of Facter. What's the version you are running? > > > > > > > > > Sean > > > On Dec 29, 10:21 am, Nan Liu wrote: > >> On Wed, Dec 28, 2011 at 7:38 PM, seanm wrote: > >> > I'm testing puppet 2.6.2 (debian) in ec2. I had two questions- > >> > 2. I'm using certname=webserver01 in my puppet.conf /w an external > >> > node classifier to distinguish nodes. I don't seem to be able to use > >> > certname as a global scope variable: why doesn't this work out of the > >> > box? and how can I get it into my manifests? (is re-parroting the > >> > certname as a variable in my ENC script the only way?) > > >> This is available as > >> $clientcert:http://docs.puppetlabs.com/guides/faq.html#are-there-variables-availa... > > >> Thanks, > > >> Nan > > > -- > > 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 > > 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 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.
AW: [Puppet Users] Puppetserver error
I'm pretty sure that, besides the other answers already provided, your main problem is the wrong user for your Puppet configuration. It should be user 'puppet' and not 'root'. That's how '/etc/puppet' should look like: drwxr-xr-x 5 puppet puppet 4.0K Dec 12 17:48 . drwxr-xr-x 79 root root12K Dec 26 04:03 .. -rw-r--r-- 1 puppet puppet 3.1K Dec 12 17:48 auth.conf drwxr-xr-x 6 puppet puppet 4.0K Dec 12 17:48 environments drwxr-xr-x 3 puppet puppet 4.0K Dec 12 17:48 manifests -rw-r--r-- 1 puppet puppet 838 Dec 12 17:48 namespaceauth.conf -rw-r--r-- 1 puppet puppet 1.8K Dec 12 17:48 puppet.conf drwxr-xr-x 6 puppet puppet 4.0K Dec 30 08:20 .svn So a command like 'chown -R puppet:puppet /etc/puppet' issued as 'root' should solve your main problem which is the 'Permission denied' error as well as the non starting Puppet process. Bernd > -Ursprüngliche Nachricht- > Von: puppet-users@googlegroups.com [mailto:puppet- > us...@googlegroups.com] Im Auftrag von Khan > Gesendet: Donnerstag, 29. Dezember 2011 17:37 > An: Puppet Users > Betreff: [Puppet Users] Puppetserver error > > Hello everyone, > I am new to puppet. I have installed on redhat Enterprise 5and seems > to be working fine. Couple days ago I was testing some permissions on / > etc folder and applied 600 /etc and sub folders. Although I have > reverted the permission but I am having issues on puppetmaster. > Currently I have these permission on etc 755 and puppet folder: > my /etc folder is 755 and puppet folder with tese permsions: > > -rw-r--r-- 1 root root 2346 May 8 2010 auth.conf > -rw-r--r-- 1 root root 419 May 19 2010 fileserver.conf > drwxr-xr-x 3 root root 4096 Dec 23 10:48 manifests > drwxr-xr-x 21 root root 4096 Oct 22 2010 modules > -rw-r--r-- 1 root root 980 May 27 2010 puppet.conf > -rw-r--r-- 1 root root 855 May 17 2010 puppet.conf.rpmnew > > I am getting these error in the log: > > puppet-master[3519]: Could not parse for environment production: > Permission denied - /etc/puppet/manifests/classes/sysctl.pp at /etc/ > puppet/manifests/site.pp:3 on node client1 > > Dec 27 14:25:46 server puppet-master[3519]: Could not parse for > environment production: Permission denied - /etc/puppet/manifests/ > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client2 > > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for > environment production: Permission denied - /etc/puppet/manifests/ > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client3 > > Dec 27 14:27:15 server puppet-master[3519]: Could not parse for > environment production: Permission denied - /etc/puppet/manifests/ > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node client4 > > Dec 27 14:27:15 server puppet-agent[10407]: Could not retrieve catalog > from remote server: Error 400 on SERVER: Could not parse for > environment production: Permission denied - /etc/puppet/manifests/ > classes/sysctl.pp at /etc/puppet/manifests/site.pp:3 on node server > Any Help will be greatly appreciated. > > -- > 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. -- 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.
