Puma with Padrino, CPU consumption will not stop
I have one problem which I am trying to solve, I have Ruby web project, written in Padrino, it is quite simply project. But I have problems with running the Puma.
Everything works fine, but after a few days, or if I make a stress test, the process of Puma is consuming 100% CPU and stays there forever. I need just to restart Puma (resp. kill it and start again).
It is happening on a few my projects, on Debian Stretch and Jessie.
Puma version is 3.11.4
and this is one of the config files:
preload_app!
rackup 'config.ru'
environment 'production'
daemonize
pidfile 'logs/osadababa.pid'
state_path 'logs/puma.state'
stdout_redirect 'logs/stdout', 'logs/stderr', true
threads 4,6
bind 'ssl://0.0.0.0:8060?key=/etc/letsencrypt/live/osadababa.cz/privkey.pem&cert=/etc/letsencrypt/live/osadababa.cz/fullchain.pem'
tag 'osadababa-dev'
I am desperate to know why and solve this annoying problem, I tried to play with configuration, without success. Now two of the processes are at 100%, but the website is working, just draining resources.
Have you some experience like this? Please any suggestions.
EDIT:
RubyGems Environment:
- RUBYGEMS VERSION: 2.7.7
- RUBY VERSION: 2.5.1 (2018-03-29 patchlevel 57) [x86_64-linux]
- INSTALLATION DIRECTORY: /usr/local/rvm/gems/ruby-2.5.1
- USER INSTALLATION DIRECTORY: /root/.gem/ruby/2.5.0
- RUBY EXECUTABLE: /usr/local/rvm/rubies/ruby-2.5.1/bin/ruby
- EXECUTABLE DIRECTORY: /usr/local/rvm/gems/ruby-2.5.1/bin
- SPEC CACHE DIRECTORY: /root/.gem/specs
- SYSTEM CONFIGURATION DIRECTORY: /usr/local/rvm/rubies/ruby-2.5.1/etc
- RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
- GEM PATHS:
- /usr/local/rvm/gems/ruby-2.5.1
- /usr/local/rvm/gems/ruby-2.5.1@global
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
- https://rubygems.org/
- SHELL PATH:
- /opt/swift/build/swift-4.1.2-RELEASE-ubuntu14.04/usr/bin
- /usr/local/rvm/gems/ruby-2.5.1/bin
- /usr/local/rvm/gems/ruby-2.5.1@global/bin
- /usr/local/rvm/rubies/ruby-2.5.1/bin
- /usr/local/sbin
- /usr/local/bin
- /usr/sbin
- /usr/bin
- /sbin
- /bin
- /usr/local/rvm/bin
I am running ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
Using Puma from Debian package distribution. I will try the upgrade and I will try to create a simple project to test whether the problem will appear too.
ruby rack puma padrino
asked Nov 12 '18 at 8:19
MlokMlok
316
add a comment |
I have one problem which I am trying to solve, I have Ruby web project, written in Padrino, it is quite simply project. But I have problems with running the Puma.
Everything works fine, but after a few days, or if I make a stress test, the process of Puma is consuming 100% CPU and stays there forever. I need just to restart Puma (resp. kill it and start again).
It is happening on a few my projects, on Debian Stretch and Jessie.
Puma version is 3.11.4
and this is one of the config files:
preload_app!
rackup 'config.ru'
environment 'production'
daemonize
pidfile 'logs/osadababa.pid'
state_path 'logs/puma.state'
stdout_redirect 'logs/stdout', 'logs/stderr', true
threads 4,6
bind 'ssl://0.0.0.0:8060?key=/etc/letsencrypt/live/osadababa.cz/privkey.pem&cert=/etc/letsencrypt/live/osadababa.cz/fullchain.pem'
tag 'osadababa-dev'
I am desperate to know why and solve this annoying problem, I tried to play with configuration, without success. Now two of the processes are at 100%, but the website is working, just draining resources.
Have you some experience like this? Please any suggestions.
EDIT:
RubyGems Environment:
- RUBYGEMS VERSION: 2.7.7
- RUBY VERSION: 2.5.1 (2018-03-29 patchlevel 57) [x86_64-linux]
- INSTALLATION DIRECTORY: /usr/local/rvm/gems/ruby-2.5.1
- USER INSTALLATION DIRECTORY: /root/.gem/ruby/2.5.0
- RUBY EXECUTABLE: /usr/local/rvm/rubies/ruby-2.5.1/bin/ruby
- EXECUTABLE DIRECTORY: /usr/local/rvm/gems/ruby-2.5.1/bin
- SPEC CACHE DIRECTORY: /root/.gem/specs
- SYSTEM CONFIGURATION DIRECTORY: /usr/local/rvm/rubies/ruby-2.5.1/etc
- RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
- GEM PATHS:
- /usr/local/rvm/gems/ruby-2.5.1
- /usr/local/rvm/gems/ruby-2.5.1@global
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
- https://rubygems.org/
- SHELL PATH:
- /opt/swift/build/swift-4.1.2-RELEASE-ubuntu14.04/usr/bin
- /usr/local/rvm/gems/ruby-2.5.1/bin
- /usr/local/rvm/gems/ruby-2.5.1@global/bin
- /usr/local/rvm/rubies/ruby-2.5.1/bin
- /usr/local/sbin
- /usr/local/bin
- /usr/sbin
- /usr/bin
- /sbin
- /bin
- /usr/local/rvm/bin
I am running ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
Using Puma from Debian package distribution. I will try the upgrade and I will try to create a simple project to test whether the problem will appear too.
ruby rack puma padrino
asked Nov 12 '18 at 8:19
MlokMlok
316
what os, what versions of ruby? can you post output ofgem envand also maybe check github.com/puma/puma/issues/1608
– lacostenycoder
Nov 12 '18 at 8:40
make that simple project as small as you can while still producing the 100% load and publish it here
– peter
Nov 12 '18 at 8:44
lacostenycoder: Ah I did not notice new puma version (I started to handle this trouble a time ago now I returned to try to find a solution - release date is near). I hope it is fixed, it seems so, but I will tell after day or two, because the stress test which I performed now, is not 100% that will go into trouble. Thanks very much for the advice! I already upgraded a few times but before version 3.12.0.
– Mlok
Nov 12 '18 at 9:22
add a comment |
I have one problem which I am trying to solve, I have Ruby web project, written in Padrino, it is quite simply project. But I have problems with running the Puma.
Everything works fine, but after a few days, or if I make a stress test, the process of Puma is consuming 100% CPU and stays there forever. I need just to restart Puma (resp. kill it and start again).
It is happening on a few my projects, on Debian Stretch and Jessie.
Puma version is 3.11.4
and this is one of the config files:
preload_app!
rackup 'config.ru'
environment 'production'
daemonize
pidfile 'logs/osadababa.pid'
state_path 'logs/puma.state'
stdout_redirect 'logs/stdout', 'logs/stderr', true
threads 4,6
bind 'ssl://0.0.0.0:8060?key=/etc/letsencrypt/live/osadababa.cz/privkey.pem&cert=/etc/letsencrypt/live/osadababa.cz/fullchain.pem'
tag 'osadababa-dev'
I am desperate to know why and solve this annoying problem, I tried to play with configuration, without success. Now two of the processes are at 100%, but the website is working, just draining resources.
Have you some experience like this? Please any suggestions.
EDIT:
RubyGems Environment:
- RUBYGEMS VERSION: 2.7.7
- RUBY VERSION: 2.5.1 (2018-03-29 patchlevel 57) [x86_64-linux]
- INSTALLATION DIRECTORY: /usr/local/rvm/gems/ruby-2.5.1
- USER INSTALLATION DIRECTORY: /root/.gem/ruby/2.5.0
- RUBY EXECUTABLE: /usr/local/rvm/rubies/ruby-2.5.1/bin/ruby
- EXECUTABLE DIRECTORY: /usr/local/rvm/gems/ruby-2.5.1/bin
- SPEC CACHE DIRECTORY: /root/.gem/specs
- SYSTEM CONFIGURATION DIRECTORY: /usr/local/rvm/rubies/ruby-2.5.1/etc
- RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
- GEM PATHS:
- /usr/local/rvm/gems/ruby-2.5.1
- /usr/local/rvm/gems/ruby-2.5.1@global
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
- https://rubygems.org/
- SHELL PATH:
- /opt/swift/build/swift-4.1.2-RELEASE-ubuntu14.04/usr/bin
- /usr/local/rvm/gems/ruby-2.5.1/bin
- /usr/local/rvm/gems/ruby-2.5.1@global/bin
- /usr/local/rvm/rubies/ruby-2.5.1/bin
- /usr/local/sbin
- /usr/local/bin
- /usr/sbin
- /usr/bin
- /sbin
- /bin
- /usr/local/rvm/bin
I am running ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
Using Puma from Debian package distribution. I will try the upgrade and I will try to create a simple project to test whether the problem will appear too.
ruby rack puma padrino
asked Nov 12 '18 at 8:19
MlokMlok
316
I have one problem which I am trying to solve, I have Ruby web project, written in Padrino, it is quite simply project. But I have problems with running the Puma.
Everything works fine, but after a few days, or if I make a stress test, the process of Puma is consuming 100% CPU and stays there forever. I need just to restart Puma (resp. kill it and start again).
It is happening on a few my projects, on Debian Stretch and Jessie.
Puma version is 3.11.4
and this is one of the config files:
preload_app!
rackup 'config.ru'
environment 'production'
daemonize
pidfile 'logs/osadababa.pid'
state_path 'logs/puma.state'
stdout_redirect 'logs/stdout', 'logs/stderr', true
threads 4,6
bind 'ssl://0.0.0.0:8060?key=/etc/letsencrypt/live/osadababa.cz/privkey.pem&cert=/etc/letsencrypt/live/osadababa.cz/fullchain.pem'
tag 'osadababa-dev'
I am desperate to know why and solve this annoying problem, I tried to play with configuration, without success. Now two of the processes are at 100%, but the website is working, just draining resources.
Have you some experience like this? Please any suggestions.
EDIT:
RubyGems Environment:
- RUBYGEMS VERSION: 2.7.7
- RUBY VERSION: 2.5.1 (2018-03-29 patchlevel 57) [x86_64-linux]
- INSTALLATION DIRECTORY: /usr/local/rvm/gems/ruby-2.5.1
- USER INSTALLATION DIRECTORY: /root/.gem/ruby/2.5.0
- RUBY EXECUTABLE: /usr/local/rvm/rubies/ruby-2.5.1/bin/ruby
- EXECUTABLE DIRECTORY: /usr/local/rvm/gems/ruby-2.5.1/bin
- SPEC CACHE DIRECTORY: /root/.gem/specs
- SYSTEM CONFIGURATION DIRECTORY: /usr/local/rvm/rubies/ruby-2.5.1/etc
- RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
- GEM PATHS:
- /usr/local/rvm/gems/ruby-2.5.1
- /usr/local/rvm/gems/ruby-2.5.1@global
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
- https://rubygems.org/
- SHELL PATH:
- /opt/swift/build/swift-4.1.2-RELEASE-ubuntu14.04/usr/bin
- /usr/local/rvm/gems/ruby-2.5.1/bin
- /usr/local/rvm/gems/ruby-2.5.1@global/bin
- /usr/local/rvm/rubies/ruby-2.5.1/bin
- /usr/local/sbin
- /usr/local/bin
- /usr/sbin
- /usr/bin
- /sbin
- /bin
- /usr/local/rvm/bin
I am running ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
Using Puma from Debian package distribution. I will try the upgrade and I will try to create a simple project to test whether the problem will appear too.
ruby rack puma padrino
ruby rack puma padrino
asked Nov 12 '18 at 8:19
MlokMlok
316
asked Nov 12 '18 at 8:19
MlokMlok
316
edited Nov 12 '18 at 9:12
Mlok
asked Nov 12 '18 at 8:19
MlokMlok
316
asked Nov 12 '18 at 8:19
MlokMlok
316
asked Nov 12 '18 at 8:19
MlokMlok
316
316
what os, what versions of ruby? can you post output ofgem envand also maybe check github.com/puma/puma/issues/1608
– lacostenycoder
Nov 12 '18 at 8:40
make that simple project as small as you can while still producing the 100% load and publish it here
– peter
Nov 12 '18 at 8:44
lacostenycoder: Ah I did not notice new puma version (I started to handle this trouble a time ago now I returned to try to find a solution - release date is near). I hope it is fixed, it seems so, but I will tell after day or two, because the stress test which I performed now, is not 100% that will go into trouble. Thanks very much for the advice! I already upgraded a few times but before version 3.12.0.
– Mlok
Nov 12 '18 at 9:22
add a comment |
what os, what versions of ruby? can you post output ofgem envand also maybe check github.com/puma/puma/issues/1608
– lacostenycoder
Nov 12 '18 at 8:40
make that simple project as small as you can while still producing the 100% load and publish it here
– peter
Nov 12 '18 at 8:44
lacostenycoder: Ah I did not notice new puma version (I started to handle this trouble a time ago now I returned to try to find a solution - release date is near). I hope it is fixed, it seems so, but I will tell after day or two, because the stress test which I performed now, is not 100% that will go into trouble. Thanks very much for the advice! I already upgraded a few times but before version 3.12.0.
– Mlok
Nov 12 '18 at 9:22
what os, what versions of ruby? can you post output of
gem env and also maybe check github.com/puma/puma/issues/1608– lacostenycoder
Nov 12 '18 at 8:40
what os, what versions of ruby? can you post output of
gem env and also maybe check github.com/puma/puma/issues/1608– lacostenycoder
Nov 12 '18 at 8:40
make that simple project as small as you can while still producing the 100% load and publish it here
– peter
Nov 12 '18 at 8:44
make that simple project as small as you can while still producing the 100% load and publish it here
– peter
Nov 12 '18 at 8:44
lacostenycoder: Ah I did not notice new puma version (I started to handle this trouble a time ago now I returned to try to find a solution - release date is near). I hope it is fixed, it seems so, but I will tell after day or two, because the stress test which I performed now, is not 100% that will go into trouble. Thanks very much for the advice! I already upgraded a few times but before version 3.12.0.
– Mlok
Nov 12 '18 at 9:22
lacostenycoder: Ah I did not notice new puma version (I started to handle this trouble a time ago now I returned to try to find a solution - release date is near). I hope it is fixed, it seems so, but I will tell after day or two, because the stress test which I performed now, is not 100% that will go into trouble. Thanks very much for the advice! I already upgraded a few times but before version 3.12.0.
– Mlok
Nov 12 '18 at 9:22
add a comment |
1 Answer
1
active
oldest
votes
Solved! New version of puma fixed this issue. Thanks all
answered Nov 16 '18 at 11:19
MlokMlok
316
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53258187%2fpuma-with-padrino-cpu-consumption-will-not-stop%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solved! New version of puma fixed this issue. Thanks all
answered Nov 16 '18 at 11:19
MlokMlok
316
add a comment |
Solved! New version of puma fixed this issue. Thanks all
answered Nov 16 '18 at 11:19
MlokMlok
316
add a comment |
Solved! New version of puma fixed this issue. Thanks all
answered Nov 16 '18 at 11:19
MlokMlok
316
Solved! New version of puma fixed this issue. Thanks all
answered Nov 16 '18 at 11:19
MlokMlok
316
answered Nov 16 '18 at 11:19
MlokMlok
316
answered Nov 16 '18 at 11:19
MlokMlok
316
answered Nov 16 '18 at 11:19
MlokMlok
316
316
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53258187%2fpuma-with-padrino-cpu-consumption-will-not-stop%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
what os, what versions of ruby? can you post output of
gem envand also maybe check github.com/puma/puma/issues/1608– lacostenycoder
Nov 12 '18 at 8:40
make that simple project as small as you can while still producing the 100% load and publish it here
– peter
Nov 12 '18 at 8:44
lacostenycoder: Ah I did not notice new puma version (I started to handle this trouble a time ago now I returned to try to find a solution - release date is near). I hope it is fixed, it seems so, but I will tell after day or two, because the stress test which I performed now, is not 100% that will go into trouble. Thanks very much for the advice! I already upgraded a few times but before version 3.12.0.
– Mlok
Nov 12 '18 at 9:22