Hi, I trying to convert a basic install of my puppetmasterd from WEBrick to Phusion. Here''s what I did and here''s what''s not working anymore. You help is greatly appreciated. --- Thanks, Allan Marcus 505-667-5666 Starting with Mac OS X server 10.5.7 I install puppet and facter. I created a puppet user and group (both ID 200). When I run puppetmasterd I get the expected "ruby is broken on mac os x, so running as root". I also use storeconfigs and it''s working great I was able to get it all working as desired, but I''m planning on 3000 clients checking in hourly, so I figured I''d better "upgrade" to Passenger. gem update <- BAD idea gem install -v 0.4.0 rack gem update --system gem install passenger passenger-install-apache2-module I set up a virtual host for port 8140 and configured it according to the puppet web pages. I also set up /usr/share/puppet/rack/ puppetmasterd/config.ru and chowned it to puppet. So I fire up apache2 and all seems well. I fire up a client and I get some permission errors on the server in /var/puppet/yaml and /var/ puppet/log, so I chown stuff in there to puppet (used to be owned by root), and the permission errors go away. I''m left with one error on the puppetmasterd server: err: Could not retrieve catalog: Rails is missing; cannot store configurations I resolved this error by gem uninstalling rails, passenger, and all the active* gems. I then did a gem install -v 2.0.5 rails gem install -v 2.2.2 passenger and update my apache config files for passenger 2.2.2 and now it seems to work. I feel like I''ve built a house of cards and one good breeze might blow it down! :-) So, questions: 1) How should the permissions of files and directories in /var/puppet look? what should be owned by puppet, and what by root? 2) Did I do this right? 3) Am I headed down the wrong path? Should I try mongrel instead? 4) What''s the deal with using these older version? Is this common in the ruby world? I''m used to generally keeping everything up to date. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Nigel Kersten
2009-Aug-06 23:55 UTC
[Puppet Users] Re: Converting to Phusion on mac issues
Allan, when I got it running on OS X Server, I *only* installed Passenger from source, not from gem at all. On Thu, Aug 6, 2009 at 4:52 PM, Allan Marcus<allan@lanl.gov> wrote:> > Hi, > > I trying to convert a basic install of my puppetmasterd from WEBrick > to Phusion. Here''s what I did and here''s what''s not working anymore. > You help is greatly appreciated. > > --- > Thanks, > > Allan Marcus > 505-667-5666 > > > Starting with Mac OS X server 10.5.7 I install puppet and facter. I > created a puppet user and group (both ID 200). When I run > puppetmasterd I get the expected "ruby is broken on mac os x, so > running as root". I also use storeconfigs and it''s working great > > I was able to get it all working as desired, but I''m planning on 3000 > clients checking in hourly, so I figured I''d better "upgrade" to > Passenger. > > gem update <- BAD idea > gem install -v 0.4.0 rack > gem update --system > gem install passenger > passenger-install-apache2-module > > I set up a virtual host for port 8140 and configured it according to > the puppet web pages. I also set up /usr/share/puppet/rack/ > puppetmasterd/config.ru and chowned it to puppet. > So I fire up apache2 and all seems well. I fire up a client and I get > some permission errors on the server in /var/puppet/yaml and /var/ > puppet/log, so I chown stuff in there to puppet (used to be owned by > root), and the permission errors go away. > > I''m left with one error on the puppetmasterd server: > err: Could not retrieve catalog: Rails is missing; cannot store > configurations > > I resolved this error by gem uninstalling rails, passenger, and all > the active* gems. I then did a > gem install -v 2.0.5 rails > gem install -v 2.2.2 passenger > and update my apache config files for passenger 2.2.2 and now it seems > to work. I feel like I''ve built a house of cards and one good breeze > might blow it down! :-) > > So, questions: > 1) How should the permissions of files and directories in /var/puppet > look? what should be owned by puppet, and what by root? > 2) Did I do this right? > 3) Am I headed down the wrong path? Should I try mongrel instead? > 4) What''s the deal with using these older version? Is this common in > the ruby world? I''m used to generally keeping everything up to date. > > > > > > >-- Nigel Kersten nigelk@google.com System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
I may have answer my own question about the permissions. On my production server I see the following, so I think I''m ok. drwxr-x--- 2 _puppet _puppet 68 Jul 10 08:34 bucket drwxr-x--- 2 root wheel 68 Jul 10 08:34 client_yaml drwxr-x--- 2 root wheel 68 Jul 10 08:34 clientbucket drwxr-xr-x 6 root wheel 204 Jul 10 10:34 cvsroot drwxr-xr-x 4 root wheel 136 Jul 10 11:18 environments drwxr-xr-x 13 root wheel 442 Aug 5 16:06 facts drwxr-xr-x 3 root wheel 102 Jul 16 18:31 lib drwxr-x--- 4 _puppet _puppet 136 Jul 10 11:53 log drwxr-x--- 2 _puppet _puppet 68 Jul 10 08:34 reports drwxr-xr-x 2 _puppet _puppet 68 Jul 10 08:34 rrd drwxrwxrwt 3 root wheel 102 Jul 27 15:19 run drwxr-xr-t 5 root wheel 170 Aug 6 17:25 state drwxr-xr-x 2 root wheel 68 Jul 24 13:39 tmp drwxr-x--- 4 _puppet _puppet 136 Jul 10 11:53 yaml BTW, my _puppet user has puppet as an alias So I guess I just need to get used to verifying all the dependent software versions before I upgrade anything. --- Thanks, Allan Marcus 505-667-5666 On Aug 6, 2009, at 5:55 PM, Nigel Kersten wrote:> > Allan, when I got it running on OS X Server, I *only* installed > Passenger from source, not from gem at all. > > > On Thu, Aug 6, 2009 at 4:52 PM, Allan Marcus<allan@lanl.gov> wrote: >> >> Hi, >> >> I trying to convert a basic install of my puppetmasterd from WEBrick >> to Phusion. Here''s what I did and here''s what''s not working anymore. >> You help is greatly appreciated. >> >> --- >> Thanks, >> >> Allan Marcus >> 505-667-5666 >> >> >> Starting with Mac OS X server 10.5.7 I install puppet and facter. I >> created a puppet user and group (both ID 200). When I run >> puppetmasterd I get the expected "ruby is broken on mac os x, so >> running as root". I also use storeconfigs and it''s working great >> >> I was able to get it all working as desired, but I''m planning on 3000 >> clients checking in hourly, so I figured I''d better "upgrade" to >> Passenger. >> >> gem update <- BAD idea >> gem install -v 0.4.0 rack >> gem update --system >> gem install passenger >> passenger-install-apache2-module >> >> I set up a virtual host for port 8140 and configured it according to >> the puppet web pages. I also set up /usr/share/puppet/rack/ >> puppetmasterd/config.ru and chowned it to puppet. >> So I fire up apache2 and all seems well. I fire up a client and I get >> some permission errors on the server in /var/puppet/yaml and /var/ >> puppet/log, so I chown stuff in there to puppet (used to be owned by >> root), and the permission errors go away. >> >> I''m left with one error on the puppetmasterd server: >> err: Could not retrieve catalog: Rails is missing; cannot store >> configurations >> >> I resolved this error by gem uninstalling rails, passenger, and all >> the active* gems. I then did a >> gem install -v 2.0.5 rails >> gem install -v 2.2.2 passenger >> and update my apache config files for passenger 2.2.2 and now it >> seems >> to work. I feel like I''ve built a house of cards and one good breeze >> might blow it down! :-) >> >> So, questions: >> 1) How should the permissions of files and directories in /var/puppet >> look? what should be owned by puppet, and what by root? >> 2) Did I do this right? >> 3) Am I headed down the wrong path? Should I try mongrel instead? >> 4) What''s the deal with using these older version? Is this common in >> the ruby world? I''m used to generally keeping everything up to date. >> >> >> >> >>> >> > > > > -- > Nigel Kersten > nigelk@google.com > System Administrator > Google, Inc. > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
So, are you using the same versions? Rails: 2.0.5 Passenger: 2.2.2 Rack: 0.4.0 --- Thanks, Allan Marcus 505-667-5666 On Aug 6, 2009, at 5:55 PM, Nigel Kersten wrote:> > Allan, when I got it running on OS X Server, I *only* installed > Passenger from source, not from gem at all. > > > On Thu, Aug 6, 2009 at 4:52 PM, Allan Marcus<allan@lanl.gov> wrote: >> >> Hi, >> >> I trying to convert a basic install of my puppetmasterd from WEBrick >> to Phusion. Here''s what I did and here''s what''s not working anymore. >> You help is greatly appreciated. >> >> --- >> Thanks, >> >> Allan Marcus >> 505-667-5666 >> >> >> Starting with Mac OS X server 10.5.7 I install puppet and facter. I >> created a puppet user and group (both ID 200). When I run >> puppetmasterd I get the expected "ruby is broken on mac os x, so >> running as root". I also use storeconfigs and it''s working great >> >> I was able to get it all working as desired, but I''m planning on 3000 >> clients checking in hourly, so I figured I''d better "upgrade" to >> Passenger. >> >> gem update <- BAD idea >> gem install -v 0.4.0 rack >> gem update --system >> gem install passenger >> passenger-install-apache2-module >> >> I set up a virtual host for port 8140 and configured it according to >> the puppet web pages. I also set up /usr/share/puppet/rack/ >> puppetmasterd/config.ru and chowned it to puppet. >> So I fire up apache2 and all seems well. I fire up a client and I get >> some permission errors on the server in /var/puppet/yaml and /var/ >> puppet/log, so I chown stuff in there to puppet (used to be owned by >> root), and the permission errors go away. >> >> I''m left with one error on the puppetmasterd server: >> err: Could not retrieve catalog: Rails is missing; cannot store >> configurations >> >> I resolved this error by gem uninstalling rails, passenger, and all >> the active* gems. I then did a >> gem install -v 2.0.5 rails >> gem install -v 2.2.2 passenger >> and update my apache config files for passenger 2.2.2 and now it >> seems >> to work. I feel like I''ve built a house of cards and one good breeze >> might blow it down! :-) >> >> So, questions: >> 1) How should the permissions of files and directories in /var/puppet >> look? what should be owned by puppet, and what by root? >> 2) Did I do this right? >> 3) Am I headed down the wrong path? Should I try mongrel instead? >> 4) What''s the deal with using these older version? Is this common in >> the ruby world? I''m used to generally keeping everything up to date. >> >> >> >> >>> >> > > > > -- > Nigel Kersten > nigelk@google.com > System Administrator > Google, Inc. > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---