Ruby thin stops working after Redmine upgrade from 3.3.0 to 4.0.6

Hi All

Our Redmine 3.3.0 was working fine until we upgraded to 4.0.6. We got "502 Bad Gateway nginx/1.10.3 (Ubuntu)" when going to the website after the upgrade, and found that the problem was caused by Thin.
systemctl status thin shows "Active: active (exited) since XXX".
Initially it was Active: running but after a few seconds, it because active (exited) when we re-ran systemctl status.
We also saw that thin.XX.pid files disappeared very fast one by one from the /run/thin/ folder.

Does anybody have any idea what's in Redmine 4.0.6 that can cause this problem with thin?

Thank you very much in anticipation

cmgui

Replies (3)

RE: Ruby thin stops working after Redmine upgrade from 3.3.0 to 4.0.6 - Added by Ivan Cenov almost 5 years ago

We used thin for a long time for many Redmine versions. However from some version (I don't remember which one) thin stopped to run Redmine. I did not investigate the case too much and switched to puma. It seems that Ruby on Rails developers have chosen puma as a standard server (when creating new RoR project puma is the default server). So, try puma and if it runs, tie to it.

RE: Ruby thin stops working after Redmine upgrade from 3.3.0 to 4.0.6 - Added by CM Gui almost 5 years ago

Thank you Ivan! Got Puma to work with Redmine.
I thought Phusion Passenger is the standard server for RoR? We tried Passenger on Redmine before and somehow it was slow. Puma appears to be faster.

For anyone interested, here are the two links we followed to get Puma working with Redmine:
[[https://blog.rudeotter.com/install-redmine-with-nginx-puma-and-mariadbmysql-on-ubuntu-14-04/]]
[[https://www.digitalocean.com/community/tutorials/how-to-deploy-a-rails-app-with-puma-and-nginx-on-ubuntu-14-04]]

Our system:
Ubuntu 16.04.6 LTS xenial
nginx version: nginx/1.10.3 (Ubuntu)
MySQL Server version: 5.7.28-0ubuntu0.16.04.2 (Ubuntu)
puma (3.12.2) (gem)

Redmine version                4.0.6.stable
  Ruby version                   2.3.1-p112 (2016-04-26) [x86_64-linux-gnu]
  Rails version                  5.2.4.1
  Environment                    production
  Database adapter               Mysql2
  Mailer queue                   ActiveJob::QueueAdapters::AsyncAdapter
  Mailer delivery                smtp

RE: Ruby thin stops working after Redmine upgrade from 3.3.0 to 4.0.6 - Added by Ivan Cenov almost 5 years ago

Hello, see here

Passenger and "rails server"

"rails server" uses Puma by default as of Rails 5.

If you add Passenger to your Gemfile, then "rails server" will launch Passenger instead of Puma. You can also choose to launch Passenger directly.

We run Redmine on Windows machine, so Passenger is not an option for us.

(1-3/3)

Project

General

Profile

Redmine