Puppet users - Jul 2013 - Not collecting exported resources without storeconfigs

# 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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

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 <djslyde111@gmail.com>
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 puppet-users+unsubscribe@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> 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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

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
<djsly...@gmail.com<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 puppet-users...@googlegroups.com <javascript:>. 
> > To post to this group, send email to
puppet...@googlegroups.com<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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Maybe an issue with puppetdb? I see some weirdness, although no apparent 
errors on it.

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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Apparently it is ignoring the settings in my puppet.conf:

# puppet config --verbose --debug print|grep storeconfig
async_storeconfigs = false
storeconfigs = false
storeconfigs_backend = active_record
thin_storeconfigs = false

Researching more!

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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Well, it seems puppet config print is useless as it is incorrect with most 
values it shows. I know storeconfigs are up and running and I think its 
going to puppetdb. I am still having issues with my mod.


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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

> Well, it seems puppet config print is useless as it is incorrect with most
> values it shows. I know storeconfigs are up and running and I think its
> going to puppetdb. I am still having issues with my mod.
How do you know? The previous error you posted "Not collecting
exported resources without storeconfigs" would lead me to believe its
an error/misconfiguration somewhere in puppet, not PuppetDB - normally
it means you haven''t switched on storeconfigs in your puppet.conf, but
I''m using your puppet.conf right now and its fine :-/. You can inspect
the logs in /var/log/puppetdb/puppetdb.log ... if anything is being
sent to the app, it should show up in there.

I can easily replicate a similar failure btw, when I remove the
storeconfigs lines from puppet.conf:

Jul 26 12:11:32 puppetdb1 puppet-master[10870]: You cannot collect
without storeconfigs being set on line 3 in file
/etc/puppet/environments/prd/manifests/site.pp
Jul 26 12:11:32 puppetdb1 puppet-master[10870]: You cannot collect
exported resources without storeconfigs being set; the collection will
be ignored on line 5 in file
/etc/puppet/environments/prd/manifests/site.pp
Jul 26 12:11:32 puppetdb1 puppet-master[10870]: Not collecting
exported resources without storeconfigs

Can you show the full error in your puppet master logs like above?
Just curious really to see if there is anything else we are missing.
Show the full puppet-master dump if you can, after a restart if
possible. I''m tempted to ask you for a full debug & trace output at
some point as well - not sure if that will give us any more info.

Also - since reporting and storeconfigs are separate sub-systems I''m
really curious to see if you are getting reports sent to PuppetDB as
well ... as you have this in your configuration. You should get log
lines in puppetdb.log that look something like this:

2013-07-26 12:15:48,114 INFO  [command-proc-46] [puppetdb.command]
[a4fc3c90-6f90-43a8-937b-0865378f1e54] [store report (EXPERIMENTAL!)]
puppet v3.2.2 - puppetdb1.vm

Perhaps if you can send me the contents of your recent puppetdb.log
that might be helpful.

> Apparently it is ignoring the settings in my puppet.conf:
>
> # puppet config --verbose --debug print|grep storeconfig
> async_storeconfigs = false
> storeconfigs = false
> storeconfigs_backend = active_record
> thin_storeconfigs = false
>
> Researching more!
It does feel like this is the case to me (that configuration is being
ignored) but I cannot replicate this with your configuration yet. BTW
you probably want to use:

# puppet master --configprint all | grep store
async_storeconfigs = false
catalog_cache_terminus = store_configs
reports = store,puppetdb
storeconfigs = true
storeconfigs_backend = puppetdb
thin_storeconfigs = false
> 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:
Although I guess I also wanted to make sure the terminus gets loaded,
which only occurs after a restart of the application.

Can you send me some more files as well, I''m curious about:

/etc/puppet/routes.yaml
/etc/puppet/puppetdb.conf

Neither of these files are overly complicated or should cause trouble,
I''m mainly curious to see if there is anything extra in your
routes.yaml causing this. Also - what version of Puppet are you using?

ken.

PS. BTW looking at your environment setup:

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

That should be ''manifest'' not ''manifests''.

-- 
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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Silly me. You are right. I should be using puppet master:

#  puppet master --configprint all | grep store
async_storeconfigs = false
catalog_cache_terminus = store_configs
reports = foreman,log,store,puppetdb
storeconfigs = true
storeconfigs_backend = puppetdb
thin_storeconfigs = false

Also, you are right about my typo with manifests instead of manifest. 
Sometimes I guess you just need a second set of eyes! It didn''t error
out,
but changing that and it looks like my module with storeconfigs is now 
working. Thank you!!!
-Larry

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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

> Also, you are right about my typo with manifests instead of manifest.
> Sometimes I guess you just need a second set of eyes!
Ain''t that the truth.
> It didn''t error out,
> but changing that and it looks like my module with storeconfigs is now
> working. Thank you!!!
Oh good to hear :-). Do you think that was the only problem? It
doesn''t sound like it should have solved it on its own, thats all. Not
that I''m complaining :-).

ken.

-- 
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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.