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 D
On 5/15/2012 2:06 PM, Eric wrote:
PassengerHighPerformance on
PassengerUseGlobalQueue on
PassengerMaxRequests 9
PassengerPoolIdleTime 60
PassengerMaxPoolSize 64
PassengerMinInstances 16
PassengerMaxInstancesPerApp 9
Your setting are as they say, not even wrong.
Try the following in the
I am having an issue with my Puppet agents receiving "connection reset by
peer" errors. I only have 4 puppet agent systems in my environment right
now. I have two Puppet Master servers running Apache HTTPD with
mod_passenger. I have disabled the "puppetmaster" service and am only
running HTTPD. See
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 uns
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 wrot
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
