Issue #11409 has been updated by Jo Rhett.
Sarcasm about me not reading your own documentation would be totally appropriate. Sarcasm about google is not. I *did* use Google extensively. I simply used additional words to get answers specific to this, and for reasons unclear to me google didn't show me the first answer in your query, which did contain all of those words I used. This frankly is more of a google failure than a failure of me to google. I am definitely looking for a better search engine these days. I will definitely try to use less specific words in google queries henceforth, but that generally has a tendency to produce 10k results with the first 100 not being relevant. ---------------------------------------- Bug #11409: passenger won't start up https://projects.puppetlabs.com/issues/11409 Author: Jo Rhett Status: Closed Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.6.12 Keywords: Branch: I've made a perfect copy of our production environment on another machine/environment so that I can test ruby and puppet version upgrades without affecting production systems. This is essential for ruby 1.8.7 upgrades. puppet master worked perfectly fine when running in webrick mode. For reasons I simply cannot trace down, I get the following errors when we first connect to the passenger application: [Thu Dec 15 05:02:29 2011] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations Could not prepare for execution: Got 1 failure(s) while initializing: change from absent to file failed: Could not set 'file on ensure: Permission denied - /nas/puppet/var/log/masterhttp.log Could not prepare for execution: Got 1 failure(s) while initializing: change from absent to file failed: Could not set 'file on ensure: Permission denied - /nas/puppet/var/log/masterhttp.log This file (and the entire heirarchy it is in) are the exact same rights as on the production system. [05:02 root@ats001 conf.d]$ ls -la /nas/puppet/var/log total 44 drwxr-x--- 2 puppet puppet 4096 Dec 15 04:20 . drwxr-xr-x 14 puppet puppet 4096 Dec 15 00:39 .. -rw-rw---- 1 puppet puppet 30965 Dec 15 04:38 masterhttp.log Su to the puppet user and I can edit files in that directory just fine. I've done funny things like change the ownership of the directory and it complains: Could not prepare for execution: Got 1 failure(s) while initializing: change from 775 to 750 failed: failed to chmod /nas/puppet/var/log: Operation not permitted - /nas/puppet/var/log So it's seeing the right directory, it just doesn't like it. The best I can imagine is that the master process isn't starting up as the puppet user? How can I validate this? Exact same OS, exact same kernel, exact same packages, exact same LDAP structure, matching (few) local accounts. This is identical in every way. What's going on here? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
