Dmitry wrote:> Or, if this situation is too uncommon, is there any way to ask puppet
> agent to always act as if master is running on remote host, even if it
> runs on the same host and to always communicate via network?
>
> Thanks.
>
> On Nov 15, 7:13 pm, Dmitry <trtrmi...@gmail.com> wrote:
>> Hello!
>>
>> I use puppet-2.7.6 to sync several config files in my network.
>> I use neither Mongrel nor Passenger (which probably means I use
>> Webrick as http backend).
>>
>> When I run puppet agent from another machine, everything is fine.
>>
>> When I run agent from the same machine server is running on, I get the
>> following error:
>> # puppet agent --server
>> =<hostname.com> --no-daemonize --onetime --verbose --no-show_diff
>> <skip>
>> err: /Stage[main]/Bsd/File[/root/.ssh/authorized_keys]: Could not
>> evaluate: Conn
>> ection reset by peer Could not retrieve file metadata for
puppet:///modules/bsd/
>> root/.ssh/authorized_keys: Connection reset by peer at /usr/local/etc/
>> puppet/mod
>> ules/bsd/manifests/init.pp:117
>>
>> If I run same command several times, I usually get the same error at
>> different stages (during request to different files puppet manages).
>> But error is always the same: Connection reset by peer.
>>
>> Sometimes it finishes w/o error, but almost always I get this error.
>> Some kind of random.
>>
>> What does it mean and how can I avoid it?
>>
>> Thanks!
>
Probably best to ask this question on the Puppet-user list rather than
the Puppet-dev list.
Regards
James Turnbull
--
James Turnbull
Puppet Labs
1-503-734-8571
To schedule a meeting with me: http://tungle.me/jamtur01
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.