This is me installing a puppetmaster for Ubuntu with the bog-standard apt repos the other day - took less than 5 minutes:
https://gist.github.com/kbarber/5209267 As you can see it was pretty straight-forward (apt-get install puppetmaster-passenger, more or less) - note this was a clean Ubuntu 12.04 installation, so do start fresh as Felix suggests. I haven't got a gist of an installation with the puppetlabs repos recently, but it should be similar - only include the Puppetlabs repos first: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu The puppetlabs repos will give you the latest version of Puppet which is probably the way to go. Note I never: * Installed passenger from brightbox * Installed using any gems * Made any manual changes (at least not with my basic setup, your mileage may vary) So either use the stuff hosted by Ubuntu, or by PL and you should be good. Let us know how you go. ken. On Tue, Apr 2, 2013 at 12:54 PM, Felix Frank <felix.fr...@alumni.tu-berlin.de> wrote: > Hi, > > On 03/26/2013 08:11 PM, thinkwell wrote: >> Puppet runs always generating scads of errors >> <http://thinkwelldesigns.com/errors2.html>.Is Passenger enabled? > > Well, the error is titled with "Passanger" so I'd say yes ;) > > The error also advises to check the webservers's logfiles. Have you? > > If apache logs aren't helpful, there may be something on the puppet side > of things. Rack applications may do some logging of their own. > >> This. Is. Getting. To. Be. One. *S**creeeeaaaammmmming.*Pain. > > Dude. > >> Thanks for your help Ramin, but why oh why can't we have up-to-date >> documentation that gives correct step-by-step installation directions? >> How esoteric does this have to be? > > I've found that ruby applications can be made to be very portable, but > the more so if you do *everything* the intended ruby way. With the > different OS environments, there are lots of half-assed compromises > (e.g. install some software through packages, others through gems etc.) > and the howto's will often reflect the respective author's personal > preference with regards to the respective details. Also, they want to > keep things simple between differen OS releases. > > Long story short, I concur that in Debian (Ubuntu propably the same), > getting Passenger via packages is a better choice than gems. I cannot > comment on 3.x vs. 2.x, but I've seen good mileage with the stock Debian > packages for apache/passenger (not tried a 3.x master yet, though). > > Sadly that won't match the docs exactly, but I think this should be > painless enough: > - start from scratch > - get the components via apt > - apply the configs from the howto as best you can > - clean up the leftover errors from the discrepancies > > HTH, > Felix > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
