Hi, everyone All works normally, but sometimes I get error like: err: Could not run Puppet configuration client: Connection reset by peer Could not retrieve file metadata for puppet:///modules/port_bind9/example.com: Connection reset by peer at /usr/local/etc/puppet/modules/port_bind9/manifests/templates.pp:36 And each time the file that couldn''t be retreived is different. Sometimes it completed without errors. Server is mongrel with nginx. It''s strange that at access.log there are 5 requests of the each file like this: 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" Also I have checked traffic using wireshark. At the result file there is only the same that I can found at access.log. The trace also don''t give me a information: debug: Finishing transaction 17213724860 debug: Loaded state in 0.01 seconds debug: Using cached certificate for ca debug: Using cached certificate for dns.space.lenobl.com debug: Using cached certificate_revocation_list for ca debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson info: Caching catalog for dns.space.lenobl.com debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson /usr/local/lib/ruby/site_ruby/1.8/puppet/parameter.rb:171:in `fail'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:153:in `init_metadata'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:145:in `each'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:145:in `init_metadata'' /usr/local/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:106:in `send'' /usr/local/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:106:in `cached_value'' /usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'' /usr/local/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:98:in `cached_value'' /usr/local/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:48:in `metadata'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:109:in `copy_source_values'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file.rb:622:in `retrieve'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:703:in `retrieve_resource'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1874:in `to_trans'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file.rb:691:in `to_trans'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1899:in `to_resource'' /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:203:in `uniqueness_key'' /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:83:in `add_resource'' /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:72:in `each'' /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:72:in `add_resource'' /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:561:in `to_catalog'' /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:531:in `each'' /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:531:in `to_catalog'' /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:468:in `to_ral'' /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:113:in `convert_catalog'' /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:108:in `retrieve_catalog'' /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:139:in `run'' /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'' /usr/local/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'' /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'' /usr/local/lib/ruby/1.8/sync.rb:230:in `synchronize'' /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'' /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:103:in `with_client'' /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:37:in `run'' /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:171:in `call'' /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:171:in `controlled_run'' /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:35:in `run'' /usr/local/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:114:in `onetime'' /usr/local/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:88:in `run_command'' /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:304:in `run'' /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:410:in `exit_on_fail'' /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:304:in `run'' /usr/local/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:59:in `execute'' /usr/local/bin/puppet:4 err: Could not run Puppet configuration client: Connection reset by peer Could not retrieve file metadata for puppet:///modules/port_bind9/example.com: Connection reset by peer at /usr/local/etc/puppet/modules/port_bind9/manifests/templates.pp:36 Is it normally that puppet agent make 5 requests of each file? It this error on agent or on a server side? -- 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.
Hi, Don''t know the cause of that error but mongrel isn''t recommended to run the puppetmaster. Passenger is preferred. Suffice to say, it sounds like a timeout issue possibly related to dns responses or just that it runs poorly under that stack. Cheers, Den On 30/04/2011, at 0:13, Dmitry <dkhramtsov.spb@gmail.com> wrote:> Hi, everyone > > All works normally, but sometimes I get error like: > err: Could not run Puppet configuration client: Connection reset by peer Could not retrieve file metadata for puppet:///modules/port_bind9/example.com: Connection reset by peer at /usr/local/etc/puppet/modules/port_bind9/manifests/templates.pp:36 > And each time the file that couldn''t be retreived is different. Sometimes it completed without errors. > > Server is mongrel with nginx. It''s strange that at access.log there are 5 requests of the each file like this: > 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" > 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" > 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" > 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" > 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" > 192.168.0.23 - - [29/Apr/2011:17:50:20 +0400] "GET /production/file_metadata/modules/jail_at_space/resolv.conf HTTP/1.1" 200 317 "-" "-" > > Also I have checked traffic using wireshark. At the result file there is only the same that I can found at access.log. > > The trace also don''t give me a information: > debug: Finishing transaction 17213724860 > debug: Loaded state in 0.01 seconds > debug: Using cached certificate for ca > debug: Using cached certificate for dns.space.lenobl.com > debug: Using cached certificate_revocation_list for ca > debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson > info: Caching catalog for dns.space.lenobl.com > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > /usr/local/lib/ruby/site_ruby/1.8/puppet/parameter.rb:171:in `fail'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:153:in `init_metadata'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:145:in `each'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:145:in `init_metadata'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:106:in `send'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:106:in `cached_value'' > /usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:98:in `cached_value'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:48:in `metadata'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:109:in `copy_source_values'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file.rb:622:in `retrieve'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:703:in `retrieve_resource'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1874:in `to_trans'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type/file.rb:691:in `to_trans'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1899:in `to_resource'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:203:in `uniqueness_key'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:83:in `add_resource'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:72:in `each'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:72:in `add_resource'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:561:in `to_catalog'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:531:in `each'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:531:in `to_catalog'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:468:in `to_ral'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:113:in `convert_catalog'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:108:in `retrieve_catalog'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:139:in `run'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'' > /usr/local/lib/ruby/1.8/sync.rb:230:in `synchronize'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:103:in `with_client'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:37:in `run'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:171:in `call'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:171:in `controlled_run'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:35:in `run'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:114:in `onetime'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:88:in `run_command'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:304:in `run'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:410:in `exit_on_fail'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:304:in `run'' > /usr/local/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:59:in `execute'' > /usr/local/bin/puppet:4 > err: Could not run Puppet configuration client: Connection reset by peer Could not retrieve file metadata for puppet:///modules/port_bind9/example.com: Connection reset by peer at /usr/local/etc/puppet/modules/port_bind9/manifests/templates.pp:36 > > > Is it normally that puppet agent make 5 requests of each file? > It this error on agent or on a server side? > -- > 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.-- 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.
Thank you!!! It was a problem with DNS-server. The second DNS-server, that was in resolv.conf, don''t answer for requests. -- 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.
I had same issue, related to DNS cache. I changed the IP address in /etc/hosts but it was still resolving to the old IP. on CentOS, you can flush dns cache with nscd -i hosts Le lundi 2 mai 2011 14:43:08 UTC+2, Dmitry a écrit :> > Thank you!!! > > It was a problem with DNS-server. > The second DNS-server, that was in resolv.conf, don''t answer for requests. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/nEpwd_wTERAJ. 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.