[Puppet Users] Apache/Passenger RHEL6 not working

2011-09-15 Thread Ashwin N
Hi

Passenger is a rack application - will run out of httpd .

Have you got anything like the following in your passenger (httpd)
configuration file:

DocumentRoot /etc/puppet/rack/public/
RackBaseURI /
Directory /etc/puppet/rack/
Options None
AllowOverride None
Order allow,deny
allow from all
/Directory

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] Apache/Passenger RHEL6 not working

2011-09-15 Thread Mark Stanislav
Here's a script that should deploy a stack with apache+passenger for
you (tested on CentOS 6);

https://raw.github.com/mstanislav/Veewee-Definitions/master/CentOS-6_x86_64-PuppetStack/postinstall.sh

Maybe you can take a look at the steps and see if there's something
you're missing.

Hope it helps!

-Mark

On Thu, Sep 15, 2011 at 12:30 AM, Ashwin N ashy.n...@gmail.com wrote:
 Hi

 Passenger is a rack application - will run out of httpd .

 Have you got anything like the following in your passenger (httpd)
 configuration file:

     DocumentRoot /etc/puppet/rack/public/
     RackBaseURI /
     Directory /etc/puppet/rack/
     Options None
     AllowOverride None
     Order allow,deny
     allow from all
     /Directory


 --
 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+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/puppet-users?hl=en.


-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] Apache/Passenger RHEL6 not working

2011-09-15 Thread Kenton Brede
On Wed, Sep 14, 2011 at 12:33 PM, Gary Larizza g...@puppetlabs.com wrote:


 On Wed, Sep 14, 2011 at 11:12 AM, Kenton Brede kbr...@gmail.com wrote:

 I'm attempting to move from a working puppetmaster setup to
 Apache/Passenger.  I'm following the instructions in the Pro Puppet
 book.  I'm using the epel repo and running puppet 2.6.6.  Passenger
 version 3.0.9 from the stealthymonkeys repo.  Running puppetd -t -d
 doesn't seem to tell me anything significant.  There's no complaining
 about SSL issues.

 My nodes can't find the catalog, based on the error message puppetd
 -t spits out:

 err: Could not retrieve catalog from remote server:
 Puppet::Resource::Catalog does not respond to from_s; can not intern
 instances from text/plain
 warning: Not using cache on failed catalog
 err: Could not retrieve catalog; skipping run

 I've googled the error and haven't found anything that helps so far.
 The catalog is currently in /etc/puppet/modules/. I really don't know
 anything about Passenger.  I fail to see in the apache/passenger
 configuration how the puppetmaster is called when a client connects to
 port 8140.  I see that apache is handling the SSL stuff but how does
 the puppetmaster fit into this?

 Any help appreciated.
 Thanks,

 --
 Kent Brede


 Kent,
 I recommend taking a look at the online document here
 -- http://docs.puppetlabs.com/guides/passenger.html  There are specific
 versions of Passenger and the Rack gem that are necessary for Puppet to work
 properly.  I suspect you're using a version of one (possibly Rack) that's
 incompatible here.

Gary,
I using gem I installed the version for rhel6, listed in the document
you recommended: Passenger 3.0.7 and Rack 1.2.2.  I also removed these
and installed the versions cited in the Pro Puppet book: Passenger
2.2.11 and Rack 1.1.0.  Both configurations resulted in the same error
as I had before:

# puppetd -t
err: Could not retrieve catalog from remote server:
Puppet::Resource::Catalog does not respond to from_s; can not intern
instances from text/plain
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

If you have any other ideas, let me know.
Thanks,
Kent

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] Apache/Passenger RHEL6 not working

2011-09-15 Thread Kenton Brede
On Thu, Sep 15, 2011 at 1:46 PM, Kenton Brede kbr...@gmail.com wrote:
 On Wed, Sep 14, 2011 at 11:30 PM, Ashwin N ashy.n...@gmail.com wrote:
 Hi

 Passenger is a rack application - will run out of httpd .

 Have you got anything like the following in your passenger (httpd)
 configuration file:

     DocumentRoot /etc/puppet/rack/public/
     RackBaseURI /
     Directory /etc/puppet/rack/
     Options None
     AllowOverride None
     Order allow,deny
     allow from all
     /Directory

 Yep I have this in my configuration:

 DocumentRoot /etc/puppet/rack/puppetmaster/public/
 Directory /etc/puppet/rack/puppetmaster/
    Options None
    AllowOverride None
    Order allow,deny
    allow from all
 /Directory

 Is there something I'm suppose to be putting in these directories?
 Ultimately following error messages I created directories and an empty
 file: 
 /etc/puppet/rack/puppetmaster/public/production/catalog/puppet2.example.com.
  Is there suppose to be something put in puppet2.example.com?
 Thanks,

To answer my own question, no do not put files in this directory.
When I removed the puppet2.example.com, the Apache/Passenger setup
started to work.

-- 
Kent Brede
http://gplus.to/kbrede
http://sandhillsnaps.com/
http://aphotoaday.sandhillsnaps.org/
http://www.pentaxphotogallery.com/kentonbrede

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] Apache/Passenger RHEL6 not working

2011-09-15 Thread Kenton Brede
I finally got this to work with passenger-3.0.7 and rack-1.2.2 by
removing a file I'd created in:
/etc/puppet/rack/puppetmaster/public/production/catalog/.  Now that I
know how this works, I'll try using a more current passenger and rack
and see if it works.

Kent

On Thu, Sep 15, 2011 at 1:37 PM, Kenton Brede kbr...@gmail.com wrote:
 On Wed, Sep 14, 2011 at 12:33 PM, Gary Larizza g...@puppetlabs.com wrote:


 On Wed, Sep 14, 2011 at 11:12 AM, Kenton Brede kbr...@gmail.com wrote:

 I'm attempting to move from a working puppetmaster setup to
 Apache/Passenger.  I'm following the instructions in the Pro Puppet
 book.  I'm using the epel repo and running puppet 2.6.6.  Passenger
 version 3.0.9 from the stealthymonkeys repo.  Running puppetd -t -d
 doesn't seem to tell me anything significant.  There's no complaining
 about SSL issues.

 My nodes can't find the catalog, based on the error message puppetd
 -t spits out:

 err: Could not retrieve catalog from remote server:
 Puppet::Resource::Catalog does not respond to from_s; can not intern
 instances from text/plain
 warning: Not using cache on failed catalog
 err: Could not retrieve catalog; skipping run

 I've googled the error and haven't found anything that helps so far.
 The catalog is currently in /etc/puppet/modules/. I really don't know
 anything about Passenger.  I fail to see in the apache/passenger
 configuration how the puppetmaster is called when a client connects to
 port 8140.  I see that apache is handling the SSL stuff but how does
 the puppetmaster fit into this?

 Any help appreciated.
 Thanks,

 --
 Kent Brede


 Kent,
 I recommend taking a look at the online document here
 -- http://docs.puppetlabs.com/guides/passenger.html  There are specific
 versions of Passenger and the Rack gem that are necessary for Puppet to work
 properly.  I suspect you're using a version of one (possibly Rack) that's
 incompatible here.

 Gary,
 I using gem I installed the version for rhel6, listed in the document
 you recommended: Passenger 3.0.7 and Rack 1.2.2.  I also removed these
 and installed the versions cited in the Pro Puppet book: Passenger
 2.2.11 and Rack 1.1.0.  Both configurations resulted in the same error
 as I had before:

 # puppetd -t
 err: Could not retrieve catalog from remote server:
 Puppet::Resource::Catalog does not respond to from_s; can not intern
 instances from text/plain
 warning: Not using cache on failed catalog
 err: Could not retrieve catalog; skipping run

 If you have any other ideas, let me know.
 Thanks,
 Kent


-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



[Puppet Users] Apache/Passenger RHEL6 not working

2011-09-14 Thread Kenton Brede
I'm attempting to move from a working puppetmaster setup to
Apache/Passenger.  I'm following the instructions in the Pro Puppet
book.  I'm using the epel repo and running puppet 2.6.6.  Passenger
version 3.0.9 from the stealthymonkeys repo.  Running puppetd -t -d
doesn't seem to tell me anything significant.  There's no complaining
about SSL issues.

My nodes can't find the catalog, based on the error message puppetd
-t spits out:

err: Could not retrieve catalog from remote server:
Puppet::Resource::Catalog does not respond to from_s; can not intern
instances from text/plain
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

I've googled the error and haven't found anything that helps so far.
The catalog is currently in /etc/puppet/modules/. I really don't know
anything about Passenger.  I fail to see in the apache/passenger
configuration how the puppetmaster is called when a client connects to
port 8140.  I see that apache is handling the SSL stuff but how does
the puppetmaster fit into this?

Any help appreciated.
Thanks,

-- 
Kent Brede
http://gplus.to/kbrede
http://sandhillsnaps.com/
http://aphotoaday.sandhillsnaps.org/

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] Apache/Passenger RHEL6 not working

2011-09-14 Thread Gary Larizza
On Wed, Sep 14, 2011 at 11:12 AM, Kenton Brede kbr...@gmail.com wrote:

 I'm attempting to move from a working puppetmaster setup to
 Apache/Passenger.  I'm following the instructions in the Pro Puppet
 book.  I'm using the epel repo and running puppet 2.6.6.  Passenger
 version 3.0.9 from the stealthymonkeys repo.  Running puppetd -t -d
 doesn't seem to tell me anything significant.  There's no complaining
 about SSL issues.

 My nodes can't find the catalog, based on the error message puppetd
 -t spits out:

 err: Could not retrieve catalog from remote server:
 Puppet::Resource::Catalog does not respond to from_s; can not intern
 instances from text/plain
 warning: Not using cache on failed catalog
 err: Could not retrieve catalog; skipping run

 I've googled the error and haven't found anything that helps so far.
 The catalog is currently in /etc/puppet/modules/. I really don't know
 anything about Passenger.  I fail to see in the apache/passenger
 configuration how the puppetmaster is called when a client connects to
 port 8140.  I see that apache is handling the SSL stuff but how does
 the puppetmaster fit into this?

 Any help appreciated.
 Thanks,

 --
 Kent Brede
 http://gplus.to/kbrede
 http://sandhillsnaps.com/
 http://aphotoaday.sandhillsnaps.org/

 --
 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+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/puppet-users?hl=en.


Kent,

I recommend taking a look at the online document here --
http://docs.puppetlabs.com/guides/passenger.html  There are specific
versions of Passenger and the Rack gem that are necessary for Puppet to work
properly.  I suspect you're using a version of one (possibly Rack) that's
incompatible here.

-- 

Gary Larizza
Professional Services Engineer
Puppet Labs

Join us for PuppetConf http://bit.ly/puppetconfsig, September 22nd and
23rd in Portland, OR!

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.