User:Woozle/Mastodon/setup/take 3/paste-7
< User:Woozle | Mastodon | setup | take 3
Jump to navigation
Jump to search
icmstdn@cloud4:~/apps/mastodon$ export RAILS_ENV=production
icmstdn@cloud4:~/apps/mastodon$ ~/.rbenv/shims/bundle exec puma -C config/puma.rb
[5421] Puma starting in cluster mode... [5421] * Version 3.11.0 (ruby 2.4.2-p198), codename: Love Song [5421] * Min threads: 5, max threads: 5 [5421] * Environment: production [5421] * Process workers: 2 [5421] * Preloading application Creating scope :cache_ids. Overwriting existing method Notification.cache_ids. [5421] * Listening on tcp://0.0.0.0:3000 [5421] Use Ctrl-C to stop bundler: failed to load command: puma (/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/bin/puma) Errno::ENOMEM: Cannot allocate memory - fork(2) /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/cluster.rb:126:in `fork' /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/cluster.rb:126:in `block in spawn_workers' /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/cluster.rb:122:in `times' /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/cluster.rb:122:in `spawn_workers' /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/cluster.rb:453:in `run' /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/launcher.rb:183:in `run' /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/cli.rb:77:in `run' /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/bin/puma:10:in `<top (required)>' /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/bin/puma:23:in `load' /home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/bin/puma:23:in `<top (required)>'
Now... is this really a memory error?
Note that this does seem to correctly change the listening port (see this for why this might be a good idea):
icmstdn@cloud4:~/apps/mastodon$ ~/.rbenv/shims/bundle exec puma -C config/puma.rb -b tcp://localhost
...but I get that same ENOMEM error.