[Puppet Users] ENC - how to set order of operations?
I need to convert my resource based system to ENC. It's mostly straightforward but I'm not sure how to handle operations like these: Class['apt'] - Package| | -- 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/b6324c21-3725-480d-b2ab-33ee48577ba6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] ENC - how to set order of operations?
Right. So how would I declare this dependency setup if I stop using node files? On Monday, February 3, 2014 9:33:40 AM UTC-8, Jose Luis Ledesma wrote: Hi Perhaps I'm confused but an ENC stores node definition and not collector nor dependencies...doesn't it? Regards, El 03/02/2014 16:13, Jon Yeargers ethr...@gmail.com javascript: escribió: I need to convert my resource based system to ENC. It's mostly straightforward but I'm not sure how to handle operations like these: Class['apt'] - Package| | -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b6324c21-3725-480d-b2ab-33ee48577ba6%40googlegroups.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/89c4d5d6-1f79-454c-8d22-1e1fb9ce15d6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] ENC - how to set order of operations?
So if a given node is named in both an ENC and the site manifest... it will use both? IE If I have some definitions that I want to send everywhere and others that are node specific.. I can use both types of node entries? On Monday, February 3, 2014 10:14:52 AM UTC-8, Dan Bode wrote: On Mon, Feb 3, 2014 at 9:45 AM, Jon Yeargers ethr...@gmail.comjavascript: wrote: Right. So how would I declare this dependency setup if I stop using node files? Even if you use an ENC, Puppet will still consult your site manifest, so using an ENC does not preclude you from setting resource dependencies via collection in your site manifest. On Monday, February 3, 2014 9:33:40 AM UTC-8, Jose Luis Ledesma wrote: Hi Perhaps I'm confused but an ENC stores node definition and not collector nor dependencies...doesn't it? Regards, El 03/02/2014 16:13, Jon Yeargers ethr...@gmail.com escribió: I need to convert my resource based system to ENC. It's mostly straightforward but I'm not sure how to handle operations like these: Class['apt'] - Package| | -- 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/b6324c21-3725-480d-b2ab-33ee48577ba6% 40googlegroups.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...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/89c4d5d6-1f79-454c-8d22-1e1fb9ce15d6%40googlegroups.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/d0568d5a-450f-45e3-9d4e-7d85e2e07d60%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Port for ENC requests?
I'm trying to debug a new ENC setup. I created a short perl script to output a few lines of YAML. It runs fine on the puppet server but when I try it on a client I get this error: Warning: Error 400 on SERVER: Failed to find client.domain.org via exec: Execution of the '/etc/puppet/ENC/plug0.pl client.domain.org' returned 13: What I've tried: - turning off SELinux / adding exceptions * no change - running the script locally * runs fine - looking for errors in apache logs * nothing in there - looking for errors in $LOGDIR/messages * nothing there either What I'm wondering about is whether these requests need a certain port to be open in the firewall. The clients in question are connected via a VPN so the traffic is somewhat non-standard. Somewhere else I should be looking for errors? What does error 13 imply? -- 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/7fb3cc93-b3ef-41f8-a169-40bffc13e2d3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Getting agent v3.4 to manage my services
I corrected the problem by including this in my /etc/init.d/script: if [ -e $PIDFILE ] then exit 0 else exit 1 fi Put this in a 'status' command for your service control script. It works in puppet v3.4. On Monday, December 30, 2013 3:11:30 PM UTC-8, Edson Manners wrote: I had this same problem and couldn't figure out why it did it. I was moving from 2.7.23 to 3.x and it was driving me nuts, I never found what was the exact cause as there weren't any errors showing up and ' puppet agent -t' ran clean. I ended up blowing away my whole puppet/passenger/puppetdb install and starting from 3.4 in order to get past it. I wish you better luck. On 12/30/2013 06:04 PM, Jon Yeargers wrote: I have a group of services that are supposed to be maintained by puppet agent. Up until I moved from 2.6 to 3.4 they were kept up to date and running (as expected). Since the upgrade of the puppet agent these services are no longer being monitored. I'm sure that the server is still seeing the files as errors in them are flagged. Running 'puppet agent --debug' shows the requests for 'service name status' go by and yet even though the service is not running there is no move to start it. Running the 'service name start' command starts the service normally. So: what have I broken by upgrading my clients? As I mentioned - this used to work. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/dba2294d-826c-46d1-817c-6fd383818220%40googlegroups.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/2af667fc-8c33-491a-aa11-8fd369ba205e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Getting agent v3.4 to manage my services
I have a group of services that are supposed to be maintained by puppet agent. Up until I moved from 2.6 to 3.4 they were kept up to date and running (as expected). Since the upgrade of the puppet agent these services are no longer being monitored. I'm sure that the server is still seeing the files as errors in them are flagged. Running 'puppet agent --debug' shows the requests for 'service name status' go by and yet even though the service is not running there is no move to start it. Running the 'service name start' command starts the service normally. So: what have I broken by upgrading my clients? As I mentioned - this used to work. -- 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/dba2294d-826c-46d1-817c-6fd383818220%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] triggering 'apt-get update'?
I'm using the puppetforge 'apt' module to deal with some repositories. It
has 'always-apt-update' as a property and I've had it set to 'true' but I'm
wondering what happens if I don't.
Is the puppet package manager 'smart' enough to get the latest versions of
packages that it's monitoring ('ensure = latest') without being told to
keep the repository up to date?
The main reason I'm asking is that the 'apt-get update' seems to always run
last in the 'agent' pass. IE it takes two runs to get the latest packages -
1 to update the cache and the 2nd to get the latest versions.
--
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/f1848bdf-c513-4d27-a156-8f6847e60650%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Execution expired? Error message during agent run
Running 'puppet agent --test' - after 5-10 minutes of execution this error appeared: err: Could not run Puppet configuration client: execution expired When I ran the same command the execution resumed and continued to completion. -- 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/dd24edc8-dff5-44de-83d1-2b16e45e0d14%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
So am I SOL on this? Is ARM considered an 'unsupported architecture' until I can create a 'dmidecode' for this platform? On Wednesday, December 11, 2013 10:55:11 AM UTC-8, Jon Yeargers wrote: I can wget and install facter but the issues continue: root@plugpc-005:/tmp# apt-get install puppet Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: facter : Depends: dmidecode but it is not installable puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). root@plugpc-005:/tmp# apt-get install puppet-common Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: facter : Depends: dmidecode but it is not installable puppet-common : Depends: ruby-shadow but it is not installable or libshadow-ruby1.8 but it is not going to be installed Depends: libaugeas-ruby but it is not going to be installed or libaugeas-ruby1.9.1 but it is not going to be installed or libaugeas-ruby1.8 but it is not going to be installed Depends: hiera (= 1.0.0) but it is not going to be installed Depends: ruby-rgen (= 0.6.5) but it is not going to be installed Recommends: lsb-release but it is not going to be installed Recommends: debconf-utils but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). Attempts to install any of these packages gives me similar errors. On Wednesday, December 11, 2013 9:50:07 AM UTC-8, Jeff Bachtel wrote: You can fetch it directly (wget, curl, whatever) from http://apt.puppetlabs.com/pool/squeeze/main/f/facter/facter_1.6.18-1puppetlabs1_all.deb Jeff On 12/11/2013 12:39 PM, Jon Yeargers wrote: root@plugpc-005:~# apt-get install ruby libopenssl-ruby pciutils Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libruby' instead of 'libopenssl-ruby' pciutils is already the newest version. libruby is already the newest version. ruby is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. There isn't a 'download' option for apt-get on this system so I tried '--download-only': root@plugpc-005:~# apt-get --download-only install facter Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: facter : Depends: dmidecode but it is not installable E: Broken packages I added '--ignore-missing' but the result was the same. On Wednesday, December 11, 2013 7:47:02 AM UTC-8, Jeff Bachtel wrote: demidecode (which is a hard dependency for facter) is not available for armel in Debian's repository. I have confirmed that facter will not fail outright when dmidecode is missing. The following facter variables will not be created, however: bios_release_date bios_vendor bios_version boardmanufacturer boardproductname boardserialnumber manufacturer productname serialnumber type uuid If that's acceptable for you, you can try apt-get install ruby libopenssl-ruby pciutils apt-get download facter dpkg -i --force-depends facter*.deb apt-get install puppet This will manually install the other facter dependencies (which should exist for armel), download the facter .deb file, then do an install of it without checking depends. The puppet install should succeed after that. I think facter's dmidecode dependency should be a Suggests vice a Depends, and it might be worth filing a bugrep to get it changed. Jeff On 12/11/2013 10:31 AM, Jon Yeargers wrote: I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along with a few other things). Then tried 'apt-get install puppet-common' - this failed as 'facter' needed a higher version. .. so tried 'facter' but this failed with: facter : Depends : dmidecode but it is not installable If I do 'apt-cache search dmidecode' it isn't available. On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote: 'apt-get update' ran fine this time. 'apt-get install puppet': Some packages could not be installed. This may
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
Just out of curiosity I created my own 'dmidecode' package with a trivial (does nothing) dmidecode executable. Once this was installed the rest of puppet v 3.3.2 installed fine. NOW: it's having trouble accepting that certain services are already running and it's trying to restart them every time. Strangely enough it doesn't happen with 'system' services (EG apache2, snmpd) but only with my code. I can't imagine this is related to my fake dmidecode but I'll keep looking into it. On Friday, December 13, 2013 4:08:10 AM UTC-8, Felix.Frank wrote: Ideally, there will be a newly released facter package that replaces this dependency by a suggestion or recommendation. It will Just Work for you then. In the meantime, these are your options: a) fetch the facter source package and build a forked package without this dependency b) fetch all deb packages you require and install them in one go using dpkg -i --force-depends or similar. Option (a) is simple if you're versed in the creation of Debian packages, and pretty difficult if you're not. HTH, Felix On 12/13/2013 12:39 PM, Jon Yeargers wrote: So am I SOL on this? Is ARM considered an 'unsupported architecture' until I can create a 'dmidecode' for this platform? -- 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/40a9fd9d-127e-48b9-8c67-c284ca6bd694%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
Answer here: http://stackoverflow.com/questions/14607385/puppet-does-not-start-a-service-varnish-when-puppet-apply-is-run On Friday, December 13, 2013 11:07:01 AM UTC-8, Jon Yeargers wrote: Just out of curiosity I created my own 'dmidecode' package with a trivial (does nothing) dmidecode executable. Once this was installed the rest of puppet v 3.3.2 installed fine. NOW: it's having trouble accepting that certain services are already running and it's trying to restart them every time. Strangely enough it doesn't happen with 'system' services (EG apache2, snmpd) but only with my code. I can't imagine this is related to my fake dmidecode but I'll keep looking into it. On Friday, December 13, 2013 4:08:10 AM UTC-8, Felix.Frank wrote: Ideally, there will be a newly released facter package that replaces this dependency by a suggestion or recommendation. It will Just Work for you then. In the meantime, these are your options: a) fetch the facter source package and build a forked package without this dependency b) fetch all deb packages you require and install them in one go using dpkg -i --force-depends or similar. Option (a) is simple if you're versed in the creation of Debian packages, and pretty difficult if you're not. HTH, Felix On 12/13/2013 12:39 PM, Jon Yeargers wrote: So am I SOL on this? Is ARM considered an 'unsupported architecture' until I can create a 'dmidecode' for this platform? -- 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/0b3e34b1-e3e1-4e8d-8a3a-23ab6be1bf8d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
'apt-get update' ran fine this time. 'apt-get install puppet': Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but 2.6.2-5+squeeze8 is to be installed E: Broken packages I also tried uninstalling puppet and then doing the install. Same result. On Tuesday, December 10, 2013 3:11:27 PM UTC-8, Moses Mendoza wrote: Hi all, apt.puppetlabs.com has been updated with additional architectures so the 'all' packages should install. Can you check if you still have the same issues? On Tue, Dec 10, 2013 at 12:01 PM, Moses Mendoza mo...@puppetlabs.comjavascript: wrote: On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers ethr...@gmail.comjavascript: wrote: I updated the repository file using the official puppet-recommended version. The corrected line is: deb http://apt.puppetlabs.com squeeze main (i mistakenly entered 'wheezy' above). When I do 'apt-get update' I'm told: W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/ReleaseUnable to find expected entry main/binary-armel/Packages in Meta-index file (malformed Release file?) On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote: That's not the issue at all I think. Is that source.list entry from a howto? Have you tried the instructions here: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu Because what apt is making of your configuration is plain wrong. On 12/10/2013 05:50 PM, Jon Yeargers wrote: If I create a '/etc/apt/sources.list.d/puppet.list' with: deb http://apt.puppetlabs.com/pool wheezy stable I get: Failed to fetch http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz 404 Not Found I'm thinking that I might need to set this up on an x86 machine and then rebuild the package file myself in a private repository. My apologies - this is a problem with our apt repository configuration - we did not set it up to include architectures other than i386 and amd64. We will be remedying this soon, so that while we may not yet have arm-specific packages, at least our all-arch packages will work. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0e4f7484-682f-44c9-b370-5a977d4085ee%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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/a2bd1ecb-dd6a-42cb-9ffc-333e9cfdc0db%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along with a few other things). Then tried 'apt-get install puppet-common' - this failed as 'facter' needed a higher version. .. so tried 'facter' but this failed with: facter : Depends : dmidecode but it is not installable If I do 'apt-cache search dmidecode' it isn't available. On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote: 'apt-get update' ran fine this time. 'apt-get install puppet': Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but 2.6.2-5+squeeze8 is to be installed E: Broken packages I also tried uninstalling puppet and then doing the install. Same result. On Tuesday, December 10, 2013 3:11:27 PM UTC-8, Moses Mendoza wrote: Hi all, apt.puppetlabs.com has been updated with additional architectures so the 'all' packages should install. Can you check if you still have the same issues? On Tue, Dec 10, 2013 at 12:01 PM, Moses Mendoza mo...@puppetlabs.com wrote: On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers ethr...@gmail.com wrote: I updated the repository file using the official puppet-recommended version. The corrected line is: deb http://apt.puppetlabs.com squeeze main (i mistakenly entered 'wheezy' above). When I do 'apt-get update' I'm told: W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/ReleaseUnable to find expected entry main/binary-armel/Packages in Meta-index file (malformed Release file?) On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote: That's not the issue at all I think. Is that source.list entry from a howto? Have you tried the instructions here: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu Because what apt is making of your configuration is plain wrong. On 12/10/2013 05:50 PM, Jon Yeargers wrote: If I create a '/etc/apt/sources.list.d/puppet.list' with: deb http://apt.puppetlabs.com/pool wheezy stable I get: Failed to fetch http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz 404 Not Found I'm thinking that I might need to set this up on an x86 machine and then rebuild the package file myself in a private repository. My apologies - this is a problem with our apt repository configuration - we did not set it up to include architectures other than i386 and amd64. We will be remedying this soon, so that while we may not yet have arm-specific packages, at least our all-arch packages will work. -- 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/0e4f7484-682f-44c9-b370-5a977d4085ee%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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/96382244-64e6-458e-a33a-81f24a4befbf%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
root@plugpc-005:~# apt-get install ruby libopenssl-ruby pciutils Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libruby' instead of 'libopenssl-ruby' pciutils is already the newest version. libruby is already the newest version. ruby is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. There isn't a 'download' option for apt-get on this system so I tried '--download-only': root@plugpc-005:~# apt-get --download-only install facter Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: facter : Depends: dmidecode but it is not installable E: Broken packages I added '--ignore-missing' but the result was the same. On Wednesday, December 11, 2013 7:47:02 AM UTC-8, Jeff Bachtel wrote: demidecode (which is a hard dependency for facter) is not available for armel in Debian's repository. I have confirmed that facter will not fail outright when dmidecode is missing. The following facter variables will not be created, however: bios_release_date bios_vendor bios_version boardmanufacturer boardproductname boardserialnumber manufacturer productname serialnumber type uuid If that's acceptable for you, you can try apt-get install ruby libopenssl-ruby pciutils apt-get download facter dpkg -i --force-depends facter*.deb apt-get install puppet This will manually install the other facter dependencies (which should exist for armel), download the facter .deb file, then do an install of it without checking depends. The puppet install should succeed after that. I think facter's dmidecode dependency should be a Suggests vice a Depends, and it might be worth filing a bugrep to get it changed. Jeff On 12/11/2013 10:31 AM, Jon Yeargers wrote: I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along with a few other things). Then tried 'apt-get install puppet-common' - this failed as 'facter' needed a higher version. .. so tried 'facter' but this failed with: facter : Depends : dmidecode but it is not installable If I do 'apt-cache search dmidecode' it isn't available. On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote: 'apt-get update' ran fine this time. 'apt-get install puppet': Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but 2.6.2-5+squeeze8 is to be installed E: Broken packages I also tried uninstalling puppet and then doing the install. Same result. On Tuesday, December 10, 2013 3:11:27 PM UTC-8, Moses Mendoza wrote: Hi all, apt.puppetlabs.com has been updated with additional architectures so the 'all' packages should install. Can you check if you still have the same issues? On Tue, Dec 10, 2013 at 12:01 PM, Moses Mendoza mo...@puppetlabs.com wrote: On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers ethr...@gmail.com wrote: I updated the repository file using the official puppet-recommended version. The corrected line is: deb http://apt.puppetlabs.com squeeze main (i mistakenly entered 'wheezy' above). When I do 'apt-get update' I'm told: W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/ReleaseUnable to find expected entry main/binary-armel/Packages in Meta-index file (malformed Release file?) On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote: That's not the issue at all I think. Is that source.list entry from a howto? Have you tried the instructions here: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu Because what apt is making of your configuration is plain wrong. On 12/10/2013 05:50 PM, Jon Yeargers wrote: If I create a '/etc/apt/sources.list.d/puppet.list' with: deb http://apt.puppetlabs.com/pool wheezy stable I get: Failed to fetch http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz 404 Not Found I'm thinking that I might need to set this up on an x86 machine and then rebuild the package file myself in a private repository. My apologies - this is a problem with our apt repository configuration - we did
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
I can wget and install facter but the issues continue: root@plugpc-005:/tmp# apt-get install puppet Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: facter : Depends: dmidecode but it is not installable puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). root@plugpc-005:/tmp# apt-get install puppet-common Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: facter : Depends: dmidecode but it is not installable puppet-common : Depends: ruby-shadow but it is not installable or libshadow-ruby1.8 but it is not going to be installed Depends: libaugeas-ruby but it is not going to be installed or libaugeas-ruby1.9.1 but it is not going to be installed or libaugeas-ruby1.8 but it is not going to be installed Depends: hiera (= 1.0.0) but it is not going to be installed Depends: ruby-rgen (= 0.6.5) but it is not going to be installed Recommends: lsb-release but it is not going to be installed Recommends: debconf-utils but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). Attempts to install any of these packages gives me similar errors. On Wednesday, December 11, 2013 9:50:07 AM UTC-8, Jeff Bachtel wrote: You can fetch it directly (wget, curl, whatever) from http://apt.puppetlabs.com/pool/squeeze/main/f/facter/facter_1.6.18-1puppetlabs1_all.deb Jeff On 12/11/2013 12:39 PM, Jon Yeargers wrote: root@plugpc-005:~# apt-get install ruby libopenssl-ruby pciutils Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libruby' instead of 'libopenssl-ruby' pciutils is already the newest version. libruby is already the newest version. ruby is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. There isn't a 'download' option for apt-get on this system so I tried '--download-only': root@plugpc-005:~# apt-get --download-only install facter Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: facter : Depends: dmidecode but it is not installable E: Broken packages I added '--ignore-missing' but the result was the same. On Wednesday, December 11, 2013 7:47:02 AM UTC-8, Jeff Bachtel wrote: demidecode (which is a hard dependency for facter) is not available for armel in Debian's repository. I have confirmed that facter will not fail outright when dmidecode is missing. The following facter variables will not be created, however: bios_release_date bios_vendor bios_version boardmanufacturer boardproductname boardserialnumber manufacturer productname serialnumber type uuid If that's acceptable for you, you can try apt-get install ruby libopenssl-ruby pciutils apt-get download facter dpkg -i --force-depends facter*.deb apt-get install puppet This will manually install the other facter dependencies (which should exist for armel), download the facter .deb file, then do an install of it without checking depends. The puppet install should succeed after that. I think facter's dmidecode dependency should be a Suggests vice a Depends, and it might be worth filing a bugrep to get it changed. Jeff On 12/11/2013 10:31 AM, Jon Yeargers wrote: I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along with a few other things). Then tried 'apt-get install puppet-common' - this failed as 'facter' needed a higher version. .. so tried 'facter' but this failed with: facter : Depends : dmidecode but it is not installable If I do 'apt-cache search dmidecode' it isn't available. On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote: 'apt-get update' ran fine this time. 'apt-get install puppet': Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve
[Puppet Users] Re: Getting latest agent on debian for ARM?
I've tried using 'gem' to install the latest build but it brings down lots of (seemingly) unnecessary bits with it. (examples, docs, etc) On Thursday, December 5, 2013 9:16:15 AM UTC-8, Jon Yeargers wrote: I'm looking to deploy several hundred ARM based machines in the near future. At this point the puppet agent version available via apt (Debian 6) is 2.6. I tried adding the apt.puppetlabs.com repository but it won't install on my systems as the CPU type isn't supported. What are my options to get 3.x? I don't see a path to compile the source. Can I copy the relevant folders to a private repository and host from there? -- 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/8cb52b29-e9a4-4192-bb16-d7efa1917d65%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Problem with report processor - undefined method
I would love DEARLY to be able to update my clients (agents) but they are running on ARM processors and I can't get the update. I posted about this here and on askpuppet but haven't found an answer yet. On Tuesday, December 10, 2013 8:16:33 AM UTC-8, Jeff Bachtel wrote: If this is accurate, I can only warn that I've run into horribly annoying, manifest-breaking issues trying to run 2.6/2.7 clients with 3.3 servers. It may not be official advice, but if you can make puppet client versions track your puppet server closer, you will have much less headache. Jeff On Thu, Dec 5, 2013 at 7:29 PM, Jon Yeargers ethr...@gmail.comjavascript: wrote: After I got puppetdb working I was looking about at the various bits of data available. Looking at the 'nodes' option I was suprised to see this: report_timestamp : null for every node. They all have this for their puppet.conf: [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates [agent] server=server_name certname=client_name pluginsync=true report=true so I assumed they were reporting. TL;DR Looking at /var/log/messages on the server I found these messages appearing: puppet-master[1090]: Report processor failed: undefined method `=' for nil:NilClass What's up? Have I misconfigured something? Clients: v 2.6 Server: v 3.3 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d0e27c25-4970-4ee8-bc75-680d057ff9aa%40googlegroups.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/d9c94126-51b1-4406-b522-6d21ef002209%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Getting latest agent on debian for ARM?
If I create a '/etc/apt/sources.list.d/puppet.list' with: deb http://apt.puppetlabs.com/pool wheezy stable I get: Failed to fetch http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz 404 Not Found I'm thinking that I might need to set this up on an x86 machine and then rebuild the package file myself in a private repository. On Tuesday, December 10, 2013 8:22:36 AM UTC-8, Jon Yeargers wrote: I've tried using 'gem' to install the latest build but it brings down lots of (seemingly) unnecessary bits with it. (examples, docs, etc) On Thursday, December 5, 2013 9:16:15 AM UTC-8, Jon Yeargers wrote: I'm looking to deploy several hundred ARM based machines in the near future. At this point the puppet agent version available via apt (Debian 6) is 2.6. I tried adding the apt.puppetlabs.com repository but it won't install on my systems as the CPU type isn't supported. What are my options to get 3.x? I don't see a path to compile the source. Can I copy the relevant folders to a private repository and host from there? -- 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/a1b10982-5296-448e-b27b-608142dd47ef%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
I updated the repository file using the official puppet-recommended version. The corrected line is: deb http://apt.puppetlabs.com squeeze main (i mistakenly entered 'wheezy' above). When I do 'apt-get update' I'm told: W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/Release Unable to find expected entry main/binary-armel/Packages in Meta-index file (malformed Release file?) On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote: That's not the issue at all I think. Is that source.list entry from a howto? Have you tried the instructions here: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu Because what apt is making of your configuration is plain wrong. On 12/10/2013 05:50 PM, Jon Yeargers wrote: If I create a '/etc/apt/sources.list.d/puppet.list' with: deb http://apt.puppetlabs.com/pool wheezy stable I get: Failed to fetch http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz 404 Not Found I'm thinking that I might need to set this up on an x86 machine and then rebuild the package file myself in a private repository. -- 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/0e4f7484-682f-44c9-b370-5a977d4085ee%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Problem with report processor - undefined method
On further inspections the YAML files are still being created but not the puppet db entries. On Thursday, December 5, 2013 4:29:44 PM UTC-8, Jon Yeargers wrote: After I got puppetdb working I was looking about at the various bits of data available. Looking at the 'nodes' option I was suprised to see this: report_timestamp : null for every node. They all have this for their puppet.conf: [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates [agent] server=server_name certname=client_name pluginsync=true report=true so I assumed they were reporting. TL;DR Looking at /var/log/messages on the server I found these messages appearing: puppet-master[1090]: Report processor failed: undefined method `=' for nil:NilClass What's up? Have I misconfigured something? Clients: v 2.6 Server: v 3.3 -- 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/6abed7eb-6cb9-439e-93be-01524276fed7%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Getting latest agent on debian for ARM?
I'm looking to deploy several hundred ARM based machines in the near future. At this point the puppet agent version available via apt (Debian 6) is 2.6. I tried adding the apt.puppetlabs.com repository but it won't install on my systems as the CPU type isn't supported. What are my options to get 3.x? I don't see a path to compile the source. Can I copy the relevant folders to a private repository and host from there? -- 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/06eb5267-9326-4a5b-91d8-cf55c734aaad%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppetdb not responding since 'yum update'
I did `yum update` on my puppet server about a week ago. Up to that point I had puppet and puppetdb running on the same machine. Since the update puppetdb doesn't appear to be listening on port 8081 anymore. When I run `puppet agent --test` on a client I get this error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for plugpc-005.client to PuppetDB at puppet.server:8081: Connection refused - connect(2) Looking at `nmap -P0 puppet.server` shows that port 8081 isn't open. Trying `telnet puppet.server 8081` confirms this. My configs are all set using the values from [here].(http://docs.puppetlabs.com/puppetdb/latest/connect_puppet_master.html). `ps -ax` shows that the processes are running: 2040 ?Ss 4:55 /usr/sbin/openvpn --daemon --writepid /var/run/openvpn/puppet.pid --config puppet.conf --cd /etc/openvpn --script-security 2 29737 ?Sl 0:37 /usr/bin/java -XX:OnOutOfMemoryError=kill -9 %p -Xmx192m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -jar /usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.d 29924 ?Sl 0:01 Passenger AppPreloader: /usr/share/puppet/rack/puppetmasterd 29963 ?Sl 0:00 Passenger RackApp: /usr/share/puppet/rack/puppetmasterd The output of `netstat -nap | grep 8081` is empty. Turning off iptables doesn't make any difference. (not that it would - nobody is listening at the port anyway) NOTE: This system was working ok before the update. I could download configs to clients and query the db for the results. So - what did I break? -- 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/f4f93c97-a763-40c4-96c6-6c341893fc74%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppetdb not responding since 'yum update'
I used 'puppetdb-ssl-setup' (after removing the ssl folder) to no avail. (sorry about cross posting - I thought I had removed the 'ask' entry) On Thursday, December 5, 2013 12:25:24 PM UTC-8, Ken Barber wrote: I responded to this in ask, but I'll answer here also. In the file /etc/puppetdb/conf.d/jetty.ini, the settings ssl-host and ssl-port must be set to listen on the SSL port (8081). However, if your ssl certs aren't yet configured this may fail for you. Usually puppetdb-ssl-setup is a good way to set these up automatically, so try this first. For ssl-host I usually recommend something like ::1 or 0.0.0.0 to listen on all ports for simplicity, but you can make this explicit if you like. ken. On Thu, Dec 5, 2013 at 7:48 PM, Jon Yeargers ethr...@gmail.comjavascript: wrote: I did `yum update` on my puppet server about a week ago. Up to that point I had puppet and puppetdb running on the same machine. Since the update puppetdb doesn't appear to be listening on port 8081 anymore. When I run `puppet agent --test` on a client I get this error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for plugpc-005.client to PuppetDB at puppet.server:8081: Connection refused - connect(2) Looking at `nmap -P0 puppet.server` shows that port 8081 isn't open. Trying `telnet puppet.server 8081` confirms this. My configs are all set using the values from [here].( http://docs.puppetlabs.com/puppetdb/latest/connect_puppet_master.html). `ps -ax` shows that the processes are running: 2040 ?Ss 4:55 /usr/sbin/openvpn --daemon --writepid /var/run/openvpn/puppet.pid --config puppet.conf --cd /etc/openvpn --script-security 2 29737 ?Sl 0:37 /usr/bin/java -XX:OnOutOfMemoryError=kill -9 %p -Xmx192m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -jar /usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.d 29924 ?Sl 0:01 Passenger AppPreloader: /usr/share/puppet/rack/puppetmasterd 29963 ?Sl 0:00 Passenger RackApp: /usr/share/puppet/rack/puppetmasterd The output of `netstat -nap | grep 8081` is empty. Turning off iptables doesn't make any difference. (not that it would - nobody is listening at the port anyway) NOTE: This system was working ok before the update. I could download configs to clients and query the db for the results. So - what did I break? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f4f93c97-a763-40c4-96c6-6c341893fc74%40googlegroups.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/6e94f3ef-4320-4b49-b430-10f646f220cc%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppetdb not responding since 'yum update'
Setting the 'ssl_host=' param to 0.0.0.0 turned the trick (so to speak). I kept trying variations on what the ssl cert was created for. Thank you for clearing this up for me. On Thursday, December 5, 2013 1:17:51 PM UTC-8, Ken Barber wrote: Can you show your jetty.ini? And the results of running puppetdb-ssl-setup ... the more information the better in these kinds of cases. Also - is PuppetDB listening to port 8080? On Thu, Dec 5, 2013 at 9:15 PM, Jon Yeargers ethr...@gmail.comjavascript: wrote: I used 'puppetdb-ssl-setup' (after removing the ssl folder) to no avail. (sorry about cross posting - I thought I had removed the 'ask' entry) On Thursday, December 5, 2013 12:25:24 PM UTC-8, Ken Barber wrote: I responded to this in ask, but I'll answer here also. In the file /etc/puppetdb/conf.d/jetty.ini, the settings ssl-host and ssl-port must be set to listen on the SSL port (8081). However, if your ssl certs aren't yet configured this may fail for you. Usually puppetdb-ssl-setup is a good way to set these up automatically, so try this first. For ssl-host I usually recommend something like ::1 or 0.0.0.0 to listen on all ports for simplicity, but you can make this explicit if you like. ken. On Thu, Dec 5, 2013 at 7:48 PM, Jon Yeargers ethr...@gmail.com wrote: I did `yum update` on my puppet server about a week ago. Up to that point I had puppet and puppetdb running on the same machine. Since the update puppetdb doesn't appear to be listening on port 8081 anymore. When I run `puppet agent --test` on a client I get this error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for plugpc-005.client to PuppetDB at puppet.server:8081: Connection refused - connect(2) Looking at `nmap -P0 puppet.server` shows that port 8081 isn't open. Trying `telnet puppet.server 8081` confirms this. My configs are all set using the values from [here].( http://docs.puppetlabs.com/puppetdb/latest/connect_puppet_master.html). `ps -ax` shows that the processes are running: 2040 ?Ss 4:55 /usr/sbin/openvpn --daemon --writepid /var/run/openvpn/puppet.pid --config puppet.conf --cd /etc/openvpn --script-security 2 29737 ?Sl 0:37 /usr/bin/java -XX:OnOutOfMemoryError=kill -9 %p -Xmx192m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -jar /usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.d 29924 ?Sl 0:01 Passenger AppPreloader: /usr/share/puppet/rack/puppetmasterd 29963 ?Sl 0:00 Passenger RackApp: /usr/share/puppet/rack/puppetmasterd The output of `netstat -nap | grep 8081` is empty. Turning off iptables doesn't make any difference. (not that it would - nobody is listening at the port anyway) NOTE: This system was working ok before the update. I could download configs to clients and query the db for the results. So - what did I break? -- 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/f4f93c97-a763-40c4-96c6-6c341893fc74%40googlegroups.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...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6e94f3ef-4320-4b49-b430-10f646f220cc%40googlegroups.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/ebec75a1-e06c-4931-9b31-b1955908cd02%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Agent speed - what is 'normal'?
(This is actually two questions): Running 'puppet agent --test' on a 1Ghz ARM based (Debian 6) fanless PC. It's pretty common to see the 'catalog run' take 120-300 seconds. Is this typical? Second (and possibly related): when I do a 'puppet agent --test (--noop)' I get this set of messages: info: Retrieving plugin info: Loading facts in facter_dot_d info: Loading facts in pe_version info: Loading facts in puppet_vardir info: Loading facts in root_home info: Loading facts in facter_dot_d info: Loading facts in pe_version info: Loading facts in puppet_vardir info: Loading facts in root_home Note the repeats. What have I misconfigured? -- 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/e1d50941-c0fb-44bf-aeae-923a2a8fc0d4%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Problem with report processor - undefined method
After I got puppetdb working I was looking about at the various bits of data available. Looking at the 'nodes' option I was suprised to see this: report_timestamp : null for every node. They all have this for their puppet.conf: [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates [agent] server=server_name certname=client_name pluginsync=true report=true so I assumed they were reporting. TL;DR Looking at /var/log/messages on the server I found these messages appearing: puppet-master[1090]: Report processor failed: undefined method `=' for nil:NilClass What's up? Have I misconfigured something? Clients: v 2.6 Server: v 3.3 -- 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/d0e27c25-4970-4ee8-bc75-680d057ff9aa%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
