On Mon, 22 Apr 2013 07:06:50 -0700 (PDT) Drew Blessing <drew.bless...@mac.com> wrote:
> We're having a very strange issue with Puppet running on Passenger. > Every day or 2, our clients start receiving Passenger back traces. > It's the generic "Ruby (Rack) application could not be started." My > initial thought was that this is a resource/configuration problem. > Maybe we're overrunning our resources or need to tune Passenger. > However, the way we have to temporarily fix it leads me to believe > it's not related to Passenger configuration or resources issues. > > A simple Apache restart will not fix the issue. In *every* case the > fix is to stop Apache, start the puppetmaster service, stop the > puppetmaster service, and start Apache again. Any other combination > will not work. So there is something significant about what's > happening when puppetmaster process starts. Any ideas what could be > causing our grief? > > Thanks for your help. > If you run puppet through passenger, passenger will start the puppet master process as the puppet user. This means that if some files cannot be accessed by the puppet user you'll have a problem. If you run puppet via `service puppetmaster start`, the puppetmaster will start as root, makes sure that `/var/lib/puppet/ssl` and stuff are owned by puppet, and will then drop priviledges and continue to run as the puppet user. Do you run the agent on the puppetmaster, too? Then check the logs (typically syslog) wether the puppet agent performed any changes, or run your agent from the commandline with `--verbose` and check the console output. E.g. I had a problem in the past where the agent pluginsynced some plugins into `/var/lib/puppet/lib` and set ownership in a way that the puppetmaster was not able to access the plugins anymore. Second: When you have the problem the next time, stop apache and then start the master as `puppet master --no-daemonize --verbose --debug`. This way you'll hopefully see if the master process "fixes" something during the startup-as-root-phase (and therefore cannot be fixed if you start your puppet master under passenger). -Stefan -- 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.
