Hey All, This is probably a gotcha of some kind. That is to say I''ve missed a configuration somewhere. I''ve recently moved over to using mongrel as the puppet server type and having nginx proxy to one of four mongrel instances. What I''m seeing though is that when I try to run a new node (one that has been created post moving to mongrel/nginx) is that it returns with the error: err: Could not retrieve catalog from remote server: wrong status line: "<html>" Nginx seems to be receiving the message (had a quick look at the log file). Though puppet doesn''t appear to be. The setup I''m using is for nginx > 0.8.7 as detailed on http://reductivelabs.com/trac/puppet/wiki/UsingMongrelNginx Thanks, Matt Delves -- 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.
Frank Sweetser
2009-Dec-22 04:18 UTC
Re: [Puppet Users] puppet, mongel, nginx and new nodes
On 12/21/2009 10:05 PM, Matthew Delves wrote:> Hey All, This is probably a gotcha of some kind. That is to say I''ve missed > a configuration somewhere. I''ve recently moved over to using mongrel as the > puppet server type and having nginx proxy to one of four mongrel > instances. > > What I''m seeing though is that when I try to run a new node (one that has > been created post moving to mongrel/nginx) is that it returns with the > error: err: Could not retrieve catalog from remote server: wrong status > line: "<html>"Sounds like mongrel or nginx might be generating an error message. Try pointing a web browser at https://<your puppetmaster>:8140 and see if you get anything helpful. -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC -- 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.
Matthew Delves
2009-Dec-22 04:34 UTC
Re: [Puppet Users] puppet, mongel, nginx and new nodes
> > Sounds like mongrel or nginx might be generating an error message. Try > pointing a web browser at https://<your puppetmaster>:8140 and see if you get > anything helpful.The error I get is: Peer''s certificate has an invalid signature. It would seem rather odd that the certificate has suddenly become invalid. Thanks, Matt Delves -- 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.
Silviu Paragina
2009-Dec-22 13:59 UTC
Re: [Puppet Users] puppet, mongel, nginx and new nodes
On 22.12.2009 06:34, Matthew Delves wrote:>> Sounds like mongrel or nginx might be generating an error message. Try >> pointing a web browser at https://<your puppetmaster>:8140 and see if you get >> anything helpful. >> > The error I get is: > > Peer''s certificate has an invalid signature. > > It would seem rather odd that the certificate has suddenly become invalid. > > Thanks, > Matt Delves > >Why aren''t you using passenger? afaik it works with nginx too? Just my 2 cents Silviu -- 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.
Matthew Delves
2009-Dec-22 21:58 UTC
Re: [Puppet Users] puppet, mongel, nginx and new nodes
> Why aren''t you using passenger? afaik it works with nginx too? Just my 2 > centsMy preference is for nginx over apache. I already have nginx hosting foreman on the same box so configuration is straight forward rather than having apache installed as well. Still no solution received on the problem. Is anyone aware of why the certificates are being rejected by the new nodes? All other nodes are behaving as expected. Thanks, Matt Delves -- 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.
Matthew Delves wrote:>> Why aren''t you using passenger? afaik it works with nginx too? Just my 2 >> cents > > My preference is for nginx over apache. I already have nginx hosting foreman on the same box so configuration is straight forward rather than having apache installed as well. >Passenger does not require Apache. -scott -- 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.
Matthew Delves
2009-Dec-23 02:16 UTC
Re: [Puppet Users] puppet, mongel, nginx and new nodes
> Passenger does not require Apache.Do you have a link to an article that explains how that is? The documentation on the puppet/reductivelabs website http://reductivelabs.com/trac/puppet/wiki/UsingPassenger shows a use of apache. Thanks, Matt Delves -- 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.
Matthew Delves wrote:>> Passenger does not require Apache. > > Do you have a link to an article that explains how that is? >http://www.modrails.com/ -- 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.
Maybe Matching Threads
- pasenger does not start puppet master under nginx
- Puppetmaster setup with separate CA server configuration help
- puppet master REST API returns 403 when running under passenger works when running from command line
- running passenger + nginx
- Nginx + Phusion Passenger 3 problem with "504 Gateway time-out"