https://htyp.org/mw/index.php?action=history&feed=atom&title=User%3AWoozle%2FMastodon%2Fsetup%2Ftake_3%2Fpaste-8
User:Woozle/Mastodon/setup/take 3/paste-8 - Revision history
2026-07-01T15:12:51Z
Revision history for this page on the wiki
MediaWiki 1.45.3
https://htyp.org/mw/index.php?title=User:Woozle/Mastodon/setup/take_3/paste-8&diff=23598&oldid=prev
Woozle: Created page with ": <code>icmstdn@cloud4:~/apps/mastodon$ '''~/.rbenv/shims/bundle exec puma -C config/puma.rb'''</code> <pre> [2870] Puma starting in cluster mode... [2870] * Version 3.11.0 (r..."
2018-01-09T18:45:00Z
<p>Created page with ": <code>icmstdn@cloud4:~/apps/mastodon$ '''~/.rbenv/shims/bundle exec puma -C config/puma.rb'''</code> <pre> [2870] Puma starting in cluster mode... [2870] * Version 3.11.0 (r..."</p>
<p><b>New page</b></p><div>: <code>icmstdn@cloud4:~/apps/mastodon$ '''~/.rbenv/shims/bundle exec puma -C config/puma.rb'''</code><br />
<pre><br />
[2870] Puma starting in cluster mode...<br />
[2870] * Version 3.11.0 (ruby 2.4.2-p198), codename: Love Song<br />
[2870] * Min threads: 5, max threads: 5<br />
[2870] * Environment: production<br />
[2870] * Process workers: 2<br />
[2870] * Preloading application<br />
Creating scope :cache_ids. Overwriting existing method Notification.cache_ids.<br />
[2870] * Listening on tcp://0.0.0.0:3000<br />
bundler: failed to load command: puma (/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/bin/puma)<br />
Errno::EADDRINUSE: Address already in use - bind(2) for "0.0.0.0" port 3000<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/binder.rb:270:in `initialize'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/binder.rb:270:in `new'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/binder.rb:270:in `add_tcp_listener'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/binder.rb:105:in `block in parse'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/binder.rb:88:in `each'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/binder.rb:88:in `parse'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/runner.rb:144:in `load_and_bind'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/cluster.rb:397:in `run'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/launcher.rb:183:in `run'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/lib/puma/cli.rb:77:in `run'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/gems/puma-3.11.0/bin/puma:10:in `<top (required)>'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/bin/puma:23:in `load'<br />
/home/icmstdn/apps/mastodon/vendor/bundle/ruby/2.4.0/bin/puma:23:in `<top (required)>'<br />
</pre><br />
So now it's actually complaining about 0.0.0.0. Let's try the tcp://localhost thing:<br />
: <code>icmstdn@cloud4:~/apps/mastodon$ '''~/.rbenv/shims/bundle exec puma -C config/puma.rb -b tcp://localhost'''</code><br />
<pre><br />
[3272] Puma starting in cluster mode...<br />
[3272] * Version 3.11.0 (ruby 2.4.2-p198), codename: Love Song<br />
[3272] * Min threads: 5, max threads: 5<br />
[3272] * Environment: production<br />
[3272] * Process workers: 2<br />
[3272] * Preloading application<br />
Creating scope :cache_ids. Overwriting existing method Notification.cache_ids.<br />
[3272] * Listening on tcp://localhost<br />
[3272] Use Ctrl-C to stop<br />
[3272] - Worker 0 (pid: 3295) booted, phase: 0<br />
[3272] - Worker 1 (pid: 3301) booted, phase: 0<br />
^C[3272] - Gracefully shutting down workers...<br />
[3272] === puma shutdown: 2018-01-09 18:39:49 +0000 ===<br />
[3272] - Goodbye!<br />
icmstdn@cloud4:~/apps/mastodon$ <br />
</pre><br />
That kinda looked like a happy process... and while that was running, I was getting a blank web page instead of errors.<br />
<br />
So, I'm kinda thinking I should add that localhost option to the config file and try a proper systemctl restart.</div>
Woozle