thr3ads.net - Puppet users - [Puppet Users] Passenger Woes [Oct 2009]

If this information is useful, please help other people find it:
Share via:

Stephen Nelson-Smith

2009-Oct-19 17:52 UTC

[Puppet Users] Passenger Woes

Hello,

I really didn''t expect this to be difficult, but I''ve been
struggling
with this all day :(

I''m running CentOS 5.3, with rubygems, rack and fastthread, from EPEL.

I''m running puppet-0.25.0-1 built from the spec file in the latest
stable tarball.

I''m using mod_passenger-2.2.5-2.el5 from Jeroen van Meeuwen (kanarip),
which is effectively EPEL too.

I''m using the config.ru file from
http://github.com/reductivelabs/puppet/blob/master/ext/rack/files/config.ru,
chowned to puppet and chmoded 644.

I''ve added:

[puppetmasterd]
    ssl_client_header = SSL_CLIENT_S_DN
    ssl_client_verify_header = SSL_CLIENT_VERIFY

to my puppet.conf as directed in the README.

I''ve set up an apache vhost as follows:

PassengerHighPerformance on
PassengerMaxPoolSize 12
PassengerPoolIdleTime 1500
# PassengerMaxRequests 1000
PassengerStatThrottleRate 120
RackAutoDetect Off
RailsAutoDetect Off

Listen 8140

LoadModule ssl_module modules/mod_ssl.so

AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl    .crl
SSLPassPhraseDialog  builtin
SSLSessionCache         shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout  300
SSLMutex default
SSLRandomSeed startup file:/dev/urandom  256
SSLRandomSeed connect builtin
SSLCryptoDevice builtin

<VirtualHost *:8140>
        SSLEngine on
        SSLProtocol -ALL +SSLv3 +TLSv1
        SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP

        SSLCertificateFile      /var/lib/puppet/ssl/certs/puppet.pem
        SSLCertificateKeyFile   /var/lib/puppet/ssl/private_keys/puppet.pem
        SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem
        SSLCACertificateFile    /var/lib/puppet/ssl/ca/ca_crt.pem

        # If Apache complains about invalid signatures on the CRL, you
can try disabling
        # CRL checking by commenting the next line, but this is not recommended.
        SSLCARevocationFile     /var/lib/puppet/ssl/ca/ca_crl.pem

        SSLVerifyClient optional
        SSLVerifyDepth  1
        SSLOptions +StdEnvVars

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

When I start apache, and browse to the puppet server on 8140 I get a
500 and see the following in the logs:

/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'': no such file to load -- rack/rewindable_input
(LoadError)
        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require''
        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/request_handler.rb:27
        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require''
        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require''
        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:34
        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require''
        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require''
        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
`spawn_application''
        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
`handle_spawn_application''
        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
`__send__''
        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
`main_loop''
        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
`start_synchronously''
        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
[ pid=5357 file=ext/apache2/Hooks.cpp:725 time=2009-10-19 23:09:10.957 ]:
  Unexpected error in mod_passenger: Cannot spawn application
''/etc/puppet/rack'': The spawn server has exited unexpectedly.
  Backtrace:
     in ''virtual
boost::shared_ptr<Passenger::Application::Session>
Passenger::ApplicationPoolServer::Client::get(const
Passenger::PoolOptions&)'' (ApplicationPoolServer.h:471)
     in ''int Hooks::handleRequest(request_rec*)''
(Hooks.cpp:521)

I''m baffled - I can''t see what''s wrong.  Please help!
:)

TIA,

S.
-- 
Stephen Nelson-Smith
Technical Director
Atalanta Systems Ltd
www.atalanta-systems.com

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

Julian Simpson

2009-Oct-19 18:32 UTC

head link

[Puppet Users] Re: Passenger Woes

Is there a file called rewindable_input.rb on the system? Looks like a  
missing gem or ruby path issue.

J.

Sent from my iPhone

On 19 Oct 2009, at 18:52, Stephen Nelson-Smith <sanelson@gmail.com>  
wrote:
>
> Hello,
>
> I really didn''t expect this to be difficult, but I''ve
been struggling
> with this all day :(
>
> I''m running CentOS 5.3, with rubygems, rack and fastthread, from
EPEL.
>
> I''m running puppet-0.25.0-1 built from the spec file in the latest
> stable tarball.
>
> I''m using mod_passenger-2.2.5-2.el5 from Jeroen van Meeuwen
(kanarip),
> which is effectively EPEL too.
>
> I''m using the config.ru file from
> http://github.com/reductivelabs/puppet/blob/master/ext/rack/files/config.ru
> ,
> chowned to puppet and chmoded 644.
>
> I''ve added:
>
> [puppetmasterd]
>    ssl_client_header = SSL_CLIENT_S_DN
>    ssl_client_verify_header = SSL_CLIENT_VERIFY
>
> to my puppet.conf as directed in the README.
>
> I''ve set up an apache vhost as follows:
>
> PassengerHighPerformance on
> PassengerMaxPoolSize 12
> PassengerPoolIdleTime 1500
> # PassengerMaxRequests 1000
> PassengerStatThrottleRate 120
> RackAutoDetect Off
> RailsAutoDetect Off
>
> Listen 8140
>
> LoadModule ssl_module modules/mod_ssl.so
>
> AddType application/x-x509-ca-cert .crt
> AddType application/x-pkcs7-crl    .crl
> SSLPassPhraseDialog  builtin
> SSLSessionCache         shmcb:/var/cache/mod_ssl/scache(512000)
> SSLSessionCacheTimeout  300
> SSLMutex default
> SSLRandomSeed startup file:/dev/urandom  256
> SSLRandomSeed connect builtin
> SSLCryptoDevice builtin
>
> <VirtualHost *:8140>
>        SSLEngine on
>        SSLProtocol -ALL +SSLv3 +TLSv1
>        SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP
>
>        SSLCertificateFile      /var/lib/puppet/ssl/certs/puppet.pem
>        SSLCertificateKeyFile   /var/lib/puppet/ssl/private_keys/ 
> puppet.pem
>        SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem
>        SSLCACertificateFile    /var/lib/puppet/ssl/ca/ca_crt.pem
>
>        # If Apache complains about invalid signatures on the CRL, you
> can try disabling
>        # CRL checking by commenting the next line, but this is not  
> recommended.
>        SSLCARevocationFile     /var/lib/puppet/ssl/ca/ca_crl.pem
>
>        SSLVerifyClient optional
>        SSLVerifyDepth  1
>        SSLOptions +StdEnvVars
>
>        DocumentRoot /etc/puppet/rack/public/
>        RackBaseURI /
>        <Directory /etc/puppet/rack/>
>                Options None
>                AllowOverride None
>                Order allow,deny
>                allow from all
>        </Directory>
> </VirtualHost>
>
> When I start apache, and browse to the puppet server on 8140 I get a
> 500 and see the following in the logs:
>
> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'': no such file to load --
rack/rewindable_input
> (LoadError)
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 
> 31:in
> `require''
>        from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ 
> phusion_passenger/rack/request_handler.rb:27
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 
> 31:in
> `gem_original_require''
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 
> 31:in
> `require''
>        from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ 
> phusion_passenger/rack/application_spawner.rb:34
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 
> 31:in
> `gem_original_require''
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 
> 31:in
> `require''
>        from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ 
> phusion_passenger/spawn_manager.rb:157:in
> `spawn_application''
>        from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ 
> phusion_passenger/spawn_manager.rb:287:in
> `handle_spawn_application''
>        from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ 
> phusion_passenger/abstract_server.rb:352:in
> `__send__''
>        from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ 
> phusion_passenger/abstract_server.rb:352:in
> `main_loop''
>        from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ 
> phusion_passenger/abstract_server.rb:196:in
> `start_synchronously''
>        from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/ 
> passenger-spawn-server:61
> [ pid=5357 file=ext/apache2/Hooks.cpp:725 time=2009-10-19  
> 23:09:10.957 ]:
>  Unexpected error in mod_passenger: Cannot spawn application
> ''/etc/puppet/rack'': The spawn server has exited
unexpectedly.
>  Backtrace:
>     in ''virtual
boost::shared_ptr<Passenger::Application::Session>
> Passenger::ApplicationPoolServer::Client::get(const
> Passenger::PoolOptions&)'' (ApplicationPoolServer.h:471)
>     in ''int Hooks::handleRequest(request_rec*)''
(Hooks.cpp:521)
>
> I''m baffled - I can''t see what''s wrong.  Please
help! :)
>
> TIA,
>
> S.
> -- 
> Stephen Nelson-Smith
> Technical Director
> Atalanta Systems Ltd
> www.atalanta-systems.com
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Stephen Nelson-Smith

2009-Oct-20 07:53 UTC

head link

[Puppet Users] Re: Passenger Woes

Hi Julian,

On Mon, Oct 19, 2009 at 7:32 PM, Julian Simpson <simpsonjulian@gmail.com>
wrote:>
> Is there a file called rewindable_input.rb on the system? Looks like a
> missing gem or ruby path issue.
Thanks Julian - I think the problem is that rubygem-rack from EPEL is
an old version that doesn''t contain rewindable_input.rb.  I''ve
installed it from the gem instead, and we appear to have a significant
improvement.  Maybe I''m warming to the idea of using gems.... :$

S.
-- 
Stephen Nelson-Smith
Technical Director
Atalanta Systems Ltd
www.atalanta-systems.com

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

Matt

2009-Oct-20 08:25 UTC

head link

[Puppet Users] Re: Passenger Woes

Stephen FWIW, I has issues getting it to work with passenger 2.2.5 and
settled on version 2.2.2 installed using the gem install passenger
-version 2.2.2

Thanks,

Matt

2009/10/19 Stephen Nelson-Smith
<sanelson@gmail.com>:>
> Hello,
>
> I really didn''t expect this to be difficult, but I''ve
been struggling
> with this all day :(
>
> I''m running CentOS 5.3, with rubygems, rack and fastthread, from
EPEL.
>
> I''m running puppet-0.25.0-1 built from the spec file in the latest
> stable tarball.
>
> I''m using mod_passenger-2.2.5-2.el5 from Jeroen van Meeuwen
(kanarip),
> which is effectively EPEL too.
>
> I''m using the config.ru file from
>
http://github.com/reductivelabs/puppet/blob/master/ext/rack/files/config.ru,
> chowned to puppet and chmoded 644.
>
> I''ve added:
>
> [puppetmasterd]
>    ssl_client_header = SSL_CLIENT_S_DN
>    ssl_client_verify_header = SSL_CLIENT_VERIFY
>
> to my puppet.conf as directed in the README.
>
> I''ve set up an apache vhost as follows:
>
> PassengerHighPerformance on
> PassengerMaxPoolSize 12
> PassengerPoolIdleTime 1500
> # PassengerMaxRequests 1000
> PassengerStatThrottleRate 120
> RackAutoDetect Off
> RailsAutoDetect Off
>
> Listen 8140
>
> LoadModule ssl_module modules/mod_ssl.so
>
> AddType application/x-x509-ca-cert .crt
> AddType application/x-pkcs7-crl    .crl
> SSLPassPhraseDialog  builtin
> SSLSessionCache         shmcb:/var/cache/mod_ssl/scache(512000)
> SSLSessionCacheTimeout  300
> SSLMutex default
> SSLRandomSeed startup file:/dev/urandom  256
> SSLRandomSeed connect builtin
> SSLCryptoDevice builtin
>
> <VirtualHost *:8140>
>        SSLEngine on
>        SSLProtocol -ALL +SSLv3 +TLSv1
>        SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP
>
>        SSLCertificateFile      /var/lib/puppet/ssl/certs/puppet.pem
>        SSLCertificateKeyFile   /var/lib/puppet/ssl/private_keys/puppet.pem
>        SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem
>        SSLCACertificateFile    /var/lib/puppet/ssl/ca/ca_crt.pem
>
>        # If Apache complains about invalid signatures on the CRL, you
> can try disabling
>        # CRL checking by commenting the next line, but this is not
recommended.
>        SSLCARevocationFile     /var/lib/puppet/ssl/ca/ca_crl.pem
>
>        SSLVerifyClient optional
>        SSLVerifyDepth  1
>        SSLOptions +StdEnvVars
>
>        DocumentRoot /etc/puppet/rack/public/
>        RackBaseURI /
>        <Directory /etc/puppet/rack/>
>                Options None
>                AllowOverride None
>                Order allow,deny
>                allow from all
>        </Directory>
> </VirtualHost>
>
> When I start apache, and browse to the puppet server on 8140 I get a
> 500 and see the following in the logs:
>
> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'': no such file to load --
rack/rewindable_input
> (LoadError)
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require''
>        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/request_handler.rb:27
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require''
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require''
>        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:34
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require''
>        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require''
>        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:157:in
> `spawn_application''
>        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
> `handle_spawn_application''
>        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> `__send__''
>        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
> `main_loop''
>        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
> `start_synchronously''
>        from
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
> [ pid=5357 file=ext/apache2/Hooks.cpp:725 time=2009-10-19 23:09:10.957 ]:
>  Unexpected error in mod_passenger: Cannot spawn application
> ''/etc/puppet/rack'': The spawn server has exited
unexpectedly.
>  Backtrace:
>     in ''virtual
boost::shared_ptr<Passenger::Application::Session>
> Passenger::ApplicationPoolServer::Client::get(const
> Passenger::PoolOptions&)'' (ApplicationPoolServer.h:471)
>     in ''int Hooks::handleRequest(request_rec*)''
(Hooks.cpp:521)
>
> I''m baffled - I can''t see what''s wrong.  Please
help! :)
>
> TIA,
>
> S.
> --
> Stephen Nelson-Smith
> Technical Director
> Atalanta Systems Ltd
> www.atalanta-systems.com
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Stephen Nelson-Smith

2009-Oct-20 16:24 UTC

head link

[Puppet Users] Re: Passenger Woes

Hi,

On Tue, Oct 20, 2009 at 9:25 AM, Matt <mattmoran76@gmail.com>
wrote:>
> Stephen FWIW, I has issues getting it to work with passenger 2.2.5 and
> settled on version 2.2.2 installed using the gem install passenger
> -version 2.2.2
I''m still on 2.2.5.  I''ve been able to exchange SSL certs, but
now if
I run puppet on a client I get this:

# puppetd --test
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Bad Request
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

In the access log I see a GET
/production/catalog/machine................. but this is a 400.

I see nothing in the error log, even on debug level.

Everything under /etc/puppet is owned by puppet.

Interestingly from a different machine, puppetd --test gives me this:

err: Could not retrieve catalog from remote server: Error 403 on
SERVER: Forbidden
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

From a third (debian) machine I get this:

# puppetd --test --server=puppet
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
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
ldap:~# puppet --version
0.24.5

So far I''ve spent two days on this, and haven''t deployed a
single
resource with puppet... :(

Any ideas?

S.
-- 
Stephen Nelson-Smith
Technical Director
Atalanta Systems Ltd
www.atalanta-systems.com

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

Matt

2009-Oct-20 20:36 UTC

head link

[Puppet Users] Re: Passenger Woes

I''d really bite the bullet Stephen and give passenger 2.2.2 a try.

2009/10/20 Stephen Nelson-Smith
<sanelson@gmail.com>:>
> Hi,
>
> On Tue, Oct 20, 2009 at 9:25 AM, Matt <mattmoran76@gmail.com> wrote:
>>
>> Stephen FWIW, I has issues getting it to work with passenger 2.2.5 and
>> settled on version 2.2.2 installed using the gem install passenger
>> -version 2.2.2
>
> I''m still on 2.2.5.  I''ve been able to exchange SSL
certs, but now if
> I run puppet on a client I get this:
>
> # puppetd --test
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Bad Request
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
>
> In the access log I see a GET
> /production/catalog/machine................. but this is a 400.
>
> I see nothing in the error log, even on debug level.
>
> Everything under /etc/puppet is owned by puppet.
>
> Interestingly from a different machine, puppetd --test gives me this:
>
> err: Could not retrieve catalog from remote server: Error 403 on
> SERVER: Forbidden
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
>
> From a third (debian) machine I get this:
>
> # puppetd --test --server=puppet
> 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
> 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
> ldap:~# puppet --version
> 0.24.5
>
> So far I''ve spent two days on this, and haven''t deployed
a single
> resource with puppet... :(
>
> Any ideas?
>
> S.
> --
> Stephen Nelson-Smith
> Technical Director
> Atalanta Systems Ltd
> www.atalanta-systems.com
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Stephen Nelson-Smith

2009-Oct-21 07:31 UTC

head link

[Puppet Users] Re: Passenger Woes

On Tue, Oct 20, 2009 at 9:36 PM, Matt <mattmoran76@gmail.com>
wrote:>
> I''d really bite the bullet Stephen and give passenger 2.2.2 a try.
OK - tried passenger 2.2.2 - same behaviour.

I''m going to blow everything away and start again from scratch and see
if I get the same results.

S.
-- 
Stephen Nelson-Smith
Technical Director
Atalanta Systems Ltd
www.atalanta-systems.com

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

nothings_absolute

2009-Oct-26 16:49 UTC

head link

[Puppet Users] Re: Passenger Woes

Did anyone find a resolution to this problem? I am getting the same
thing with Solaris and have tried both 2.2.2 and 2.2.5 and get "Error
400 on SERVER: Bad Request" with both versions.

passenger-status seems to work properly:
passenger-status
----------- General information -----------
max      = 12
count    = 0
active   = 0
inactive = 0
Waiting on global queue: 0



On Oct 21, 1:31 am, Stephen Nelson-Smith <sanel...@gmail.com>
wrote:> On Tue, Oct 20, 2009 at 9:36 PM, Matt <mattmora...@gmail.com> wrote:
>
> > I''d really bite the bullet Stephen and givepassenger2.2.2 a
try.
>
> OK - triedpassenger2.2.2 - same behaviour.
>
> I''m going to blow everything away and start again from scratch and
see
> if I get the same results.
>
> S.
> --
> Stephen Nelson-Smith
> Technical Director
> Atalanta Systems Ltdwww.atalanta-systems.com--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Seemingly Similar Threads

Search for more possibly parallel threads

Puppet users - Oct 2009 - Passenger Woes

[Puppet Users] Passenger Woes

[Puppet Users] Re: Passenger Woes

[Puppet Users] Re: Passenger Woes

[Puppet Users] Re: Passenger Woes

[Puppet Users] Re: Passenger Woes

[Puppet Users] Re: Passenger Woes

[Puppet Users] Re: Passenger Woes

[Puppet Users] Re: Passenger Woes

Seemingly Similar Threads