Issue #10881 has been updated by Sean Kelly.

I, too, am seeing this on FreeBSD. I'm testing Puppet 3 on a second master and 
am getting Connection reset by peer quite frequently when running an agent 
against the local host.

[smkelly@spurs /usr/local/etc/puppet]$ sudo puppet agent --test --server 
`hostname`
...
Error: /Stage[main]/Sudo/File[sudoers]: Could not evaluate: Connection reset by 
peer Could not retrieve file metadata for puppet:///modules/sudo/sudoers: 
Connection reset by peer
Error: /Stage[main]/Bash/File[/etc/bashrc]: Could not evaluate: Connection 
reset by peer Could not retrieve file metadata for 
puppet:///modules/bash/bashrc: Connection reset by peer

It does not consistently fail in the same spot. I started puppet master with 
--debug, and there is nothing in the log that indicates anything.

Note that this is with the internal (WEbrick?) server. Since I'm testing a 
single client, it seemed overkill to do otherwise.

[smkelly@spurs /usr/local/etc/puppet]$ uname -a
FreeBSD spurs.hou.flightaware.com 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r244088: 
Mon Dec 10 16:49:40 UTC 2012     
[email protected]:/usr/obj/usr/src/sys/GENERIC  amd64
[smkelly@spurs /usr/local/etc/puppet]$ pkg_info|egrep '(ruby|puppet|facter)'
facter-1.6.16       A cross-platform Ruby library for retrieving facts from OS
puppet-3.0.2_1      A configuration management framework written in Ruby
ruby-1.8.7.371,1    An object-oriented interpreted scripting language
ruby18-bdb-0.6.6    Ruby interface to Sleepycat's Berkeley DB revision 2 or lat
ruby18-gems-1.8.24  Package management framework for the Ruby language
ruby18-iconv-1.8.7.371,1 An iconv wrapper class for Ruby
rubygem-bzip2-0.2.7 Ruby C bindings to libbzip2
rubygem-hiera-1.1.2 A pluggable data store for hierarchical data
rubygem-json_pure-1.7.6 Parse JSON texts and generate them from ruby data 
structure
rubygem-ruby-augeas-0.4.1 Ruby bindings for Augeas

----------------------------------------
Bug #10881: Could not evaluate: Connection reset by peer Could not retrieve 
file metadata
https://projects.puppetlabs.com/issues/10881#change-82289

Author: Lenny Smith
Status: Investigating
Priority: Normal
Assignee: 
Category: 
Target version: 
Affected Puppet version: 2.7.6
Keywords: 
Branch: 


Getting a bunch of these errors, while trying to run puppetd --test 
**locally**. Other remote puppet clients can use this host as puppet master 
without any problems. Also, this host can use other hosts as puppet masters 
without errors during client runs.
Note: these problems appear from time to time and always are different 
regarding their resources. Sometimes no errors are produced at all (run 
performs successfully).

puppet 2.7.6 + nginx + passenger
freebsd 8.2

Both A and PTR records are present for puppet.myhost.com.

Full random error example:

    puppet.myhost.com #> puppetd --test --server=puppet.myhost.com
    info: Caching catalog for puppet.myhost.com
    info: Applying configuration version '1321454159'
    err: /Stage[main]/Rsync::Freebsd/File[/usr/local/etc/rsyncd.conf]: Could 
not evaluate: Connection reset by peer Could not retrieve file metadata for 
puppet:///rsync/myhost.com/rsyncd.conf: Connection reset by peer at 
/home/puppet/rsync/init.pp:61                                                   
                                                                
    notice: /Stage[main]/Rsync::Freebsd/Service[rsyncd]: Dependency 
File[/usr/local/etc/rsyncd.conf] has failures: true
    warning: /Stage[main]/Rsync::Freebsd/Service[rsyncd]: Skipping because of 
failed dependencies
    notice: Finished catalog run in 3.19 seconds

Thanks in advance.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to