Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2017-05-16 Thread Moses Mendoza (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6061 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 
 
Running puppet master using rack/passenger is deprecated - can you consider using puppet server instead? https://docs.puppet.com/puppetserver/2.7/install_from_packages.html. Distros don't necessarily have puppet server packages yet, so installing from Puppet's repos is best bet. Alternatively, if you need to use the distro packages, can you file a bug with your linux distro maintainers of the package you're using?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2017-05-16 Thread Sean McDonald (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6061 
 
 
 
  Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Labels:
 
 triaged 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2016-12-06 Thread CYK (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 CYK updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6061 
 
 
 
  Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 

Change By:
 
 CYK 
 
 
 

Priority:
 
 Normal Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2016-08-22 Thread Jon Skarpeteig (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jon Skarpeteig commented on  PUP-6061 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 
 
I'm seeing this issue as well; 
Ubuntu 16.04 Ruby 2.3.0 Puppet 4.6.0 
Debug output: 
 Web application could not be started  /usr/lib/x86_64-linux-gnu/ruby/2.3.0/openssl.so: symbol EC_GROUP_new_curve_GF2m, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference - /usr/lib/x86_64-linux-gnu/ruby/2.3.0/openssl.so (LoadError) /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /usr/lib/ruby/2.3.0/openssl.rb:13:in `' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/monkey_patches.rb:97:in `' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:16:in `' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:15:in `' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:14:in `' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:12:in `' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' config.ru:42:in `block in ' /usr/lib/ruby/vendor_ruby/rack/builder.rb:55:in `instance_eval' /usr/lib/ruby/vendor_ruby/rack/builder.rb:55:in `initialize' config.ru:1:in `new' config.ru:1:in `' /usr/share/passenger/helper-scripts/rack-preloader.rb:110:in `eval' /usr/share/passenger/helper-scripts/rack-preloader.rb:110:in `preload_app' /usr/share/passenger/helper-scripts/rack-preloader.rb:156:in `' /usr/share/passenger/helper-scripts/rack-preloader.rb:30:in `' /usr/share/passenger/helper-scripts/rack-preloader.rb:29:in `'  
  Error ID 0a2a7a53 Application root /usr/share/puppet/rack/puppetmasterd Environment (value of RAILS_ENV, RACK_ENV, WSGI_ENV, NODE_ENV and PASSENGER_APP_ENV) development 
 Ruby interpreter command /usr/bin/ruby 
 User and groups uid=105(puppet) gid=112(puppet) groups=112(puppet)  Environment variables APACHE_RUN_DIR = /var/run/apache2 APACHE_PID_FILE = /var/run/apache2/apache2.pid PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin APACHE_LOCK_DIR = /var/lock/apache2 LANG = C APACHE_RUN_USER = www-data APACHE_RUN_GROUP = www-data APACHE_LOG_DIR = /var/log/apache2 PWD = /usr/share/puppet/rack/puppetmasterd PASSENGER_USE_FEEDBACK_FD = true SERVER_SOFTWARE = Apache/2.4.18 (Ubuntu) Phusion_Passenger/5.0.27 PASSENGER_DEBUG_DIR = /tmp/passenger.spawn-debug.7tRY7n USER = puppet LOGNAME = puppet SHELL = /bin/false HOME = /opt/puppetlabs/server/data/puppetserver IN_PASSENGER = 1 PYTHONUNBUFFERED = 1 NODE_PATH = /usr/share/passenger/node RAILS_ENV = development RACK_ENV = development WSGI_ENV = development NODE_ENV = development PASSENGER_APP_ENV = development HTTPS = on SSL_TLS_SNI = foreman SSL_SERVER_S_DN_CN = foreman SSL_SERVER_I_DN_CN = Puppet CA: foreman SSL_CLIENT_S_DN_CN =

Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2016-03-23 Thread Eric Sorenson (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-6061 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 
 
Bharath this is not really a supported configuration. 
Can you show what operating system version and puppet package you are using? I'm curious how you got to this point. 
Without this information we cannot help further. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2016-03-23 Thread Eric Sorenson (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6061 
 
 
 
  Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Component/s:
 
 Puppet Server 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2016-03-23 Thread Eric Sorenson (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson assigned an issue to Bharath 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6061 
 
 
 
  Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Assignee:
 
 Bharath 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2016-03-20 Thread Chris Price (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-6061 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 
 
Bharath Have you considered using Puppet Server (via the puppetserver distro packages) instead of Passenger? This is our recommended path for the future, and we intend to remove support for Webrick and Passenger eventually. 
Michael Stahnke can you provide any information on how to get Passenger working with PC1/Puppet 4? My understanding is that it requires building Passenger instead of using the gem? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2016-03-15 Thread Bharath (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bharath updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6061 
 
 
 
  Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bharath 
 
 
 
 
 
 
 
 
 
 Installed Puppet Server Version 4.3.2 with Passenger. Get an error when i test from puppet agentroot@puppet:~# ruby -vruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux]root@puppet:~# puppet --version4.3.2root@puppet:~# [ 2016-03-01 17:19:52.2785 15461/b587eb40 age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /usr/share/puppet/rack/puppetmasterd: An error occurred while starting up the preloader.  Error ID: 15b066cc  Error details saved to: /tmp/passenger-error-QQEnrc.html  Message from application: /usr/lib/ruby/1.9.1/i686-linux/openssl.so: symbol EC_GROUP_new_curve_GF2m, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference - /usr/lib/ruby/1.9.1/i686-linux/openssl.so (LoadError)  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /usr/lib/ruby/1.9.1/openssl.rb:17:in `'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/monkey_patches.rb:89:in `'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:16:in `'  /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:15:in `'  /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:14:in `'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:12:in `'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'  config.ru:43:in `block in '  /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/builder.rb:55:in `instance_eval'  /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/builder.rb:55:in `initialize'  config.ru:1:in `new'  config.ru:1:in `'  /var/lib/gems/1.9.1/gems/passenger-5.0.24/src/helper-scripts/rack-preloader.rb:110:in `eval'  /var/lib/gems/1.9.1/gems/passenger-5.0.24/src/helper-scripts/rack-preloader.rb:110:in `preload_app'  /var/lib/gems/1.9.1/gems/passenger-5.0.24/src/helper-scripts/rack-preloader.rb:156:in `'  /var/lib/gems/1.9.1/gems/passenger-5.0.24/src/helper-scripts/rack-preloader.rb:30:in `'  /var/lib/gems/1.9.1/gems/passenger-5.0.24/src/helper-scripts/rack-preloader.rb:29:in `' Content of config.ru# a config.ru, for use with every rack-compatible webserver.# SSL needs to be handled outside this, though.# if puppet is not in your RUBYLIB:#$LOAD_PATH.unshift('/opt/puppetlabs/puppet/lib')$LOAD_PATH.unshift('/opt/puppetlabs/puppet/lib/ruby/vendor_ruby')$0 = "master"# if you want debugging:# ARGV << "--debug"ARGV << "--rack"# Rack applications typically don't start as root.  

Jira (PUP-6061) Puppet - Passenger Could not spawn process for application

2016-03-15 Thread Bharath (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bharath created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6061 
 
 
 
  Puppet - Passenger Could not spawn process for application  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Puppet Server 
 
 
 

Created:
 

 2016/03/15 10:47 PM 
 
 
 

Fix Versions:
 

 PUP 4.3.2 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Bharath 
 
 
 
 
 
 
 
 
 
 
Installed Puppet Server Version 4.3.2 with Passenger. Get an error when i test from puppet agent 
root@puppet:~# ruby -v ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux] root@puppet:~# puppet --version 4.3.2 root@puppet:~#  
[ 2016-03-01 17:19:52.2785 15461/b587eb40 age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /usr/share/puppet/rack/puppetmasterd: An error occurred while starting up the preloader. Error ID: 15b066cc Error details saved to: /tmp/passenger-error-QQEnrc.html Message from application: /usr/lib/ruby/1.9.1/i686-linux/openssl.so: symbol EC_GROUP_new_curve_GF2m, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference - /usr/lib/ruby/1.9.1/i686-linux/openssl.so (LoadError) /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' /usr/lib/ruby/1.9.1/openssl.rb:17:in `' /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'