Hi,
I''ve enabled storeconfigs on my puppetmaster:
[puppetmasterd]
storeconfigs = true
thin_storeconfigs = true
dbadapter = sqlite3
dblocation = $statedir/clientconfigs.sqlite3
And added this code to one of my nodes:
@@file { "/tmp/foo": content => "fjskfjs\n", tag =>
"foofile", }
File <<| tag == ''foofile'' |>>
But, the problem is that file is not being realized...
I use puppetmaster on Passenger/Apache... File
$statedir/clientconfigs.sqlite3 isn''t being created, I''ve
created it
manually, gave permission to puppet master user, but nothing, file is
still 0 bytes...
Any ideas?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Martin Alfke
2013-Jan-14 18:55 UTC
Re: [Puppet Users] storeconfigs and exported resources?
Hi Jkov, On 14.01.2013, at 19:03, Jakov Sosic <jsosic@srce.hr> wrote:> Hi, > > > I''ve enabled storeconfigs on my puppetmaster: > > [puppetmasterd] > storeconfigs = true > thin_storeconfigs = true > dbadapter = sqlite3 > dblocation = $statedir/clientconfigs.sqlite3Have you restarted your puppetmaster after doing the configuration changes? Is the ruby-sqlite extension installed? - Martin> > > And added this code to one of my nodes: > > @@file { "/tmp/foo": content => "fjskfjs\n", tag => "foofile", } > File <<| tag == ''foofile'' |>> > > But, the problem is that file is not being realized... > > > I use puppetmaster on Passenger/Apache... File > $statedir/clientconfigs.sqlite3 isn''t being created, I''ve created it > manually, gave permission to puppet master user, but nothing, file is > still 0 bytes... > > > > Any ideas? > > > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 01/14/2013 07:55 PM, Martin Alfke wrote:>> I''ve enabled storeconfigs on my puppetmaster: >> >> [puppetmasterd] >> storeconfigs = true >> thin_storeconfigs = true >> dbadapter = sqlite3 >> dblocation = $statedir/clientconfigs.sqlite3 > > Have you restarted your puppetmaster after doing the configuration changes? > Is the ruby-sqlite extension installed?Yes, I''ve restarted puppetmaster (httpd). sqlite3-ruby rubygem is installed. Should I maybe install sqlite rubygem? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
David Schmitt
2013-Jan-14 21:01 UTC
Re: [Puppet Users] storeconfigs and exported resources?
On 2013-01-14 20:12, Jakov Sosic wrote:> On 01/14/2013 07:55 PM, Martin Alfke wrote: > >>> I''ve enabled storeconfigs on my puppetmaster: >>> >>> [puppetmasterd] >>> storeconfigs = true >>> thin_storeconfigs = true >>> dbadapter = sqlite3 >>> dblocation = $statedir/clientconfigs.sqlite3 >> >> Have you restarted your puppetmaster after doing the configuration changes? >> Is the ruby-sqlite extension installed? > > Yes, I''ve restarted puppetmaster (httpd). > > sqlite3-ruby rubygem is installed. Should I maybe install sqlite rubygem? >You also need to run the puppetmaster with --db-migrate (or similar) once. D. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 01/14/2013 10:01 PM, David Schmitt wrote:> You also need to run the puppetmaster with --db-migrate (or similar) once.Tried, but didn''t help either... :-/ If only I had a way to debug it... No errors in log, nothing... -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 01/15/2013 01:22 AM, Jakov Sosic wrote:> On 01/14/2013 10:01 PM, David Schmitt wrote: > >> You also need to run the puppetmaster with --db-migrate (or similar) >> once. > > Tried, but didn''t help either... :-/ If only I had a way to debug it... > No errors in log, nothing...OK, I''ve switched to MySQL backend for storeconfigs, but still nothing... I just don''t get it, what am I doing wrong? Can I debug this somehow? Any idea? This is my new puppet.conf on master: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl modulepath = $confdir/environments/$environment/modules:$confdir/environments/$environment/forge:$confdir/modules:/usr/share/puppet/modules [production] manifest = $confdir/manifests/site.pp [dev] manifest = $confdir/manifests/site.pp [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig environment = dev [puppetmasterd] storeconfigs = true thin_storeconfigs = true dbadapter = mysql dbname = storeconfigs dbuser = puppet dbpassword = foobar dbserver = localhost dbsocket = /var/lib/mysql/mysql.sock ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY I''ve tried connecting through localhost and everything works fine... This is my node manifest: @@file { "/tmp/foo": content => "fjskfjs\n", tag => ''bla'' } File <<| tag == ''bla'' |>> but the file is never generated, and mysql database has no tables in it :( -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 01/19/2013 03:57 AM, Jakov Sosic wrote:> I''ve tried connecting through localhost and everything works fine... > > This is my node manifest: > > @@file { "/tmp/foo": content => "fjskfjs\n", tag => ''bla'' } > File <<| tag == ''bla'' |>> > > > but the file is never generated, and mysql database has no tables in it :(Hm, maybe this has to do something with my issue? http://links.puppetlabs.com/activerecord-deprecation Should I move to puppetdb instantly? I''m on puppet 3.0.2. -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Yes, if you want to use exported resource this is the current endorsed path. On Sat, Jan 19, 2013 at 3:01 AM, Jakov Sosic <jsosic@srce.hr> wrote:> On 01/19/2013 03:57 AM, Jakov Sosic wrote: > >> I''ve tried connecting through localhost and everything works fine... >> >> This is my node manifest: >> >> @@file { "/tmp/foo": content => "fjskfjs\n", tag => ''bla'' } >> File <<| tag == ''bla'' |>> >> >> >> but the file is never generated, and mysql database has no tables in it :( > > > > Hm, maybe this has to do something with my issue? > > http://links.puppetlabs.com/activerecord-deprecation > > > Should I move to puppetdb instantly? I''m on puppet 3.0.2. > > > > -- > Jakov Sosic > www.srce.unizg.hr > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 01/19/2013 04:26 AM, Ken Barber wrote:> Yes, if you want to use exported resource this is the current endorsed path.Thank you for your answer. I did set up puppetdb as described in official documentation, and my puppet.conf now looks like: [puppetmasterd] storeconfigs = true thin_storeconfigs = false storeconfigs_backend = puppetdb ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY But, I''m still getting one big zero from exported resources :( Looking at puppetdb.log, I see only "replacing facts" but never "replacing catalog"... So back to square one :-/ -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 01/19/2013 05:35 AM, Jakov Sosic wrote:> On 01/19/2013 04:26 AM, Ken Barber wrote: > >> Yes, if you want to use exported resource this is the current endorsed >> path. > > Thank you for your answer. > > I did set up puppetdb as described in official documentation, and my > puppet.conf now looks like: > > [puppetmasterd] > storeconfigs = true > thin_storeconfigs = false > storeconfigs_backend = puppetdb > ssl_client_header = SSL_CLIENT_S_DN > ssl_client_verify_header = SSL_CLIENT_VERIFY > > But, I''m still getting one big zero from exported resources :( > > Looking at puppetdb.log, I see only "replacing facts" but never > "replacing catalog"... So back to square one :-/I''ve found this one googling around: http://www.mentby.com/Group/puppet-users/puppetdb-indicated-only-facts-were-replaced-no-sign-of-catalog.html But I don''t see the solution... :) -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 01/19/2013 05:44 AM, Jakov Sosic wrote:> On 01/19/2013 05:35 AM, Jakov Sosic wrote: >> On 01/19/2013 04:26 AM, Ken Barber wrote: >> >>> Yes, if you want to use exported resource this is the current endorsed >>> path. >> >> Thank you for your answer. >> >> I did set up puppetdb as described in official documentation, and my >> puppet.conf now looks like: >> >> [puppetmasterd] >> storeconfigs = true >> thin_storeconfigs = false >> storeconfigs_backend = puppetdb >> ssl_client_header = SSL_CLIENT_S_DN >> ssl_client_verify_header = SSL_CLIENT_VERIFY >> >> But, I''m still getting one big zero from exported resources :( >> >> Looking at puppetdb.log, I see only "replacing facts" but never >> "replacing catalog"... So back to square one :-/ > > I''ve found this one googling around: > > http://www.mentby.com/Group/puppet-users/puppetdb-indicated-only-facts-were-replaced-no-sign-of-catalog.html > > > > But I don''t see the solution... :)Still no help? :-/ Any idea how should I approach to debugging this ? -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On 02/01/2013 11:45 PM, Jakov Sosic wrote:>> But I don''t see the solution... :) > > Still no help? :-/ Any idea how should I approach to debugging this ?OK, after i put this into my routes.yaml: catalog: cache: puppetdb lines in the puppetdb.log with "[replace catalog]" finally started to appear. But, still nothing with exported resources... they just don''t get collected... -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Here is the documentation for wiring up the puppetmaster to puppetdb: http://docs.puppetlabs.com/puppetdb/1.1/connect_puppet_master.html Make sure you follow all of these steps and see how you go. Also remember to restart your puppetmaster :-). It sounds like at least your routes.yaml isn''t complete ... but that is more of a facts thing. If that doesn''t help, give us the following info: * Version of Puppet * OS version/distro * Are you using the authoritative puppetdb packages we host, if so what versions of puppetdb and puppetdb-terminus do you have installed? * Maybe provide us with the contents of your puppet.conf and puppetdb.conf as well. ken. On Sat, Feb 2, 2013 at 12:18 AM, Jakov Sosic <jsosic@srce.hr> wrote:> On 02/01/2013 11:45 PM, Jakov Sosic wrote: > >>> But I don''t see the solution... :) >> >> Still no help? :-/ Any idea how should I approach to debugging this ? > > OK, after i put this into my routes.yaml: > > catalog: > cache: puppetdb > > lines in the puppetdb.log with "[replace catalog]" finally started to > appear. > > > But, still nothing with exported resources... they just don''t get > collected... > > -- > 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?hl=en. > 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On 02/02/2013 12:31 PM, Ken Barber wrote:> Here is the documentation for wiring up the puppetmaster to puppetdb: > > http://docs.puppetlabs.com/puppetdb/1.1/connect_puppet_master.html > > Make sure you follow all of these steps and see how you go. Also > remember to restart your puppetmaster :-). It sounds like at least > your routes.yaml isn''t complete ... but that is more of a facts thing. > > If that doesn''t help, give us the following info: > * Version of Puppet > * OS version/distro > * Are you using the authoritative puppetdb packages we host, if so > what versions of puppetdb and puppetdb-terminus do you have installed? > * Maybe provide us with the contents of your puppet.conf and > puppetdb.conf as well.I followed the howto, but exported resources just don''t get applied on agents... # cat /etc/puppet/puppet.conf [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl modulepath $confdir/environments/$environment/modules:$confdir/modules:/usr/share/puppet/modules [production] manifest = $confdir/manifests/site.pp [dev] manifest = $confdir/manifests/site.pp [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig environment = dev [puppetmasterd] storeconfigs = true thin_storeconfigs = false storeconfigs_backend = puppetdb ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY # cat /etc/puppet/routes.yaml --- master: facts: terminus: puppetdb cache: yaml catalog: cache: puppetdb # cat /etc/puppetdb/conf.d/config.ini [global] vardir = /var/lib/puppetdb logging-config = /etc/puppetdb/conf.d/../log4j.properties resource-query-limit = 20000 Packages: # rpm -qa | grep puppet | sort puppet-3.0.2-1.el6.noarch puppetdb-1.1.0-1.el6.noarch puppetdb-terminus-1.1.0-1.el6.noarch puppetlabs-release-6-6.noarch puppet-server-3.0.2-1.el6.noarch This is my node example code, that doesn''t work: node ''somenode'' { @@file { "/tmp/foo": content => "fjskfjs\n", tag => ''bla'' } File <<| tag == ''bla'' |>> } What am I missing here?! -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
> I followed the howto, but exported resources just don''t get applied on > agents...The documentation is fairly precise, looking at your configuration snippet:> # cat /etc/puppet/puppet.conf > [main] > logdir = /var/log/puppet > rundir = /var/run/puppet > ssldir = $vardir/ssl > modulepath > $confdir/environments/$environment/modules:$confdir/modules:/usr/share/puppet/modules > [production] > manifest = $confdir/manifests/site.pp > [dev] > manifest = $confdir/manifests/site.pp > [agent] > classfile = $vardir/classes.txt > localconfig = $vardir/localconfig > environment = dev > [puppetmasterd] > storeconfigs = true > thin_storeconfigs = false > storeconfigs_backend = puppetdb > ssl_client_header = SSL_CLIENT_S_DN > ssl_client_verify_header = SSL_CLIENT_VERIFYAnd then comparing it to the ''Edit puppet.conf'' section: http://docs.puppetlabs.com/puppetdb/1.1/connect_puppet_master.html#edit-puppetconf You can see that the section is called [master] not [puppetmasterd]. This needs to be changed, and then you''ll need to restart your puppetmaster. The [puppetmasterd] section hasn''t been used since 0.25.x I think, although I could be wrong. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Also your routes.yaml doesn''t match the documentation I gave you either, nor should you be setting thin_storeconfigs any more as stated in another section. You probably want to take a fresh top to bottom look through the documentation, like I said its fairly precise and you shouldn''t go stray if you follow it step by step: http://docs.puppetlabs.com/puppetdb/1.1/connect_puppet_master.html ken. On Sun, Feb 3, 2013 at 10:11 PM, Ken Barber <ken@puppetlabs.com> wrote:>> I followed the howto, but exported resources just don''t get applied on >> agents... > > The documentation is fairly precise, looking at your configuration snippet: > >> # cat /etc/puppet/puppet.conf >> [main] >> logdir = /var/log/puppet >> rundir = /var/run/puppet >> ssldir = $vardir/ssl >> modulepath >> $confdir/environments/$environment/modules:$confdir/modules:/usr/share/puppet/modules >> [production] >> manifest = $confdir/manifests/site.pp >> [dev] >> manifest = $confdir/manifests/site.pp >> [agent] >> classfile = $vardir/classes.txt >> localconfig = $vardir/localconfig >> environment = dev >> [puppetmasterd] >> storeconfigs = true >> thin_storeconfigs = false >> storeconfigs_backend = puppetdb >> ssl_client_header = SSL_CLIENT_S_DN >> ssl_client_verify_header = SSL_CLIENT_VERIFY > > And then comparing it to the ''Edit puppet.conf'' section: > > http://docs.puppetlabs.com/puppetdb/1.1/connect_puppet_master.html#edit-puppetconf > > You can see that the section is called [master] not [puppetmasterd]. > This needs to be changed, and then you''ll need to restart your > puppetmaster. > > The [puppetmasterd] section hasn''t been used since 0.25.x I think, > although I could be wrong. > > 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On 02/03/2013 10:11 PM, Ken Barber wrote:> You can see that the section is called [master] not [puppetmasterd]. > This needs to be changed, and then you''ll need to restart your > puppetmaster.Damn...... I''m really ashamed now :-/ -- Jakov Sosic www.srce.unizg.hr -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On 02/03/2013 10:19 PM, Ken Barber wrote:> Also your routes.yaml doesn''t match the documentation I gave you > either, nor should you be setting thin_storeconfigs any more as stated > in another section.Yeah, but if I remove the section for catalog, I don''t get "replacing catalogs" in puppetdb log... But since my initial problem was wrong section name in puppet.conf, maybe I can do without storing catalog cache in puppetdb? Because, things work as a charm now that [puppetmasterd] is renamed to [master] BTW documentation says that thin_storeconfigs must be set to false or removed, mine were set to false so that was OK I presume. Thank you very very much... what a bad typo on my side :-/ -- Jakov Sosic www.srce.unizg.hr -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
>> Also your routes.yaml doesn''t match the documentation I gave you >> either, nor should you be setting thin_storeconfigs any more as stated >> in another section. > > Yeah, but if I remove the section for catalog, I don''t get "replacing > catalogs" in puppetdb log... But since my initial problem was wrong section > name in puppet.conf, maybe I can do without storing catalog cache in > puppetdb? Because, things work as a charm now that [puppetmasterd] is > renamed to [master]This should be the case, take a look here: https://gist.github.com/4706585 You can see without those lines in routes.yaml it still sends a replace catalog. You simply shouldn''t need that part. If for some reason you do, then something isn''t right, and we are probably better to drill into the ''why'' now rather than later :-). Please, if you can take a second look, and try removing the lines to confirm that would be appreciated. I just simply cannot replicate your case.> BTW documentation says that thin_storeconfigs must be set to false or > removed, mine were set to false so that was OK I presume.Okay, fair enough.> Thank you very very much... what a bad typo on my side :-/No problemo :-). 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On 02/04/2013 02:02 PM, Ken Barber wrote:> You can see without those lines in routes.yaml it still sends a > replace catalog. You simply shouldn''t need that part. If for some > reason you do, then something isn''t right, and we are probably better > to drill into the ''why'' now rather than later :-). Please, if you can > take a second look, and try removing the lines to confirm that would > be appreciated. I just simply cannot replicate your case.Hi, I''ve taken second look, and you''re right. Without that lines, "replace catalog" is called. So, my routes.yaml now looks like the one in documentation, like this: --- master: facts: terminus: puppetdb cache: yaml>> Thank you very very much... what a bad typo on my side :-/ > > No problemo :-).Also, please note that puppetmasterd section is still in the official documentation, like for example here: http://docs.puppetlabs.com/guides/exported_resources.html So that''s what got me on the wrong track in the first place. Thank you for your help and for pointing obvious mistake on my part :) -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
> Also, please note that puppetmasterd section is still in the official > documentation, like for example here: > > http://docs.puppetlabs.com/guides/exported_resources.html > > So that''s what got me on the wrong track in the first place.Aaah - righto - well I''ve raised a pull request on that, our docs team just did a quick scan and it looks like the last instance of it: https://github.com/puppetlabs/puppet-docs/pull/134 Hopefully this should be fixed on the public site soon. Thanks for the heads up Jakov :-). 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
That hash been changed now on docs.puppetlabs.com Jakov, again ... thanks. On Wed, Feb 6, 2013 at 8:56 PM, Ken Barber <ken@puppetlabs.com> wrote:>> Also, please note that puppetmasterd section is still in the official >> documentation, like for example here: >> >> http://docs.puppetlabs.com/guides/exported_resources.html >> >> So that''s what got me on the wrong track in the first place. > > Aaah - righto - well I''ve raised a pull request on that, our docs team > just did a quick scan and it looks like the last instance of it: > > https://github.com/puppetlabs/puppet-docs/pull/134 > > Hopefully this should be fixed on the public site soon. Thanks for the > heads up Jakov :-). > > 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On 02/07/2013 02:35 PM, Ken Barber wrote:> That hash been changed now on docs.puppetlabs.com Jakov, again ... thanks.No problem, always glad to help back :) -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.