Puppet - Passenger Could not spawn process for application

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 `<top (required)>'
/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 `<top (required)>'
/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 `<module:Util>'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:15:in `<module:Puppet>'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:14:in `<top (required)>'
/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 `<top (required)>'
/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 `<top (required)>'
/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 <main>'
/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 `<main>'
/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 `<module:App>'
/var/lib/gems/1.9.1/gems/passenger-5.0.24/src/helper-scripts/rack-preloader.rb:30:in `<module:PhusionPassenger>'
/var/lib/gems/1.9.1/gems/passenger-5.0.24/src/helper-scripts/rack-preloader.rb:29:in `<main>'

Content of config.ru

1. a config.ru, for use with every rack-compatible webserver.

1. SSL needs to be handled outside this, though.

1. 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"

1. if you want debugging:
2. ARGV << "--debug"

ARGV << "--rack"

1. Rack applications typically don't start as root. Set --confdir, --vardir,
2. --logdir, --rundir to prevent reading configuration from
3. ~/ based pathing.
   ARGV << "--confdir" << "/etc/puppetlabs/puppet"
   ARGV << "--vardir" << "/opt/puppetlabs/server/data/puppetmaster"
   ARGV << "--logdir" << "/var/log/puppetlabs/puppetmaster"
   ARGV << "--rundir" << "/var/run/puppetlabs/puppetmaster"
   ARGV << "--codedir" << "/etc/puppetlabs/code"

1. always_cache_features is a performance improvement and safe for a master to
2. apply. This is intended to allow agents to recognize new features that may be
3. delivered during catalog compilation.
   ARGV << "--always_cache_features"

1. NOTE: it's unfortunate that we have to use the "CommandLine" class
2. here to launch the app, but it contains some initialization logic
3. (such as triggering the parsing of the config file) that is very
4. important. We should do something less nasty here when we've
5. gotten our API and settings initialization logic cleaned up.
   #
6. Also note that the "$0 = master" line up near the top here is
7. the magic that allows the CommandLine class to know that it's
8. supposed to be running master.
   #
9. --cprice 2012-05-22

require 'puppet/util/command_line'

1. we're usually running inside a Rack::Builder.new {} block,
2. therefore we need to call run here.
   run Puppet::Util::CommandLine.new.execute