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 <makhan...@gmail.com> 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 <aaron.grew...@gmail.com>
> wrote:
>>
>> Run puppet --genconfig for an example.
>>
>>
>> On Thu, Dec 29, 2011 at 11:12 AM, Mohammad Khan <makhan...@gmail.com>
>> wrote:
>> > same results after changes , what should i add into master section?
>> >
>> >
>> > On Thu, Dec 29, 2011 at 2:08 PM, Aaron Grewell <aaron.grew...@gmail.com>
>> > 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 <makhan...@gmail.com>
>> >> 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
>> >> >> <makhan...@gmail.com>
>> >> >> 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
>> >> >> > <justin.stol...@gmail.com>
>> >> >> > 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 <makhan...@gmail.com> 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.
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > 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.
>> >>
>> >
>> >
>> >
>> > --
>> > 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.
>>
>
>
>
> --
> 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.

Reply via email to