Hello, After running the puppetmaster on Webrick and struggling with clients dropping regularly, I have decided to migrate my install to Mongrel. I have followed the documentation posted on the Puppet wiki but continue to receive the following errors on the client: err: Could not call puppetmaster.getconfig: #<RuntimeError: HTTP- Error: 502 Proxy Error> err: Could not retrieve configuration: HTTP-Error: 502 Proxy Error On the server log, the error is represented as the following: (20014)Internal error: proxy: error reading status line from remote server 127.0.0.1 proxy: NOT Closing connection to client although reading from backend server 127.0.0.1 failed. Here is the rundown of my environment: Debian 5.0 (Lenny) Apache 2.2.9 with all of the required modules (proxy, proxy_http, proxy_balancer) Puppet 0.24.5 installed using apt My Apache config is virtually identical to the one shown at http://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel, with the proper changes made. My /etc/default/puppetmaster configuration includes the following: START=yes SERVERTYPE=mongrel PUPPETMASTERS=2 PORT=18140 It is apparent that this is not so much of a puppetmaster issue as it is an Apache proxy issue, but I cannot seem to find anything regarding this particular issue when using puppet. Please let me know if there is any other information I can provide and I would be happy to do so. Thanks! -- 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.
Just wanted to report to say that I have still been unsuccessful with this. Any thoughts regarding the issue would be greatly appreciated. Thanks. On Dec 14, 12:54 pm, jkois <jeffrey.k...@gmail.com> wrote:> Hello, > After running the puppetmaster on Webrick and struggling with clients > dropping regularly, I have decided to migrate my install to Mongrel. I > have followed the documentation posted on the Puppet wiki but continue > to receive the following errors on the client: > err: Could not call puppetmaster.getconfig: #<RuntimeError: HTTP- > Error: 502 Proxy Error> > err: Could not retrieve configuration: HTTP-Error: 502 Proxy Error > > On the server log, the error is represented as the following: > (20014)Internal error: proxy: error reading status line from remote > server 127.0.0.1 > proxy: NOT Closing connection to client although reading from backend > server 127.0.0.1 failed. > > Here is the rundown of my environment: > Debian 5.0 (Lenny) > Apache 2.2.9 with all of the required modules (proxy, proxy_http, > proxy_balancer) > Puppet 0.24.5 installed using apt > > My Apache config is virtually identical to the one shown athttp://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel, > with the proper changes made. My /etc/default/puppetmaster > configuration includes the following: > START=yes > SERVERTYPE=mongrel > PUPPETMASTERS=2 > PORT=18140 > > It is apparent that this is not so much of a puppetmaster issue as it > is an Apache proxy issue, but I cannot seem to find anything regarding > this particular issue when using puppet. Please let me know if there > is any other information I can provide and I would be happy to do so. > > Thanks!-- 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.
On 12/20/2010 04:17 PM, jkois wrote:> Just wanted to report to say that I have still been unsuccessful with > this. Any thoughts regarding the issue would be greatly appreciated.First off, why not Passenger? Second, the puppet in lenny is really a bug-ridden old rag. Consider a) using a backport package b) rolling your own package or even c) installing your master by hand All are far superior to the lenny package. That being said,> On Dec 14, 12:54 pm, jkois <jeffrey.k...@gmail.com> wrote: >> Hello, >> After running the puppetmaster on Webrick and struggling with clients >> dropping regularly, I have decided to migrate my install to Mongrel. I >> have followed the documentation posted on the Puppet wiki but continue >> to receive the following errors on the client: >> err: Could not call puppetmaster.getconfig: #<RuntimeError: HTTP- >> Error: 502 Proxy Error> >> err: Could not retrieve configuration: HTTP-Error: 502 Proxy Error >> >> On the server log, the error is represented as the following: >> (20014)Internal error: proxy: error reading status line from remote >> server 127.0.0.1 >> proxy: NOT Closing connection to client although reading from backend >> server 127.0.0.1 failed. >> >> Here is the rundown of my environment: >> Debian 5.0 (Lenny) >> Apache 2.2.9 with all of the required modules (proxy, proxy_http, >> proxy_balancer) >> Puppet 0.24.5 installed using apt >> >> My Apache config is virtually identical to the one shown athttp://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel, >> with the proper changes made. My /etc/default/puppetmaster >> configuration includes the following: >> START=yes >> SERVERTYPE=mongrel >> PUPPETMASTERS=2 >> PORT=18140Have you tried and found out what the puppetmaster actually responds when sent an HTTP request? It''s obviously not what apache expects, so it is probably reporting some kind of error instead. It would go a long way to know what that response actually is. HTH, Felix -- 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 make a good case for simply upgrading to the backport version and using passenger - I had it working flawlessly within minutes. I had considered doing the upgrade but didn''t realize how big of a difference it would make. Thanks for the push required to take the leap! Just as a quick summary: I used the lenny backports to upgrade puppet to 2.6.x and followed the instructions at http://projects.puppetlabs.com/projects/puppet/wiki/Using_Passenger. Did not run into any unexpected issues that wasn''t covered in the documentation. Thanks again, Jeff On Dec 20, 10:34 am, Felix Frank <felix.fr...@alumni.tu-berlin.de> wrote:> On 12/20/2010 04:17 PM, jkois wrote: > > > Just wanted to report to say that I have still been unsuccessful with > > this. Any thoughts regarding the issue would be greatly appreciated. > > First off, why not Passenger? > Second, the puppet in lenny is really a bug-ridden old rag. Consider > a) using a backport package > b) rolling your own package or even > c) installing your master by hand > All are far superior to the lenny package. > > That being said, > > > > > On Dec 14, 12:54 pm, jkois <jeffrey.k...@gmail.com> wrote: > >> Hello, > >> After running the puppetmaster on Webrick and struggling with clients > >> dropping regularly, I have decided to migrate my install to Mongrel. I > >> have followed the documentation posted on the Puppet wiki but continue > >> to receive the following errors on the client: > >> err: Could not call puppetmaster.getconfig: #<RuntimeError: HTTP- > >> Error: 502 Proxy Error> > >> err: Could not retrieve configuration: HTTP-Error: 502 Proxy Error > > >> On the server log, the error is represented as the following: > >> (20014)Internal error: proxy: error reading status line from remote > >> server 127.0.0.1 > >> proxy: NOT Closing connection to client although reading from backend > >> server 127.0.0.1 failed. > > >> Here is the rundown of my environment: > >> Debian 5.0 (Lenny) > >> Apache 2.2.9 with all of the required modules (proxy, proxy_http, > >> proxy_balancer) > >> Puppet 0.24.5 installed using apt > > >> My Apache config is virtually identical to the one shown athttp://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel, > >> with the proper changes made. My /etc/default/puppetmaster > >> configuration includes the following: > >> START=yes > >> SERVERTYPE=mongrel > >> PUPPETMASTERS=2 > >> PORT=18140 > > Have you tried and found out what the puppetmaster actually responds > when sent an HTTP request? It''s obviously not what apache expects, so it > is probably reporting some kind of error instead. It would go a long way > to know what that response actually is. > > HTH, > Felix-- 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.