Hi Ken:

Yes, I most definitely restarted HTTPd since I have it running over 
Passenger. Although, I do see that when I make changes to puppet.conf it 
reloads according to /var/log/messages. My puppetdb version is 1.3.2-1. I 
do have puppetdb-terminus installed via RPM like puppetdb. Here is my 
puppet.conf:

# cat /etc/puppet/puppet.conf
### File managed with puppet ###
## Module:           'puppet'
## Template source:  'MODULES/puppet/templates/puppet.conf.erb'

[main]
    # 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

    # Allow services in the 'puppet' group to access key (Foreman + proxy)
    privatekeydir = $ssldir/private_keys { group = service }
    hostprivkey = $privatekeydir/$certname.pem { mode = 640 }

    # Puppet 3.0.x requires this in both [main] and [master] - harmless on 
agents
    autosign       = $confdir/autosign.conf { mode = 664 }


[agent]
    # 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
    report      = true
    pluginsync  = true
    masterport  = 8140
    environment = prd
    certname    = my.puppetserver.com
    server      = my.puppetserver.com
    listen      = true
    splay       = false
    runinterval = 1800
    noop        = false
    graph       = true
    pluginsync  = true
### Next part of the file is managed by a different template ###
## Module:           'puppet'
## Template source:  'MODULES/puppet/templates/server/puppet.conf.erb'

[master]
    autosign       = $confdir/autosign.conf { mode = 664 }
    reports        = foreman,log,store,puppetdb
    external_nodes = /etc/puppet/node.rb
    node_terminus  = exec
    ca             = true
    ssldir         = /var/lib/puppet/ssl
    downcasefacts  = true
    storeconfigs   = true
    storeconfigs_backend = puppetdb

[prd]
    modulepath     = /etc/puppet/modules:/etc/puppet/modules/prd
    manifests      = /etc/puppet/environments/prd/manifests/site.pp

Thank you!
-Larry
On Thursday, July 25, 2013 11:00:53 AM UTC-4, Ken Barber wrote:
>
> Can you post your _full_ puppet.conf? Also - what version of PuppetDB 
> are you running, and do you have the puppetdb-terminus package 
> installed on your master? I don't think this is the issue - just 
> checking. 
>
> Also - Stupid question, but you obviously restarted 
> puppet/apache/whatever after making the changes to puppet.conf right? 
> I don't mean to insult, but you'll be amazed how often people forget 
> that :-). 
>
> On Thu, Jul 25, 2013 at 3:58 PM, Larry Long <[email protected]<javascript:>> 
> wrote: 
> > I really don't want to go back to ActiveRecord... any ideas anyone? 
> > 
> > 
> > On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long wrote: 
> >> 
> >> # cat /etc/redhat-release 
> >> CentOS release 6.4 (Final) 
> >> # puppet --version 
> >> 3.2.3 
> >> # rpm -q puppetdb 
> >> puppetdb-1.3.2-1.el6.noarch 
> >> 
> >> I am now receiving "Not collecting exported resources without 
> >> storeconfigs" for my opsview module. It was working fine on puppet 2.7 
> with 
> >> Activerecord/MySQL. I am still new to puppetdb so maybe I am missing 
> >> something. This is from puppet.conf: 
> >> 
> >>     storeconfigs   = true 
> >>     thin_storeconifgs = false 
> >>     storeconfigs_backend = puppetdb 
> >> 
> >> Any ideas? 
> >> 
> >> Thanks, 
> >> -Larry 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Puppet Users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to [email protected] <javascript:>. 
> > To post to this group, send email to 
> > [email protected]<javascript:>. 
>
> > Visit this group at http://groups.google.com/group/puppet-users. 
> > For more options, visit https://groups.google.com/groups/opt_out. 
> > 
> > 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to