Re: [Puppet Users] Re: Nagios with Hiera
Should be possible by no puppetmaster, via git copy every /etc/puppet to your instances. Just use different hiera yaml/etc. I dont have time to build it now. Any body have done with nagios by hiera? On Tue, Dec 16, 2014 at 3:55 AM, Tony Thayer wrote: > > How would using nagios resources with Hiera differ from using it with > other resource types? > > > On Monday, December 15, 2014 12:22:47 AM UTC-8, Heriyanto wrote: >> >> Hi All.. >> >> Is that any example Nagios module without storeconfig but using Hiera in >> RHEL? >> Because don't have time now for build the module need finish deployment >> about 1 week :), >> I try search via puppetforge so far I have only found with storeconfig >> for RHEL, but for debian found by dhoppe. Anybody have an experienced using >> dhoppe module for RHEL? >> >> Thanks for any help. >> >> Regards, >> Heriyanto >> > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/fd3669eb-2f58-421a-a9bc-29d2e752705c%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/fd3669eb-2f58-421a-a9bc-29d2e752705c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAPMu_m69qbqkxN6vmPKTBMfswyiGNgxmE2%3DYb%3DJS3LwXgV3t5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Nagios with Hiera
Hi All.. Is that any example Nagios module without storeconfig but using Hiera in RHEL? Because don't have time now for build the module need finish deployment about 1 week :), I try search via puppetforge so far I have only found with storeconfig for RHEL, but for debian found by dhoppe. Anybody have an experienced using dhoppe module for RHEL? Thanks for any help. Regards, Heriyanto -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAPMu_m77Ycjcqz0BiNoB1kMCmzHy0ga5cZkw8r5RiO_bNR%3Ds6g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: PuppetDB database tunning
Already update to 1.3.1, the old database still there. Theres script for remove it via postgres script or puppet stanza to clean this such as after 30days old? On Wed, May 29, 2013 at 12:19 PM, shell heriyanto wrote: > Hi Ken thanks for your reply, > We using Postgresql, we just have about 150 puppet agent, and for 130 > agent its just run once per day, every day its take about 150MB. > We using puppetDB 1.1.0. I will try to update puppetDB today. > > > On Tue, May 28, 2013 at 10:23 PM, Ken Barber wrote: > >> What kind of database is this? Postgresql or the built-in HSQLDB? And >> - how are you calculating the database size? >> >> On Tue, May 28, 2013 at 12:19 PM, shell heriyanto >> wrote: >> > no efect, this my configuration: >> > >> > gc-interval = 60 >> > node-ttl = 30m >> > node-purge-ttl = 30m >> > report-ttl = 30m >> > >> > I make ttl fast to see the change but still, my database still grow >> bigger. >> > Its need to remove the database fast and create again, to make this >> work? >> > how ttl work? is it just count when we do add the option, so the older >> > database still save? >> > >> > thanks for any comment. >> > >> > >> > >> > On Thu, May 23, 2013 at 9:50 AM, shell heriyanto < >> shell.heriya...@gmail.com> >> > wrote: >> >> >> >> This what i'am find, thank you Klavs. >> >> >> >> >> >> On Wed, May 22, 2013 at 9:44 PM, Klavs Klavsen >> wrote: >> >>> >> >>> http://docs.puppetlabs.com/puppetdb/1.3/maintain_and_tune.html >> >>> >> >>> Den onsdag den 22. maj 2013 09.56.36 UTC+2 skrev Heriyanto: >> >>>> >> >>>> Hi, >> >>>> >> >>>> I've been use puppetdb about 6 months ago, and now the database more >> >>>> than 6gigs >> >>>> Is that any way to "recycle" database? the data on database more than >> >>>> 30days >> >>>> removed, I try to find is that any option in puppetDB so far, or we >> need >> >>>> to tune from database side(i use postgresql)? >> >>>> >> >>>> Thanks for any comment. >> >>>> >> >>>> Best regards, >> >>>> Heriyanto >> >>> >> >>> -- >> >>> 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+unsubscr...@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+unsubscr...@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+unsubscr...@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+unsubscr...@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.
Re: [Puppet Users] Re: PuppetDB database tunning
Hi Ken thanks for your reply, We using Postgresql, we just have about 150 puppet agent, and for 130 agent its just run once per day, every day its take about 150MB. We using puppetDB 1.1.0. I will try to update puppetDB today. On Tue, May 28, 2013 at 10:23 PM, Ken Barber wrote: > What kind of database is this? Postgresql or the built-in HSQLDB? And > - how are you calculating the database size? > > On Tue, May 28, 2013 at 12:19 PM, shell heriyanto > wrote: > > no efect, this my configuration: > > > > gc-interval = 60 > > node-ttl = 30m > > node-purge-ttl = 30m > > report-ttl = 30m > > > > I make ttl fast to see the change but still, my database still grow > bigger. > > Its need to remove the database fast and create again, to make this work? > > how ttl work? is it just count when we do add the option, so the older > > database still save? > > > > thanks for any comment. > > > > > > > > On Thu, May 23, 2013 at 9:50 AM, shell heriyanto < > shell.heriya...@gmail.com> > > wrote: > >> > >> This what i'am find, thank you Klavs. > >> > >> > >> On Wed, May 22, 2013 at 9:44 PM, Klavs Klavsen > wrote: > >>> > >>> http://docs.puppetlabs.com/puppetdb/1.3/maintain_and_tune.html > >>> > >>> Den onsdag den 22. maj 2013 09.56.36 UTC+2 skrev Heriyanto: > >>>> > >>>> Hi, > >>>> > >>>> I've been use puppetdb about 6 months ago, and now the database more > >>>> than 6gigs > >>>> Is that any way to "recycle" database? the data on database more than > >>>> 30days > >>>> removed, I try to find is that any option in puppetDB so far, or we > need > >>>> to tune from database side(i use postgresql)? > >>>> > >>>> Thanks for any comment. > >>>> > >>>> Best regards, > >>>> Heriyanto > >>> > >>> -- > >>> 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+unsubscr...@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+unsubscr...@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+unsubscr...@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+unsubscr...@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.
Re: [Puppet Users] Re: PuppetDB database tunning
no efect, this my configuration: gc-interval = 60 node-ttl = 30m node-purge-ttl = 30m report-ttl = 30m I make ttl fast to see the change but still, my database still grow bigger. Its need to remove the database fast and create again, to make this work? how ttl work? is it just count when we do add the option, so the older database still save? thanks for any comment. On Thu, May 23, 2013 at 9:50 AM, shell heriyanto wrote: > This what i'am find, thank you Klavs. > > > On Wed, May 22, 2013 at 9:44 PM, Klavs Klavsen wrote: > >> http://docs.puppetlabs.com/puppetdb/1.3/maintain_and_tune.html >> >> Den onsdag den 22. maj 2013 09.56.36 UTC+2 skrev Heriyanto: >> >>> Hi, >>> >>> I've been use puppetdb about 6 months ago, and now the database more >>> than 6gigs >>> Is that any way to "recycle" database? the data on database more than >>> 30days >>> removed, I try to find is that any option in puppetDB so far, or we need >>> to tune from database side(i use postgresql)? >>> >>> Thanks for any comment. >>> >>> Best regards, >>> Heriyanto >>> >> -- >> 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+unsubscr...@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+unsubscr...@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.
Re: [Puppet Users] Re: facter wrong report
Hi Ellison, thank you for help, theres some bug i think in that version, now i use 1.6.18-3.el6 its solved. On Wed, May 22, 2013 at 11:49 PM, Ellison Marks wrote: > I'm on 1.7.1, Facter finds xen fine. > > is_virtual => true > virtual => xen > > odd part is I'm not sure the detection method has changed since 1.6. It > just check if any of these paths exist: > > > "/proc/sys/xen", "/sys/bus/xen", "/proc/xen" > > > On Wednesday, May 22, 2013 1:06:02 AM UTC-7, Heriyanto wrote: >> >> Hi, >> >> I just check from my virtual machine: >> [root@host ~]# facter|grep virtual >> is_virtual => false >> virtual => physical >> >> My operating system is CentOS 6.4 running as domu, running under dom0 >> CentOS 5.9. >> I use facter-1.6.6-1.el6. Its bug? >> >> Thanks for any comment. >> >> Regards, >> Heriyanto >> >> -- > 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+unsubscr...@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+unsubscr...@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.
Re: [Puppet Users] Re: PuppetDB database tunning
This what i'am find, thank you Klavs. On Wed, May 22, 2013 at 9:44 PM, Klavs Klavsen wrote: > http://docs.puppetlabs.com/puppetdb/1.3/maintain_and_tune.html > > Den onsdag den 22. maj 2013 09.56.36 UTC+2 skrev Heriyanto: > >> Hi, >> >> I've been use puppetdb about 6 months ago, and now the database more than >> 6gigs >> Is that any way to "recycle" database? the data on database more than >> 30days >> removed, I try to find is that any option in puppetDB so far, or we need >> to tune from database side(i use postgresql)? >> >> Thanks for any comment. >> >> Best regards, >> Heriyanto >> > -- > 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+unsubscr...@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+unsubscr...@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.
[Puppet Users] facter wrong report
Hi, I just check from my virtual machine: [root@host ~]# facter|grep virtual is_virtual => false virtual => physical My operating system is CentOS 6.4 running as domu, running under dom0 CentOS 5.9. I use facter-1.6.6-1.el6. Its bug? Thanks for any comment. Regards, Heriyanto -- 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+unsubscr...@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.
[Puppet Users] PuppetDB database tunning
Hi, I've been use puppetdb about 6 months ago, and now the database more than 6gigs Is that any way to "recycle" database? the data on database more than 30days removed, I try to find is that any option in puppetDB so far, or we need to tune from database side(i use postgresql)? Thanks for any comment. Best regards, Heriyanto -- 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+unsubscr...@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.
Re: [Puppet Users] Re: AWS OpsWorks announcement using Chef
I hope so, successful James.. I also have many AWS nodes. On Thu, Feb 21, 2013 at 11:44 AM, jim watts wrote: > Great. > > The company I work for is both a large AWS customer and user of puppet. > Very interested in how this progresses. > > -jim > > > On Wednesday, 20 February 2013 18:40:54 UTC+11, James Turnbull wrote: >> >> Vaidas Jablonskis wrote: >> > It makes sense for Amazon to go with something like Chef, because it is >> > more cloud oriented and it's easier to hack something up just to get it >> > up and running quicker. Chef is more like shell scripting on steroids I >> > would say, at least, that's how many people use it. >> > >> >> We're going to be talking to AWS about adding Puppet support to OpsWorks >> soon. It is our understanding from them that this is based on an >> acquisition they made of a Chef-based solution rather than an >> endorsement of Chef. >> >> More news when we have it! >> >> Thanks >> >> James >> >> -- >> James Turnbull >> 1-503-734-8571 >> To schedule a meeting with me: http://doodle.com/jamtur01 >> > -- > 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+unsubscr...@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+unsubscr...@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.
Re: [Puppet Users] Re: Error: Could not retrieve catalog from remote server: execution expired
Hi i also have this problem when working with nagios, always expire... is
that any solution for this, from puppet configuration byself? my nagios
production server can't working anymore. Even i already use puppetDB. I see
many people have same problem on the net.
Thanks,
~Heriyanto
On Thu, Jan 17, 2013 at 4:02 PM, Luke Bigum wrote:
> I'm not sure if there's a way to increase the timeout for exported
> resource reconstruction, however rather than doing a Puppet resource
> collection you can query the raw data from PuppetDB:
>
> https://github.com/dalen/puppet-puppetdbquery
>
> Here is an example a colleague of mine used to vastly speed up the catalog
> of our Nagios server. Here it queries exported 'hostgroup_member' resources
> with a specific tag, then uses the returned hash of data in a template to
> define all Nagios hostgroups:
>
> $hostgroup_members = pdbresourcequery(
> [ 'and',
> [ '=', 'tag', $nagios::params::sites ],
> [ '=', 'type', 'Nagios::Config::Hostgroup_member' ],
> [ '=', 'exported', true ]
> ]
> )
> file { $nagios::params::hostgroups_yaml:
> content => template('nagios/nagios_hostgroups.yaml.erb'),
> notify => Class['nagios::service'],
> }
>
> This cut our catalog down from over 2 minutes in compile/collect time to
> around 20-30 seconds.
>
> Hope that helps,
>
> -Luke
>
> On Wednesday, January 16, 2013 11:35:23 PM UTC, Joshua Buss wrote:
>>
>> Wow, I just found this by googling for the error message and I'm getting
>> the exact same problem.. unable to run puppet agent on the same machine
>> where I have the puppet master running.. times out on loading plugin. I'm
>> running on ubuntu server 11.10, version 2.7.1-1ubuntu3.7
>>
>> On Monday, January 7, 2013 1:19:41 PM UTC-6, Rob Smith wrote:
>>>
>>> Hi everyone,
>>>
>>> I recently ran into an issue where my puppetmaster can't run puppet on
>>> itself. It errors out with the following:
>>> Error: Could not retrieve catalog from remote server: execution expired
>>> Warning: Not using cache on failed catalog
>>> Error: Could not retrieve catalog; skipping run
>>>
>>> I'm running Puppet 3 with passanger and puppetdb (hsql). I've tried
>>> restarting puppetdb and apache to no effect. If I wipe out puppetdb, it'll
>>> work again until all 17 servers are back into the catalog and it times out
>>> from then on. The puppet master is also my nagios node so it does have a
>>> huge amount of resources to assemble.
>>>
>>> Can I configure puppet to wait longer for the catalog generation step?
>>> I've search the docs without anything standing out to me.
>>>
>>> Thanks,
>>> ~Rob
>>>
>> --
> 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/-/ffFFsG4HM0YJ.
>
> 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 unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@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.
Re: [Puppet Users] Announce: Puppet-Dashboard 1.2.14 Available
Yes its also work for me. Just need to add some permission on some folder in /usr/share/puppet-dashboard to make init.d file run On Sat, Nov 10, 2012 at 4:46 AM, Moses Mendoza wrote: > On Fri, Nov 9, 2012 at 12:54 PM, Moses Mendoza > wrote: > > On Fri, Nov 9, 2012 at 5:34 AM, Stefan Heijmans > wrote: > >> el5 was not supported, as it has an dependency on ruby 1.8.7 and el5 > comes > >> default with ruby 1.8.5. > >> now that they deliver ruby 1.8.7 with puppet 3 for el5, they perhaps can > >> also build them for el5. > > > > That is indeed true, you're right. So we did:) You should now be able > > to `yum install puppet-dashboard` on el5 hosts from the Puppet Labs > > yum repo, yum.puppetlabs.com. I also noticed dashboard wasn't quite > > happy with the older rubygems in el5, so we built rubygems-1.3.7 for > > el5 and added it to the dependencies repo on yum.puppetlabs.com as > > well (el5 has rubygems-1.3.1, el6 has 1.3.7). Worked great for me. > > Just a side note to avoid confusion: rubygems-1.3.1 is in EPEL for > el5, not core. > > > Enjoy. > > > > Moses > > -- > 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] Announce: Puppet-Dashboard 1.2.14 Available
Great..! Its that any RPM for el5? because i don't see on http://yum.puppetlabs.com/el/5/products/x86_64/. Thanks On Thu, Nov 8, 2012 at 5:36 AM, Moses Mendoza wrote: > Puppet Dashboard 1.2.14 is a bugfix release of Puppet Dashboard. > > This release is available for download at: > https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.14.tar.gz > > Debian packages are available at https://apt.puppetlabs.com > > RPM packages are available at https://yum.puppetlabs.com > > See the Verifying Puppet Download section at: > http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet > > Please report feedback via the Puppet Labs Redmine site, using an > affected version of 1.2.14: > http://projects.puppetlabs.com/projects/dashboard > > Documentation is available at: > http://docs.puppetlabs.com/dashboard/index.html > > === > ## Puppet Dashboard 1.2.14 Bug Fixes ## > === > > An error in the packaging of Puppet Dashboard 1.2.13 resulted in > several empty directories normally shipped with Puppet Dashboard > getting excluded from the source tarball and packages, e.g. 'tmp', > 'log', and 'spool'. This release is a re-packaging of Puppet Dashboard > 1.2.13 to include these directories. It includes no other changes. > > -- > 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] Puppet 3.x load balancer
Dear All, I just plan want to migrate puppetmaster from 2.6 to puppet 3.0 in production, can you give me some advice about load balancer, because now im still using mongrel. Somebody have experience migrating puppet 2.6.x or 2.7.x to puppet 3.0.x on production?. Thanks. Regards, Heriyanto -- 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] Benchmark puppetDB
Hello Chris, Thanks for your reply, i already solved this by use my production modules. But yes, its take some time to build half my of production enviroment. Thank for yours great work. Regards, Heriyanto On Thu, Oct 25, 2012 at 12:38 AM, Chris Price wrote: > Hello Heriyanto, > > Were you able to come up with something to solve your problem? We don't > currently have any sort of sample catalog that could be used to easily > benchmark the performance difference in your environment, though your > e-mail has prompted some internal discussion about how we could conceivably > provide something like that in the future. > > I suspect that if you simply time any agent run in your environment (for > an agent with a non-trivial number of resources) against legacy > storedconfigs, and then time it again with PuppetDB, you should notice some > difference (because legacy storeconfigs must synchronously insert all of > the catalog data into the database before the run completes). You could > also run your master with the "--debug" flag, which might provide you with > some timing info for the various phases of the process. > > However, the biggest benefits come when you have a master that is under > some load from concurrent agent requests. That might be a bit more tricky > to simulate in your own environment if the blog posts and other data we've > posted isn't sufficient, but we would be happy to try to help if you have > questions! > > Thanks > Chris > > > On Wednesday, October 17, 2012 5:45:07 AM UTC-7, Heriyanto wrote: > >> Hi Nan, >> >> Thank for your reply, yes that what im talking about, i can't prove just >> with link to puppet blog, >> yes you right catalog compile should give our output, do you have some >> example of one >> with large number of resources for my testing? >> >> Thank for your help >> Regards, >> >> On Tue, Oct 16, 2012 at 1:12 AM, Nan Liu wrote: >> >>> On Mon, Oct 15, 2012 at 1:41 AM, shell heriyanto >>> wrote: >>> > I know puppetDB its more faster than storeconfigs, but to replace >>> > storeconfigs with puppetDB into production server >>> > Its need more explanation than some link from puppetlabs, need prove >>> to my >>> > bos and team. >>> > For testing i just have 1 puppetmaster and 1 and 2 puppet agent, how i >>> can >>> > look different performance? >>> > Its that any idea / or complex puppet stanza to benchmark / compare >>> this >>> > with storeconfigs? >>> >>> A catalog compile should show the difference in speed (especially one >>> with large number of resources). This is discussed in the Puppet DB >>> blog post. Also Deepak has great talk at Puppet Conf discussing why >>> PuppetDB is async (which isn't something quite as easy to benchmark >>> with just 2 agents): >>> >>> http://youtu.be/xw83cRofkpM >>> >>> HTH, >>> >>> 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...@googlegroups.com. >>> To unsubscribe from this group, send email to puppet-users...@** >>> googlegroups.com. >>> >>> For more options, visit this group at http://groups.google.com/** >>> group/puppet-users?hl=en<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 view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/vTscH5wWHWEJ. > > 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] Benchmark puppetDB
Hi Nan, Thank for your reply, yes that what im talking about, i can't prove just with link to puppet blog, yes you right catalog compile should give our output, do you have some example of one with large number of resources for my testing? Thank for your help Regards, On Tue, Oct 16, 2012 at 1:12 AM, Nan Liu wrote: > On Mon, Oct 15, 2012 at 1:41 AM, shell heriyanto > wrote: > > I know puppetDB its more faster than storeconfigs, but to replace > > storeconfigs with puppetDB into production server > > Its need more explanation than some link from puppetlabs, need prove to > my > > bos and team. > > For testing i just have 1 puppetmaster and 1 and 2 puppet agent, how i > can > > look different performance? > > Its that any idea / or complex puppet stanza to benchmark / compare this > > with storeconfigs? > > A catalog compile should show the difference in speed (especially one > with large number of resources). This is discussed in the Puppet DB > blog post. Also Deepak has great talk at Puppet Conf discussing why > PuppetDB is async (which isn't something quite as easy to benchmark > with just 2 agents): > > http://youtu.be/xw83cRofkpM > > HTH, > > 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.
[Puppet Users] Benchmark puppetDB
Dear All, I know puppetDB its more faster than storeconfigs, but to replace storeconfigs with puppetDB into production server Its need more explanation than some link from puppetlabs, need prove to my bos and team. For testing i just have 1 puppetmaster and 1 and 2 puppet agent, how i can look different performance? Its that any idea / or complex puppet stanza to benchmark / compare this with storeconfigs? Regards, Thanks -- 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: puppetd --tags doesnt work for some module
Thank you, i already solved by forcing with cobbler into, environment that
i want.
On Tue, Sep 25, 2012 at 10:05 PM, jcbollinger wrote:
>
>
> On Tuesday, September 25, 2012 5:29:07 AM UTC-5, Heriyanto wrote:
>
>> Thanks for your reply john, the funny thing is:
>>
>> running on production environment with "environment=production" option on
>> puppet.conf:
>> puppetd --test --env staging # its work
>> puppetd --test --env staging --tags ntp # its work
>> puppetd --test --env staging --tags http # its doesn't work
>>
>> running on testing environment with "environment=testing" option on
>> puppet.conf:
>> puppetd --test --env staging # its work
>> puppetd --test --env staging --tags ntp # its work
>> puppetd --test --env staging --tags http # its work
>>
>> if there is something wrong with my init.pp on testing its also doesn't
>> work.
>>
>> Regards
>> thanks
>>
>>
>> On Mon, Sep 24, 2012 at 9:29 PM, jcbollinger wrote:
>>
>>>
>>>
>>> On Sunday, September 23, 2012 11:55:44 PM UTC-5, Heriyanto wrote:
>>>>
>>>> Dear All,
>>>>
>>>> I have enviroment testing, staging and production for puppet,
>>>> when i trying to test running staging on production, run command:
>>>> puppetd --test --env staging # its work
>>>> puppetd --test --env staging --tags ntp # its work
>>>> puppetd --test --env staging --tags http # its doesn't work
>>>>
>>>> Strange usually I never got a problem like this, its just not working
>>>> for one module just for http.
>>>> even i change enviroment on puppet.conf file from production into
>>>> staging.
>>>>
>>>
>>>
>>> "Doesn't work" means what? Does the agent emit an error message?
>>>
>> its just Finish applying catalog, without any changes.
>>
>>>
>>> Does anything useful show up in the master's log? If you run the agent
>>> with the --debug flag then does the additional output shed any more light
>>> on the problem?
>>>
>> Already did, but nothing error report or something wrong.
>>
>>>
>>>
>>>
>>>> I already check on the other file, like site.pp and the other file.
>>>> This working before, until i make some
>>>> change on init.pp for http module, but my changes is nothing important
>>>> related into this. Just copying some file.
>>>>
>>>>
>>> If you revert your changes does the expected function return? If so,
>>> then I have to disagree with your assertion that the changes are
>>> unimportant. If you present the old and new versions then perhaps we can
>>> figure out why the change had this unexpected effect.
>>>
>>> my change just add
>> file { "/etc/httpd/conf/magic":
>> owner => root,
>> group => apache,
>> mode => 640,
>> source => ["puppet:///http/conf/magic",
>> ],
>> notify => Service['httpd'],
>> }
>>
>>
> That change did not of itself cause the behavior you describe. Depending
> on your process, however, you may have accidentally caused other changes.
> For example, if you keep your manifests in a version control system and you
> work with a local copy, then perhaps you committed additional changes along
> with that change. Or could someone else have made a change that caused the
> result you report?
>
> Alternatively, are you certain that the exact command you are now issuing
> produced different results in the past? For example, I find it slightly
> suspicious that you are using "--env" instead of "--environment",
> especially in light of the new information about the affect of setting the
> environment in puppet.conf.
>
> You can test what environment you're getting by adding this to your
> site.pp:
>
> notify { 'my environment':
> message => "My environment is ${environment}."
> }
>
> My best guess at this point is that you do not declare anything tagged
> with "http" in environment "production", whereas in some other
> environments, including "testing", you do. If you do not otherwise declare
> an environment for a node then it is placed in environment "production".
>
>
> John
>
> --
> 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/-/aXx0xpS43PsJ.
>
> 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] Re: puppetd --tags doesnt work for some module
Thanks for your reply john, the funny thing is:
running on production environment with "environment=production" option on
puppet.conf:
puppetd --test --env staging # its work
puppetd --test --env staging --tags ntp # its work
puppetd --test --env staging --tags http # its doesn't work
running on testing environment with "environment=testing" option on
puppet.conf:
puppetd --test --env staging # its work
puppetd --test --env staging --tags ntp # its work
puppetd --test --env staging --tags http # its work
if there is something wrong with my init.pp on testing its also doesn't
work.
Regards
thanks
On Mon, Sep 24, 2012 at 9:29 PM, jcbollinger wrote:
>
>
> On Sunday, September 23, 2012 11:55:44 PM UTC-5, Heriyanto wrote:
>>
>> Dear All,
>>
>> I have enviroment testing, staging and production for puppet,
>> when i trying to test running staging on production, run command:
>> puppetd --test --env staging # its work
>> puppetd --test --env staging --tags ntp # its work
>> puppetd --test --env staging --tags http # its doesn't work
>>
>> Strange usually I never got a problem like this, its just not working for
>> one module just for http.
>> even i change enviroment on puppet.conf file from production into staging.
>>
>
>
> "Doesn't work" means what? Does the agent emit an error message?
>
its just Finish applying catalog, without any changes.
>
> Does anything useful show up in the master's log? If you run the agent
> with the --debug flag then does the additional output shed any more light
> on the problem?
>
Already did, but nothing error report or something wrong.
>
>
>
>> I already check on the other file, like site.pp and the other file. This
>> working before, until i make some
>> change on init.pp for http module, but my changes is nothing important
>> related into this. Just copying some file.
>>
>>
> If you revert your changes does the expected function return? If so, then
> I have to disagree with your assertion that the changes are unimportant.
> If you present the old and new versions then perhaps we can figure out why
> the change had this unexpected effect.
>
> my change just add
file { "/etc/httpd/conf/magic":
owner => root,
group => apache,
mode => 640,
source => ["puppet:///http/conf/magic",
],
notify => Service['httpd'],
}
> John
>
> --
> 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/-/eAEDuIko4TsJ.
> 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] puppetd --tags doesnt work for some module
Dear All, I have enviroment testing, staging and production for puppet, when i trying to test running staging on production, run command: puppetd --test --env staging # its work puppetd --test --env staging --tags ntp # its work puppetd --test --env staging --tags http # its doesn't work Strange usually I never got a problem like this, its just not working for one module just for http. even i change enviroment on puppet.conf file from production into staging. I already check on the other file, like site.pp and the other file. This working before, until i make some change on init.pp for http module, but my changes is nothing important related into this. Just copying some file. thank for any help Regards -- 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] "Could not find dependency Package" even the package already theres.
asterisk package already installed. I don't plan installation for this package
managed by puppet.
just want manage the file configuration.
it come up when i yum search.
actually how "require => Package" working? its checking to repos or into system?
Thanks
On 07/31/2012 03:32 PM, Marc Lucke wrote:
> On 31/07/2012, at 6:25 PM, heriyanto wrote:
>
>> Dear All,
>>
>> I just do something simple just want to copy file, this my syntax,
>>
>>class asterisk::conf {
>>file { "/etc/asterisk/extensions.conf":
>>owner => asterisk,
>>group => asterisk,
>>mode=> 644,
>>source => "puppet:///modules/asterisk/extensions.conf",
>>require => Package["asterisk"],
>>
>> this one doesn't work require => Package["asterisk"], the package
>> already installed.
>> but when i trying with vim as name package its work, even i already
>> remove the package.
>> something wrong? i never found this before on puppet. Thanks.
> do you have something like:
>
> package { asterisk: ensure => installed …. }
>
> if you search your repos for asterisk does it come up?
>
--
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] "Could not find dependency Package" even the package already theres.
Dear All,
I just do something simple just want to copy file, this my syntax,
class asterisk::conf {
file { "/etc/asterisk/extensions.conf":
owner => asterisk,
group => asterisk,
mode=> 644,
source => "puppet:///modules/asterisk/extensions.conf",
require => Package["asterisk"],
this one doesn't work require => Package["asterisk"], the package
already installed.
but when i trying with vim as name package its work, even i already
remove the package.
something wrong? i never found this before on puppet. Thanks.
Best regards,
Heriyanto
--
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 class not working after use augeas-0.10.0-3
Thank you, Dom, now its working good, epel already release new puppet and resolved my issue. On 05/04/2012 03:31 PM, Dominic Cleal wrote: On 04/05/12 04:57, heriyanto wrote: Yes nice.. its work thank you Dominic, but its still execute even its already changed its normal for new augeas? because for old augeas not trying to change if already change. "returns: executed successfully" Which version of Puppet are you using? Bug #11414 affected all Puppet when used with Augeas 0.10.0, which made the resources "run" on every single run, but never change things. http://projects.puppetlabs.com/issues/11414 This was fixed in Puppet 2.7.10, though I'd strongly recommend using 2.7.14 if you can (due to other bugs). It wasn't fixed in 2.6, though if you're using EPEL then there's a patch in that 2.6 RPM. -- 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 class not working after use augeas-0.10.0-3
Yes nice.. its work thank you Dominic, but its still execute even its
already changed its normal for new augeas? because for old augeas not
trying to change if already change. "returns: executed successfully"
my onlyif doesn't work. onlyif => "match
*[/files/etc/modprobe.conf[install = '$module /bin/true']] size == 0",
and this script doesn't work anymore:
if $ssh_port != '' {
augeas { "ssh_port" :
context => "/files/etc/ssh/sshd_config",
changes => [
"set Port $ssh_port",
],
notify => Service[
"sshd"
],
}
}
Thank you for any help.
Regards,
On 05/01/2012 08:06 PM, Dominic Cleal wrote:
On 01/05/12 13:00, heriyanto wrote:
Hi ,
This my puppet class, working nicely. But after i upgarde augeas into
augeas-0.10.0-3
There was an incompatible change to the modprobe lens in Augeas 0.10.0:
"Modprobe: Parse commands in install/remove stanzas (this introduces a
backwards incompatibility)"
from http://augeas.net/news.html
define modprobe::disableModule ( $module = '' )
{
augeas::basic-change {"$name":
file=> "/etc/modprobe.conf",
lens=> "modprobe.lns",
changes => "set install[0] '$module /bin/true'",
onlyif => "match *[/files/etc/modprobe.conf[install =
'$module /bin/true']] size == 0",
}
}
The value of the node is no longer a concatenation of the module name
and the command, the two were split up. Try this:
define modprobe::disableModule ( $module = '' )
{
augeas::basic-change {"$name":
file=> "/etc/modprobe.conf",
lens=> "modprobe.lns",
changes => [
"set install[.='$module'] '$module'",
"set install[.='$module']/command /bin/true",
],
}
}
This creates two nodes instead of just the one, e.g.
/files/etc/modprobe.conf/install = "foo"
/files/etc/modprobe.conf/install/command = "/bin/true"
I've also changed the install[0] so it doesn't always overwrite the
first install line and instead creates an install line per module.
Cheers,
--
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 class not working after use augeas-0.10.0-3
Hi ,
This my puppet class, working nicely. But after i upgarde augeas into
augeas-0.10.0-3
class modprobe {
modprobe::disableModule{"Disable cramfs, 2.2.2.5": module =>
"cramfs" }
modprobe::disableModule{"Disable freevxfs, 2.2.2.5": module =>
"freevxfs" }
modprobe::disableModule{"Disable jffs2, 2.2.2.5":module =>
"jffs2" }
modprobe::disableModule{"Disable hfs, 2.2.2.5": module =>
"hfs" }
modprobe::disableModule{"Disable hfsplus, 2.2.2.5": module =>
"hfsplus" }
modprobe::disableModule{"Disable squashfs, 2.2.2.5":
module => "squashfs" }
modprobe::disableModule{"Disable udf, 2.2.2.5": module =>
"udf" }
modprobe::disableModule{"Disable usb-storage, 2.2.2.1":module
=> "usb-storage" }
modprobe::disableModule{"Disable ipv6, 2.5.3.1.1":module =>
"ipv6" }
modprobe::turnOffModule{"Disable bluetooth, 3.3.14.3": module =>
"bluetooth" }
modprobe::turnOffModule{"Disable net-pf-31, 3.3.14.3": module =>
"net-pf-31" }
}
modprobe::disableModule{"Disable DCCP, 2.5.7.1": module =>
"dccp" }
modprobe::disableModule{"Disable SCTP, 2.5.7.2": module =>
"sctp" }
modprobe::disableModule{"Disable RDS, 2.5.7.3": module => "rds" }
modprobe::disableModule{"Disable TIPC, 2.5.7.4": module =>
"tipc" }
define modprobe::disableModule ( $module = '' )
{
augeas::basic-change {"$name":
file=> "/etc/modprobe.conf",
lens=> "modprobe.lns",
changes => "set install[0] '$module /bin/true'",
onlyif => "match *[/files/etc/modprobe.conf[install =
'$module /bin/true']] size == 0",
}
}
define modprobe::turnOffModule ( $module ='' )
{
augeas::basic-change { "$name" :
file=> "/etc/modprobe.conf",
lens=> "modprobe.lns",
changes => [
"set alias[last()+1] $module",
"set alias[last()]/modulename off",
],
onlyif => "match *[/files/etc/modprobe.conf[alias =
'$module']] size == 0",
}
}
The error message:
info: Retrieving plugin
info: Loading facts in unlabeled_device_files
info: Loading facts in unlabeled_device_files
info: Caching catalog for id41-nd016.asyx.com
info: Applying configuration version '1335867684'
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
squashfs, 2.2.2.5]/Augeas::Basic-change[Disable squashfs,
2.2.2.5]/Augeas[Disable squashfs, 2.2.2.5]/returns: change from
need_to_run to 0 failed: Save failed with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
SCTP, 2.5.7.2]/Augeas::Basic-change[Disable SCTP,
2.5.7.2]/Augeas[Disable SCTP, 2.5.7.2]/returns: change from need_to_run
to 0 failed: Save failed with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
TIPC, 2.5.7.4]/Augeas::Basic-change[Disable TIPC,
2.5.7.4]/Augeas[Disable TIPC, 2.5.7.4]/returns: change from need_to_run
to 0 failed: Save failed with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
cramfs, 2.2.2.5]/Augeas::Basic-change[Disable cramfs,
2.2.2.5]/Augeas[Disable cramfs, 2.2.2.5]/returns: change from
need_to_run to 0 failed: Save failed with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
udf, 2.2.2.5]/Augeas::Basic-change[Disable udf, 2.2.2.5]/Augeas[Disable
udf, 2.2.2.5]/returns: change from need_to_run to 0 failed: Save failed
with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
DCCP, 2.5.7.1]/Augeas::Basic-change[Disable DCCP,
2.5.7.1]/Augeas[Disable DCCP, 2.5.7.1]/returns: change from need_to_run
to 0 failed: Save failed with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
jffs2, 2.2.2.5]/Augeas::Basic-change[Disable jffs2,
2.2.2.5]/Augeas[Disable jffs2, 2.2.2.5]/returns: change from need_to_run
to 0 failed: Save failed with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
RDS, 2.5.7.3]/Augeas::Basic-change[Disable RDS, 2.5.7.3]/Augeas[Disable
RDS, 2.5.7.3]/returns: change from need_to_run to 0 failed: Save failed
with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
hfsplus, 2.2.2.5]/Augeas::Basic-change[Disable hfsplus,
2.2.2.5]/Augeas[Disable hfsplus, 2.2.2.5]/returns: change from
need_to_run to 0 failed: Save failed with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
freevxfs, 2.2.2.5]/Augeas::Basic-change[Disable freevxfs,
2.2.2.5]/Augeas[Disable freevxfs, 2.2.2.5]/returns: change from
need_to_run to 0 failed: Save failed with return code false
err: /Stage[main]/Modprobe/Modprobe::Modprobe::Disablemodule[Disable
hfs, 2.2.2.5]/Augeas::Basic-change[Disable hfs,
Re: [Puppet Users] puppet on solaris 11
Maybe you can check this log installation for solaris 11 http://log.unixhat.com/2012/02/setup-instalasi-solaris-sebagai-puppet.html On 02/16/2012 10:53 AM, Tim Dunphy wrote: Hello Darin, Thanks for your input. Well I've tried the repo that you suggested however the result appears to be the same: root@sol5:~# puppet file /etc/hosts /opt/csw/lib/ruby/site_ruby/1.8/puppet/application.rb:219:in `find': undefined method `join' for Puppet::Application::File:Class (NoMethodError) from /opt/csw/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:60:in `execute' from /opt/csw/bin/puppet:4 Same exact error as when I install puppet via gem or source. Any further thoughts? thanks! tim On Wed, Feb 15, 2012 at 5:02 PM, Darin Perusich wrote: Puppet package for solaris are available from OpenCSW.org and are kept up to date by the maintainer. You may find this easier and cleaner then mucking around with source and gem installs. -- Later, Darin On Wed, Feb 15, 2012 at 4:40 PM, Tim Dunphy wrote: hello, I've been asked to install puppet client onto a solaris 11 machine. I found some instructions that referenced a website called 'codenursary.com' however that website does not appear to be online anymore. http://projects.puppetlabs.com/projects/1/wiki/Puppet_Solaris codenursery.com However I attempted both a gem install of puppet as well as a source install with ./install.rb and I get the same results whenever I try to run a puppet foo command: root@sol3:/opt/puppet-2.7.10# puppet file /etc/hosts /usr/ruby/1.8/lib/ruby/site_ruby/1.8/puppet/application.rb:219:in `find': undefined method `join' for Puppet::Application::File:Class (NoMethodError) from /usr/ruby/1.8/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:60:in `execute' from /usr/ruby/1.8/bin/puppet:4 So kind puppeteers I would like to know what on earth I am doing wrong and how can I get a working puppet installation under Solaris 11 x86? Thanks you tim tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B -- 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. -- 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] [ask] Upgrade for CVE-2011-3872 AltNames Vulnerability
Thank for your reply Nigel, my host is about hundreds. Is it ok if i just upgrade puppetmaster to 2.6.12 and still using old puppet.conf with certdnsnames? if is work well, after that i upgrade all my agent. Thank you for any reply. On 10/25/2011 11:12 PM, Nigel Kersten wrote: On Mon, Oct 24, 2011 at 8:28 PM, heriyanto <mailto:shell.heriya...@gmail.com>> wrote: Base on CVE-2011-3872, i want to upgrade all puppet master and agent, my plan upgrade puppet master first then the agent, whether the configuration I can still be used? if use version 2.6.12 as a puppet master and agent still 2.6.6 for temporary then after that i upgrade to 2.6.12 for the agent? because my configuration already complex, and also using certdnsnames. Or anybody have good plan for upgrading? i can't recreate CA because i have much hosts. Upgrading the master is the important part, not the agents, but you should ultimately do them as well anyway. How many hosts do you have? If you can cluster SSH commands to them you can follow the SSH recipe for migrating them to a new CA. https://github.com/puppetlabs/puppetlabs-cve20113872/blob/master/README-ssh-only.markdown or if you can cope with a webrick master, we have a recipe there that will work for 2.6.x and 2.7.x webrick puppet masters. https://github.com/puppetlabs/puppetlabs-cve20113872/tree/master/bin/webrick If you have some other setup, you may be able to fork that module and modify it to work with your deployment. Best regards, Heriyanto -- 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 <mailto:puppet-users@googlegroups.com>. To unsubscribe from this group, send email to puppet-users+unsubscribe@ googlegroups.com <mailto:puppet-users%2bunsubscr...@googlegroups.com>. For more options, visit this group at http://groups.google.com/ group/puppet-users?hl=en <http://groups.google.com/group/puppet-users?hl=en>. -- Nigel Kersten Product Manager, 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] [ask] Upgrade for CVE-2011-3872 AltNames Vulnerability
Base on CVE-2011-3872, i want to upgrade all puppet master and agent, my plan upgrade puppet master first then the agent, whether the configuration I can still be used? if use version 2.6.12 as a puppet master and agent still 2.6.6 for temporary then after that i upgrade to 2.6.12 for the agent? because my configuration already complex, and also using certdnsnames. Or anybody have good plan for upgrading? i can't recreate CA because i have much hosts. Best regards, Heriyanto -- 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 dashboard cannot work behind a Apache reverse proxy?
Dear All, I already deploy puppet-dashboard with passanger. i'm want to try puppet-dasboard work in like myserver.com/puppet-report using apache proxy reverse, but still getting work, its just show the index then when i try to click some link like nodes, its will be goto myserver.com/nodes, not to myserver.com/puppet-report/nodes its just work if i try to reverse to myserver.com. where my false, should i not using passanger or something wrong my config . i'm realy need help because i already try 3 days and still not work, because puppet-dashboard its very important to monitor about hundreds our hosts. this is my vhost configuration in puppet-dashboard server: 1. 192.168.x.x /etc/httpd/conf.d/dashboard.conf where the puppet dashboard deployed: LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger-3.0.7/ext/apache2/mod_passenger.so PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-3.0.7 PassengerRuby /usr/bin/ruby PassengerHighPerformance on PassengerMaxPoolSize 12 PassengerPoolIdleTime 1500 PassengerStatThrottleRate 120 RailsAutoDetect On ServerName server.myserver.local DocumentRoot /usr/share/puppet-dashboard/public/ Options None AllowOverride AuthConfig Order allow,deny allow from all ErrorLog /var/log/httpd/server.myserver.local_error.log LogLevel warn CustomLog /var/log/httpd/server.myserver.local_access.log combined ServerSignature On 2. 203.x.x.x /etc/httpd/conf.d/dashboard.conf this where the apache should reverse: ServerName www.myserver.local ProxyRequests Off ProxyPreserveHost On ProxyPass /puppet-report http://www.myserver.com/ ProxyPassReverse /puppet-report http://www.myserver.com/ Order deny,allow Allow from all any something wrong with my configuration? with this config its already show in www.myserver.com/puppet-report but when i click some link like nodes its always goto www.myserver.com/nodes/ not www.myserver.com/puppet-report/nodes/ I appreciate every reply you give. Thank you very much. Regards Heriyanto -- 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.
