[Puppet Users] Cannot dry run puppet on the puppetmaster
For some reason I am unable to run dry runs of the puppet client on my puppetmaster server. Running puppetd with the --test, --noop and verbose / debug flags results in nothing for about a minute or two then this output... $ time puppetd --test --noop -v err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run err: Could not run Puppet configuration client: execution expired real4m2.971s user0m0.803s sys 0m2.115s There's nothing else in the logs besides that output. Not really sure how to debug this. All my other puppet clients function just fine. Thanks - Trey -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Dashboard Questions
There is bug open for your first question: http://projects.puppetlabs.com/issues/3535 On Fri, May 6, 2011 at 12:47 PM, Christopher Lee chr...@spiralweb.com wrote: Hello, I am playing with Puppet Dashboard and I have a few questions. First, as we start using puppet we are planning on running puppet agent from cron or via mcollective runs in --noop mode every few hours as an audit function. If anything is changed we would like to have it show up in Puppet Dashboard so we can alarm on it and then manually find out why it was changed before reverting back. I noticed dashboard only reports green good run, no errors or yellow changes where made. If I run in noop it returns green because no changes where made but I would like to see it tell me changes needed to be made but where not. Does this make since? Is there away to get this functionality? Second, we have two data centers and two puppet masters. I would like to run one dashboard. I can see from reporting this not to be a big deal but if I start using dashboard as an external node provider will I have issues. Looking at the settings.yml file for dashboard the setting seem to be very specific to one master. Am I going to start running into issue trying to use one dashboard with two puppetmaster (more more in the future). -chrisl -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Generate Compiled catalog/yaml for a node?
On Sat, May 7, 2011 at 5:50 AM, Yushu Yao y...@lbl.gov wrote: Thanks Folks for the answers. Before I go into this direction, I just want to make sure one thing from the developers: Is this a feature that you think will stay inside puppet? (in 3.0, 4.0, etc) Or has there been any discussion to remove this feature? Feel safer if I know this feature will stay long. Thanks You're only going to see more flexible control over out of band catalog compilation like this Yushu, not less. We won't be removing this feature, we'll be improving it. -- Nigel Kersten Product, Puppet Labs @nigelkersten -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Dashboard Questions
On Fri, May 6, 2011 at 4:47 PM, Christopher Lee chr...@spiralweb.comwrote: Hello, I am playing with Puppet Dashboard and I have a few questions. First, as we start using puppet we are planning on running puppet agent from cron or via mcollective runs in --noop mode every few hours as an audit function. If anything is changed we would like to have it show up in Puppet Dashboard so we can alarm on it and then manually find out why it was changed before reverting back. I noticed dashboard only reports green good run, no errors or yellow changes where made. If I run in noop it returns green because no changes where made but I would like to see it tell me changes needed to be made but where not. Does this make since? Is there away to get this functionality? Chris, we're actually working on this exact issue in the next few days, showing Pending changes in a much more obvious manner with noop/simulation runs. We'll have this ready within the next two Dashboard point releases. Second, we have two data centers and two puppet masters. I would like to run one dashboard. I can see from reporting this not to be a big deal but if I start using dashboard as an external node provider will I have issues. Looking at the settings.yml file for dashboard the setting seem to be very specific to one master. Am I going to start running into issue trying to use one dashboard with two puppetmaster (more more in the future). As far as an external node classifier goes, you really shouldn't have problems with multiple masters, both configured to use Dashboard as their ENC. -- Nigel Kersten Product, Puppet Labs @nigelkersten -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Cannot dry run puppet on the puppetmaster
On May 7, 2011, at 12:13 AM, treydock wrote: For some reason I am unable to run dry runs of the puppet client on my puppetmaster server. Running puppetd with the --test, --noop and verbose / debug flags results in nothing for about a minute or two then this output... $ time puppetd --test --noop -v err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run err: Could not run Puppet configuration client: execution expired real 4m2.971s user 0m0.803s sys 0m2.115s There's nothing else in the logs besides that output. Not really sure how to debug this. All my other puppet clients function just fine. As generic advice, I'd try adding the --debug flag. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Cannot dry run puppet on the puppetmaster
Here's the output using debug option. $ puppetd --debug -v --test --noop debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ dscl does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows is missing debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/ var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/classes.txt]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/ var/lib/puppet/state] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/certs/host.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/public_keys/host.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/ssl/private_keys/host.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/run/puppet/agent.pid]: Autorequiring File[/var/run/ puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/ lib/puppet/state] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/ lib/puppet] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: Finishing transaction 23490701527140 debug: /File[/var/lib/puppet/ssl/private_keys/host.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/certs/host.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/public_keys/host.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/ var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: Finishing transaction 23490701689280 debug: Using cached certificate for ca debug: Using cached certificate for host debug: Finishing transaction 23490701176540 debug: Loaded state in 0.00 seconds debug: Using cached certificate for ca debug: Using cached certificate for host debug: Using cached certificate_revocation_list for ca debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run debug: Using cached certificate for ca debug: Using cached certificate for itscantitheft.tamu.edu debug: Using cached certificate_revocation_list for ca debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (b64_zlib_yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using b64_zlib_yaml err: Could not run Puppet configuration client: execution expired Thanks - Trey On May 7, 7:35 pm, Patrick kc7...@gmail.com wrote: On May 7, 2011, at 12:13 AM,treydockwrote: For some reason I am unable
