The user Jared_Needell reports an issue with the Rails console in Discourse after an update, where rails c results in an interrupt error. notriddle advises using proper code formatting and notes that the command works for them, with a delay before the prompt appears. dnsmichi explains that delays are normal due to server load and that the error is likely caused by a Ctrl+C interruption. neounix confirms the console works but takes around 10 seconds to load.
I recently updated Discourse after being out of date for 6-7 months. I noticed ./launcher ssh app doesn’t work anymore and if I use enter app then rails c, I get an error.
root@rdu-forums-01-app:/var/www/discourse/plugins/categorywatcher# rails c
^C/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:292:in `require': Interrupt
from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:292:in `block in require'
from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:258:in `load_dependency'
from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:292:in `require'
Opening the rails console can take a while, depending on the work load of your application and server. This isn’t really app specific, you can see that with Gitlab too.
The exception you are seeing originates from Crtl+C (^C before the stacktrace), interpreted as interrupt signal by the current running process.