0
Under review

how to setup puma in a new rails website?

Daniel Tsionit 6 ár síðan updated by okay PADAK 6 ár síðan 14
Hi, I followed after this tutorial step by step and got stuck on this part:



under content tab I don't see puma support...

and on the plugins tab I get error on puma bundle dependency...


In this case, you need to make sure that Bundler is available on default $PATH. If you e.g. use RVM and Bundler is hidden somewhere in /usr/lib..., then you can symlink it into /usr/bin and restart Ajenti.
I used which bundle and it's somewhere deep in .rvm folder...
How do I fix its $PATH...?

 
+1
You can either modify system (not user's) PATH on your system (no idea where and which OS you use) or just run sudo ln -s `which bundle` /usr/bin/bundle
OK it worked! thanks!

now there is another error in the puma service.. 




and this is my supervisor logs:


2014-09-10 08:08:17,683 INFO spawned: 'store1ajentilocal-ruby-puma-0' with pid 3974
2014-09-10 08:08:17,692 INFO exited: store1ajentilocal-ruby-puma-0 (exit status 127; not expected)
2014-09-10 08:08:18,440 INFO gave up: store1ajentilocal-ruby-puma-0 entered FATAL state, too many start retries too quickly
2014-09-10 08:08:27,338 WARN received SIGTERM indicating exit request
2014-09-10 08:08:27,475 CRIT Supervisor running as root (no user in config file)
2014-09-10 08:08:27,513 INFO RPC interface 'supervisor' initialized
2014-09-10 08:08:27,514 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-09-10 08:08:27,516 INFO daemonizing the supervisord process
2014-09-10 08:08:27,518 INFO supervisord started with pid 3982
2014-09-10 08:08:28,522 INFO spawned: 'store1ajentilocal-ruby-puma-0' with pid 3984
2014-09-10 08:08:28,527 INFO exited: store1ajentilocal-ruby-puma-0 (exit status 127; not expected)
2014-09-10 08:08:29,532 INFO spawned: 'store1ajentilocal-ruby-puma-0' with pid 3985
2014-09-10 08:08:29,537 INFO exited: store1ajentilocal-ruby-puma-0 (exit status 127; not expected)
2014-09-10 08:08:31,544 INFO spawned: 'store1ajentilocal-ruby-puma-0' with pid 3986
2014-09-10 08:08:31,548 INFO exited: store1ajentilocal-ruby-puma-0 (exit status 127; not expected)
2014-09-10 08:08:34,556 INFO spawned: 'store1ajentilocal-ruby-puma-0' with pid 3987
2014-09-10 08:08:34,560 INFO exited: store1ajentilocal-ruby-puma-0 (exit status 127; not expected)
2014-09-10 08:08:35,561 INFO gave up: store1ajentilocal-ruby-puma-0 entered FATAL state, too many start retries too quickly
2014-09-10 08:08:35,932 WARN received SIGTERM indicating exit request
2014-09-10 08:08:36,106 CRIT Supervisor running as root (no user in config file)
2014-09-10 08:08:36,147 INFO RPC interface 'supervisor' initialized
2014-09-10 08:08:36,147 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-09-10 08:08:36,149 INFO daemonizing the supervisord process
2014-09-10 08:08:36,152 INFO supervisord started with pid 3993
2014-09-10 08:08:37,157 INFO spawned: 'store1ajentilocal-ruby-puma-0' with pid 3995
2014-09-10 08:08:37,161 INFO exited: store1ajentilocal-ruby-puma-0 (exit status 127; not expected)
2014-09-10 08:08:38,166 INFO spawned: 'store1ajentilocal-ruby-puma-0' with pid 3996
2014-09-10 08:08:38,188 INFO exited: store1ajentilocal-ruby-puma-0 (exit status 127; not expected)
2014-09-10 08:08:40,194 INFO spawned: 'store1ajentilocal-ruby-puma-0' with pid 3997
2014-09-10 08:08:40,198 INFO exited: store1ajentilocal-ruby-puma-0 (exit status 127; not expected)
2014-09-10 08:08:43,204 INFO spawned: 'store1ajentilocal-ruby-puma-0' with pid 3998
2014-09-10 08:08:43,208 INFO exited: store1ajentilocal-ruby-puma-0 (exit status 127; not expected)
2014-09-10 08:08:44,209 INFO gave up: store1ajentilocal-ruby-puma-0 entered FATAL state, too many start retries too quickly
278,1 Bot





Any Idea?


You should see details in your application's production.log
Hi all. I have some troubles running my ajenti server and I was wondering if someone here can help me with that..
I need a professional support please. trying to install multiple rails applications (spree) on one server.

please contact me... 
thanks ahead. 
Have you checked the application's production.log for Puma errors, as I suggested?
Didn't find it... my log folder is empty.
I had to do the following:
$ ln -s `which bundle` /usr/bin/bundle
$ ln -s `which puma` /usr/bin/puma
$ ln -s `which ruby_executable_hooks` /usr/bin/ruby_executable_hooks
$ ln -s `which ruby` /usr/bin/ruby

It seems however that Ajenti isn't yet ready for RVM or Rails. Way too much messing around.

Hopefully the devs will take RVM into consideration as using the pre-packaged ruby is a pain especially when using Ruby 2 and Rails 4.

Thanks for sharing. it was helpful.
In the same subject, I ran into a new error regarding to user\file permissions...
puma still not working. I tried clicking on "FIX FILE PERMISSIONS" btn.

I tried switching to the nginx user : 'www-data' and running the puma command in my app directory like this:

bundle exec puma -e production -t 4 -b unix:///var/run/ajenti-v-puma-store1ajentilocal-ruby-puma-0.sock

Then it crashed printing this error:


[www-data@ajenti www]$ bundle exec puma -e production -t 4 -b unix:///var/run/ajenti-v-puma-store1ajentilocal-ruby-puma-0.sock
Puma starting in single mode...
* Version 2.9.1 (ruby 2.1.2-p95), codename: Team High Five
* Min threads: 0, max threads: 4
* Environment: production
[WARNING] You are not setting Devise.secret_key within your application!
You must set this in config/initializers/devise.rb. Here's an example:

Devise.secret_key = "656e3159c231b92ae6008fa57dfd80e53eca27e0271e032e8e7bfa47cb7afd7f1b46a9e9dbac24a5ebc899fb86a24e123692"
Instance method "open" is already defined in Object, use generic helper instead or set StateMachine::Machine.ignore_method_conflicts = true.
* Listening on unix:///var/run/ajenti-v-puma-store1ajentilocal-ruby-puma-0.sock
/usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/lib/puma/binder.rb:268:in `unlink': Permission denied @ unlink_internal - /var/run/ajenti-v-puma-store1ajentilocal-ruby-puma-0.sock (Errno::EACCES)

from /usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/lib/puma/binder.rb:268:in `rescue in add_unix_listener'
from /usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/lib/puma/binder.rb:265:in `add_unix_listener'
from /usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/lib/puma/binder.rb:119:in `block in parse'
from /usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/lib/puma/binder.rb:82:in `each'
from /usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/lib/puma/binder.rb:82:in `parse'
from /usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/lib/puma/runner.rb:119:in `load_and_bind'
from /usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/lib/puma/single.rb:73:in `run'
from /usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/lib/puma/cli.rb:499:in `run'
from /usr/local/rvm/gems/ruby-2.1.2/gems/puma-2.9.1/bin/puma:10:in `<top (required)>'
from /usr/local/rvm/gems/ruby-2.1.2/bin/puma:23:in `load'
from /usr/local/rvm/gems/ruby-2.1.2/bin/puma:23:in `<main>'
from /usr/local/rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `eval'
from /usr/local/rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `<main>'


It seems like user file permissions... I am running spreecommerce by the way on centos 6.5 using nginx, mariadb and
puma.

I appreciate any kind of help.
Thanks ahead.


Try to remove the mentioned socket file by hand.
the same error

puma server not starting

bundle exec puma -e production -t 4 -b unix:///var/run/ajenti-v-puma-store1ajentilocal-ruby-puma-0.sock

check but:


Your Gemfile lists the gem redcarpet (~> 2.3.0) more than once.
You should probably keep only one of them.
While it's not a problem now, it could cause errors if you change the version of just one of them later.
/usr/local/rvm/gems/ruby-2.1.2/gems/bundler-1.7.7/lib/bundler/rubygems_integration.rb:256:in `block in replace_gem': puma is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
from /usr/local/rvm/gems/ruby-2.1.2/bin/puma:22:in `<main>'
from /usr/local/rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `eval'
from /usr/local/rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `<main>'

gem install redcarpet 

not fix 

need help please