Puppet users - Jul 2009 - trouble with passenger and 0.25.0beta2

Hi,

I''m currently trying to get my puppetmaster work in passenger, but have
not
succeeded so far.

Passenger itself seems to work (a small "hello world" app runs fine),
but
when I point a puppet client (0.24.8) to it, I get:

info: Retrieving plugins
err: Could not call fileserver.list: #<RuntimeError: HTTP-Error: 500 Internal
Server Error>
err: /File[/var/lib/puppet/lib]: Failed to generate additional resources during
transaction: HTTP-Error: 500 Internal Server Error
err: Could not call fileserver.describe: #<RuntimeError: HTTP-Error: 500
Internal Server Error>
err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of resource:
HTTP-Error: 500 Internal Server Error Could not describe /plugins: HTTP-Error:
500 Internal Server Error
info: Retrieving facts
err: Could not call fileserver.list: #<RuntimeError: HTTP-Error: 500 Internal
Server Error>
err: /File[/var/puppet/facts]: Failed to generate additional resources during
transaction: HTTP-Error: 500 Internal Server Error
err: Could not call fileserver.describe: #<RuntimeError: HTTP-Error: 500
Internal Server Error>
err: /File[/var/puppet/facts]: Failed to retrieve current state of resource:
HTTP-Error: 500 Internal Server Error Could not describe /facts: HTTP-Error: 500
Internal Server Error
err: Could not call puppetmaster.getconfig: #<RuntimeError: HTTP-Error: 500
Internal Server Error>
err: Could not retrieve catalog: HTTP-Error: 500 Internal Server Error
warning: Not using cache on failed catalog

and in apache logs, nothing more than a few:
  "POST /RPC2 HTTP/1.1" 500 20152 "-" "XMLRPC::Client
(Ruby 1.8.5)"
(this is with "--debug" in config.ru).

It''s on redhat el5 with the following gems installed:

activerecord (2.1.0)
activesupport (2.1.0)
fastthread (1.0.7)
passenger (2.2.2)
rack (1.0.0)
rake (0.8.1)

I previously tried with passenger 2.2.4 but downgraded after coming
accross http://projects.reductivelabs.com/issues/2386. With 2.2.4, I had
more verbose errors: http://pastie.org/547061

I vaguely suspect a path-related problem, because of the "uninitialized
constant Puppet::SSL::Base" I got with 2.2.4, but I have no idea what I
should define where.

Any hints or pointers welcome !

Thanks,
Marc




--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

usually you can get some info by point a browser at your puppetmaster

you can also get a fully working passenger setup from here:
http://github.com/ohadlevy/puppet-multipuppetmaster/tree/master

cheers,
Ohad
On Thu, Jul 16, 2009 at 5:27 PM, Marc Fournier
<marc.fournier@camptocamp.com
> wrote:
>
> Hi,
>
> I''m currently trying to get my puppetmaster work in passenger, but
have not
> succeeded so far.
>
> Passenger itself seems to work (a small "hello world" app runs
fine), but
> when I point a puppet client (0.24.8) to it, I get:
>
> info: Retrieving plugins
> err: Could not call fileserver.list: #<RuntimeError: HTTP-Error: 500
> Internal Server Error>
> err: /File[/var/lib/puppet/lib]: Failed to generate additional resources
> during transaction: HTTP-Error: 500 Internal Server Error
> err: Could not call fileserver.describe: #<RuntimeError: HTTP-Error: 500
> Internal Server Error>
> err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of
> resource: HTTP-Error: 500 Internal Server Error Could not describe
/plugins:
> HTTP-Error: 500 Internal Server Error
> info: Retrieving facts
> err: Could not call fileserver.list: #<RuntimeError: HTTP-Error: 500
> Internal Server Error>
> err: /File[/var/puppet/facts]: Failed to generate additional resources
> during transaction: HTTP-Error: 500 Internal Server Error
> err: Could not call fileserver.describe: #<RuntimeError: HTTP-Error: 500
> Internal Server Error>
> err: /File[/var/puppet/facts]: Failed to retrieve current state of
> resource: HTTP-Error: 500 Internal Server Error Could not describe /facts:
> HTTP-Error: 500 Internal Server Error
> err: Could not call puppetmaster.getconfig: #<RuntimeError: HTTP-Error:
500
> Internal Server Error>
> err: Could not retrieve catalog: HTTP-Error: 500 Internal Server Error
> warning: Not using cache on failed catalog
>
> and in apache logs, nothing more than a few:
>  "POST /RPC2 HTTP/1.1" 500 20152 "-"
"XMLRPC::Client (Ruby 1.8.5)"
> (this is with "--debug" in config.ru).
>
> It''s on redhat el5 with the following gems installed:
>
> activerecord (2.1.0)
> activesupport (2.1.0)
> fastthread (1.0.7)
> passenger (2.2.2)
> rack (1.0.0)
> rake (0.8.1)
>
> I previously tried with passenger 2.2.4 but downgraded after coming
> accross http://projects.reductivelabs.com/issues/2386. With 2.2.4, I had
> more verbose errors: http://pastie.org/547061
>
> I vaguely suspect a path-related problem, because of the
"uninitialized
> constant Puppet::SSL::Base" I got with 2.2.4, but I have no idea what
I
> should define where.
>
> Any hints or pointers welcome !
>
> Thanks,
> Marc
>
>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

> usually you can get some info by point a browser at your puppetmaster
Thanks, I didn''t know that ! I was turned away by an ssl certificate
error, thinking that my browser had no client cert and that was not an
issue.

There is indeed quite useful things there:

Error message:
  undefined method `new'' for Puppet::Daemon:Module

Exception class:
  NoMethodError

Application root:
  /etc/puppet/rack

Backtrace:

  #                                       File                                  
Line      Location
  0 /srv/puppet/lib/puppet/application/puppetmasterd.rb                         
36   in `run_preinit''
  1 /srv/puppet/lib/puppet/application.rb                                       
213  in `run''
  2 config.ru                                                                   
24
  3
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.1/vendor/rack-0.9.1/lib/rack/builder.rb
29   in `instance_eval''
  4
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.1/vendor/rack-0.9.1/lib/rack/builder.rb
29   in `initialize''
  5 config.ru                                                                   
1    in `new''
  6 config.ru                                                                   
1



Would this be a bug I should report in puppet''s bugtracker ?


> you can also get a fully working passenger setup from here:
> http://github.com/ohadlevy/puppet-multipuppetmaster/tree/master
Thanks, I''ll look at all this !

Is it required to have the "apache" user in group "puppet" ?
I can''t find
apache2::passenger ?

Marc



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Hi
> Is it required to have the "apache" user in group
"puppet" ? I can''t find
> apache2::passenger ?
passenger works that way that an application is executed as the user  
which owns the config.ru, so simply own config.ru by the user puppet,  
restart and your puppetmaster will run as user puppet.

cheers pete


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

On Thu, Jul 16, 2009 at 3:15 AM, Marc
Fournier<marc.fournier@camptocamp.com> wrote:
> Backtrace:
>
>  #                                       File                              
         Line      Location
>  0 /srv/puppet/lib/puppet/application/puppetmasterd.rb                    
          36   in `run_preinit''
>  1 /srv/puppet/lib/puppet/application.rb                                  
          213  in `run''
>  2 config.ru                                                              
          24
>  3
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.1/vendor/rack-0.9.1/lib/rack/builder.rb
29   in `instance_eval''
>  4
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.1/vendor/rack-0.9.1/lib/rack/builder.rb
29   in `initialize''
>  5 config.ru                                                              
          1    in `new''
>  6 config.ru                                                              
          1
>
>
>
> Would this be a bug I should report in puppet''s bugtracker ?
The backtrace shows you''re using passenger 2.2.1, try removing that
gem and reinstalling 2.2.2.

-jab

-- 
John A. Barbuto                         jbarbuto@corp.sourceforge.com
Senior System Administrator             SourceForge, 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
-~----------~----~----~----~------~----~------~--~---

On Thu, Jul 16, 2009 at 6:15 PM, Marc Fournier
<marc.fournier@camptocamp.com
> wrote:
>
> Is it required to have the "apache" user in group
"puppet" ? I can''t find
> apache2::passenger ?
>
Not really, its there because of other non related reasons...

just for completeness:
class apache2::passenger {
# Package is avail be only for GI5
  package{"rubygem-passenger":
    ensure => "2.2.2-1",
    require => Package["httpd"],
    before => Service["httpd"],
  }
  file{"/etc/httpd/conf.d/passenger.conf":
    source =>
"puppet:///apache2/push/etc/httpd/conf.d/passenger.conf",
    mode => 644, owner=> root, group => root,
    notify => Exec["reload-apache2"],
  }
}
cat apache2/files/push/etc/httpd/conf.d/passenger.conf
LoadModule passenger_module
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.2/ext/apache2/mod_passenger.so
PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-2.2.2
PassengerRuby /usr/bin/ruby
PassengerMaxPoolSize 15
PassengerMaxRequests 3000
PassengerStatThrottleRate 600

 Ohad

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Hello,
> The backtrace shows you''re using passenger 2.2.1, try removing
that
> gem and reinstalling 2.2.2.
Thanks for pointing that out, John ! The sort of obvious thing I tend to
zap when obnubilating over a problem...

So I finally sorted this out. After reinstalling passenger 2.2.2, I got
the same error as with 2.2.4: http://pastie.org/547061

And as I initially suspected, it indeed was a path related problem.

When putting this in my config.ru:
  $:.push(''/srv/puppet/lib'')

I obtain thee following RUBYLIB search path:
 
["/usr/lib/ruby/gems/1.8/gems/passenger-2.2.2/vendor/rack-1.0.0-git/lib",
"/usr/lib/ruby/gems/1.8/gems/passenger-2.2.2/lib",
"/usr/lib/ruby/gems/1.8/gems/passenger-2.2.2/ext",
"/usr/lib/ruby/gems/1.8/gems/fastthread-1.0.7/bin",
"/usr/lib/ruby/gems/1.8/gems/fastthread-1.0.7/lib",
"/usr/lib/ruby/gems/1.8/gems/fastthread-1.0.7/ext",
"/usr/lib/ruby/site_ruby/1.8",
"/usr/lib64/ruby/site_ruby/1.8",
"/usr/lib64/ruby/site_ruby/1.8/x86_64-linux",
"/usr/lib/ruby/site_ruby", "/usr/lib64/ruby/site_ruby",
"/usr/lib64/site_ruby/1.8",
"/usr/lib64/site_ruby/1.8/x86_64-linux",
"/usr/lib64/site_ruby", "/usr/lib/ruby/1.8",
"/usr/lib64/ruby/1.8", "/usr/lib64/ruby/1.8/x86_64-linux",
".", "/srv/puppet/lib"]

And I had an RPM based puppet-0.24.8 installed in
/usr/lib/ruby/site_ruby/1.8/puppet which got used instead of 0.25.0beta2 in
/srv/puppet/lib...

The workaround I used was to put this in my config.ru instead:

  $:.insert(0, ''/srv/puppet/lib'')

which sets RUBYLIB as so:
  ["/srv/puppet/lib",
"/usr/lib/ruby/gems/1.8/gems/passenger-2.2.2/blabla...

I now have a few ssl-cert & permission related problems which are probably
easy to figure out.

Conclusion:
 - passenger 2.2.2 seems to currently be the only option
 - watch out when different puppet versions live on the same host

Thanks for you help folks !
Marc




--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---