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. 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Patrick
2011-May-08 00:35 UTC
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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
treydock
2011-May-08 03:12 UTC
[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 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Christian Kauhaus
2011-May-09 06:37 UTC
Re: [Puppet Users] Re: Cannot dry run puppet on the puppetmaster
Am 08.05.2011 05:12, schrieb treydock:> Here''s the output using debug option. > [...] > 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 runThere''s not much to see here. It would probably more informative to start the server with the --debug flag and see what is going on there. Regards Christian -- Dipl.-Inf. Christian Kauhaus <>< · kc@gocept.com · systems administration gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 11 · fax +49 345 1229889 1 Zope and Plone consulting and development -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Reasonably Related Threads
- Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
- retrieving module directory
- Configuration is not applied notice: Finished catalog run in 0.01 seconds
- on puppet master server , puppet agent can't connect to itself
- Next Problem: Puppet 2.7 + Passenger won't connect