[Puppet Users] Re: puppet module generate skeleton not working on PE?
Peter, When I ran the puppet module generate as non-rootit worked like a charm! Maybe some of the other talented people on this forum may have a clue as to why. Thanks again. Stephen On Wednesday, 26 February 2014 07:25:43 UTC+11, Peter wrote: > > Hi, > > I am not sure on the underlying reasons but this doesnt work under the > root account. I ran into the same issue when I was playing with it on a > dev box. > > Peter > > -- 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/237baac5-aa62-4388-bb84-f6b98798b300%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] How to use puppet modules on the forge on vagrant
Hi, you can find a fully working project with vagrant in my github repo: https://github.com/DavidS/dasz-configuration There you can check how the Vagrantfile is configured and how the filesystem layout looks like. You'll see both puppet and puppet_server configured vagrants there. Regards, David On 2014-02-25 00:12, bkoo...@ucr.edu wrote: I am trying to use this module https://forge.puppetlabs.com/puppetlabs/ntp#usage on vagrant but when I copy the manifests to the puppet module path on vagrant I get this error Could not find parent resource type 'ntp::params' of type hostclass in production at /tmp/vagrant-puppet-1/modules-0/ntp/manifests/init.pp:1 on node ubuntu params.pp is in the manifest so I have no idea whats causing this error. -- 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/cdfda81cbf207891f666f4ea578e22c5%40hosting.edv-bus.at. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] How to use puppet modules on the forge on vagrant
it is always handy to show your command. Assuming you did a a pupept apply, add the --modulepath to the command. puppet apply --modulepath=/tmp/vagrant-puppet-1/modules-0/ /tmp/vagrant-puppet-1/modules-0/ntp/tests/init.pp puppet knows now where to find the other classes. HTH grts jo On 02/25/2014 12:12 AM, bkoo...@ucr.edu wrote: I am trying to use this module https://forge.puppetlabs.com/puppetlabs/ntp#usage on vagrant but when I copy the manifests to the puppet module path on vagrant I get this error Could not find parent resource type 'ntp::params' of type hostclass in production at /tmp/vagrant-puppet-1/modules-0/ntp/manifests/init.pp:1 on node ubuntu params.pp is in the manifest so I have no idea whats causing this error. -- 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/0e83ec59-58a9-4380-8cce-5b24becaa487%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Johan De Wit Open Source Consultant Red Hat Certified Engineer (805008667232363) Puppet Certified Professional 2013 (PCP006) _ Open-Future Phone +32 (0)2/255 70 70 Zavelstraat 72 Fax +32 (0)2/255 70 71 3071 KORTENBERG Mobile+32 (0)474/42 40 73 BELGIUM http://www.open-future.be _ Next Events: Zabbix Certified Training | http://www.open-future.be/zabbix-certified-training-10-till-12th-march Zabbix for Large Environments Training | http://www.open-future.be/zabbix-large-environments-training-13-till-14th-march Puppet Intruction Course | http://www.open-future.be/puppet-introduction-course-14th-april Puppet Advanced Training | http://www.open-future.be/puppet-advanced-training-15-till-17th-april Subscribe to our newsletter | http://eepurl.com/BUG8H -- 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/530D8878.208%40open-future.be. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Does r10k play nicely with Puppet Enterprise gems?
Thanks Adrien! On Wednesday, February 26, 2014 10:41:28 AM UTC+11, Adrien Thebo wrote: > > Hi Steven, > > I'm glad that you've found r10k useful! > > r10k has pretty a lightweight set dependencies that should play nicely > with the rest of Puppet Enterprise, and it's important to me that r10k can > easily be installed and behave well in PE. I know that r10k is frequently > deployed in PE environments and I haven't heard of any issues with r10k > that are due to being installed in the PE rubygems environment. Installing > r10k via `/opt/puppet/bin/gem install r10k` should work, and Zack Smith's > r10k module has first class support for PE ( > https://github.com/acidprime/r10k/blob/master/manifests/params.pp#L29-L39) > which are pretty encouraging indications that it should work well for you > if you install it into the PE stack. > > On Tuesday, February 25, 2014 2:06:42 AM UTC-8, Steven James wrote: >> >> As r10k is a gem install, and has quite a few gem dependenciesdoes >> anybody know if it plays nicely with Puppet Enterprise? >> >> As long as I use PE's /opt/puppet/bin/{bundle,rake} when doing the >> builds, should all be fine? >> >> Anybody have any stories or woe and dispair, or just lots of associated >> happiness? >> >> Thanks for your input! >> >> StevenJ >> PS R10Kwell done Adrien! Great product! >> >> -- 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/d36eb856-69c6-4465-8420-e74c1a59ecd3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Does r10k play nicely with Puppet Enterprise gems?
Hi Steven, I'm glad that you've found r10k useful! r10k has pretty a lightweight set dependencies that should play nicely with the rest of Puppet Enterprise, and it's important to me that r10k can easily be installed and behave well in PE. I know that r10k is frequently deployed in PE environments and I haven't heard of any issues with r10k that are due to being installed in the PE rubygems environment. Installing r10k via `/opt/puppet/bin/gem install r10k` should work, and Zack Smith's r10k module has first class support for PE (https://github.com/acidprime/r10k/blob/master/manifests/params.pp#L29-L39) which are pretty encouraging indications that it should work well for you if you install it into the PE stack. On Tuesday, February 25, 2014 2:06:42 AM UTC-8, Steven James wrote: > > As r10k is a gem install, and has quite a few gem dependenciesdoes > anybody know if it plays nicely with Puppet Enterprise? > > As long as I use PE's /opt/puppet/bin/{bundle,rake} when doing the builds, > should all be fine? > > Anybody have any stories or woe and dispair, or just lots of associated > happiness? > > Thanks for your input! > > StevenJ > PS R10Kwell done Adrien! Great product! > > -- 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/02f363f6-cc9b-4c88-80b4-41b7fa375a6f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Custom service status not working
I have a service set up with a custom status check, but when I run puppet it ignores my custom status command and runs the standard upstart status check. My service definition is as follows: service { "gamedeploy-${title}": ensure => running, provider => upstart, start => "/sbin/initctl start gamedeploy-${title} GAME=${game} COMPONENT=${title} ENVIRONMENT=${::environment} DELAY=${delay}", stop => "/sbin/initctl stop gamedeploy-${title} COMPONENT=${title}", status => "/sbin/initctl status gamedeploy-${title} COMPONENT=${title}", hasstatus => false, hasrestart => false, require=> File["gamedeploy_init_${title}"], } And here's the puppet debug output: Debug: Executing '/sbin/status gamedeploy-frontend' Debug: Executing '/sbin/initctl start gamedeploy-frontend GAME=test COMPONENT=frontend ENVIRONMENT=stage DELAY=5' Error: Could not start Service[gamedeploy-frontend]: Execution of '/sbin/initctl start gamedeploy-frontend GAME=test COMPONENT=frontend ENVIRONMENT=stage DELAY=5' returned 1: Error: /Stage[main]/Deploy/Deploy_service[frontend]/Service[gamedeploy-frontend]/ensure: change from stopped to running failed: Could not start Service[gamedeploy-frontend]: Execution of '/sbin/initctl start gamedeploy-frontend GAME=test COMPONENT=frontend ENVIRONMENT=stage DELAY=5' returned 1: Debug: Executing '/sbin/initctl start gamedeploy-frontend GAME=test COMPONENT=frontend ENVIRONMENT=stage DELAY=5' As you can see, it should be using "/sbin/initctl status gamedeploy-frontend COMPONENT=frontend" as the check, but instead just uses "/sbin/status gamedeploy-frontend". Anyone know why? Thanks, Guy -- 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/CA%2BgQdWC%2BqOMStASxecHyL9Fd%3D%2BoStMQs%3D9cFpKxiigh1J8F-cQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet agent gives error undefined method `empty?' for nil:NilClass
I have a puppet master which has over 50 puppet agents talking to it just fine. But I have one particular server on which the agent, after connecting and exchanging keys, gives the following error: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `empty?' for nil:NilClass at /etc/puppet/modules/server/iptables/manifests/init.pp:7 on node curatevanilla.library.nd.edu Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Having read other posts, and knowing that we do use hiera, this looks like a hiera problem. If I comment out classes which don't use hiera, the agent will run them all. But add any in which use hiera and that will be the class which fails (iptables above is just the first one it hits). How do I best track down where the problem really is? I have made sure that the /etc/hiera.yaml file is in place and it matches other servers which work. I've tried clearing out /var/lib/puppet on the server and letting that get rebuilt. If I move /var/lib/hiera out of the way, it does not get rebuilt, probably because the download does not get that far. Any suggestions on what might allow me to find the conflict. Thanks, Tom -- 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/2b9fe2ac-6646-44e0-b344-1b65d35e2e27%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet module generate skeleton not working on PE?
Hi, I am not sure on the underlying reasons but this doesnt work under the root account. I ran into the same issue when I was playing with it on a dev box. Peter -- 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/a0edb41f-d3f7-403b-bf20-1f3840505a5e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Style and Formatting Best Practice
On 2014-02-20 23:51, Charles McLaughlin wrote: Hello, I'm trying to develop Puppet style guidelines at my job and would like some feedback and opinions on a few patterns. Please just follow the official style guide (or suggest improvements there if necessary). Regards, David -- 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/530CF428.4040502%40dasz.at. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] File resource fails on Windows 7 x64 (other resources with different file works)
There are actually two different issues here: On Tue, Feb 18, 2014 at 12:31 PM, jmp242 wrote: > Here's another test where I just added --test to your command, and passed > to a log file. It should show my issue. Anyway, it does look very similar > an error, though I can't figure out why any of the string manipulation > would fail on openvpn.exe and not on fusion.exe ... > > On Tuesday, February 18, 2014 3:26:23 PM UTC-5, Rob Reynolds wrote: > >> I didn't see the error that you described (your log notes an issue with >> forking), but have a look at https://tickets.puppetlabs. >> com/browse/PUP-1389 (which speaks of the require_file issues you >> describe). We've recently fixed that issue and it will be in the next >> release. I'm not sure these are the same issues, however. >> >> >> On Tue, Feb 18, 2014 at 1:54 PM, jmp242 wrote: >> >>> As far as I can tell. I'm on Windows, and it scrolls off the screen. It >>> didn't seem to capture much when I tried to redirect to a file. >>> >>> >>> On Tuesday, February 18, 2014 2:51:01 PM UTC-5, Rob Reynolds wrote: >>> Is this the correct log file for the error you described? On Tue, Feb 18, 2014 at 1:06 PM, jmp242 wrote: > Puppet 3.4.2, as specified. I've attached a log file. > > > >From the log file: "Error: Could not run: fork() function is unimplemented on this machine" This is https://tickets.puppetlabs.com/browse/PUP-1275. You either need to explicitly specify --onetime, or --test (which automatically sets onetime). Unfortunately this means you cannot setup a listening puppet agent and use kick on it. This is a regression introduced in http://projects.puppetlabs.com/issues/17361 > > On Friday, February 7, 2014 12:35:32 PM UTC-5, Rob Reynolds wrote: > >> First question - what version of puppet? >> >> Second question - can you run puppet apply (or agent) with --trace >> --debug --verbose and post the relevant results? We have some recent >> fixes >> related to this. >> >> >> On Thu, Feb 6, 2014 at 3:27 PM, jmp242 wrote: >> >>> I'm really lost as to why this is failing. >>> >>> file{ 'openvpn.exe': >>> path => 'C:/ProgramData/puppetfiles/openvpn.exe', >>> source => "puppet:///modules/openvpn/openvpn.exe", >>> owner => 'SYSTEM', >>> group => 'Administrators', >>> mode => 0770, >>> provider => windows, >>> ensure => present, >>> } >>> >>> gives me this error: >>> >>> ReplaceFile(C:/ProgramData/puppetfiles/openvpn.exe, >>> C:/ProgramData/puppetfiles/openvpn.exe20140206-5012-wvhezn): The >>> system cannot find the file specified. >>> >>> >>> change from absent to file failed: >>> ReplaceFile(C:/ProgramData/puppetfiles/openvpn.exe, >>> C:/ProgramData/puppetfiles/openvpn.exe20140206-5012-wvhezn): The >>> system cannot find the file specified. >>> >> This is https://tickets.puppetlabs.com/browse/PUP-1389. This was due to memory corruptions in the windows gems we use ( https://tickets.puppetlabs.com/browse/PUP-1368), and a ruby bug with wide-character NULLs ( http://svn.ruby-lang.org/cgi-bin/viewvc.cgi?revision=41920&view=revision) that will sometimes cause this error. This issue is resolved in the 3.4.3 release. > >>> I have no idea why. I'm using Puppet agent 3.4.2. A very similar >>> resource: >>> >>> file { 'fusion.exe': >>> path => 'C:/ProgramData/puppetfiles/fusion.exe', >>> source => "puppet:///modules/fusionagent/fusion.exe", >>> owner => 'SYSTEM', >>> group => 'Administrators', >>> mode => 0770, >>> provider => windows, >>> ensure => present, >>> } >>> >>> works... >>> >>> >>> -- >>> 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. >>> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/puppet-users/8a72f9a1-1402 >>> -4e2d-80fb-703a5133e50e%40googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> >> >> -- >> Rob Reynolds >> Developer, Puppet Labs >> >> *Join us at PuppetConf 2014, September 23-24 in San Francisco - * >> http://bit.ly/pupconf14 >> > -- > 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. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/puppet-users/ee3cdc52-1ef0-49aa-9e4b-2b0f11cf529d%40goog > legroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. > -- Rob Reynolds
Re: [Puppet Users] Possible issue with nagios_* commands
Hi, there will be appropriate options to the nagios types starting with 3.5, see https://tickets.puppetlabs.com/browse/PUP-1327 As a workaround you can now manage the configs as file { } resources. This should not interfere with the nagios types. HTH, Felix On 02/25/2014 06:01 PM, JonY wrote: > I'm trying to setup a nagios server via puppet to monitor the other > servers in the group. I can get the various stored info from puppet db > but when the *.cfg files are created in the nagios folder they are all > root:root 0600. > > IE nagios can't read them. > > I can work around this but I'm wondering if there is some config that > I've missed. -- 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/530CCE8F.30202%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Possible issue with nagios_* commands
On Tue, 25 Feb 2014 09:01:43 -0800 (PST) JonY wrote: > I'm trying to setup a nagios server via puppet to monitor the other > servers in the group. I can get the various stored info from puppet > db but when the *.cfg files are created in the nagios folder they are > all root:root 0600. > > IE nagios can't read them. > > I can work around this but I'm wondering if there is some config that > I've missed. I recall having the same problem. In fact, here's what I have in my own nagios module : # Work around a puppet bug where created files are 600 root:root file { [ '/etc/nagios/nagios_command.cfg', '/etc/nagios/nagios_contact.cfg', '/etc/nagios/nagios_contactgroup.cfg', '/etc/nagios/nagios_host.cfg', '/etc/nagios/nagios_hostdependency.cfg', '/etc/nagios/nagios_hostgroup.cfg', '/etc/nagios/nagios_service.cfg', '/etc/nagios/nagios_servicegroup.cfg', '/etc/nagios/nagios_timeperiod.cfg', ]: ensure => present, owner => 'root', group => 'nagios', mode => '0640', before => Service['nagios'], } Matthias -- Matthias Saou ██ ██ ██ ██ Web: http://matthias.saou.eu/ ██ Mail/XMPP: matth...@saou.eu ██ ██ GPG: 4096R/E755CC63██ ██ ██ 8D91 7E2E F048 9C9C 46AF ██ ██ ██ ██ 21A9 7A51 7B82 E755 CC63 -- 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/20140225180713.5ce8b79d%40r2d2.marmotte.net. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Possible issue with nagios_* commands
I'm trying to setup a nagios server via puppet to monitor the other servers in the group. I can get the various stored info from puppet db but when the *.cfg files are created in the nagios folder they are all root:root 0600. IE nagios can't read them. I can work around this but I'm wondering if there is some config that I've missed. -- 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/134d2a63-1aea-43d4-adf6-e00ad4282bb4%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: notify on agent from puppet function
Unfortunately, the message could be computed only in function. Do I understand correctly that it is impossible to push Notify in catalog from function during compilation. On Tue, Feb 25, 2014 at 5:26 PM, jcbollinger wrote: > > > On Monday, February 24, 2014 8:15:29 AM UTC-6, bazil wrote: >> >> Hi all, >> >> could you advice any way to put a message in puppet agent output from >> puppet function on master. >> >> > > Not directly, because functions run on the master, during catalog > compilation. If the message can be computed on the master, then you can > cause it to be emitted into the agent's log via a Notify resource. > > > John > > -- > 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/5a518de3-e563-4e2c-867f-80c859b8767e%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- Best regards, Vasil Mikhalenya -- 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/CAPc4iSARXjUHL1XraiSK11c2ygg3u6BNbEthfQkJPdeu-gLzvQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: yum tries to downgrade a package (ensure => version)
On Tuesday, February 25, 2014 4:07:06 AM UTC-6, Jose Luis Ledesma wrote: > > Hi, > >I have found a problem trying to upgrade a rhel6 package (libcgroup), > the current version installed is: > > libcgroup-0.37-7.el6.x86_64 > >And I want to install this version: > > libcgroup-0.37-7.2.el6_4.x86_64 > >So I created a class that states: > > package { 'libcgroup': > ensure => '0.37-7.2.el6_4', > } > > But when I run puppet agent -t : > > Error: Could not update: Failed to update to version 0.37-7.2.el6_4, got > version 0.37-7.el6 instead > Error: /Stage[main]/Checks::Linux::Libcgroup/Package[libcgroup]/ensure: > change from 0.37-7.el6 to 0.37-7.2.el6_4 failed: Could not update: Failed > to update to version 0.37-7.2.el6_4, got version 0.37-7.el6 instead > > >When I run the debug yum tries to downgrade the package: > > Debug: Package[libcgroup](provider=yum): Downgrading package libcgroup > from version 0.37-7.el6 to 0.37-7.2.el6_4 > Debug: Executing '/usr/bin/yum -d 0 -e 0 -y downgrade > libcgroup-0.37-7.2.el6_4' > >And obviously this package exists on the repo: > > > # yum install libcgroup-0.37-7.2.el6_4 > Loaded plugins: product-id, security, subscription-manager > This system is not registered to Red Hat Subscription Management. You can > use subscription-manager to register. > Setting up Install Process > Resolving Dependencies > --> Running transaction check > ---> Package libcgroup.x86_64 0:0.37-7.el6 will be updated > --> Processing Dependency: libcgroup = 0.37-7.el6 for package: > libcgroup-devel-0.37-7.el6.x86_64 > ---> Package libcgroup.x86_64 0:0.37-7.2.el6_4 will be an update > --> Running transaction check > ---> Package libcgroup-devel.x86_64 0:0.37-7.el6 will be updated > ---> Package libcgroup-devel.x86_64 0:0.37-7.2.el6_4 will be an update > --> Finished Dependency Resolution > > Dependencies Resolved > > > = > Package Arch > Version Repository Size > > = > Updating: > libcgroup x86_64 > 0.37-7.2.el6_4 rhel 111 k > Updating for dependencies: > libcgroup-devel x86_64 > 0.37-7.2.el6_4 rhel35 k > > Transaction Summary > > = > Upgrade 2 Package(s) > > > If I set "ensure => latest" in the package definition it works. > > any hint? > This looks like a Puppet bug (probably https://tickets.puppetlabs.com/browse/PUP-682, or at least related to that). Note in particular that Puppet thinks it needs to *down*grade the installed package version, and that it issues a yum command appropriate for that purpose. Yum understands RPM version-release codes differently than Puppet seems to do, and recognizes the specified package version as an update, which it therefore refuses to apply as a downgrade. In the end, the original package remains installed. Per comments in JIRA, work addressing the general issue is being performed in the context of https://tickets.puppetlabs.com/browse/PUP-1244. You could consider commenting on the issue. In the meantime, your best workaround is probably to ensure 'latest'. If you have your nodes pointed at an internal repository (which I would recommend in any case) then you can control what version is available for installation be controlling what packages are in that repository. John -- 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/d69f1082-3622-4e99-aa4d-02673974cb3b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: notify on agent from puppet function
On Monday, February 24, 2014 8:15:29 AM UTC-6, bazil wrote: > > Hi all, > > could you advice any way to put a message in puppet agent output from > puppet function on master. > > Not directly, because functions run on the master, during catalog compilation. If the message can be computed on the master, then you can cause it to be emitted into the agent's log via a Notify resource. John -- 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/5a518de3-e563-4e2c-867f-80c859b8767e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] How to purge and install package on same run?
I've got a situation where I need to remove a set of packages and then install the upgraded versions. I can't just upgrade. It's rare that I have to upgrade the software but I'd like to have something in place to upgrade when I have to. What's the best way to handle these types of situations with Puppet? Is there anyway to force $purge_pkgs to run and then have $install_pkgs run after on the same run? As written below, I think what happens is the packages are uninstalled but when the compile runs, $install_pkgs are already installed, so it does nothing. Class upgrade: - if $upg == 'yes' { package { $purge_pkgs: ensure => 'purged', install_options => '-y', } } package { $install_pkgs: ensure => installed, install_options => '-y', } Bunch of other bits run. -- Any advice appreciated. Thanks, -- Kent -- 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/CA%2BnSE38fD8XVEeb74CKmFyBhcw5-syMj%3DL-XMu%3Dk0pPUhvOSUQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] install_options =>{$:: variable} -syntax
On Tuesday, February 25, 2014 5:10:25 AM UTC-6, Helen Paterson wrote: > > class installjava7::x86 { > > > >package { 'Java 7 Update 51': > ensure =>'7.0.510' , > source => '\\cam-OPS20\Install\IT > Apps\Java\jre-7u51-windows-i586.exe', > install_options => [ > '/s','STATIC=1','JAVAUPDATE=0','AUTOUPDATECHECK=0',"INSTALLDIR=${::javahome}"], > notify => Exec["winfirewalljava"], > > >} > >exec { "winfirewalljava": > command => "${::posh_cmd} -Command \"netsh advfirewall firewall add > rule name=Java dir=in action=allow > program='\"${::javahome}\"\\bin\\java.exe' ENABLE=yes\"", > refreshonly => true, > require => Package ['Java 7 Update 51'], > > } > > } > > site.pp > > $agenthome ="d:\\buildagent" > $javahome ="d:\\buildagent\\jre" > > On Tuesday, February 25, 2014 10:45:14 AM UTC, Felix.Frank wrote: >> >> Hi, >> >> On 02/25/2014 11:30 AM, Helen Paterson wrote: >> > Thank you, although that works, it means all other install options are >> > ignored ','JAVAUPDATE=0','AUTOUPDATECHECK=0. as check for updates is >> enabled >> >> that wouldn't appear to be a puppet related problem. To be safe, though, >> can you share the relevant manifest snippet in its current form again? >> >> I don't use Puppet on Windows, but I observe that the docs' Windows-based example of the install_options parameter ( http://docs.puppetlabs.com/references/3.stable/type.html#package-attribute-install_options) uses a different structure for options that are name=value pairs. Perhaps, then, this would work better: install_options => [ '/s', { 'STATIC' => '1' }', { 'JAVAUPDATE' => '0' }', { 'AUTOUPDATECHECK' => '0' }, { 'INSTALLDIR' => "${::javahome}" } ], Note, too, that although Puppet expects you always to use forward slash (/) in your manifests as a file separator in paths, even when the target node is Windows, it does not know or try to guess what install options are paths. It does no translation on the options, therefore you may need to ensure that paths among your options use Windows-standard backslash (\) file separators in any paths. Overall, though, Puppet is dependent on the package's installer. If it ignores certain options when others are specified, then that's out of Puppet's hands. That's why Felix said the problem doesn't appear to be Puppet-related. John -- 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/634b3a54-01ff-4e5c-bc10-6a5cb232d825%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Best practices: client/server VS Git
> This is the approach we are currently taking and it allows you to use > virtual resources. This is the only thing which should drive you to this > setup - the other is much simpler in my opinion. Of course there might > be a way to use a central PuppetDB service in masterless setup but at > least I am unaware of how to do this. It is possible: http://docs.puppetlabs.com/puppetdb/1.6/connect_puppet_apply.html 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNTn7VkKDNw4yEi%3DpX1Xd9FRJTff9_w1FtB1XX0TF7%2BcFRQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] No resources and catalog information with puppetdb
> with my puppetdb > - I can't query any resource or catalog > - exported resources are not working > > > This is working : > > # echo '["=", ["fact", "rubyversion"], "1.8.7"]' > queryfile > # curl -X GET http://localhost:8080/v3/nodes --data-urlencode > query@queryfile 2>/dev/null | tail -7 > }, { > "name" : "el6.labolinux.fr", > "deactivated" : null, > "catalog_timestamp" : null, > "facts_timestamp" : "2014-02-25T08:18:07.529Z", > "report_timestamp" : "2014-02-25T08:18:10.018Z" > > I can also query with success the facts, metrics, reports > (reports=store,puppetdb) endpoints. > > But it is not working with the resources or catalog endpoint : > > curl -X GET 'http://localhost:8080/v3/resources/User' > -> [] > > curl -X GET 'http://localhost:8080/v3/resources/Package' > -> [] > > curl -X GET 'http://localhost:8080/v3/resources/File' > -> [] > > curl -X GET http://localhost:8080/v3/catalogs/el6.labolinux.fr > -> { "error" : "Could not find catalog for el6.labolinux.fr" } > > curl -X GET http://localhost:8080/v3/nodes 2>/dev/null | grep name | grep > el6.labolinux.fr > -> "name" : "el6.labolinux.fr", > > In addition, this is not working from the puppet master : > > # puppet node status el6.labolinux.fr > Error: Could not retrieve status for el6.labolinux.fr: SSL_connect SYSCALL > returned=5 errno=0 state=SSLv3 read finished A This is the smoking gun. It looks like an SSL error is being thrown. > # puppet cert list el6.labolinux.fr > + "el6.labolinux.fr" (SHA256) > 76:00:C9:B9:0C:31:61:9C:A5:D9:B4:49:D7:17:39:76:15:9D:18:2C:E0:07:41:6B:6C:3A:4D:68:E1:BF:65:0D > > I think that a consequence is that my exported resources don't work. > > Here is my configuration. > > On the master : > > # dpkg-query -W | egrep 'puppet(master|db)' > puppetdb-terminus 1.6.2-1puppetlabs1 > puppetmaster3.4.3-1puppetlabs1 > puppetmaster-common 3.4.3-1puppetlabs1 > > In puppet.conf on the master : > > [master] > storeconfigs=true > storeconfig_backend=puppetdb > reports=store,puppetdb > > In routes.yaml on the master : > > --- > master: > facts: > terminus: puppetdb > cache: yaml > > In puppetdb.conf on the master : > > [main] > server=el6.labolinux.fr > port=8081 > soft_write_failure=true Set the soft_write_failure to false, and you should be seeing far more errors relating to SSL I bet. I think the problem stems from the errors being masked and probably just being stored in the masters log. This is the correct behaviour when this setting is true, so as to allow the master to continue to run when PuppetDB is not operational. Switching to false will make the real error surface most probably. Can you try changing that setting, restarting the puppet master and display the results for us? Or find the error in the location where you puppet master outputs its logs (daemon.log on Debian usually I think?). > On the puppetdb node : > > [root@el6 ~]# rpm -qa | grep '^puppet' > puppet-3.3.2-1.el6.noarch Why is your Puppet agent on the puppetdb node running an older revision then the master? I presume you are running Puppet on the PuppetDB node as well to manage that host correct? > puppetdb-1.6.2-1.el6.noarch > > Database backend configuration : > > [database] > classname = org.postgresql.Driver > subprotocol = postgresql > subname = //127.0.0.1:5432/puppetdb > username = puppetdb > > What am I missing ? This looks like a basic SSL setup issue but I have limited data to work on. Try running "puppetdb ssl-setup", storing the results then using "puppetdb ssl-setup -f" to force a manual repair of the certificates PuppetDB uses. Make sure you restart PuppetDB before trying again. 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNTmPhj2xpBiitN2e3q3%2BDmt43w%2BDLidA3j8yX_oS9h3cuA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] How to use puppet modules on the forge on vagrant
I am trying to use this module https://forge.puppetlabs.com/puppetlabs/ntp#usage on vagrant but when I copy the manifests to the puppet module path on vagrant I get this error Could not find parent resource type 'ntp::params' of type hostclass in production at /tmp/vagrant-puppet-1/modules-0/ntp/manifests/init.pp:1 on node ubuntu params.pp is in the manifest so I have no idea whats causing this error. -- 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/0e83ec59-58a9-4380-8cce-5b24becaa487%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet module template mentioned at contributor summit
On Wed, Feb 05, 2014 at 06:38:24PM +0100, Gareth Rushgrove wrote: > This came up in discussion a couple of times at the Puppet contributor > summit at Config Management Camp in Gent over the last couple of days > so I thought I'd write up. > > A while ago I put together a pretty complete/opinionated skeleton for > puppet modules. Especially if you're not too familiar with ruby or the > ruby ecosystem, or just getting started with testing it should be a > useful starting point. > > https://github.com/garethr/puppet-module-skeleton Damn! I have to confess that I have used your module and I have a Guardfile that also checks the templates. Maybe it's time I send a pull request (shame) :). Just know that there are people out there that are using this! > > I've added a bunch more features (including a Guardfile, resource > coverage and support for Beaker integration tests) and got round to > writing up a blog post about what and why: > > http://www.morethanseven.net/2014/02/05/a-template-for-puppet-modules/ > > Hopefully it's useful to a few people. Any features or issues let me know. > > Gareth > > -- > Gareth Rushgrove > @garethr > > devopsweekly.com > morethanseven.net > garethrushgrove.com > > -- > 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/CAFi_6y%2BiRQPPKk8yTLBMiHCNOsLdNFYeaPO8oTCCcuaASj6SaQ%40mail.gmail.com. > 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140225133511.GF26036%40nikolavp-desktop. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] install_options =>{$:: variable} -syntax
class installjava7::x86 { package { 'Java 7 Update 51': ensure =>'7.0.510' , source => '\\cam-OPS20\Install\IT Apps\Java\jre-7u51-windows-i586.exe', install_options => [ '/s','STATIC=1','JAVAUPDATE=0','AUTOUPDATECHECK=0',"INSTALLDIR=${::javahome}"], notify => Exec["winfirewalljava"], } exec { "winfirewalljava": command => "${::posh_cmd} -Command \"netsh advfirewall firewall add rule name=Java dir=in action=allow program='\"${::javahome}\"\\bin\\java.exe' ENABLE=yes\"", refreshonly => true, require => Package ['Java 7 Update 51'], } } site.pp $agenthome ="d:\\buildagent" $javahome ="d:\\buildagent\\jre" On Tuesday, February 25, 2014 10:45:14 AM UTC, Felix.Frank wrote: > > Hi, > > On 02/25/2014 11:30 AM, Helen Paterson wrote: > > Thank you, although that works, it means all other install options are > > ignored ','JAVAUPDATE=0','AUTOUPDATECHECK=0. as check for updates is > enabled > > that wouldn't appear to be a puppet related problem. To be safe, though, > can you share the relevant manifest snippet in its current form again? > > Thanks, > Felix > -- 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/14e1ba4c-d43a-4f58-8a3d-06fcb48b18d9%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] install_options =>{$:: variable} -syntax
Hi, On 02/25/2014 11:30 AM, Helen Paterson wrote: > Thank you, although that works, it means all other install options are > ignored ','JAVAUPDATE=0','AUTOUPDATECHECK=0. as check for updates is enabled that wouldn't appear to be a puppet related problem. To be safe, though, can you share the relevant manifest snippet in its current form again? Thanks, Felix -- 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/530C743A.4010800%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] install_options =>{$:: variable} -syntax
Thank you, although that works, it means all other install options are ignored ','JAVAUPDATE=0','AUTOUPDATECHECK=0. as check for updates is enabled On Tuesday, February 25, 2014 9:57:45 AM UTC, Johan De Wit wrote: > > Hi Helen, > > "INSTALLDIR=${::agenthome}\jre" > > HTH > > Jo > should do the trick > > On 02/25/2014 10:52 AM, Helen Paterson wrote: > > Hi, > > What is the syntax for install_options containing a variable ? > > This code below works fine,but i'd like to remove D:\BuildAgent\jre' and > replace it with ${::javahome}, what should the syntax be? > > > > > > install_options => [ > > '/s','STATIC=1','JAVAUPDATE=0','AUTOUPDATECHECK=0', > 'INSTALLDIR=D:\BuildAgent\jre' ], > > exec { *"winfirewalljava"*: > > command => > > "${::posh_cmd} -Command \"netsh advfirewall firewall add rule name=Java > dir=in action=allow program='D:\\BuildAgent\\jre\\bin\\java.exe' > ENABLE=yes\"", > > > > > this does not work > > install_options => [ > > '/s','STATIC=1','JAVAUPDATE=0','AUTOUPDATECHECK=0', > 'INSTALLDIR=\"$::agenthome\"\jre'], > > > > Thanks > > Helen > -- > 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 . > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/ef2cd5ee-4d09-48de-adfc-89a419e29e87%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > > > Upcoming Events: > > Zabbix Certified Training | > http://www.open-future.be/zabbix-certified-training-10-till-12th-march > > Zabbix for Large Environments Training | > http://www.open-future.be/zabbix-large-environments-training-13-till-14th-march > > Puppet Introduction Course | > http://www.open-future.be/puppet-introduction-course-14th-april > > Puppet Advanced Training | > http://www.open-future.be/puppet-advanced-training-15-till-17th-april > > Subscribe to our newsletter: http://eepurl.com/BUG8H > > -- 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/0960435b-3979-4e48-9be4-8b85799bc69e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Does r10k play nicely with Puppet Enterprise gems?
As r10k is a gem install, and has quite a few gem dependenciesdoes anybody know if it plays nicely with Puppet Enterprise? As long as I use PE's /opt/puppet/bin/{bundle,rake} when doing the builds, should all be fine? Anybody have any stories or woe and dispair, or just lots of associated happiness? Thanks for your input! StevenJ PS R10Kwell done Adrien! Great product! -- 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/CAB_ORUuUbuchMm0aWPE_s3S7ciagYApCLCHG-w-%3DT_xi03btmQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] yum tries to downgrade a package (ensure => version)
Hi, I have found a problem trying to upgrade a rhel6 package (libcgroup), the current version installed is: libcgroup-0.37-7.el6.x86_64 And I want to install this version: libcgroup-0.37-7.2.el6_4.x86_64 So I created a class that states: package { 'libcgroup': ensure => '0.37-7.2.el6_4', } But when I run puppet agent -t : Error: Could not update: Failed to update to version 0.37-7.2.el6_4, got version 0.37-7.el6 instead Error: /Stage[main]/Checks::Linux::Libcgroup/Package[libcgroup]/ensure: change from 0.37-7.el6 to 0.37-7.2.el6_4 failed: Could not update: Failed to update to version 0.37-7.2.el6_4, got version 0.37-7.el6 instead When I run the debug yum tries to downgrade the package: Debug: Package[libcgroup](provider=yum): Downgrading package libcgroup from version 0.37-7.el6 to 0.37-7.2.el6_4 Debug: Executing '/usr/bin/yum -d 0 -e 0 -y downgrade libcgroup-0.37-7.2.el6_4' And obviously this package exists on the repo: # yum install libcgroup-0.37-7.2.el6_4 Loaded plugins: product-id, security, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package libcgroup.x86_64 0:0.37-7.el6 will be updated --> Processing Dependency: libcgroup = 0.37-7.el6 for package: libcgroup-devel-0.37-7.el6.x86_64 ---> Package libcgroup.x86_64 0:0.37-7.2.el6_4 will be an update --> Running transaction check ---> Package libcgroup-devel.x86_64 0:0.37-7.el6 will be updated ---> Package libcgroup-devel.x86_64 0:0.37-7.2.el6_4 will be an update --> Finished Dependency Resolution Dependencies Resolved = Package Arch Version Repository Size = Updating: libcgroup x86_64 0.37-7.2.el6_4 rhel 111 k Updating for dependencies: libcgroup-devel x86_64 0.37-7.2.el6_4 rhel35 k Transaction Summary = Upgrade 2 Package(s) If I set "ensure => latest" in the package definition it works. any hint? -- 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/e135cb09-a92e-4992-bead-dbf0d54ea269%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] install_options =>{$:: variable} -syntax
Hi Helen, "INSTALLDIR=${::agenthome}\jre" HTH Jo should do the trick On 02/25/2014 10:52 AM, Helen Paterson wrote: Hi, What is the syntax for install_options containing a variable ? This code below works fine,but i'd like to remove D:\BuildAgent\jre' and replace it with ${::javahome}, what should the syntax be? install_options => [ '/s','STATIC=1','JAVAUPDATE=0','AUTOUPDATECHECK=0','INSTALLDIR=D:\BuildAgent\jre'], exec{ /"winfirewalljava"/: command => "${::posh_cmd}-Command \"netsh advfirewall firewall add rule name=Java dir=in action=allow program='D:\\BuildAgent\\jre\\bin\\java.exe' ENABLE=yes\"", this does not work install_options => [ '/s','STATIC=1','JAVAUPDATE=0','AUTOUPDATECHECK=0','INSTALLDIR=\"$::agenthome\"\jre'], Thanks Helen -- 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/ef2cd5ee-4d09-48de-adfc-89a419e29e87%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. Next Events: Zabbix Certified Training | http://www.open-future.be/zabbix-certified-training-10-till-12th-march Zabbix for Large Environments Training | http://www.open-future.be/zabbix-large-environments-training-13-till-14th-march Puppet Intruction Course | http://www.open-future.be/puppet-introduction-course-14th-april Puppet Advanced Training | http://www.open-future.be/puppet-advanced-training-15-till-17th-april Subscribe to our newsletter | http://eepurl.com/BUG8H -- 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/530C6919.5070908%40open-future.be. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet module generate skeleton not working on PE?
Hi I'm wondering if anybody has successfully managed to get any `puppet module generate` templates (e.g. https://github.com/garethr/puppet-module-skeleton) working on a Puppet Enterprise box? I've tried both of the github skeleton modules on two different versions of PE, but not joy. Seems straight forward enough, git clone the module, cd into the module directory, run the git command as per instructions, then run puppet module generate from the same dir. [root@master puppet-module-skeleton]# find skeleton -type f | git checkout-index --stdin --force --prefix="$HOME/.puppet/var/puppet-module/" -- [root@master puppet-module-skeleton]# puppet module generate my-module Notice: Generating module at /home/training/puppet-module-skeleton/my-module my-module my-module/Modulefile my-module/README my-module/manifests my-module/manifests/init.pp my-module/spec my-module/spec/spec_helper.rb my-module/tests my-module/tests/init.pp Under manifests dir above, I only see the regular init.pp. The skeleton templates contain params.pp, config.pp and service.pp. Maybe it's a Puppet Opensource only thing? Maybe someone knows the code to hack to make it work in the PE framework? -- Regs, Stephen J Wallace M +61 (0)415 306731 http://au.linkedin.com/in/stephenwallace -- 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/CAFB-iqeUJwUy3FkfuLKqSiQeSXkD5K6aoX3_z54ee%3DoroPF4Bw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] install_options =>{$:: variable} -syntax
Hi, What is the syntax for install_options containing a variable ? This code below works fine,but i'd like to remove D:\BuildAgent\jre' and replace it with ${::javahome}, what should the syntax be? install_options => [ '/s','STATIC=1','JAVAUPDATE=0','AUTOUPDATECHECK=0', 'INSTALLDIR=D:\BuildAgent\jre' ], exec { *"winfirewalljava"*: command => "${::posh_cmd} -Command \"netsh advfirewall firewall add rule name=Java dir=in action=allow program='D:\\BuildAgent\\jre\\bin\\java.exe' ENABLE=yes\"", this does not work install_options => [ '/s','STATIC=1','JAVAUPDATE=0','AUTOUPDATECHECK=0', 'INSTALLDIR=\"$::agenthome\"\jre'], Thanks Helen -- 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/ef2cd5ee-4d09-48de-adfc-89a419e29e87%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] No resources and catalog information with puppetdb
Hello, with my puppetdb - I can't query any resource or catalog - exported resources are not working This is working : # echo '["=", ["fact", "rubyversion"], "1.8.7"]' > queryfile # curl -X GET http://localhost:8080/v3/nodes --data-urlencode query@queryfile 2>/dev/null | tail -7 }, { "name" : "el6.labolinux.fr", "deactivated" : null, "catalog_timestamp" : null, "facts_timestamp" : "2014-02-25T08:18:07.529Z", "report_timestamp" : "2014-02-25T08:18:10.018Z" I can also query with success the facts, metrics, reports (reports=store,puppetdb) endpoints. But it is not working with the resources or catalog endpoint : curl -X GET 'http://localhost:8080/v3/resources/User' -> [] curl -X GET 'http://localhost:8080/v3/resources/Package' -> [] curl -X GET 'http://localhost:8080/v3/resources/File' -> [] curl -X GET http://localhost:8080/v3/catalogs/el6.labolinux.fr -> { "error" : "Could not find catalog for el6.labolinux.fr" } curl -X GET http://localhost:8080/v3/nodes 2>/dev/null | grep name | grep el6.labolinux.fr -> "name" : "el6.labolinux.fr", In addition, this is not working from the puppet master : # puppet node status el6.labolinux.fr Error: Could not retrieve status for el6.labolinux.fr: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A # puppet cert list el6.labolinux.fr + "el6.labolinux.fr" (SHA256) 76:00:C9:B9:0C:31:61:9C:A5:D9:B4:49:D7:17:39:76:15:9D:18:2C:E0:07:41:6B:6C:3A:4D:68:E1:BF:65:0D I think that a consequence is that my exported resources don't work. Here is my configuration. On the master : # dpkg-query -W | egrep 'puppet(master|db)' puppetdb-terminus 1.6.2-1puppetlabs1 puppetmaster3.4.3-1puppetlabs1 puppetmaster-common 3.4.3-1puppetlabs1 In puppet.conf on the master : [master] storeconfigs=true storeconfig_backend=puppetdb reports=store,puppetdb In routes.yaml on the master : --- master: facts: terminus: puppetdb cache: yaml In puppetdb.conf on the master : [main] server=el6.labolinux.fr port=8081 soft_write_failure=true On the puppetdb node : [root@el6 ~]# rpm -qa | grep '^puppet' puppet-3.3.2-1.el6.noarch puppetdb-1.6.2-1.el6.noarch Database backend configuration : [database] classname = org.postgresql.Driver subprotocol = postgresql subname = //127.0.0.1:5432/puppetdb username = puppetdb What am I missing ? Louis Coilliot -- 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/CAE9jN32UqUR3uTuHNJqse5hBiLr84qCwC6ri3TD9oFJSY%2BumJA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Best practices: client/server VS Git
On Thu, Feb 20, 2014 at 07:15:50AM -0800, Julien Deloubes wrote: > Hello there, > i'm actually learning Puppet in order to pass the exam. > I have no professional experience on the product yet, and wanting some > feedback from you professional devops. > For the moment i see 2 ways for Puppet to synchronize nodes: > -Puppet client/server way with a puppetmaster node This is the approach we are currently taking and it allows you to use virtual resources. This is the only thing which should drive you to this setup - the other is much simpler in my opinion. Of course there might be a way to use a central PuppetDB service in masterless setup but at least I am unaware of how to do this. > -Decentralized way, with node pull their configuration from a Git repo and > make a puppet apply on their own. This is the thing that we were doing until there were some needs for hosts to configure them selfs based on configuration on other hosts(virtual resources) > > Can you told me what is the pro/cons for this two methods? > And for a large scale of node which is the preferred one? > > Thanks for your help. > > -- 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/20140225090149.GD26036%40nikolavp-desktop. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Let puppet configure your monitoring (here: nimsoft)
I am not familiar with nimsoft but I will try to help anyways here - sorry if I am missing something but you can correct me. Let's say you want to monitor the oracle instance: First you specify the nimsoft_oracle_connection you already have written(as I saw from the readme in github) and then on the actual server that is checking each host in your network you will have build the configuration with something like https://github.com/dalen/puppet-puppetdbquery. For that you will surely need a puppetDB configuration setup that is connected to your puppet master. Something like the following should then work(WARNING not tested code): class nimsoft::server { $hosts = query_nodes('Nimsoft_oracle_connection["PROD""]') file { '/etc/nimsoft-config-file': template('template-that-interpolates-hosts variable') } } Hope this helps at least a little -- Nikola On Sun, Feb 23, 2014 at 11:01:10PM +0100, Stefan Schulte wrote: > Hi puppet users, > > just wanted to know if there are any puppet users who are using nimsoft > as a monitoring tool? We are currently switching to nimsoft at $work and > I noticed that for a proper monitoring configuration I need information > that is already written down in our puppet manifests. > > E.g. to correctly set up logfile monitoring I need to know if the server > is running an oralce database and if so I need to know the configured > oracle instances and the location of the alertlog files. Since we > install the oracle software and instances through puppet, puppet already > has all the info. > > I created a few custom types to modify the nimsoft agent's configuration > [1] and would love to get some feedback from other nimsoft users or just > share your experience with nimsoft and puppet and how you automate things. > > If you use a different monitoring tool: How much is your monitoring > puppetized? Do you configure your monitoring by hand? Is your monitoring > system so smart that it does not need a lot of manual configuration, or > do you use tools like puppet to automatically create configurations? > > -Stefan > > [1] https://github.com/stschulte/puppet-nimsoft > > -- > 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/530A6FA6.6070904%40taunusstein.net. > 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140225083238.GC26036%40nikolavp-desktop. For more options, visit https://groups.google.com/groups/opt_out.